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


 No service interruptions.


Resolved Reports


1413: Elabftw upgrade and move

The ElabFTW server will be upgraded and also moved to another host on Monday October 27th, this will be a little bit more involved than a normal version upgrade, and you can expect some downtime during the move and upgrade. Update: upgrading was done on the old server, moving to the new server ran into some unexpected issues, we will plan a new date for that. Update: move was done on Sunday November 2nd, some users report problems logging in, but that appears to be temporary due to elab running on a different ip address and machine. ...

1412: Physical server move

On Thursday 23rd we will move the host of the rstudio website and another server to another location. This will cause some downtime, starting from about 9 O’clock and it should be done within 1 hour.

1410: gitlab registry unavailable

The GitLab registry used by gitlab.science.ru.nl and gitlab.pep.cs.ru.nl is currently unavailable due to a disk failure in the storage backend. The faulty drive is being replaced, after which the registry should be available again.

1409: Miii server issues

Due to some cleanup changes, the miii server ended up without the proper firewall rules and account configuration scripts that it was supposed to get. We were able to fix the server eventually, but during the day, users were unable to work until it was fixed.

1408: Network reconfiguration vmhosts

With the changes in the networks, we are able to optimise some vlan configurations to utilise the high speed link, which was impossible before. The network reconfiguration may need a reboot of the server, but otherwise not too much downtime is expected. The reboot takes about 5-10 minutes if necessary. The list of vm’s affected (only those without redundant functionality are listed): vmhost05: mestrenova143 pagespep pep1 nolaivalkhof mestrenova150 fsecure pep2 pages licensevm1 goudsmit zaaivm stormvogel nolaigoffert desdapi vmhost06: ...

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. We are assuming the root cause might be that, now more traffic is passing through our firewalls, this degrades the performance in some way. ...

1405: ssh session hanging due to firewall config

A change in the firewall config had the uncalculated effect that ssh-sessions got blocked/dropped. The config has been reversed.

Updated Oct 22, 2025  ·  Miek Gieben · Created Sep 17, 2025

1406: Server "oliver" needs to be moved

We need to move a server to another location, during the move some of the services are unavailable, including licenses for: Cadence Labview Originlab Cst Maple Server ExelisIdl Mathematica Synopsys Genesys Matlab VirtualMachine GurobiTokenServer Mentorgraphics Xilinx Hdlworks Moe IntelCompiler New Everything should be completed by 10:00.

1404: printing via lp science blocked

Due to the gateway change the printing traffic followed a different route which ran into default blockages in the central firewall, after the problem was found a fix was implemented to allow this traffic to the printserver via the new route.

1403: websites and other services unavailable from everywhere they were supposed to be

After switching the gateway for one of our busiest vlans to our own firewalls, a lot of websites were only available from outside that vlan, it took a while to understand the issue and find a fix for it. We now have a temporary fix in place that should make the websites work again.