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

FS#3553 — FS#7495 — vCenter Access

Attached to Project— Dedicated Cloud
Incident
Backend / Core
CLOSED
100%
Our monitoring systems spotted accesses to vCenter as unavailable.

We're working to restore these accesses.


Date:  Friday, 19 October 2012, 01:52AM
Reason for closing:  Done
Comment by OVH - Thursday, 18 October 2012, 16:27PM

Switches crash managing vCenter infrastructure.

pcc-40-n5# 2012 Oct 18 15:51:06 pcc-40-n5 %SYSMGR-2-SERVICE_CRASHED: Service "fwm" (PID 3171) hasn't caught signal 6 (core will be saved).

pcc-40-n5#
Broadcast message from root (console) (Thu Oct 18 15:51:19 2012):

The system is going down for reboot NOW!


Comment by OVH - Friday, 19 October 2012, 01:47AM

95% of vCenter are online now. The rest are being fixed.


Comment by OVH - Friday, 19 October 2012, 01:50AM

All is UP regarding vCenter access. There is vCenter which has not rebooted.
A diagnosis is processing.

[2012-10-18 17:55:46.684 02120 info 'App'] [Vpxd::ServerApp::Init:1004] Calling: VpxdInvtVm::Init3()
[2012-10-18 17:55:46.684 02120 warning 'VpxProfiler'] ServerApp::Init took 3110 ms
[2012-10-18 17:55:46.684 02120 error 'App'] [VpxdMain] Failed to initialize: vim.fault.MissingNetworkIpConfig
[2012-10-18 17:55:46.684 02120 error 'App'] Failed to intialize VMware VirtualCenter. Shutting down...
[2012-10-18 17:56:43.773 02120 info 'App'] Forcing shutdown of VMware VirtualCenter now

Remaining vShield Manager are booting.


Comment by OVH - Friday, 19 October 2012, 01:52AM

The vCenter had a vApp in a non consistent state.

We have fixed the problem directly in the SQL data base server.

All is performing now.