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.
Every half year we do clusternode maintenance, with at least a package ugprade and a reboot, but sometimes other maintenance can happen, such as changes in filesystems or network configurations. The upcoming date for this maintenance is February 6th, 2026 (Friday)
On Tuesday evening January 21 between 7:00 pm and 12:00 pm maintanance will be carried out on the network devices in Huygens wing 2. Therefore the wired and wireless networks will not be available at some moments at all locations in wing 2 and corridors between wings 2 and 4, on all floors.
On Monday evening January 13 between 7:00 pm and 12:00 pm maintanance will be carried out on the network devices in Huygens wing 1. Therefore the wired and wireless networks will not be available at some moments in many locations in wing 1 and corridors between wings 1 and 3, on all floors.
Due to an error by an ISC network administrator, all internal and external RU network traffic was blocked for a short period.
The replacement of the old home server “bundle” has been postponed and will now guaranteed take place on Monday morning December 23. Because the data have been synchronized with the new server, there will not be much downtime. The new server should be very dependable: hardware RAID-6, double processors and power supplies and a 5-year support contract from the supplier. The performance has improved, e.g. by using hardware RAID with a 1 GB write cache with battery backup. ...
In the course of these two days, above network shares will be moved to new servers. During the move action, a share will not be available. If you encounter any problems connecting to a network share using Windows, always connect using the “share-name minus srv” naming scheme: \\sharenaam-srv.science.ru.nl\sharenaam. See also Diskruimte#Naming. Affected network shares: acfiles2 botany botany-general carta comsol digicd encapson encapson2 exoarchief felix gi2 gi3 hfml-45t hfml-data hfml-engineering ifl iris mailmanincludes mbaudit1 mbaudit2 mbbioel mbcns mbcortex mbdata mbread mbwrite mestrelab mi2 mi3 milkun4 milkun4rw molchem molchem2 molphtec mol-secr multimedia neuropi ns3 nwi-backup onlyme owc pcb planthgl plantkunde-hgl sdisk/software share snn sofie spmdata1 tdisk/cursus tece teceleiding temp tracegastemp wallpaper xpcursus xpsoftware ...
Tuesday night December 17 19:00-24:00 hours, maintenance work will be done affecting the data network in Huygens wing 1. The wired and wireless network will suffer service interruptions a few times during that period. The main inconvenience will be on the ground floor.
C&CZ changed the DHCP-configuration of the KM MFP’s, because KM had told us all KM’s had an identical configuration after the upgrade of the night of December 4. Soon thereafter the KM’s outside of the Huygens building showed problems. After changing the DHCP-configuration back to the previous version and restarting the MFP’s, the problem was resolved. The firmware upgrade of these machines still has to take place.
Wednesday night, the firmware of the Konica Minolta multifunctionals will be upgraded. This should resolve existing problems, like the not waking up from sleep mode. Please report all remaining problems, for MFP-hardware and paper to KM via phone: 55955 option 4.
Tuesday morning around half past nine, there was a short power dip for RU/UMCN, probably due to a switch error at Liander. This power dip, that is not listed on the power interruption website, made all systems restart that were not on UPS power. Because only the network switches in Huygens wing 1 and 7 are on UPS power, a lot of users lost their connection to the network, including wireless and IP-telephony, for about 20 minutes. Apparatus that restarted faster than the network, might have needed an extra restart to restore the connection to the network. ...
The ISC let us know that after the installation of patches installed in BASS during the weekend of December 1, the possibility to use a recent version of Java (version 7) had erroneously disappeared. As of February 11, 2014 this issue has been resolved. The function in BASS to work with all versions of Java SE (JRE) on the client (PC) has been reactivated. Furthermore all JAR-files in BASS have received a security certificate (they have been signed), with which it possible for BASS to work with the latest Java SE versions (Java SE 7.51 en hoger). BASS users who work with Forms, will see pop-up windows asking “Do you want to run this application?”. Of this a description has been made on the RU Intranet. ...