CPK messages are initially sent to the CPK mailing list, you can (un)subscribe via this link. You can also follow the service interruption messages via RSS using the link in the title under the RSS icon. If the CPK takes more time to resolve, any updates are published on this website.
For RU wide service interruption see meldingen.ru.nl.
In Huygens wing 2 a network switchmodule crashed twice. About 30 pc’s in the Study Area lost their connection to the network for some time. The switchmodule will be replaced on 2016-01-21 at 07:30 am.
Affected sites: aerochem akn aqua bb2syllabus bgard boekingen boekwur bomengids cac cafe celbi dossiers est2b exo filosofie fnwi hfml iconic ifl irmacrash itp2011 iwwrbook kanboard kndv labservant leonardo math mbfys mbp nieuwescheikunde nlt notebooks olympus pilab piwik printeger projecten puff pz qpl quantumcs refbase resourceanalysis rrl scheiolymp setup siam sigma-lustrum sito smartech4health studiereis sws tango taskboard tk toernooi tredd trooster ubuntumirror vsc w4kangoeroe wortel
The virtual hosts fret, wolf and vos received updates to libvirt packages, causing the network interfaces of the virtual machines running on them to fail. Solved after reboot (fret) or restart of the libvirt daemons and the virtual machines. Affected virtual machines: bfacdc03 bfacdc04 drukker est2 gitlab3 ms2 nwidc01 redmine2 smtp1 smtp2 ts2
The server lilo3/4 stalled at shutdown during the monday morning reboot. Solution: power cycle. Cause currently unknown.
The server comas1 did not start due to some possible timing problems between the raid array and OS. Solution: skipping the mount of /vd0 and /vd1 during boot (key S), mounts fixed manually later on followed by exportfs -uaf; exportfs -raf. Machine failed for unknown reason at boot. Solved by rebooting.
Yesterday at ca. 15:52 a SURFnet core router crashed, taking down the RU Internet connection. At 16:09 the connection was restored. This was reported yesterday on a temporary SURFnet service interruptions page and on the ISC/CIM service interruptions page. Details can be found on the SURFnet Network Tickets mailing list.
After a reboot of the print server (and waiting ca. 10 minutes) printers could be attached again.
As a result of a short network service interruption last night, there were some problems with obtaining ip addresses on the wireless network eduroam.
System crashed possibly caused by an erroneous harddisk causing all CPUs to lockup.