rrd.journal as last log

[Alexander Fox]

Hi

I Have the Problem some Days Server crasht and is not Availaible and I must reboot complete. Than this I have in the syslog as last log

Jun 13 16:14:11 server rrdcached[1455]: flushing old values
Jun 13 16:14:11 server rrdcached[1455]: rotating journals
Jun 13 16:14:11 server rrdcached[1455]: started new journal /var/lib/rrdcached/journal//rrd.journal.1371132851.672604
Jun 13 16:14:11 server rrdcached[1455]: removing old journal /var/lib/rrdcached/journal//rrd.journal.1371125651.672613
Jun 13 16:17:01 server /USR/SBIN/CRON[1030431]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

The PVE Version

root@server ~ # pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1

It is an Debian Squeeze 64, any Idee whats the Problem is ?

 

[Miguel Moreira]

I have similar experience, after a couple days working my node, I receive this logs. and inmediatly after, I lost my node



Nov 2 21:46:48 xxxxxxx rrdcached[5156]: flushing old values
Nov 2 21:46:48 xxxxxxx rrdcached[5156]: rotating journals
Nov 2 21:46:48 xxxxxxx rrdcached[5156]: started new journal /var/lib/rrdcached/journal/rrd.journal.1541206008.932379
Nov 2 21:46:48 xxxxxxx rrdcached[5156]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1541198808.932405
Nov 2 22:46:48 xxxxxxx rrdcached[5156]: flushing old values
Nov 2 22:46:48 xxxxxxx rrdcached[5156]: rotating journals
Nov 2 22:46:48 xxxxxxx rrdcached[5156]: started new journal /var/lib/rrdcached/journal/rrd.journal.1541209608.932136
Nov 2 22:46:48 xxxxxxx rrdcached[5156]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1541202408.932132
Nov 5 08:12:38 xxxxxxx kernel: [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 5 08:12:38 xxxxxxx kernel: [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable

this is my pveversion


pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-8-pve)
pve-manager: 5.2-10 (running version: 5.2-10/6f892b40)
pve-kernel-4.15: 5.2-11
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.10.17-2-pve: 4.10.17-20
ceph: 12.2.8-pve1
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-41
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-30
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-3
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-29
pve-docs: 5.2-9
pve-firewall: 3.0-14
pve-firmware: 2.0-6
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-38
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve2~bpo1

 

[MultiLAN]

Hi, sorry for comment in this old thread, but I´ve the same problem discribed in this topic.

How did you resolve it?