Reports 1-1 of 1 Clear search Modify search
Computers Network (Network)
dibiase - 16:37 Thursday 17 June 2021 (52180) Print this report
Failure of some Virtul Machine hosted on the same HW Enclosure

Reboot needed to some Virtual Machines hosted in Chassis8 due to Failure. Please restart services on those machines.

Virtual machine envolved are:

  • ctrl6
  • ctrl22
  • farmn1
  • farmn13
  • ctrl12
  • farmn2
  • farmn5
  • farmn7
  • olserver111
  • olserver121
  • olserver130
  • stol04
  • mysql2.ego-gw.it
  • olserver116
  • olserver139
  • olserver140
  • olserver142
  • datagw
  • olserver132 - Mysql
  • dbserver01
  • igwacc-ego.virgo-gw.eu
  • ctrl16
  • farmn10
  • farmn14
  • farmn15
  • seiscomphost
  • rdserver2
  • cvmfs0
  • cvmfsmgr
  • pub14 
  • swtest3
  • condorcl-test
  • olsvn
  • seevogh01
  • submit-test
  • w6
  • dataldr
  • cvmfsclient
  • swtest6
  • olnode1-test
  • olnode2-test
  • olnode3-test
  • olnode4-test
  • lscgw
  • cvmfs1
  • swtest5
  • win-vtf
  • vCenter VMware

 

 

Comments to this report:
berni, carbognani - 21:42 Thursday 17 June 2021 (52183) Print this report

The python processes running on the Virtual Machine involved in the failure did not restart, in particular:

- olserver130: SusDAQBridge, SatServer, PduServer;

- olserver137: DMSserver.

We spent about two hours to understand that the processes were complaining about the leap-second file;  indeed inside /virgoData/LeapSeconds there was not a leap-seconds.list but only .old or _old files.

The problem was solved copyng the leap-seconds.list_old (the most recent one) into leap-seconds.list.

 

At around 16:46  UTC everything was restarted and back normal.

Search Help
×

Warning

×