lxc-monitord.log >2GB spam

Marcel40625

Active Member
Dec 7, 2016
6
0
41
34
Hello,
im getting from time to time many errors in my "lxc-monitord.log"
for the first i solved this with creating a cronjob to clear the logfile every 5 min ...
dont know whats running wrong but it kills my log partion and after the partion is full the backups dont work anymore ...

i will update the system in the next days ... if this is already fixed, ignore me :)

here a snippet of the log:

Code:
   lxc-monitord 20161106230011.490 NOTICE   lxc_monitord - lxc_monitord.c:main:416 - pid:970 monitoring lxcpath /var/lib/lxc
   lxc-monitord 20161106230046.810 NOTICE   lxc_monitord - lxc_monitord.c:main:421 - no remaining clients, exiting
   lxc-monitord 20161106230046.811 NOTICE   lxc_monitord - lxc_monitord.c:main:429 - monitor exiting
   lxc-monitord 20161107110025.330 NOTICE   lxc_monitord - lxc_monitord.c:main:416 - pid:18412 monitoring lxcpath /var/lib/lxc
   lxc-monitord 20161107110027.111 ERROR    lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:307 - write failed to client sock:5 32 Broken pipe
   lxc-monitord 20161107110027.111 ERROR    lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Connection reset by peer - read fifo failed : Connection reset by peer
   lxc-monitord 20161107110027.111 ERROR    lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Connection reset by peer - read fifo failed : Connection reset by peer
   lxc-monitord 20161107110027.111 ERROR    lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Connection reset by peer - read fifo failed : Connection reset by peer
   lxc-monitord 20161107110027.111 ERROR    lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Connection reset by peer - read fifo failed : Connection reset by peer
  ...
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  lxc-monitord 20161107110028.824 ERROR  lxc_monitord - lxc_monitord.c:lxc_monitord_fifo_handler:298 - Broken pipe - read fifo failed : Broken pipe
  ...
  till the end of the file

proxmox-ve: 4.3-66 (running kernel: 4.4.19-1-pve)
pve-manager: 4.3-3 (running version: 4.3-3/557191d3)
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-91
pve-firmware: 1.1-9
libpve-common-perl: 4.0-75
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-66
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6.2-2
pve-container: 1.0-78
pve-firewall: 2.0-31
pve-ha-manager: 1.0-35
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.5-1
lxcfs: 2.0.4-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!