Proxmox 4.2 error "Looping too fast. Throttling execution a little."

[mbaldini]

Hello.

I'd like to start with my congratulations on the very well done job of creating and updating Proxmox, one of the best Linux software I use.

I'm writing because I'm having a strange problem on a new Proxmox server installed 2 weeks ago.
It's a single server, no cluster, pveversion is

proxmox-ve: 4.2-51 (running kernel: 4.4.8-1-pve)
pve-manager: 4.2-5 (running version: 4.2-5/7cf09667)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.8-1-pve: 4.4.8-51
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-75
pve-firmware: 1.1-8
libpve-common-perl: 4.0-62
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-17
pve-container: 1.0-64
pve-firewall: 2.0-27
pve-ha-manager: 1.0-31
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie

Filesystem is ZFS, output of zpool status is

  pool: rpool
state: ONLINE
  scan: scrub repaired 0 in 55h38m with 0 errors on Mon May 23 08:39:00 2016
config:

        NAME                                    STATE     READ WRITE CKSUM
        rpool                                   ONLINE       0     0     0
          raidz2-0                              ONLINE       0     0     0
            sdb2                                ONLINE       0     0     0
            sdc2                                ONLINE       0     0     0
            sdd2                                ONLINE       0     0     0
            sde2                                ONLINE       0     0     0
        logs
          sda2                                  ONLINE       0     0     0
        cache
          29c54f9a-68d2-488d-8263-9a8fb9631a88  ONLINE       0     0     0

errors: No known data errors

CPU is

vendor_id       : GenuineIntel
cpu family      : 6
model           : 60
model name      : Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz
stepping        : 3
microcode       : 0x1c
cpu MHz         : 3302.750

RAM is (output of free-h)

             total       used       free     shared    buffers     cached
Mem:           15G        12G       3.1G        46M       1.7G       220M
-/+ buffers/cache:        10G       5.0G
Swap:         8.0G         0B       8.0G

On this server there are 3 VMs, one with Windows 2012 server std, one with Debian 8 and one with Mikrotik routeros

      VMID NAME                 STATUS     MEM(MB)    BOOTDISK(GB) PID
       100 Windows-2012         running    8196              64.00 2796
       101 Debian8              running    1024              32.00 6350
       110 mikrotik-dude        running    512                4.12 2887

This morning I had a lot of problems, the 3 VMs were unreacheable (not responding to ping), proxmox was responding ot ping but not ssh nor web interface were connecting, I logged on physical console and I got a lot of lines in syslog

May 23 08:36:57 pve-castiglione systemd[1]: Looping too fast. Throttling execution a little.
May 23 08:36:58 pve-castiglione systemd[1]: Looping too fast. Throttling execution a little.
May 23 08:36:59 pve-castiglione systemd[1]: Looping too fast. Throttling execution a little.
May 23 08:37:00 pve-castiglione systemd[1]: Looping too fast. Throttling execution a little.
May 23 08:37:01 pve-castiglione systemd[1]: Looping too fast. Throttling execution a little.
May 23 08:37:02 pve-castiglione systemd[1]: Looping too fast. Throttling execution a little.
May 23 08:37:03 pve-castiglione pvestatd[2681]: can't lock file '/var/log/pve/tasks/.active.lock' - Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/Tools.pm line 137.
May 23 08:37:03 pve-castiglione systemd[1]: Looping too fast. Throttling execution a little.
May 23 08:37:03 pve-castiglione pve-firewall[2679]: 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 137.

I restarted the host and now it's working without problems, but I don't think these errors are good. Now I disabled the PVE firewall from the interface (Options - Enable Firewall: No) but it's the first time I see these strange errors on Proxmox (I have other proxmox servers).

What should I do? The server should be good or it's possibile that the error will happen again in future?

Thsnk

 

[mbaldini]

Today same errors.
After a
service pve-firewall restart
errors are gone, but I think there will be errors again. And I disabled the Firewall from Proxmox GUI.
I don't understand what is going on, it's the only Proxmox installation that is giving these problems.