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.

 

Service Interruptions


1359: Ceph filesystem failure

Ceph filesystem failure. Services required for the CephFS filesytem cannot start. Failure of these services wil cause failure to access files on Ceph. We are in contact with our support party 42on to remedy the problem. Duration is currently unknown. Update 2024-01-22 We’re working with 42on on the issue and have a meeting scheduled for 17:00 today. Update 2024-01-23 An initial dentry_recover was successful and according to 42on the Ceph journals are OK....

January 19, 2024 · updated April 1, 2024

Resolved Reports


1362: Sieve difference(s) current mailbox server

After migrating to a new mailbox server on Sunday, March 31, we noticed different behaviour in the processing of mailbox filters (by the Sieve software). Firstly, the ‘include’ of global spam+virus filtering rules had a side-effect which has been fixed using a newer version of the software. Secondly, the default behaviour of the ‘fileinto’ statement underwent a change: previously, it featured an implicit ‘stop’ statement, but now it requires an explicit ‘stop’ statement after the ‘fileinto’ to achieve the same effect....

April 5, 2024 · updated April 5, 2024 ·  Erik

1361: homeserver home1 nfs problem

home1 had a problem with the nfs server after the reboot. Another reboot fixed it.

April 1, 2024 · updated April 1, 2024 ·  Simon

1360: mailserver will be replaced Easter weekend

In Easter Weekend (March 30th 2024) the new mailserver will replace the old one. The final switch will take a short while, during which mail clients (eg Thunderbird, mail on your phone, etc.) will not be able to connect to the science mailserver. (This is a week later than announced, due to some issues that need to be resolved before final migration) Central mail services (Microsoft @ru.nl) are independent of our mailserver and thus will not be affected at all....

March 22, 2024 · updated April 1, 2024 ·  Simon

1358: GitLab TLS Issue

On December 10, 2023 the main GitLab TLS certificate expired. A new certificate was generated, but it lacked a proper certificate chain. Browsers disregard that chain, but other GitLab components do care, which meant that the registry and the runners were unable to connect to GitLab. On Monday the 11th we renewed all certificates using Let’s Encrypt. Let’s Encrypt will also auto-renew these.

December 11, 2023 · updated April 1, 2024

1357: jitsi videoconferencing unavailable

Jitsi (or actually the internal prosody service) had an old certificate, causing it to refuse startup after the normal reboot. The expired certificate was replaced and after a restart of the prosody service it works again.

December 6, 2023 · updated April 1, 2024 ·  Simon

1356: Network problems after maintenance on the RU core router

After maintenance on the central routers, our servers on the 25Gbit network couldn’t send traffic to the internet. The cause or nature of the problem appears to be in the central RU routing. By resetting the interface to our network, RU Connectivity can fix this, when it occurs again. RU Connectivity contacted their maintenance provider to investigate this problem. Final solution: After a few failed attempts, it was possible to define a static route in the central routers to our networks....

December 4, 2023 · updated April 1, 2024 ·  Simon

1355: Jupyterhub restarted

Some users were unable to login, the server had become unstable, which made a reboot necessary. Unfortunately, the jupyterhub service still needs a manual startup, which didn’t happen until 13:24 hours. The service is now working again. We are working to fix the reboot problem.

November 17, 2023 · updated April 1, 2024 ·  Simon

1354: DHCP server down due to config error

A typo that could propagate to shutdown the DHCP server had the effect that some network devices did not get an IP address when they were switched on and that others, whose address lease expired in this period, lost their IP address and thus their access to the network.. We’ll improve the process to prevent a typo from bringing down the DHCP server in the future.

November 9, 2023 · updated April 1, 2024 ·  Peter

1353: Jupyterhub22 refused to start this morning

After a scheduled reboot of the machine running jupyterhub, jupyter failed to start properly. The service started after invoking a manual start command. The measures taken to resolve this recurring problem have not proven to be sufficient.

November 8, 2023 · updated April 1, 2024 ·  Bram