CPK

rss feed

Service interruptions

A CPK is C&CZ’s way of reporting a problem or service interruption. Follow the mailing list or RSS feed, and check the service interruptions page for live status updates.

A CPK is how C&CZ reports a problem or service interruption. We publish one when something goes wrong, when we need to do planned maintenance, or when we want to let you know about something that affects the services we run.

Note

What’s a CPK? CPK is short for the Dutch C&CZ Probleem Kaart — C&CZ problem card. The name is simply how we’ve always done it, and it has stuck with us ever since.

How to follow CPK messages

CPK messages are first sent to the CPK mailing list — you can (un)subscribe there. You can also follow the service interruption messages via RSS.

When a CPK takes longer to resolve, we publish updates on the service interruptions page.

University-wide interruptions

For Radboud University-wide service interruptions, see meldingen.ru.nl.

 No service interruptions.


Resolved

April 2014

CPK#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.

Updated Oct 8, 2026

CPK#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.

Updated Oct 8, 2026

CPK#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.

Updated Oct 8, 2026

March 2014

CPK#1076 Print/phpMyAdmin server problem

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

Updated Oct 8, 2026

CPK#1074 U:/ home server pile problem

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

Updated Oct 8, 2026

CPK#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.

Updated Oct 8, 2026

CPK#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.

Updated Oct 8, 2026

CPK#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.

Updated Oct 8, 2026

February 2014

CPK#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.

Updated Oct 8, 2026

January 2014

CPK#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. This will affect all floors in Wing 2 and rooms along the corridors between wings 2 and 4 (all floors).

Updated Oct 8, 2026