Cpk | C&CZ News

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.

Service Interruptions

1407: NFS problems under investigation

When we moved the gateways of our networks from the old location to the new firewalls, we have received some complaints about NFS filesystems having slowness, longer delays or unavailability. In general NFS should never be a requirement for a clusternode job if you can avoid it, because this I/O is always much slower than local I/O from /scratch. We are investigating how we can optimise the network to resolve this issue, but we are hard pressed to know the exact cause of the problem....

1415: Clusternode maintenance day - February 6th 2026

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)

Resolved Reports

1078: U: / home server bundle problems

From the moment of yesterday’s snapshots (13:00 hours), more and more processes were hung at the server. The first complaints arrived at C&CZ ca. 11:15 hours this morning. Therefore we decided ca. 11:35 to restart the server. The reboot resolved the problem. The number of snapshots will be reduced in order to try to prevent problems due to snapshots in the future.

1077: Printer pr-hg-00-002 did not print from Windows/Mac

Probably due to a too large printjob, the printer queue on the server (printto/printsmb/ooievaar) for the pr-hg-00-002 printer got stuck onWednesday morning. C&CZ was only informed of this problem at the end of Thursday. Friday morning this has been fixed by emptying the printqueue with old jobs.

1076: Print/phpMyAdmin server problem

The server didn’t react for unknown reasons. A reboot of the machine solved the problem.

1074: U:/ home server pile problem

The server had a problem with one partition. A reboot of the machine solved the problem.

1075: Linux login server lilo3 reboot due to NFS-problems

The Linux login server lilo3 didn’t have the homedirectories of some users. It took a reboot to fix this.

1073: File server heap problems

The fileserver failed to start after the Monday morning reboot, because of filesystem errors (LVmd2-7). Manually fixing the errors solved the problem and the machine started successfully.

1072: U: / home server pile and Linux login server lilo/stitch problems

The server had a high load and stopped servicing users, probably because of problems with the creation of new snapshots at 13:00 hours. A reboot solved the problem.

1069: Network interruptions in Huygens wing 5

On Monday evening, February 3rd between 19:00 - 24:00 (7:00 - 12:00 pm) maintanance will be carried out on the network devices in Huygens Wing 5. Therefore the wired and wireless networks will not be available at some moments at all locations in this Wing, on all floors.

1068: Again network interruptions in Huygens wing 2

The announced proceedings on Tuesday, January 21st on the network equipment unfortunately did not take place due to a sudden instability of the network in Wing 1 the same day. In order to prevent further instability issues in Wing 2, it was necessary to solve the problems in Wing 1 first. These problems have been identified and corrected. The network maintenance in Wing 2 will now take place Tuesday, January 28th between 19:00 and 24:00 ( 7:00 pm to 12:00 ) during which the wireless and cabled networks will be off line for some time....

1067: Network interruptions in Huygens wing 2

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.