OVHcloud Web Hosting Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
FS#4762 — server8.sqlprive
Incident Report for Web Cloud
Resolved
Private servers have been moved to new physical servers, following the failure of the server8.sqlprive and the consecutive failure of the replacement server.

Be careful, given to the physical server's change, you must select another server for the FTP connection. Consult your private sql manager
by clicking on \"summary\" in the left menu to know your new physical server for the FTP.

This change has no impact at the level of the functioning of your databases.

Update(s):

Date: 2010-11-04 17:35:27 UTC
The last 2 servers were re-put online.

We are waiting so that we check if a problem persists before the closure of this intervention.

Date: 2010-11-02 14:02:51 UTC
The functions of the manager are available again.

Date: 2010-11-02 13:50:14 UTC
Practically, all of the servers were re-put online. There is still a familiar problem with two private servers which we will fix as soon as possible. If you still encounter further difficulties with your private server, you can send an email on tony@ovh.net indicating the name or the IP of your server in addition to a rapid description of the encountered problem.

NB: the functions of the manager will be available a few minutes later while updating the information concerning every service.


Date: 2010-11-02 13:35:32 UTC
90% of the private servers were re-put online. We will finish the remaining 10%.

Date: 2010-11-02 12:11:45 UTC
The 1st is functional. We launch the copies of other private sql.
We need to count between 45min to 1h for all of the sql to be up.

Date: 2010-11-02 12:09:59 UTC
The data were mounted on another server. We are dispatching the private servers on the other existing physical servers.

Date: 2010-11-02 12:08:38 UTC
This does not go well. We will try to mount the discs
on a server in production then copy the data on
different sql. The goal is to restart the service as soon
as possible. We will see after that the why and the wherefore
of the hard.

Date: 2010-11-02 12:05:06 UTC
The new server is ready. We will proceed to the replacement.

Date: 2010-11-02 08:50:16 UTC
The intervention time is bad. We did not have enough
hardware crashes in order to be able to prepare for the
modification procedures. We will improve this in the next days.

Date: 2010-11-02 07:43:00 UTC
The server was changed with a spare on Saturday, yet, the spare presents a default as well. We will probably have to replace the server again.

Date: 2010-11-02 07:41:29 UTC
The server is showing again instabilities of a hardware origin. An intervention is ongoing.

Date: 2010-11-01 16:26:08 UTC
There were two problematic zones that we have fixed.



Date: 2010-11-01 16:21:14 UTC
The problem has been fixed on Saturday. No more alerts.

We have several clients that escalated problems.
The concerned team was called back to check the
problem.
Posted Oct 30, 2010 - 23:14 UTC