C&CZ Problem Card

medewerkers, studenten Due to a management operation (planned around this time), the DIY website was unusable. Since the time was very early, it’s expected nobody was inconvenienced by this temporary unavailability.

medewerkers, studenten A configuration change unwantedly made the smtp service unusable. When we noticed this, it was repaired immediately.

medewerkers, studenten A configuration change had as unwanted effect the disappearance of all very long mail aliases. When this was reported next morning, it was repaired immediately.

medewerkers, studenten Due to a simple management command the switch (as-ak008-04) crasht and had to be reset manually. The switch sits between the network and servers for gitlab+mattermost, licenses and the database for DHZ(diy).

medewerkers, studenten Services will not be available for a while because of a GitLab and Mattermost upgrade.

The ISC announced: For security reasons, the certificate of the wifi server will be replaced in the evening of Friday, July 10. This has consequences for connecting your mobile device to Eduroam when you’re on campus: • If you get the message that you have to accept the new certificate to use eduroam, choose ‘yes’. You can then use eduroam again; • If you don’t get this message and can’t connect to Eduroam, choose the wireless network ’eduroam-config’. Accept the terms and conditions. Follow the instructions to reinstall Eduroam. ...

Several parts have been replaced. We assume the problem, that occurred twice, is now resolved. For dual-boot pcs, the boot menu was served by an alternative method during the repair.

Affected : Users of Science VPN and Eduroam based on science account The certificate of the LDAP servers has been replaced this morning, this has also changed the certificate chain. The radius server uses LDAP as authentication backend and in the radius configuration the certificate chain had to be changed too. This was initially overlooked. Radius is the authentication mechanism used by all VPN servers and Eduroam

The server went down in the same way as the previous time (3rd of June 2020). The cause is most likely a system board problem. This part will be replaced Tomorrow by a support engineer.

by a website) and various websites. The server couldn’t be reached after the scheduled weekly reboot, not even on its management interface. Because also C&CZ employees work from home and the interruption didn’t get enough urgency fast enough, the interruption lasted too long, apologies for that. The support partner has been contacted and the server has been updated, but the origin of the problem is still unclear. We will also look at making these services more redundant or more easily movable to a different server. ...