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_green
icon_green
 

FS#4100 — FS#8037 — 46.105.112.0/24

Attached to Project— Network
Incident
the whole network
CLOSED
100%
The update is not done properly.
http://status.ovh.net/?do=details&id=4091

Install has failed. Return code 0x40930039 (aborting due to failed upgrade).
Please identify the cause of the failure, and try 'install all' again.

Date:  Monday, 11 February 2013, 01:34AM
Reason for closing:  Done
Comment by OVH - Monday, 11 February 2013, 01:06AM

We have reversed the role of the VPC
to switch primary to secondary and secondary to primary.
This has caused a cutoff in the service.

We believe that this allows us to decrease
the breakdown time due to to the FEX update.


Comment by OVH - Monday, 11 February 2013, 01:08AM

We are retrying the VPC action


Comment by OVH - Monday, 11 February 2013, 01:11AM

Okay, we have tried to do our best but it got worse.
We will do the old action which will generate
a 15 minutes breakdown starting from now.

the A is UP and is updating the FEX all from the beginning.


Comment by OVH - Monday, 11 February 2013, 01:11AM

Still 3 FEX are down.


Comment by OVH - Monday, 11 February 2013, 01:12AM

2 more FEX


Comment by OVH - Monday, 11 February 2013, 01:12AM

1 more


Comment by OVH - Monday, 11 February 2013, 01:12AM

02/10/2013 23:44:49.312663: Module register received
02/10/2013 23:44:49.313470: Image Version Mismatch
02/10/2013 23:44:49.313679: Registration response sent
02/10/2013 23:44:49.313858: Requesting satellite to download image
02/10/2013 23:50:18.23809: Image preload successful.
02/10/2013 23:50:19.149814: Deleting route to FEX
02/10/2013 23:50:19.156902: Module disconnected
02/10/2013 23:50:19.157457: Module Offline
02/10/2013 23:50:19.160406: Deleting route to FEX
02/10/2013 23:50:19.169426: Module disconnected
02/10/2013 23:50:19.170815: Offlining Module
02/10/2013 23:50:19.187956: Deleting route to FEX
02/10/2013 23:50:19.197621: Module disconnected
02/10/2013 23:50:19.199081: Offlining Module
02/10/2013 23:54:49.345669: Module timed out


Comment by OVH - Monday, 11 February 2013, 01:13AM

The FEX 107 is probably dead. We are rebooting it
in hard, meanwhile we are preparing the spare.


Comment by OVH - Monday, 11 February 2013, 01:14AM

We are replacing the FEX with a spare.


Comment by OVH - Monday, 11 February 2013, 01:16AM

Thereafter the replacement, the uplinks
are again up and the FEX is updated.
The old one is therefore dead. we are counting
8 minutes of software update and 3 minutes extra to boot.


Comment by OVH - Monday, 11 February 2013, 01:20AM

We have replaced the spare with another one
and remains the same, we are unable to remount the service.

We have cut the A upkink, the same
we have cut the B uplink, it's better,
the FEX is being detected by the system.

We are reconnecting to all EG servers which are on 107
on the new spare with only the B uplink. We are resetting the service
then we'll check why the A uplink is causing this problem.


Comment by OVH - Monday, 11 February 2013, 01:21AM

All servers are UP on the B uplink.

we are going to connect the A uplink


Comment by OVH - Monday, 11 February 2013, 01:22AM

Its UP on A. we are cutting the B uplink.


Comment by OVH - Monday, 11 February 2013, 01:34AM

All OK. the new spare is compatible with the A and B.

We believe that the first spare had a malfunction of
the update procedure then was unable to start it. we'll check tomorrow.

All UP.

We do apologize for the breakdown.