OpenVZ Forum: Support » Can main node issue casue guest vps to lose all logs?

Home » General » Support » Can main node issue casue guest vps to lose all logs?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Can main node issue casue guest vps to lose all logs? [message #40373]

Sun, 15 August 2010 05:14

scyllar
Messages: 1
Registered: August 2010

Junior Member

Hello I am new here so if I posted the wrong place please correct me.

The issue is with my new VPS on OpenVZ. One day I found all the log records before a certain time have just gone in the air, after a VPS down time, but I have been able to check the records a few mins ago, which seems so weird to me. According to my provider it is because -

Quote:

The main node under which the VPS is hosted faced some temporaray issue and the concerned department have worked on it to rectify the issue and improve the performance.
we checked with the another node too which is hosted under the main node it is too facing the same issue, that is having the logs from Aug 15.But presently your VPS is working fine.Please let us know if any further concerns.

My question is: is it even possible for OpenVZ technology to delete all VPS guest's logs due to a main node issue? If it is possible, what kind of main node issue could have done so? ( I was previously told to be "Network" issue by this provider while I asked them why the VPS is down.)

P.S

The logs in comparison

Before:

Quote:

[root@www ~]$ tail -30 /var/log/messages
Aug 7 08:00:50 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="13617"] restart
Aug 7 08:03:29 www shutdown[19568]: shutting down for system reboot
Aug 7 08:12:31 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 7 08:12:31 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="8043"] restart
Aug 8 00:50:19 www shutdown[26330]: shutting down for system reboot
Aug 8 00:50:58 www kernel: Kernel logging (proc) stopped.
Aug 8 00:51:00 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 8 00:51:00 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="3388"] restart
Aug 8 00:59:01 www shutdown[3461]: shutting down for system reboot
Aug 8 00:59:08 www kernel: Kernel logging (proc) stopped.
Aug 8 01:01:06 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 8 01:01:06 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="18412"] restart
Aug 9 01:44:03 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 9 01:44:03 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="18412"] restart
Aug 10 01:44:04 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 10 01:44:04 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="18412"] restart
Aug 11 01:44:04 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 11 01:44:04 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="18412"] restart
Aug 12 01:44:02 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 12 01:44:02 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="18412"] restart
Aug 13 01:44:03 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 13 01:44:03 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="18412"] restart
Jan 22 06:25:34 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Jan 22 06:25:34 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="20170"] restart
Aug 14 08:03:49 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 14 08:03:49 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="27750"] restart
Aug 14 16:57:41 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 14 16:57:41 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="3281"] restart
Aug 14 20:27:10 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 14 20:27:10 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="31781"] restart

After:

Quote:

Then some time later (also from local ssh log):
[root@www ~]$ tail -30 /var/log/messages
Aug 15 01:44:04 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 15 01:44:04 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="31781"] restart

What is your best guess? Thank you in advance.

Report message to a moderator

Re: Can main node issue casue guest vps to lose all logs? [message #40452 is a reply to message #40373]

Thu, 19 August 2010 19:21

curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany

Senior Member

Hi,

have you check the "logrotation" ?
Have you any logs like messages.0 messages.1.gz ...

Seems that every day at 01:44 rsyslogd is restarted, and the logs go to be rotated.

If package logrotate is installed please check the period of logrotation config for rsyslog
like /etc/logrotate.d/rsyslog

But in your logs are is a strange entry:

---8<...
Aug 13 01:44:03 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 13 01:44:03 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="18412"] restart

Jan 22 06:25:34 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Jan 22 06:25:34 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="20170"] restart

^_ what's that, time warp :: please check the hardware node time

Aug 14 08:03:49 www kernel: imklog 3.18.6, log source = /proc/kmsg started.
Aug 14 08:03:49 www rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="27750"] restart
---8<...

Bye,
Thorsten

Report message to a moderator

Previous Topic:	nagios: Warning: The check of host '****' could not be performed due to a fork() error:
Next Topic:	Out of band console access

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Aug 05 07:20:19 GMT 2024

Total time taken to generate the page: 0.02984 seconds