Topic: Post restore from backup server migration

[elSpike]

Hi there.

I have noticed that since doing a backup2ws (disaster recovery option) I have had a an issue with administering the system.

I now cannot get LDAP to start on reboot, I have to manually start it from console, changing it from public to private in the Directory secion of server manager does nothing either.

This causes the addressbook to display an "unable to connect to file/directory" error when searching (obviously as the service hasnt been started)

I have tried the fix suggested in bug 77 (i think it was that) where you expand the template. But this does not do anything.

I have applied the U4 update to a basic 5.6 install as well as trying to apply each update (1,2,3,4) in turn.

Any ideas why this would happen?

Cheers
elSpike

[Cyrus Bharda]

elSpike,

I cant comment on your actual problem, but I can save you some time when updating, all the updates are cumulative, meaning the updates in 1, 2 and 3 are contained in 4, so you only need to apply 4 to get them all

Cyrus Bharda

[elSpike]

Cyrus,

thanks, I knew that but my twisted 2am mind thought, "Maybe if I install all the patches like I did on the old machine I can trick it into working."

cheers

[Cyrus Bharda]

elSpike,

Thought so just reminding.  Is there any messages in the message log or boot log in reguards to the ldapd not starting? Unfortunatly I do not use the ldap functionality of SME so that's about as far as my limited knowledge can take you,

Cyrus Bharda

[elSpike]

No there are no messages as it isnt even being considered for start-up.

Looking at the relevent templates it seems it is looking for some tringer in a db somwhere that says, "start up ldap". unfortunatly I dont know enough about the db structures in e-smith to go poking in there.

I thought by changing the directory access from private to public etc. it would trigger the db to say "yes he does want ldap running" but it hasnt worked.

I might try installing a bare install and using the "backup" module then restore with it. if that doesnt work I can then submit it as a bug.

Unfortunatly I suspect it is either an issue with the backup2ws contrib or how I reinstalled the box.

cheers
elSpike out.

[Ray Mitchell]

elSpike wrote:
> I have tried the fix suggested in bug 77 (i think it was
> that) where you expand the template. But this does not do
> anything.

Do you mean this bug, it sounds a bit different to the one you describe (see below).

Also this issue re backup2ws, don't know if you are running into the restore issue problem.

http://forums.contribs.org/index.php?topic=17397.msg67744#msg67744

Regs
Ray


LDAP not working after domain name change
Applies to version: 5.6
Fixed in version:  
Problem: The LDAP server is not correctly reconfigured after changing the domain name from the console. This causes failures in webmail and other applications which access the LDAP database.
Workaround: # stop ldap
/etc/rc.d/init.d/ldap stop

# remove old ldap data
rm /home/e-smith/db/ldap/*ldif
rm /var/lib/ldap/*

# rebuild directory from scratch
/etc/e-smith/events/actions/ldap-rebuild

# start ldap
/etc/rc.d/init.d/ldap start

[elSpike]

Hi there Ray,

No the issue is not the same thing as you outlined in both instances.

The LDAP directory is there. and when I "/sbin/service ldap start" everything runs fine.

The bug I was refering to was:

http://www.e-smith.org/bugs/index.php3?op=showBug&bugID=77

I have duplicated it twice now so I assume it is an issue with backup2ws.

cheers

elSpike