pve-firewall: perl-error in syslog every few seconds

G

grl

Renowned Member
Oct 20, 2011
24
1
68
Hi!

Just updated my play-around-proxmox machine from proxmox 2 to 4.1.
Went through pretty smooth - I don't have any fancy things on that box, as its just to play around.

But now I get an error-line every few seconds in syslog:
Code: 
pve-firewall[1242]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 136.

Any idea where to search for that? As it happens every few seconds my syslog is pretty crowded at the moment...
Code: 
# pveversion --verbose
proxmox-ve: 4.1-37 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-13 (running version: 4.1-13/cfb599fb)
pve-kernel-4.2.8-1-pve: 4.2.8-37
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-32
qemu-server: 4.0-55
pve-firmware: 1.1-7
libpve-common-perl: 4.0-48
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-40
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-5
pve-container: 1.0-44
pve-firewall: 2.0-17
pve-ha-manager: 1.0-21
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1
fence-agents-pve: not correctly installed



regards
Lukas
 
  • Like
Reactions: chrone
pve-firewall localnet
Code: 
local hostname: pve
local IP address: 10.0.0.5
network auto detect: 10.0.0.0/24
using detected local_network: 10.0.0.0/24

pveversion --verbose
Code: 
proxmox-ve: 4.3-66 (running kernel: 4.2.6-1-pve)
pve-manager: 4.3-1 (running version: 4.3-1/e7cdc165)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.16-1-pve: 4.4.16-64
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-46
qemu-server: 4.0-88
pve-firmware: 1.1-9
libpve-common-perl: 4.0-73
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-61
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6.1-6
pve-container: 1.0-75
pve-firewall: 2.0-29
pve-ha-manager: 1.0-35
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.4-1
lxcfs: 2.0.3-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
zfsutils: 0.6.5.7-pve10~bpo80
 
I have a same problem.
It starts to spam such messages after about two weeks uptime.
After reboot the problem is gone for next two weeks.
So there's no solution ?
 
I catched it when it started to spam.

Jan 26 22:08:45 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - got timeout
Jan 26 22:08:45 pve pve-firewall[3400]: firewall update time (45.781 seconds)
Jan 26 22:08:45 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:08:46 pve pvestatd[3399]: status update time (56.472 seconds)
Jan 26 22:08:47 pve kernel: audit: type=1400 audit(1485457727.727:21): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=22730 comm="(tor)" flags="rw, rslave"
Jan 26 22:08:51 pve pve-ha-lrm[3433]: loop take too long (36 seconds)
Jan 26 22:08:51 pve pve-ha-crm[3421]: loop take too long (34 seconds)
Jan 26 22:09:57 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:10:32 pve pve-firewall[3400]: firewall update time (63.057 seconds)
Jan 26 22:10:54 pve pve-ha-crm[3421]: loop take too long (59 seconds)
Jan 26 22:11:03 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:03 pve pve-firewall[3400]: firewall update time (6.413 seconds)
Jan 26 22:11:03 pve pveproxy[4953]: proxy detected vanished client connection
Jan 26 22:11:03 pve pveproxy[4953]: proxy detected vanished client connection
Jan 26 22:11:03 pve pveproxy[4953]: proxy detected vanished client connection
Jan 26 22:11:04 pve pveproxy[4954]: proxy detected vanished client connection
Jan 26 22:11:04 pve pvestatd[3399]: status update time (126.587 seconds)
Jan 26 22:11:04 pve kernel: audit: type=1400 audit(1485457864.456:22): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=22781 comm="(tor)" flags="rw, rslave"
Jan 26 22:11:05 pve kernel: audit: type=1400 audit(1485457865.384:23): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=22824 comm="(tor)" flags="rw, rslave"
Jan 26 22:11:06 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:08 pve pve-ha-lrm[3433]: loop take too long (137 seconds)
Jan 26 22:11:16 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:26 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:36 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:46 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:56 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:12:06 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:12:16 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Click to expand...

# pveversion --verbose
proxmox-ve: 4.4-78 (running kernel: 4.4.35-2-pve)
pve-manager: 4.4-5 (running version: 4.4-5/c43015a5)
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.35-2-pve: 4.4.35-78
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-102
pve-firmware: 1.1-10
libpve-common-perl: 4.0-85
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-71
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.1-1
pve-container: 1.0-90
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.6-5
lxcfs: 2.0.5-pve2
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80
Click to expand...
 
So will be there a fix to stop this hell ?

Jan 17 19:52:11 pve pve-firewall[3400]: starting server
Jan 17 19:52:11 pve systemd[1]: Started Proxmox VE firewall.
Jan 26 22:08:45 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - got timeout
Jan 26 22:08:45 pve pve-firewall[3400]: firewall update time (45.781 seconds)
Jan 26 22:08:45 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:09:57 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:10:32 pve pve-firewall[3400]: firewall update time (63.057 seconds)
Jan 26 22:11:03 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:03 pve pve-firewall[3400]: firewall update time (6.413 seconds)
Jan 26 22:11:06 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:16 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:26 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:36 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:46 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:11:56 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:12:06 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:12:16 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:12:26 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:12:36 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:12:46 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:12:56 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:13:06 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:13:16 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:13:26 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:13:36 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:13:46 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:13:56 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:14:06 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:14:16 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:14:26 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:14:36 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:14:46 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:14:56 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:15:06 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:15:16 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:15:26 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Jan 26 22:15:36 pve pve-firewall[3400]: status update error: can't lock file '/var/lock/pvefw.lck' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 143.
Click to expand...
 
Last edited:
that seems to be a bug. if you restart the pve-firewall service, the log messages should go away (a more permanent fix should be available soon)
 
  • Like
Reactions: chrone
You must log in or register to reply here.
Top Bottom