Hey. I got the following error in my system log, maybe there is anyone who has an idea on how to get rid of it?
Nov 28 11:30:41 proxmox-test pveproxy[15918]: panic: sv_setpvn_fresh called with negative strlen -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/AnyEvent/Handle.pm line 2083.
Nov 28 11:30:45 proxmox-test pveproxy[15917]: panic: sv_setpvn_fresh called with negative strlen -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/AnyEvent/Handle.pm line 2083.
Nov 28 11:30:46 proxmox-test pveproxy[15918]: worker exit
Nov 28 11:30:46 proxmox-test pveproxy[1143]: worker 15918 finished
Nov 28 11:30:46 proxmox-test pveproxy[1143]: starting 1 worker(s)
Nov 28 11:30:46 proxmox-test pveproxy[1143]: worker 16024 started
Nov 28 11:30:50 proxmox-test pveproxy[15917]: worker exit
Nov 28 11:30:50 proxmox-test pveproxy[1143]: worker 15917 finished
Nov 28 11:30:50 proxmox-test pveproxy[1143]: starting 1 worker(s)
Nov 28 11:30:50 proxmox-test pveproxy[1143]: worker 16028 started
Nov 28 11:31:29 proxmox-test pveproxy[16024]: panic: sv_setpvn_fresh called with negative strlen -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/AnyEvent/Handle.pm line 2083.
Nov 28 11:31:34 proxmox-test pveproxy[16024]: worker exit
Nov 28 11:31:34 proxmox-test pveproxy[1143]: worker 16024 finished
Nov 28 11:31:34 proxmox-test pveproxy[1143]: starting 1 worker(s)
Nov 28 11:31:34 proxmox-test pveproxy[1143]: worker 16140 started
Nov 28 11:31:41 proxmox-test pveproxy[16028]: panic: sv_setpvn_fresh called with negative strlen -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/AnyEvent/Handle.pm line 2083.
Nov 28 11:31:45 proxmox-test pveproxy[15976]: panic: sv_setpvn_fresh called with negative strlen -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/AnyEvent/Handle.pm line 2083.
Nov 28 11:31:46 proxmox-test pveproxy[16028]: worker exit
Nov 28 11:31:46 proxmox-test pveproxy[1143]: worker 16028 finished
in file Handle.pm =
LINE 2083---> while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
unless (length $tmp) {
$self->{_on_starttls}
and (delete $self->{_on_starttls})->($self, undef, "EOF during handshake"); # ???
&_freetls;
if ($self->{on_stoptls}) {
$self->{on_stoptls}($self);
return;
} else {
# let's treat SSL-eof as we treat normal EOF
delete $self->{_rw};
$self->{_eof} = 1;
}
I have -> reinstalled proxmox several times, on several harddrives of the same PC.
This pc is used for internal testing and therefore we wanted to build an isolated enviornment. Actually I do not think that we will have any problem in doing this but it annoying to not know what is going on, yes, I am newbie in these stuff so please be patient.
Please just let me know if you need any other information.
Not only that this error is disturbing but it seems that I cannot stay connected on console(shell) too much because it will close with an error "Connection closed, error 1006".
While I can open shells in other programs, it is still annoying not knowing what is going on. maybe has anyone any idea?
Thank you in advance, much appreciated.
Edit: Console on windows freeze as well, not only linux/debian fedora etc. It comes back in few seconds but this glitch is annoying and should not exist.
I have not even installed any VMs, shell from proxmox freeze anyway,
root@proxmox-test ~ # pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-4-pve)
pve-manager: 8.3.0 (running version: 8.3.0/c1689ccb1065a83b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.0
libpve-storage-perl: 8.2.9
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.9-1
proxmox-backup-file-restore: 3.2.9-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.1
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-1
pve-ha-manager: 4.0.6
pve-i18n: 3.3.1
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.0
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
Nov 28 11:30:41 proxmox-test pveproxy[15918]: panic: sv_setpvn_fresh called with negative strlen -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/AnyEvent/Handle.pm line 2083.
Nov 28 11:30:45 proxmox-test pveproxy[15917]: panic: sv_setpvn_fresh called with negative strlen -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/AnyEvent/Handle.pm line 2083.
Nov 28 11:30:46 proxmox-test pveproxy[15918]: worker exit
Nov 28 11:30:46 proxmox-test pveproxy[1143]: worker 15918 finished
Nov 28 11:30:46 proxmox-test pveproxy[1143]: starting 1 worker(s)
Nov 28 11:30:46 proxmox-test pveproxy[1143]: worker 16024 started
Nov 28 11:30:50 proxmox-test pveproxy[15917]: worker exit
Nov 28 11:30:50 proxmox-test pveproxy[1143]: worker 15917 finished
Nov 28 11:30:50 proxmox-test pveproxy[1143]: starting 1 worker(s)
Nov 28 11:30:50 proxmox-test pveproxy[1143]: worker 16028 started
Nov 28 11:31:29 proxmox-test pveproxy[16024]: panic: sv_setpvn_fresh called with negative strlen -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/AnyEvent/Handle.pm line 2083.
Nov 28 11:31:34 proxmox-test pveproxy[16024]: worker exit
Nov 28 11:31:34 proxmox-test pveproxy[1143]: worker 16024 finished
Nov 28 11:31:34 proxmox-test pveproxy[1143]: starting 1 worker(s)
Nov 28 11:31:34 proxmox-test pveproxy[1143]: worker 16140 started
Nov 28 11:31:41 proxmox-test pveproxy[16028]: panic: sv_setpvn_fresh called with negative strlen -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/AnyEvent/Handle.pm line 2083.
Nov 28 11:31:45 proxmox-test pveproxy[15976]: panic: sv_setpvn_fresh called with negative strlen -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/AnyEvent/Handle.pm line 2083.
Nov 28 11:31:46 proxmox-test pveproxy[16028]: worker exit
Nov 28 11:31:46 proxmox-test pveproxy[1143]: worker 16028 finished
in file Handle.pm =
LINE 2083---> while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
unless (length $tmp) {
$self->{_on_starttls}
and (delete $self->{_on_starttls})->($self, undef, "EOF during handshake"); # ???
&_freetls;
if ($self->{on_stoptls}) {
$self->{on_stoptls}($self);
return;
} else {
# let's treat SSL-eof as we treat normal EOF
delete $self->{_rw};
$self->{_eof} = 1;
}
I have -> reinstalled proxmox several times, on several harddrives of the same PC.
This pc is used for internal testing and therefore we wanted to build an isolated enviornment. Actually I do not think that we will have any problem in doing this but it annoying to not know what is going on, yes, I am newbie in these stuff so please be patient.
Please just let me know if you need any other information.
Not only that this error is disturbing but it seems that I cannot stay connected on console(shell) too much because it will close with an error "Connection closed, error 1006".
While I can open shells in other programs, it is still annoying not knowing what is going on. maybe has anyone any idea?
Thank you in advance, much appreciated.
Edit: Console on windows freeze as well, not only linux/debian fedora etc. It comes back in few seconds but this glitch is annoying and should not exist.
I have not even installed any VMs, shell from proxmox freeze anyway,
root@proxmox-test ~ # pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-4-pve)
pve-manager: 8.3.0 (running version: 8.3.0/c1689ccb1065a83b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.0
libpve-storage-perl: 8.2.9
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.9-1
proxmox-backup-file-restore: 3.2.9-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.1
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-1
pve-ha-manager: 4.0.6
pve-i18n: 3.3.1
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.0
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
Attachments
Last edited: