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)[/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. ...

Due to a configuration error the licenseserver for several of our licenses did not start automatically. Previously the server did autostart, however the cause of the configuration change is unknown. The configuration of the license server has been fixed.

Due to some unexpected reaction to a config change, the licenseserver for several of our licenses was misconfigured for about 40minutes. The change was reverted, but it took long enough for users to run into license problems.

Even though we closed CPK #1359, the user’s shares are not all restored. We have recovered the data from cephfs to temporary storage that is not accessible to users, it will take a bit more time to find new permanent locations for this data. The storage will not be cluster based anymore, but single server ZFS with snapshots.

Some of our network shares were temporarily unavailable earlier due to a configuration error. The issue has been resolved and all shares should be accessible now. We want to assure you that the configuration error that occurred did not impact the integrity or security of the data stored on the file server. We apologize for any inconvenience this may have caused. In the meantime, we’re working on making information about network shares readily available on DIY for your reference.