1253: NFS service interruption
Due to a configuration error, the NFS service on file server ‘peck’ refused to start. After fixing the error, the NFS service started up correctly.
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.
Due to a configuration error, the NFS service on file server ‘peck’ refused to start. After fixing the error, the NFS service started up correctly.
At the weekly reboot of vmhost ‘oscar’, it did not boot properly. The listed virtual machines are not running at the moment. We are working on it. Update: most probably, the problems where caused by full snapshots. After removal of the snapshots, the system booted properly.
Due to an administrative error the mailboxen of a few hundreds of users became inaccessible. Mail couldn’t be read from or delivered to these mailboxes until this had been repaired. In this period the mailclient of 19 users tried to read the mailbox and thus possibly reported an error.
A new receiving mailserver was introduced July 1. This server has the most recent version of Ubuntu and other software and settings that are more conforming to the directives (in Dutch). After the introduction, problems appeared with receiving mail from Microsoft Office 365 Exchange Online (mail.protection.outlook.com). An even bigger problem was that some accepted mails were not forwarded, but bounced to the sender. Because that problem couldn’t be fixed immediately, the newly introduced server has been shut down on July 2. At the end of August, C&CZ will test the probable solution. If the test succeeds, the new incoming server will be put into production. ...
Due to a faulty RU core network device, several service couldn’t be reached. This device is in a redundant setup. The ISC network department will start an investigation what exactly happened and how to prevent nuisance in the future.
Yesterday afternoon a DNS error with science.ru.nl (due to the introduction of the secure DNSSEC) made science.ru.nl disappear from the internet for many users, when viewed from outside campus. In the evening this error has been corrected. Because of the caching of DNS responses, the last problems should disappear tonight. In the meantime one can use workarounds like rebooting the home router and/or pc, using a different network (mobile provider) or using rainloop.science.ru.nl instead of roundcube.science.ru.nl for webmail access. ...
Because a web application used too much memory, all websites of this webserver had problems. After restarting the webserver, all websites could be reached again. We will make sure that web applications get memory limits, which will prevent this problem in the future.
Due to a faulty network switch, approx 40 network connections in Huygens wing 4 were temporarily unavailable. The switch has been replaced.
This morning, the Matlab license server stopped, because yesterday an error had been made in the upgrade to version R2019a. After the error had been corrected, the license server was restarted, which resolved the problem.
The poster printer has to be repaired, but we can’t easily fix it. We hope to have the printer operational again in the near future. In the meantime you might use the RU copyshop.