Date & time of incident:
Tuesday, April 16, 2013 - 15:00
Post date:
Tuesday, April 16, 2013 - 15:01
Incident Description:
The EOSALICE headnode got rebooted accidentally. This week's planned software update will be anticipated in order to only restart the EOS namespace once.
Service Element Affected:
EOS Service
Specific Service detail:
EOSALICE
Impact:
Service is unavailable
Status:
Resolved
Resolution date:
Tue, Apr 16, 16:05
Posted by:
IT-DSS
Unit responsible for resolution:
IT Department
Updates
Namespace has been switched
Namespace has been switched to a standby box, is still booting. We expect the service to be available again in the next few minutes.