rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_red
icon_red
icon_green
icon_green
icon_red
icon_red
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_red
icon_blue
icon_red
icon_orange
icon_red
icon_red
icon_red
icon_red
icon_red
icon_red
icon_red
icon_green
icon_red
icon_orange
icon_green
 

FS#609 — FS#4656 — rbx2 room 26

Attached to Project— Network
Incident
the whole network
CLOSED
100%
One of the UPS in Room 26 was defected for a few seconds.
It up. And the servers are coming back.

We are putting resources on the defected servers.
We are looking meanwhile at the problem's origin.

Date:  Wednesday, 13 October 2010, 15:31PM
Reason for closing:  Done
Comment by OVH - Thursday, 30 September 2010, 16:59PM

The UPS has crashed and rebooted ... simply.
The builder explored the site to explain the origin of the crash.


Comment by OVH - Thursday, 30 September 2010, 20:16PM

63 servers remaining. the servers return back alone afterwords,
We have solved all the problems of "check disk/ctrl-d".
It remains just some cases with very hard configurations that are broken at boot. We are fixing them one by one. it will take time.


Comment by OVH - Friday, 01 October 2010, 15:12PM

The context:
In case of an electricity cut, once the power generators start, the UPS are planned to resupply progressively (following a ramp of intensity during 1 minute). This allows mounting the progressive charge of power generators.

The problem:
We suppose a software bug while the UPS performs the ramp. The logs indicate that whatever the break time is, the UPS remains discharged for 4 further minutes! It just needs few short micro-cuts to completely discharge the batteries ... That's what happened.

The manufacturer should bring investigations. While waiting and to prevent, we are going to disable the ramp's functionality on all the UPS (and simulate the behaviour by shifting few seconds the charge of every UPS).