Need some warning on LDAP upgrades! - users - Fedora Mailing-Lists

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

1989

1988

1987

1986

1985

1984

1983

1982

1981

1980

Need some warning on LDAP upgrades!

NFS locking ...maybe?

Anyone know what this means?

Tim Alberts

Wednesday, 23 May 2007 Wed, 23 May '07

7:44 p.m.

I just downloaded the updates today and all my user accounts and passwords were completely wiped from my LDAP server? Not sure exactly how this happened, hopefully it's not supposed to happen. If it is, we really need some warning when updates are going to bring down our entire network!

Reply

Show replies by date

Ed Greshko

Wednesday, 23 May Wed, 23 May

8:01 p.m.

Tim Alberts wrote:

I just downloaded the updates today and all my user accounts and passwords were completely wiped from my LDAP server? Not sure exactly how this happened, hopefully it's not supposed to happen. If it is, we really need some warning when updates are going to bring down our entire network!

I doubt that what happened was an intended consequence of the update. However, I've always found it good to back up any sort of database before upgrading the server. That goes for LDAP, MySQL, etc.... I've also found it sensible to manually stop the server before doing an update.

Reply

Jason L Tibbitts III

8:15 p.m.

>>>> "TA" == Tim Alberts <talberts(a)msiscales.com> writes:

TA> I just downloaded the updates today and all my user accounts and TA> passwords were completely wiped from my LDAP server? Yes, this happened to me as well, and caused quite a bit of trouble because it didn't just kill the server (which would have been OK because I have multiple servers). Instead it loaded an nice empty database and proceeded to serve that. Sadly, I had tested the update that sat in the testing repository and warned that it shouldn't be put out, but after some months it was pushed anyway. All you need to do is stop the server and then copy the contents of /var/lib/ldap/rpmorig to /var/lib/ldap, make sure the ownership is correct (should be ldap:ldap) and start the server. But do tar everything off first just in case. - J<

Reply

Tim Alberts

Thursday, 24 May Thu, 24 May

10:36 a.m.

Jason L Tibbitts III wrote:

Yes, this happened to me as well, and caused quite a bit of trouble because it didn't just kill the server (which would have been OK because I have multiple servers). Instead it loaded an nice empty database and proceeded to serve that. Sadly, I had tested the update that sat in the testing repository and warned that it shouldn't be put out, but after some months it was pushed anyway.

This is precisely what happened to my server. The database was gone, the server was still running. For those who mentioned, yes all my databases are backed up regularly. I've been running networks long enough to know that rule. The system was quickly restored once I realized the problem, but that ten minutes of phones ringing off the hook from clients wanting to know why they can't get email etc. I will add, that rather than copying database directories as was suggested, I use an export to LDIF and import from LDIF as follows: Export: ldapsearch -x > database.ldif Import: ldapadd -x -D "cn=Manager,dc=mydomain,dc=com" -W -f database.ldif This way the database is backed up in a general ldif file that I believe is standard for LDAP servers, not just openldap.

Reply

6191

days inactive

6191

days old

users@lists.fedoraproject.org

Manage subscription

3 comments

3 participants

tags (0)

participants (3)

Ed Greshko
Jason L Tibbitts III
Tim Alberts