We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

This is futile


xvd
26-03-2015, 14:29
Unfortunately turning off RTM does not help.

Now I am in reboot hell - one reboot after another.

And SYS support? Ignoring all tickets.

LawsHosting
26-03-2015, 13:51
Quote Originally Posted by xvd
So if I understand it - there may be a problem in SYS real-time monitoring which causes the reboots?
Try turning off RTM for a while to see if it is that?

xvd
26-03-2015, 13:25
Quote Originally Posted by Kamilleri
Experiencing the same behavior...
RBX2 - Rack: 21A08 - Server ID: 231310
(http://forum.ovh.co.uk/showthread.ph...%28same-day%29)
Interesting Kamilleri ... there is some resemblance to your problem even though I run different distribution of Linux (specifically Ubuntu 12.04).

So if I understand it - there may be a problem in SYS real-time monitoring which causes the reboots?

Anyway, the lack of SYS support is very worrying. Their response time is 2-3 days and the response is not helpful at all.

Kamilleri
26-03-2015, 07:59
Experiencing the same behavior...
RBX2 - Rack: 21A08 - Server ID: 231310
(http://forum.ovh.co.uk/showthread.ph...%28same-day%29)

xvd
25-03-2015, 14:05
Quote Originally Posted by alvaroag
What do you get on your syslog?
That's the weird part - there is no information that would indicate a problem. Just BANG - reboot out of the blue.

For example:

Mar 25 13:01:15 iegh01 kernel: [ 25.200492] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Mar 25 13:01:15 iegh01 kernel: [ 25.201175] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 25 13:02:22 iegh01 kernel: imklog 5.8.6, log source = /proc/kmsg started.
Mar 25 13:02:22 iegh01 rsyslogd: [origin software="rsyslogd" swVersion="5.8.6" x-pid="704" x-info="http://www.rsyslog.com"] start
Mar 25 13:02:22 iegh01 rsyslogd: rsyslogd's groupid changed to 103
Mar 25 13:02:22 iegh01 rsyslogd: rsyslogd's userid changed to 101
Mar 25 13:02:22 iegh01 rsyslogd-2039: Could not open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
Mar 25 13:02:22 iegh01 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Mar 25 13:02:22 iegh01 kernel: [ 0.000000] Initializing cgroup subsys cpu
Mar 25 13:02:22 iegh01 kernel: [ 0.000000] Linux version 3.2.0-70-generic (buildd@tipua) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #105-Ubuntu SMP Wed Sep 24 19:49:16 UTC 2014 (Ubuntu 3.2.0-70.105-generic 3.2.63)

alvaroag
25-03-2015, 13:27
What do you get on your syslog?

xvd
25-03-2015, 13:12
Thank you for the suggestion, Criot.

I am not using OVH kernel (yes - I learned the hard way some time ago). I was using "3.2.0-75-generic #110-Ubuntu SMP" kernel

Few minutes ago I tried to downgrade to "3.2.0-70-generic #105-Ubuntu SMP". I know this kernel works on a nearly identical SYS server - both in terms of hardware and software - with no problem. Unfortunately, very quickly I got 3 self-initiated reboots.

Criot
25-03-2015, 12:08
The most common cause is the OVH kernel, make sure you're using the operating systems distro kernel and not the OVH one.

xvd
25-03-2015, 11:54
Dealing with SYS support is like pulling teeth.

We were delivered a faulty server which keeps randomly freezing and rebooting.

The SYS support claims that they checked and "there is nothing wrong with the server" even though the server will reboot within minutes (or max. hours) after initiating a SSH session or sometimes even without connecting to the server.

Anybody had a similar problem? What shall one do in such a situation?

[Of course the server is paid up so they are happy to keep the money but obviously we cannot use the server]