OpenVZ Forum


Home » General » Support » Failed Restart
Failed Restart [message #13551] Tue, 29 May 2007 20:56 Go to next message
Ashley is currently offline  Ashley
Messages: 40
Registered: December 2006
Member
When every i restart a host node, it takes too hard reboots to get the server up.

When i first send the server for a restart this is the start of the log "messages"
---------------------
May 28 20:58:36 IS-1672 kernel: VE: 208: stopped
May 28 20:58:37 IS-1672 kernel: VE: 208: started
May 28 20:58:39 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 21:00:14 IS-1672 kernel: VE: 208: stopped
May 28 21:00:15 IS-1672 kernel: VE: 208: started
May 28 21:00:17 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 21:02:25 IS-1672 kernel: VE: 208: stopped
May 28 21:02:26 IS-1672 kernel: VE: 208: started
May 28 21:02:27 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 21:03:10 IS-1672 kernel: VE: 208: stopped
May 28 21:03:10 IS-1672 kernel: VE: 208: started
May 28 21:03:12 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 22:11:26 IS-1672 sshd(pam_unix)[23419]: session opened for user root by root(uid=0)
May 28 22:27:27 IS-1672 kernel: VE: 247: started
May 28 22:27:27 IS-1672 kernel: VE: 247: stopped
May 28 22:39:54 IS-1672 syslogd 1.4.1: restart.
May 28 22:39:54 IS-1672 syslog: syslogd startup succeeded
May 28 22:39:54 IS-1672 kernel: klogd 1.4.1, log source = /proc/kmsg started.
May 28 22:39:54 IS-1672 kernel: Linux version 2.6.18-8.el5.028stab031.1PAE (root@rhel5-32-build) (gcc version 4.1.1 20061011$
May 28 22:39:54 IS-1672 kernel: BIOS-provided physical RAM map:
----------------------------

The last message that the server leaves before hanging is.

----------------------------
May 28 22:39:23 IS-1672 fsck: /vz: Clearing
May 28 22:39:23 IS-1672 fsck: orphaned inode 3032496 (uid=0, gid=0, mode=041777, size=20480)
May 28 22:39:23 IS-1672 fsck: /vz: Clearing orphaned inode 3034380 (uid=100, gid=101, mode=0100600, size=0)
May 28 22:39:23 IS-1672 fsck: /vz: Clearing orphaned inode 3034379 (uid=100, gid=101, mode=0100600, size=0)
May 28 22:39:23 IS-1672 fsck: /vz: Clearing orphaned inode 3034378 (uid=100, gid=101, mode=0100600, size=0)
May 28 22:39:23 IS-1672 fsck: /vz: Clearing orphaned inode 3034333 (uid=100, gid=101, mode=0100600, size=0)
May 28 22:39:23 IS-1672 fsck: /vz: clean, 781052/8962048 files, 13670906/17918499 blocks
May 28 22:39:29 IS-1672 fsck: /dev/sdb1: Clearing orphaned inode 8831123 (uid=0, gid=0, mode=0100600, size=0)
May 28 22:39:29 IS-1672 fsck: /dev/sdb1: Clearing
May 28 22:39:29 IS-1672 fsck: orphaned inode 9176186 (uid=0, gid=0, mode=0100644, size=490)
May 28 22:39:29 IS-1672 fsck: /dev/sdb1: Clearing orphaned inode 9176297 (uid=0, gid=0, mode=0100644, size=1208)
May 28 22:39:30 IS-1672 fsck: /dev/sdb1: Clearing orphaned inode 12125163 (uid=0, gid=0, mode=0140777, size=0)
May 28 22:39:30 IS-1672 fsck: /dev/sdb1: clean, 123223/19546112 files, 6361169/39072080 blocks
May 28 22:39:47 IS-1672 rc.sysinit: Checking filesystems succeeded
May 28 22:39:47 IS-1672 rc.sysinit: Mounting local filesystems: succeeded
May 28 22:39:47 IS-1672 rc.sysinit: Enabling local filesystem quotas: succeeded
May 28 22:39:48 IS-1672 rc.sysinit: Enabling swap space: succeeded
May 28 22:39:48 IS-1672 init: Entering runlevel: 3
May 28 22:39:48 IS-1672 sysstat: Calling the system activity data collector (sadc):
May 28 22:39:48 IS-1672 sysstat:
May 28 22:39:48 IS-1672 rc: Starting sysstat: succeeded
May 28 22:39:48 IS-1672 sysctl: warning: /etc/sysctl.conf(8): invalid syntax, continuing...
May 28 22:39:48 IS-1672 sysctl: net.ipv4.ip_forward = 1
May 28 22:39:48 IS-1672 sysctl: net.ipv4.conf.default.proxy_arp = 0
May 28 22:39:48 IS-1672 sysctl: net.ipv4.conf.all.rp_filter = 1
May 28 22:39:48 IS-1672 sysctl: kernel.sysrq = 1
May 28 22:39:48 IS-1672 sysctl: net.ipv4.conf.default.send_redirects = 1
May 28 22:39:48 IS-1672 sysctl: net.ipv4.conf.all.send_redirects = 0
May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_mem = 999999 1572864 1972864
May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_wmem = 4096 65536 524288
May 28 22:39:48 IS-1672 sysctl: net.core.wmem_max = 1048576
May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_rmem = 4096 87380 524288
May 28 22:39:48 IS-1672 sysctl: net.core.rmem_max = 1048576
May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_sack = 0
May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_timestamps = 0
May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_max_tw_buckets = 1800000
May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_orphan_retries = 4
May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_fin_timeout = 30
May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_window_scaling = 0

May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_fin_timeout = 30
May 28 22:39:48 IS-1672 sysctl: net.ipv4.tcp_window_scaling = 0
May 28 22:39:48 IS-1672 network: Setting network parameters: succeeded
May 28 22:39:49 IS-1672 network: Bringing up loopback interface: succeeded
May 28 22:39:53 IS-1672 network: Bringing up interface eth0: succeeded
May 28 22:39:53 IS-1672 ifup: Bringing up interface venet0:
May 28 22:39:53 IS-1672 ifup: Configuring interface venet0:
May 28 22:39:53 IS-1672 ifup: net.ipv4.conf.venet0.send_redirects = 0
May 28 22:39:53 IS-1672 network: Bringing up interface venet0: succeeded
May 28 22:40:15 IS-1672 proftpd[4923]: IS-1672 - error setting IPV6_V6ONLY: Protocol not available
May 28 22:40:15 IS-1672 proftpd[4923]: IS-1672 - ProFTPD 1.3.0 (stable) (built Wed Sep 13 17:13:34 EDT 2006) standalone mode$
May 28 22:40:15 IS-1672 proftpd: - IPv6 getaddrinfo 'IS-1672' error: Name or service not known
May 28 22:40:15 IS-1672 proftpd: proftpd startup succeeded
May 28 22:40:15 IS-1672 httpd: httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for Serv$
May 28 22:40:16 IS-1672 httpd: httpd startup succeeded
May 28 22:40:16 IS-1672 crond: crond startup succeeded
May 28 22:40:17 IS-1672 xfs[4971]: ignoring font path element /usr/X11R6/lib/X11/fonts/misc:unscaled (unreadable)
May 28 22:40:17 IS-1672 xfs[4971]: ignoring font path element /usr/X11R6/lib/X11/fonts/75dpi:unscaled (unreadable)
May 28 22:40:17 IS-1672 xfs[4971]: ignoring font path element /usr/X11R6/lib/X11/fonts/100dpi:unscaled (unreadable)
May 28 22:40:17 IS-1672 xfs[4971]: ignoring font path element /usr/X11R6/lib/X11/fonts/Type1 (unreadable)
May 28 22:40:17 IS-1672 xfs: xfs startup succeeded
May 28 22:40:18 IS-1672 anacron: anacron startup succeeded
May 28 22:40:18 IS-1672 atd: atd startup succeeded
May 28 22:40:18 IS-1672 kernel: Netfilter messages via NETLINK v0.30.
May 28 22:40:18 IS-1672 kernel: ip_conntrack: parameter ip_conntrack_enable_ve0 is obsoleted. In ovzkernel >= 2.6.15 connect$
May 28 22:40:18 IS-1672 kernel: ip_conntrack version 2.4 (8179 buckets, 65432 max) - 232 bytes per conntrack
May 28 22:40:19 IS-1672 kernel: VE: 102: started
May 28 22:40:34 IS-1672 kernel: lo: Disabled Privacy Extensions
--------------------------------

The last message is "Diabled Privacy Extensions" that is the last message.

When i then have the server hard rebooted again it displays

--------------------------------
May 28 22:45:44 IS-1672 kernel: VE: 102: started
May 28 22:45:57 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 22:46:56 IS-1672 kernel: VE: 104: started
May 28 22:47:10 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 22:48:14 IS-1672 kernel: VE: 105: started
May 28 22:48:21 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 22:48:49 IS-1672 kernel: VE: 108: started
May 28 22:49:04 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 22:50:42 IS-1672 kernel: VE: 202: started
May 28 22:50:44 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 22:50:51 IS-1672 kernel: VE: 205: started
May 28 22:50:58 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 22:50:59 IS-1672 kernel: VE: 206: started
May 28 22:51:10 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 22:51:18 IS-1672 kernel: VE: 207: started
May 28 22:51:28 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 22:51:38 IS-1672 kernel: VE: 208: started
May 28 22:51:46 IS-1672 kernel: lo: Disabled Privacy Extensions
May 28 22:51:47 IS-1672 kernel: VE: 209: started
May 28 22:51:51 IS-1672 messagebus: messagebus startup succeeded
----------------------------
However the server starts find and there is no problem.

I have seen some bug reports about a kernel message which sound likely, however it is fixed in a kernel which is not avaliable yet for Centos. Currently using "Linux IS-1672 2.6.18-8.el5.028stab031.1PAE #1 SMP Sat Apr 28 01:22:56 MSD 2007 i686 i686 i386 GNU/Linux"

With most uptodate operating system.

Thanks , Sorry about long post.
Re: Failed Restart [message #13639 is a reply to message #13551] Thu, 31 May 2007 19:17 Go to previous messageGo to next message
Ashley is currently offline  Ashley
Messages: 40
Registered: December 2006
Member
Anyone?
Re: Failed Restart [message #13702 is a reply to message #13551] Mon, 04 June 2007 07:01 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Ashley, can you, please, explain your problem more clearly! I just don't understand your problem...
For simplicity, do it in the following way: "I give the command XXX, and I expect YYY to happen, but ZZZ happens" Smile Without any logs for the beginning.

Thank you,
Vasily.
Re: Failed Restart [message #13708 is a reply to message #13551] Mon, 04 June 2007 08:10 Go to previous messageGo to next message
Ashley is currently offline  Ashley
Messages: 40
Registered: December 2006
Member
When ever i run the command vzctl restart or vzctl stop with a vps id number it restarts every single vps or stops every single vps.

This sometimes causes the server to Kernel Panic if the VPS have a high load, but normal this just causes every VPS to restart, even if i just run the command vzctl restart 102.

[Updated on: Mon, 04 June 2007 08:13]

Report message to a moderator

Re: Failed Restart [message #13710 is a reply to message #13708] Mon, 04 June 2007 08:15 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hmm... Sounds like something fantastic! Wink Can you give me an ssh access to your node?

Thanks,
Vasily
Re: Failed Restart [message #13713 is a reply to message #13710] Mon, 04 June 2007 08:21 Go to previous messageGo to next message
Ashley is currently offline  Ashley
Messages: 40
Registered: December 2006
Member
I am currently requesting a KVM over ip, due the kernel errors, once that it setup if you wish i can give you SSH and KVM access to the node.

Is this ok?
Re: Failed Restart [message #13715 is a reply to message #13713] Mon, 04 June 2007 09:13 Go to previous messageGo to next message
Ashley is currently offline  Ashley
Messages: 40
Registered: December 2006
Member
I now have managed to get the Kernel Opps which occurs.

Attached Imageindex.php?t=getfile&id=352&private=0
Re: Failed Restart [message #13716 is a reply to message #13715] Mon, 04 June 2007 10:09 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
It's very good! There must be a bit more messages above it, concerning EIP register. Can post it too, please!

Thank you,
Vasily.
Re: Failed Restart [message #13718 is a reply to message #13715] Mon, 04 June 2007 11:19 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hello,

We fixed one important bug related to VE stop and iptables (http://bugzilla.openvz.org/show_bug.cgi?id=561) in 028stab033 kernel. Can you, please, try it and inform us about results?

Thank you,
Vasily.
Re: Failed Restart [message #13719 is a reply to message #13718] Mon, 04 June 2007 11:46 Go to previous messageGo to next message
Ashley is currently offline  Ashley
Messages: 40
Registered: December 2006
Member
I am currently running 2.6.18-8.1.3.el5.028stab033.1PAE.

Since upgrading to this kernel i no longer have problems with the restarting the VPS, i only receive the kernel error when restarting the server.
Re: Failed Restart [message #13720 is a reply to message #13719] Mon, 04 June 2007 11:56 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Thank you for info!
Quote:

... i only receive the kernel error when restarting the server
What exact kernel error do you receive?

Thanks,
Vasily
Re: Failed Restart [message #13721 is a reply to message #13720] Mon, 04 June 2007 12:03 Go to previous messageGo to next message
Ashley is currently offline  Ashley
Messages: 40
Registered: December 2006
Member
The kernel error i receive is the screen shot posted above, it happens during the server shutting down, and happens just after all the VPS are shutdown.

Thanks

Re: Failed Restart [message #13782 is a reply to message #13715] Tue, 05 June 2007 09:42 Go to previous messageGo to next message
adobriyan is currently offline  adobriyan
Messages: 80
Registered: November 2006
Member
This bug lives at http://bugzilla.openvz.org/show_bug.cgi?id=607
now. And I've reproduced it couple of times.
Re: Failed Restart [message #13786 is a reply to message #13551] Tue, 05 June 2007 10:28 Go to previous messageGo to next message
Ashley is currently offline  Ashley
Messages: 40
Registered: December 2006
Member
Ok thanks, i will remove iptables_nat for the moment in all my configs.

Thanks
Re: Failed Restart [message #13793 is a reply to message #13786] Tue, 05 June 2007 13:02 Go to previous message
adobriyan is currently offline  adobriyan
Messages: 80
Registered: November 2006
Member
patch has been sent. yell on bug if it doesn't work
http://bugzilla.openvz.org/show_bug.cgi?id=607#c3
Previous Topic: Good Tutoral to set CONF files
Next Topic: vzmigrate public key
Goto Forum:
  


Current Time: Wed Nov 06 08:21:32 GMT 2024

Total time taken to generate the page: 0.04777 seconds