C&CZ Problem Card

The fileserver we call bushel crashed for as yet unknown reasons on Friday evening. From then until the manual reboot, all its shares were down. All affected shares: /vol/acfiles /vol/aerochem /vol/aggrgtindroplets /vol/akolkmandata /vol/albert /vol/amsbackup /vol/amscommon /vol/archivespruijt /vol/avance600 /vol/beevee /vol/bioniccell /vol/bio-orgchem /vol/bko /vol/boltje /vol/ccz /vol/cczhelpdesk /vol/cczsecr /vol/celbio1 /vol/celbio2 /vol/celbio3 /vol/chemprac /vol/chemstaff /vol/coastoffon /vol/cognac /vol/communicatie /vol/cursusdossiers /vol/desda /vol/devneurob /vol/diafragma /vol/dis /vol/ecogen /vol/ehef1 /vol/ehef2 /vol/ehef3 /vol/ehef4 /vol/epsylon /vol/femtospin /vol/frequencycomb /vol/fsr /vol/gissig /vol/gmi /vol/goudsmit1 /vol/goudsmit4 /vol/goudsmitoldusers /vol/grafting /vol/hafnerlab01 /vol/hafnerlab02 /vol/hafnerlab03 /vol/heatgenes /vol/heatyield /vol/hfml-backup /vol/hfml-backup2 /vol/hfml-backup3 /vol/hfml-backup4 /vol/hfml-backup5 /vol/highres /vol/honours /vol/huckgroup /vol/icis /vol/ifl-d1 /vol/imappdir /vol/imappdocs /vol/imappsecr /vol/immbureau /vol/immstaff /vol/impuls /vol/introcie /vol/invbio /vol/invbio2 /vol/isptinspec /vol/jupyter /vol/kaartenbak /vol/kangoeroe /vol/khaj /vol/korevaarstudents /vol/kuijperslab01 /vol/linova500 /vol/linova800 /vol/liquids /vol/mbaudit1 /vol/mbaudit3 /vol/mbaudit4 /vol/mbonderwijs /vol/mbsl /vol/mlf90 /vol/mlfalgemeen /vol/mlfsec /vol/modprspm19 /vol/molbiol /vol/morph /vol/mpcoldmollab /vol/mwstudiereis /vol/neuroinf /vol/neuroinf2 /vol/nmr500data /vol/nmrliquid400 /vol/nmrliquid500 /vol/nmrsolid000 /vol/nmrsolid300 /vol/nmrsolid400 /vol/nmrsolid600 /vol/nmrsolid850 /vol/nmrsolid950 /vol/nmrspectra /vol/oii /vol/olcii-archief /vol/olympus /vol/pcsm-share /vol/pcsoftmattersecr /vol/ppimm /vol/pracnat /vol/ruversatest /vol/sbs /vol/secrmolbiol /vol/sigma /vol/sigmacies /vol/snn3 /vol/snn4 /vol/soheto /vol/solids /vol/spacdata3 /vol/spectra /vol/spibdossier /vol/spm /vol/spm30cobp /vol/spm30febp /vol/spm30fecobp /vol/spm30mkdata1 /vol/spm30mkprojects1 /vol/spm30procobp23 /vol/spmdata3 /vol/spmdata4 /vol/spmdata5 /vol/spmdata6 /vol/spmdata7 /vol/spmexfoliation /vol/spmmagstm /vol/spmnanolab /vol/spmstaff /vol/ssi /vol/staff-hfml /vol/stroom /vol/studiereis2013 /vol/sucudo-transfer /vol/tartarus /vol/tf2devices /vol/thalia /vol/ucm /vol/unl /vol/uscm-ssi /vol/uscm-ssi-archive /vol/vsc /vol/vsc1 /vol/vsc10 /vol/vsc11 /vol/vsc12 /vol/vsc13 /vol/vsc14 /vol/vsc15 /vol/vsc16 /vol/vsc2 /vol/vsc3 /vol/vsc4 /vol/vsc5 /vol/vsc6 /vol/vsc7 /vol/vsc8 /vol/vsc9 /vol/vscadmin /vol/wiskalg /vol/wiskunde

With the introduction of Ubuntu 24.04 by C&CZ, it turned out that the uids/gids of some users had to be changed because they were too small. This was immediately rolled out on servers, since those are always powered on, but needed a workaround on Ubuntu client PCs. Today it became clear that this workaround ignored new accounts, so first year students and new employees couldn’t use Ubuntu clients. This has been fixed now and all C&CZ managed Ubuntu client PCs in computer labs and the Library of Science have been updated.

Gitlab pages was unavailable due to a problem with the underlying S3 storage. It took a while to fix, due to confusing messages in the logfiles of the service. title: gitlab pages onbruikbaar door storing in rados gw

The backing store for gitlab-pages, accessed via the S3 protocol, went into failure mode for still unknown reasons. After restarting several servers of the storage cluster, the service became available again. update 20-08-2024 It happened again Today at 12:15, fixed quicky (within 20 min)

Recently we have received and confirmed issues with delivering e-mail to certain domains, so far: adelaide.edu.au applemusic.com arizona.edu benwhale.com biologists.com communications.ssrn.com editorialmanager.com email.arizona.edu flinders.edu.au herts.ac.uk hireright.com hpeprint.com inhousevtm.com insideapple.apple.com ioppublishing.org mail.coinbase.com math.arizona.edu medicalschemes.com mq.edu.au newcastle.edu.au nonzeroratio.com skao.int sussex.ac.uk sydney.edu.au telegram.com uct.ac.za unimelb.edu.au uon.edu.au uow.edu.au uws.edu.au vistaprint.com webofscience.com westernsydney.edu.au woodpartners.com woolcock.org.au The mechanism by which this fails is getting clearer, but we are still figuring out how to deal with this. What most of these domains have in common is that they are hosted by the same service provider (mimecast.com). It appears to be something with the negotiation failing before the mail can be sent, which was no problem before as mails took another route after delivery failure. ...

After a network configuration update, we are currently experiencing issues with the Science VPN connections, resulting in no traffic passing through. We are investigating the cause of this issue. As an alternative, we recommend using EduVPN from SURF.

We apologize for the inconvenience, but due to a software error, an (end date notification email)[https://cncz.science.ru.nl/howto/emailcodes/#login-3] was mistakenly sent to too many recipients. Please disregard and delete the email. If the email was intended for you, we will resend it next week. We are working on a fix to prevend this kind of error in the future.

Science LDAP services are all unavailable, our radius service depends on this, so this also doesn’t work. The TLS certificate has expired, after renewing the certificate and restarting the service it works again.

Due to a configuration error on the fileserver bushel, the NFS process did not run after a reboot. After correcting this error, the NFS service has been restarted.

After a software upgrade and reboot of the AR-114-9 modules, dhcp relay from the Picos network is broken. The cause is still not 100% clear, we will update this incident when we know more. We tried setting up dhcp servers within the picos network, but this didn’t solve the issue. We now suspect the picos switch itself, which we will try to restart in the morning of June 6th (between 7:30 and 8:30). This will affect all connections behind the picos switches. We hope the downtime will be less than 10 minutes. ...