As already described in this past posting, we have recreated our LDAP server infrastructure and will now retire the old server. For the last 4 weeks we've been sniffing for LDAP queries that still use the old server and we've addressed each of those requests individually. Since we can't guarantee to detect each and every single network packet, now is your last chance to migrate to the new servers in case you haven't done so already. The old server will go offline on

Friday, March 16

Please let us know if you have any questions.

executive summary: you only need to read this if you run a service or tool that uses our LDAP server

A surprisingly large number of people at D-PHYS run services or use tools that connect to our LDAP server to obtain user information. If you are among those, this post is meant to inform you that our LDAP infrastructure is about to change and you need to take action in order to keep your service up and running. You can read about the details and technical background here. The situation right now is:

• The new servers are running and sync with the current master.
• We have started migrating services from the old server to the new ones.
• The old server will be turned off in 2018.
• You can now start to migrate your service / tool to the new LDAP infrastructure.
• In early 2018 we will start searching for clients that still use the old server and address them individually.

So if you're affected, please change your LDAP connection according to the documentation or get in touch if you have any questions.

Tomorrow,

Tuesday, January 29, starting at 07:15 am

there will be a short downtime of our LDAP server since we have to perform some maintenance work. You will not be able to log in or use our file services during this downtime. The expected duration is < 15 min however, so most of you won't even notice.

On Monday, August 2nd, starting at 18:00, we need to modify our LDAP user database to incorporate structural changes needed for a new service we're currently setting up. This will cause a downtime of about 1 h, probably even shorter, that will affect user logins, email and file server access. We will post an update when things are back to normal. Update, 18:30: Things are now back to normal. 🙂

We apologize in advance for any inconvenience this service interruption might cause.

On Wednesday, 7th of April 2010, starting at 6pm and lasting until approximately 9pm, there will be several maintenance downtimes for nearly all of our services due to several software upgrades and relocation of servers.

So if you're using one of our managed workstations or thin clients, or use data residing on group drives, please save all your work and preferably log out/disconnect before Wednesday, 6pm. And even if the services seem back after the first short downtime, don't expect to be able to work again from that point on since we will have several short but also some not so short service downtimes in a row.

Update, 20:30h: Most servers and workstations are back online. Not yet ready for usage are: fatboy, the IDL license server and the Condor master server. They will be back later tonight.

Update, 22:45h: fatboy is back online again. But two infrastructure servers (which haven't been touched by today's maintenance) seem to have hardware issues. Because of that the maintenance of the IDL license server and the Condor master server have been postponed until further notice.

A security-update on one of our clusters failed unexpectedly and caused a downtime of our authentication server and printer server which needed manual intervention. All services should be back again by now. We apologize for the inconvenience caused by this. Update 18:00: The thin clients work again, too.

There will be a short maintenance downtime of our authentication server this evening at 7pm. This means that you won't be able to log in to any managed D-PHYS workstation or D-PHYS service for about 5 minutes. Update 19:01: Maintenance successfully over.
(more…)

On Tuesday, the 2nd of December 2008, beginning at 6pm, we will migrate the services on our current authentication server to our high-availability cluster. During the migration you will not be able to login on any of our managed workstations, home and group drives or web services. Existing login sessions on workstations should survive the downtime, but it is usually better if you log out before migration. Additionally, *.dhcp.phys.ethz.ch dynamic hostnames will not work either.

Update, 22:30: Migration done. Everything should be back to normal.

Update, Wed Dec 03, 09:30: We found and corrected a problem with the web browser proxy.pac.