Initial CPK messages are sent to the CPK mailing list, you can (un)subscribe via this link. You can also follow the disruption messages via RSS using the link in the title under the RSS icon. If the CPK takes longer to resolve any updates are published on the website.

 

Service Interruptions


1344: Increased chance of SPAM/phishing mails in Science mailbox

The RU contract with the anti-SPAM/anti-phishing service Proofpoint expired September 21, 2023, which means that ‘Proofpoint End User Digest’ mails are not sent anymore after that date. C&CZ is migrating Science mailboxes to the anti-SPAM/anti-phishing service of Microsoft Exchange Online Protection. There is an increased chance of receiving SPAM/phishing mails in the Science mailbox during this migration period. P.S. the RU central mailboxes (with addresses ending in @ru.nl) have already been migrated to Microsoft Exchange Online Protection....

September 14, 2023 · updated February 28, 2024 ·  Erik

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 March 15, 2024

Resolved Reports


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 February 28, 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 February 28, 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 February 28, 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 February 28, 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 February 28, 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 February 28, 2024 ·  Bram

1352: DNS broken for z.science.ru.nl

Due to a misconfiguration of the DNS in the z.science.ru.nl zone, all shares were not available during the outage. Extra tests are added to prevent a future occurrence.

October 23, 2023 · updated February 28, 2024

1351: All Science services down 15 minutes Thursday Oct 19 07:00-07:15 due to router reboot

The router for most Science services urgently needs a reboot. This has been scheduled for early morning. In the unlikely case that this reboot fails, ILS Connectivity is on campus to fix it.

October 18, 2023 · updated February 28, 2024 ·  Peter

1350: Mailman not accepting messages

In preparation of the migration to Microsoft Exchange Online Protection (MS EOP), we added another mail exchange server (mx5) to be addressed directly by MS EOP. However, having had mx4 in production for some time, we forgot to test mx5 in conjunction with our mailman server (zaaivm). This could result in a bounced mail ’not accepting messages’ for FNWI users (employees and students) using @ru.nl addresses. Meanwhile, mx5 has been made known to zaaivm thus resolving this issue....

October 2, 2023 · updated February 28, 2024 ·  Erik