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

1087: Eduroam problem

Some Eduroam users didn’t get an IP number, because one of the IP ranges had no free leases. This ranges contained all @science.ru.nl users. The ISC networking department first decreased the lease time. Now they also make this range free for use by @science.ru.nl users. This will prevent the problem from occuring again soon.

1085: And again Print/phpMyAdmin server problem

Again a reboot of the machine was necessary to restore the functionality. As a patch we will reboot this server each night.

1086: U-number authentication problem Eduroam

The new RU IdM system erroneously rewrote the RU password hash when data about a person changed. This primariliy affected employees of FNWI, because for this group the Science email address had been incorporated in IdM. This will make it possible to use the Science address as an external mail address when resetting RU passwords. When the problem was recognized, it was fixed swiftly by restoring the RU password hashes from backup....

1084: Peage MFP Huygens building in maintenance April 28/29/30

April 28/29/30, the Peage MFP and the Peage POS near the restaurant in the Huygens building cannot be used. The ISC will then investigate whether Peage can also be made available for employees instead of only for students. April 28, the MFP will be moved to the test location, April 30 it will be moved back.

1093: Poster printer "kamerbreed" broken

The printer has to be repaired. Spare parts have been ordered. We hope to have the printer operational again mid-May.

1083: After replacement still Print/phpMyAdmin server problem

Although the hardware of the server was replaced, the server didn’t react for unknown reasons. A reboot of the machine solved the problem. We will think about ways to tackle this problem.

1082: Print/phpMyAdmin server replacement Thursday April 17 08:30-09:20

Because of the recent problems with this server, we are going to replace the server, in order to prevent further service interruptions.

1081: U:/ home server pile problem

The server had a problem with one partition, which had started during the creation of new snapshots. We waited with the reboot untill after working hours. A reboot of the machine solved the problem. To prevent these problems in the future, we will no longer make local snapshots of homeservers, but of course the daily backups of the homeservers by the backup server will be continued.

1080: And yet again Print/phpMyAdmin server problem

Just like four days ago, the server didn’t react for unknown reasons. A reboot of the machine solved the problem. We plan to replace the server next Thursday 08:30-09:00 hours, in order to prevent further service interruptions.

1079: Again Print/phpMyAdmin server problem

Just like two weeks ago, the server didn’t react for unknown reasons. A reboot of the machine solved the problem. Together with the supplier we will try to find out what to replace to prevent this in the future.