Header Search Widget
IRIS

Instructional & Research Information Systems

LDAP

LDAP (Lightweight Directory Access Protocol) service

filesystem problem in LDAP server may have caused temporary authentication failures

by

One of the LDAP servers in our pair became unresponsive due to a filesystem problem. Some services (such as Jabber) had authentication problems during this time. The system is back online now after running fsck.

The current LDAP servers are old legacy systems slated to be replaced in the very near future. The configuration of these servers and the services that rely on it is non-optimal which results in problems with authentication to some (but not all) services that rely on LDAP.

The new LDAP system is in its final testing phases now and will completely replace the aging infrastructure we have now.

The problem with the system was detected by IT staff with one of our monitoring systems which alerted us. We are not aware of any impact to the community and have received no reports from anyone. If you experienced any authentication problems between 1-2am then please let us know by writing to help@eecs.berkeley.edu

Resolved as of 2013-09-07 01:57:00

LDAP & Jabber outage this morning, May 15, 2013

by

The department’s primary LDAP server ldap.eecs stopped responding early this morning around 12:30am. This affected a few other services which rely on ldap.eecs; we had reports of problems accessing Repo, and jabber.eecs stopped accepting connections at some point.

ldap.eecs was restarted at 7:00am and this would have restored most affected services. However, the jabber server seemed to be hung and had to be restarted; this was not noticed until around 10:30am.

Our ldap servers are aging and there is a current project underway to upgrade them to more modern hardware and software. An announcement about the scope of this project will be made in the coming weeks.

We are also planning to implement better monitoring of our jabber server so that future outages will be detected much more quickly.

Resolved as of 2013-05-15 07:00:00

May 3, 2013 directory server malfunctioning

by

LDAP directory service from ldap.CS.Berkeley.EDU was malfunctioning from about Friday May 3, 2013 01:56 to about 06:57.

It appears authenticated outgoing smtp service on gateway.EECS.Berkeley.EDU also malfunctioned during that time frame when gateway.EECS.Berkeley.EDU failed to use ldap.EECS.Berkeley.EDU for LDAP directory service instead of ldap.CS.Berkeley.EDU

Resolved as of 2013-05-03 06:57:00

no directory service from ldap.eecs Wednesday December 28th in the morning

by

The Entrust SSL certificate that is due to expire December 31, 2011 will be removed. A new 2048 bit CSR will be generated. We will apply for a new InCommon SSL certificate. After the new SSL certificate is issued, it will be installed and ldap directory service should resume.
[Read more…] about no directory service from ldap.eecs Wednesday December 28th in the morning

LDAP Outage

by

“There was a short LDAP outage between 2:50pm and 3:00pm today, that has been resolved. Impacted areas included IRIS web forms. If there are further problems with the server, please email help@eecs.berkeley.edu so we can investigate further. ”

Resolved as of 2011-08-17 15:04:00

December 28th Shutdown

by

IMAP/mail, home/project, Windows services (AD/WINS/printing), LDAP/NIS/DNS, DHCP and most other IDSG and IMG services will be affected. We will try to keep some basic network services running (DHCP, DNS/NIS), possibly in a reduced capacity.

While EECS-Secure, EECS-Guest and EECS-Open wireless LANS will be out of service during this time, the EECS and AirBears wireless LANS will remain operational during the outage.

The reason for this extended downtime is multi fold. The first is to repair the UPS that failed a couple of weeks back. The repaired unit will be placed back on line and extensive testing must be done to ensure it’s operation before we can depend on the UPS again. The second is to move data around which will allow us to remove from service a piece of software used to manage storage. This software is no longer under development and we need to remove our dependency on it. Lastly, some routine maintenance will be done which can only be done when systems are down. These are the kind of things that can only be done between semesters and we ask for you understanding during this disruption in service.

While the stated outage is from 10:00AM to 9:00PM, it may not take that long. This is a worst case scenario. If possible, services will be brought up sooner than 9:00 PM.
[Read more…] about December 28th Shutdown