Topic: I stupidly installed the LDAP contrib to a 7.4 server

[dolittle]

Hi,
my fingers were too fast, ignoring the warnings and I installed the LDAP contrib to my 7.4 Server. Which is a half production server. Now I can't access the admin interface anymore.

Please don't pick on me. I'm already banging my head against the wall.

Is there a way to uninstall the contrib or can anybody tell me who to ask? Additionally is there a way to save the current config to prevent that I have to setup everything from scratch again? I have to add that I'm not too deep into the SME server yet.

Thanks very much in advance

Update: May be there's a way to get the web interface running again. This would help a lot.

[janet]

dolittle

You need to find out what got installed, usually there may be other dependent packages as well as the main two referred to in the wiki.

You could look at the yum install log file for details otherwise you could run the commands again on a fresh clean server and see what is listed for install eg
yum install e-smith-base+ldap e-smith-samba+ldap --enablerepo=smetest --enablerepo=smeupdates-testing

BUT do not proceed with the install ie say N for no, after making a note of all the packages listed for install

Then the standard way to remove packages is done like this

rpm -e e-smith-base+ldap e-smith-samba+ldap otherpackagenames

(replacing otherpackagenames with actual names)

Then to reinstall standard base packages do

yum update
signal-event post-upgrade
signal-event reboot

It is not advisable to use
yum remove e-smith-base+ldap e-smith-samba+ldap
as many more packages can be removed than should be if you are not careful or fully understanding what is happening.

I note there is a warning about not expecting removal to be necessarily successfull on a production server, so I'd suggest ensuring you have a backup or remove a RAID drive for safekeeping until you resolve the matter.
You may need to redo the procedure on a test server and see if your can successfully remove everything back to a good working state, before trying to fix your production server.

You should learn from this experience and ONLY do testing on a TEST server.

[dolittle]

Thanks for the reply I'll give it a try and report back to make other users benefit from my dumb experiences.

Update:
Fortunately my log is still visible. It reads
Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 e-smith-base+ldap       i386       5.0.0-5.el4.sme  smetest           369 k
 e-smith-samba+ldap      noarch     2.0.0-6.el4.sme  smetest            91 k
Installing for dependencies:
 cpu                     i386       1.4.3-5.el4.sme  smetest           220 k
 nscd                    i386       2.3.4-2.41       base              140 k
 nss_ldap                i386       253-5.el4        base              1.1 M
Updating for dependencies:
 e-smith-lib             noarch     2.0.0-2.el4.sme  smeupdates-testing  131 k

Transaction Summary
=============================================================================


More information to follow

[JohnG]

For what it's worth, I installed the LDAP contrib to a 7.4 and it's still working fine. I just have the sysmon and mail queue contribs installed and it was an upgrade from 7.3. Good luck.

[JohnG]

Can you access the password change page?

https://[yourserver]/user-password

[dolittle]

yes I can. But I can't change the password.

May be the update went wrong. Right now im getting the following messages:

Code: [Select]

....lots of lines...
Mar  4 15:20:21 mailfile slapadd: bdb_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003)
Mar  4 15:20:21 mailfile slapadd: bdb_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003)
Mar  4 15:20:21 mailfile slapcat: bdb_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003)
Mar  4 15:20:22 mailfile smbd[20128]: [2009/03/04 15:20:22, 0] services/services_db.c:svcctl_init_keys(420)
Mar  4 15:20:22 mailfile smbd[20128]:   svcctl_init_keys: key lookup failed! (WERR_ACCESS_DENIED)
Mar  4 15:20:22 mailfile smbd[20128]: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Mar  4 15:20:22 mailfile smbd[20128]: nss_ldap: could not search LDAP server - Server is unavailable
Mar  4 15:20:22 mailfile smbd[20128]: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Mar  4 15:20:22 mailfile smbd[20128]: nss_ldap: could not search LDAP server - Server is unavailable
Mar  4 15:20:21 mailfile slapcat: bdb_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003)
Mar  4 15:20:23 mailfile slapadd: bdb_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003)
Mar  4 15:20:23 mailfile slapadd: bdb_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003)
Mar  4 15:20:23 mailfile slapcat: bdb_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003)
Mar  4 15:20:23 mailfile slapcat: bdb_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003)
....lots of lines...
Mailfile is the name of my server

[cactus]

Since you state you were able to see the transaction log, did you do the following after installing the LDAP packages:

Code: [Select]

signal-event post-upgrade
signal-event reboot

[dolittle]

sure. But I already gave up and right now I'm reinstalling the server.

Thanks for your help.