Cpk | C&CZ News

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

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

1415: Clusternode maintenance day - February 6th 2026

Every half year we do clusternode maintenance, with at least a package ugprade and a reboot, but sometimes other maintenance can happen, such as changes in filesystems or network configurations. The upcoming date for this maintenance is February 6th, 2026 (Friday)

1417: Network changes websites

To make the network less complicated and more easily manageable, we need to make vlans for the subnets 131.174.8.0/24 and 131.174.9.0/24, this will involve some servers getting a new ip address. This affects firewall rules as well. We must coordinate this with ILS networking and the changes will cause disruptions between a few minutes up to a quarter of an hour. List of sites: alice.science.ru.nl alicecontrol.science.ru.nl coursetimetable.science.ru.nl dmarcreport.science.ru.nl edutools.science.ru.nl eduview.science.ru.nl...

Resolved Reports

1168: Gitlab upgrade

Because of an upgrade of gitlab to version 8.5.1, the GitLab service will be offline for a while.

1167: Virtual servers problem

Because of automated updates, Several virtual host had become unreachable. Server vos: gitlab3, bfacdc04, smtp2, redmine2 Server wolf: smtp1, bfacdc03, est2 Rebooted vos and wolf.

1166: miii server problem

For unknown reasons, the miii mail server was unavailable. Rebooted.

1165: IMAP mail server problem

For unknown reasons, the IMAP mail server was unavailable. The service cyrus-imapd was not correctly started. Starting this service service cyrus-imapd start solved the problem.

1164: IMAP mail server problem

For unknown reasons, the IMAP mail server was unavailable. Mail services were halted after some time because of logging activity. As a temporary workaround logging is now performed using UDP instead of TCP.

1163: Fileserver problems

The Ubuntu 14.04 fileservers “flock” and “muckle” had problems a few times. After we reverted to the previous kernel version, the service seems to be stable again.

1162: Matlab license server crashed

Last night the Matlab license server crashed, because the number of open file handles reached the maximum configured, because a user started a lot of Matlab processes. Because we do not yet monitor this properly and it was not reported to us, we could only repair it this morning. We increased the number of file handles by a factor of four. We assume that this will be sufficient to wait till the reboot of next Monday, when it will again be enlarged, this time by a factor of sixteen....

1161: Server lilo4 Monday morning reboot slowed

The server lilo4 stalled at shutdown during the monday morning reboot. Solution: it continued its reboot after server wielewaal became available.

1160: Webserver down: tftp & egw

Quite a number of websites of ICIS were not available amongst which was eGroupWare. Furthermore, the boot process of workstations was impaired (because of the missing tftp). A reboot of the server seems to be sufficient to solve the issue. Affected websites: blackgem brainhealth croatia14 croatia15 cs eduspec eduspecorg egw ethergids fbkr kickstart mhealth oni snn

1159: No free IP numbers in Vlan136

The DHCP server didn’t have free leases on Vlan136, so new devices on Vlan136 didn’t get an IP address, so didn’t have a working network connection. After we freed some unused numbers for PCs with a fixed address, we were able to drastically enlarge the number of leases on Vlan136.