PVE suddenly displaying "no content" instead of syslog messages

[lpallard]

Hello

my PVE node has decided to display "no content" and a blank page instead of the syslog messages that you usually can see under syslog tab of the WebGUI.. Not sure when this started to happen, but first time I saw this (about 2 weeks ago) at that time I thought that the syslog was simply empty, nothing more..

Then today I had to do some minor VM changes and decided to take a look at syslog to see if it worked only to discover that it still does that.

See attached screenshot.

A SSH session to PVE shows dmesg to be normal, and /var/log/messages is totally empty... Is that normal??

I guess somehow the PVE web GUI has lost contact with the syslog???

Can someone help me troubleshoot this?

thanks!

 

[mir]

I have seen this after an upgrade of rsyslog package. To fix do the following from the command line:
1) killall rsyslogd
2) service rsyslog start

 

[lpallard]

I have seen this after an upgrade of rsyslog package. To fix do the following from the command line:
1) killall rsyslogd
2) service rsyslog start

Worked!!

So I take that rsyslogd was somehow in a half-awake state and needed to be brought back fresh..

Are the PVE devs aware of this?

Thanks Mir for the suggestion! It worked !

 

[dietmar]

Are the PVE devs aware of this?

I never saw that - rsyslog works perfectly for me, even after updates.

 

[lpallard]

I never saw that - rsyslog works perfectly for me, even after updates.

Obviously something is not quite right. Mir's reply made me remember that I indeed updated some packages and rsyslogd was one of them.

 

[Mannekino]

I had the same problem. It seems a bug in the Linux kernel. It has already been reported I don't know if it has been fixed yet. Please see the following:

https://www.debian.org/security/2014/dsa-3047
http://forums.debian.net/viewtopic.php?f=10&t=117939
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763700
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763831

I think it has been fixed in the most recent update. I just tested to see if I can restart rsyslogd using the init.d script and that works again.

 

[375gnu]

1) killall rsyslogd

And what about your openvz containers? It's better to do kill `cat /run/rsyslogd.pid`.