CPK

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

June 2013

CPK#1045 BASS RU problem

The central BASS RU environment has been updated last weekend. Part of this upgrade was a change of the web address of the second logon screen, as announced on our BASS page. This morning it became clear that access to the second logon screen via the Port Forwarder didn’t work anymore. Therefore the UCI rolled back the change of the second logon screen. This means that AFTER LOGGING ON TO THE PROXY at https://admin.ru.nl/ BASS is available again via https://bassruap01.uci.ru.nl:8010/OA_HTML/AppsLocalLogin.jsp ...

May 2013

CPK#1021 OpenID server problem

During the renewal of the OpenID server a configuration error was made. When users reported problems logging in, we started searching for the origin of problem. When it was found, it could easily be corrected and the server could be restarted with the correct configuration.

CPK#1020 Homeserver bundle crashed

The fileserver crashed. After a reboot everything was back to normal.

April 2013

CPK#1018 Homeserver bundle failed reboot

The fileserver failed to reboot during the regular Monday morning shutdown schedule. It was possible to gain access to the system console only after having removed all power from the chassis. Snapshots were removed using the rescue reboot but rebooting the machine resulted in a faulty filesystem. We were able to boot the system after all filesystems had been checked offline. These actions resulted in a unusual long downtime.

CPK#1019 Fileserver stack crashed due to failed hard disk

Problem: Crash due to defective disk Solution: Deactivated disk using hot spare and reboot

CPK#1017 Homeserver bundle failed reboot

The fileserver failed the regular Monday morning reboot. Only after a rescue boot and a manual removal of all snapshots rebooting the machine worked.

CPK#1016 Disk server stack offline

Problem: Stack: Crash due to failing disk. Solution: Deactivated disk using hot spare

CPK#1015 Disk server pile offline

Pile did not shutdown properly during weekly reboot due to a kernel panic. Solution: Executed power-cycle of the system

March 2013

CPK#1014 Mail problems after supplying password to phishers

Again a Science user supplied his Science password to phishers. We notice that because Internet criminals use these passwords to get into the Science mail servers (horde webmail, smtp) in order to send spam. PLEASE: do not naively click on a link in an e-mail!

CPK#1012 Disk server pile offline

Was waiting for interactive input after reporting a warning (^d)