Results 126 to 150 of 270
-
08-02-2013, 09:14 AM #126Web Hosting Guru
- Join Date
- May 2012
- Location
- Germany
- Posts
- 264
I'm sorry to hear you're also having problems, though it sounds like in the case of your first server it was a cooling issue that has since been fixed. I hope that server doesn't crash again. If it does you can also ask our technicians about a BIOS update.
As for the "new" EX6S, we are still planning that and it's good to know you'd be interested in an SSD version. Thanks for letting us know!
-
08-02-2013, 09:55 AM #127Newbie
- Join Date
- Dec 2012
- Posts
- 14
Thanks for your quick answer. I have just made a HW diff on all our EX40, and it seems in fact that the server with the beta BIOS did not crash since
the upgrade (I assumed so because we restarted it several times since the upgrade and I assumed it had crashed again.)
The beta BIOS is V2.4B3, released on 07/10/2013 . I'll make sure this is the newest one and will request an upgrade on our other servers.
I will post an update on this topic once we have enough data to make a new feedback.
-
08-02-2013, 10:04 AM #128Web Hosting Guru
- Join Date
- May 2012
- Location
- Germany
- Posts
- 264
That's great to hear! As mentioned before, a BIOS update seems to solve the issue, so I'm glad that is the case with you.
The beta BIOS is V2.4B3, released on 07/10/2013 . I'll make sure this is the newest one and will request an upgrade on our other servers.
I will post an update on this topic once we have enough data to make a new feedback.
-
08-03-2013, 07:35 AM #129Junior Guru
- Join Date
- Feb 2006
- Location
- ::1/128
- Posts
- 247
I hope for a positive outcome too.
ex40-ssd crashed on the first 6 hours. Only centos 64bit installed (minimal). Didn't even had time for any other configurations (apache / bind / panel / and so on).
I've sent a ticket, replied with
"as requested we've checked the and optimized the BIOS-settings".
Second time I got a reply
"Unfortunately the server didn't showed a screen output and didn't respond to
keystrokes. Because of this we can't tell you the reason of the issue."
Hope for a fix. If something can't even has screen output or any keystroke doesn't work, I hardly believe it's a software issue.
-
08-03-2013, 11:57 AM #130Web Hosting Evangelist
- Join Date
- May 2009
- Location
- Markham, Canada
- Posts
- 458
In our case BIOS V2.14B3 *seems* to have resolved this. 20+ hours of uptime so far. Can only tell for sure after 2-3 days have passed.
We use basic centos-6 64-bit installation too.Dan
Check out our premium self-managed SSD VPS
-
08-03-2013, 12:22 PM #131Divided by Zero
- Join Date
- Jun 2009
- Posts
- 1,219
I also see those messages in kernel.log:
Aug 3 12:35:07 node kernel: CPU1: Core power limit notification (total events = 4)
Aug 3 12:35:07 node kernel: CPU4: Core power limit notification (total events = 4)
Aug 3 12:35:07 node kernel: CPU7: Core power limit notification (total events = 2)
Aug 3 12:35:07 node kernel: CPU0: Core power limit notification (total events = 4)
Aug 3 12:35:07 node kernel: CPU5: Core power limit notification (total events = 4)
Aug 3 12:35:07 node kernel: CPU3: Core power limit notification (total events = 4)
Aug 3 12:35:07 node kernel: CPU6: Core power limit notification (total events = 4)
Aug 3 12:35:07 node kernel: CPU2: Core power limit notification (total events = 4)
Aug 3 12:35:07 node kernel: CPU4: Package power limit notification (total events = 3)
Aug 3 12:35:07 node kernel: CPU7: Package power limit notification (total events = 1)
Aug 3 12:35:07 node kernel: CPU0: Package power limit notification (total events = 4)
Aug 3 12:35:07 node kernel: CPU5: Package power limit notification (total events = 4)
Aug 3 12:35:07 node kernel: CPU3: Package power limit notification (total events = 4)
Aug 3 12:35:07 node kernel: CPU6: Core power limit normal
Aug 3 12:35:07 node kernel: CPU2: Core power limit normal
Aug 3 12:35:07 node kernel: CPU4: Core power limit normal
Aug 3 12:35:07 node kernel: CPU7: Core power limit normal
Aug 3 12:35:07 node kernel: CPU0: Core power limit normal
Aug 3 12:35:07 node kernel: CPU5: Core power limit normal
Aug 3 12:35:07 node kernel: CPU3: Core power limit normal
Aug 3 12:35:07 node kernel: CPU4: Package power limit normal
Aug 3 12:35:07 node kernel: CPU7: Package power limit normal
Aug 3 12:35:07 node kernel: CPU0: Package power limit normal
Aug 3 12:35:07 node kernel: CPU5: Package power limit normal
Aug 3 12:35:07 node kernel: CPU3: Package power limit normal
Aug 3 12:35:07 node kernel: CPU1: Core power limit normal
-
08-03-2013, 01:02 PM #132Web Hosting Evangelist
- Join Date
- May 2009
- Location
- Markham, Canada
- Posts
- 458
Dan
Check out our premium self-managed SSD VPS
-
08-03-2013, 01:53 PM #133Divided by Zero
- Join Date
- Jun 2009
- Posts
- 1,219
Well, I just had the server for some hours until it suddenly went down. They did a 12 hours hardware check and found no issue. They brought the server back and it is running well since then. But we are only talking about approx. 3 days without problems.
root@node ~ # uptime
19:51:39 up 3 days, 16:50, 1 user, load average: 0.34, 0.28, 0.27
root@node ~ #
-
08-03-2013, 03:12 PM #134Divided by Zero
- Join Date
- Jun 2009
- Posts
- 1,219
Okay, Update: I opened a ticket with Hetzner about the above kernel.log events and received a very friendly answer within 30mins by a Support Tech. I was told that this error message results from a kernel bug and that it could be fixed by adding
-----------------%<-----------------
clearcpuid=229
-----------------%<-----------------
as Kernel parameter within Grub.
I then asked whether this change would be crucial and was told (< 5mins) that this messages are non-critical, followed by a brief explanation in german that I am too lazy to translate, but that have been helpful. I am quite impressed by the speed and friendliness of their support on a weekend...
-
08-03-2013, 03:25 PM #135Web Hosting Evangelist
- Join Date
- May 2009
- Location
- Markham, Canada
- Posts
- 458
clearcpuid=229
When our EX40 server was upgraded to BIOS V2.14B3, these messages stopped WITHOUT disabling PLN, which is a very promising result. Server did not crash either, but we are waiting for 3-5 days before we can call this a solution.Dan
Check out our premium self-managed SSD VPS
-
08-04-2013, 06:42 AM #136Divided by Zero
- Join Date
- Jun 2009
- Posts
- 1,219
Well, damn...
My EX40-SSD became unresponsive again for 1.5 and another 1 hour this night. So 2.5 hours of downtime.
I have no idea why. I will still try to work with their support because they were quick & friendly until now, but I am about to loose faith in that new server...
-
08-04-2013, 01:44 PM #137Web Hosting Evangelist
- Join Date
- May 2009
- Location
- Markham, Canada
- Posts
- 458
Ask them to update BIOS in your server to V2.14B3, looks like it fixes these issues.
Dan
Check out our premium self-managed SSD VPS
-
08-04-2013, 02:17 PM #138Junior Guru Wannabe
- Join Date
- Mar 2011
- Posts
- 76
-
08-04-2013, 02:20 PM #139Web Hosting Evangelist
- Join Date
- May 2009
- Location
- Markham, Canada
- Posts
- 458
This version number is from dmidecode output: V2.14B3
So far we have 47 hours of uptime (before that we were getting 8-14 before the crash).Dan
Check out our premium self-managed SSD VPS
-
08-04-2013, 02:33 PM #140Junior Guru
- Join Date
- Feb 2006
- Location
- ::1/128
- Posts
- 247
-
08-04-2013, 02:48 PM #141Divided by Zero
- Join Date
- Jun 2009
- Posts
- 1,219
They "prophylactically" swapped the RAM in my EX40-SSD now. While I tend to cancel it already because I do not have the time and will to chase errors with the server that I have not caused, I will give it a chance for some days. Let's see if it crashes again. That is really unfortunate - I like Hetzner's panel and their support was quick and friendly too throughout the weekend...
-
08-04-2013, 03:10 PM #142Hello World
- Join Date
- Nov 2009
- Location
- /etc/my.cnf
- Posts
- 10,657
UK Based Proactive Server Management.
Zabbix Enterprise 24/7 Monitoring.
-
08-04-2013, 03:35 PM #143Web Hosting Evangelist
- Join Date
- May 2009
- Location
- Markham, Canada
- Posts
- 458
We have the following RAM modules in our server (from dmidecode):
Kingston 99U5471-037.A00LF
Configured Clock Speed: 1333 MHzDan
Check out our premium self-managed SSD VPS
-
08-04-2013, 03:38 PM #144Divided by Zero
- Join Date
- Jun 2009
- Posts
- 1,219
Here, after the Swap:
Kingston 99U5471-037.A00LF
Configured Clock Speed: 1600 MHz
-
08-04-2013, 04:21 PM #145Junior Guru Wannabe
- Join Date
- Mar 2011
- Posts
- 76
-
08-04-2013, 04:22 PM #146Junior Guru Wannabe
- Join Date
- Jul 2010
- Posts
- 38
-
08-04-2013, 04:28 PM #147Junior Guru Wannabe
- Join Date
- Mar 2011
- Posts
- 76
OK here is what i have notice.
We have 2 servers SSD version.
Both servers have the V2.14B3 version on it and both server ware heaving problems.
I open ticket for one of the servers to perform the bios check/upgrade/configuration and after they return the server i have the same BIOS version but i notice that the RAM clock speed is downgraded from 1600MHz to 1333MHz.
-
08-05-2013, 06:10 AM #148Web Hosting Guru
- Join Date
- May 2012
- Location
- Germany
- Posts
- 264
Hello everyone, here's a general response to the questions and comments posted in this thread.
If the BIOS update doesn't fix the issue, then the "issue" is most likely not with the RAM, but is either some other hardware problem or a software problem. Please try to make sure it is not a software problem yourself. If the server freezes or crashes while it is in the Rescue System then it is most likely a hardware problem. Our technicians can do a hardware check and will obviously replace any faulty hardware.
One of the fixes we found that helped (before we got the BIOS update) was changing the speed of the RAM to 1333Mhz. If you have gotten a BIOS update the RAM can be run at 1600Mhz.
Also, all new servers we provide already have the latest BIOS, so they shouldn't have any problems.
The "power limit" notifications are basically a bug, and can be ignored or removed. See also the following bug report (comment 35 is helpful):
https://bugzilla.kernel.org/show_bug.cgi?id=36182
-
08-05-2013, 12:46 PM #149Junior Guru Wannabe
- Join Date
- Mar 2011
- Posts
- 76
-
08-05-2013, 01:31 PM #150Web Hosting Evangelist
- Join Date
- May 2009
- Location
- Markham, Canada
- Posts
- 458
On EX40 this notification occurs on *any* kernel - we have tested this with 2.6.32, 3.0.88 and 3.10.4 kernels on stock Centos-6 64-bit. Perhaps the fix was not yet pushed into mainline kernel?
Regardless, looks like the BIOS update did solve *something*, as we have had no crashes for the past 72 hours now (and we did not touch anything on the server and even went back to 2.6.32 kernel).Dan
Check out our premium self-managed SSD VPS
Similar Threads
-
Hetzner billing issues
By Munch1 in forum Web Hosting LoungeReplies: 5Last Post: 03-20-2012, 12:58 PM -
Hetzner experiences ?
By SpaceStation in forum Dedicated ServerReplies: 14Last Post: 01-09-2012, 05:33 AM -
Anyone had issues with hetzner later?
By alex2012 in forum Dedicated ServerReplies: 9Last Post: 12-15-2011, 02:06 PM -
Anyone having network issues with Hetzner?
By ppwill in forum Dedicated ServerReplies: 4Last Post: 07-02-2011, 04:46 PM -
Hetzner DC 12 Network Issues
By Afterburst-Nick in forum Providers and Network Outages and UpdatesReplies: 1Last Post: 07-12-2010, 05:23 PM