Koozali.org formerly Contribs.org

Backup fails because slapd not running

Backup fails because slapd not running
« on: October 01, 2012, 11:32:53 PM »
Hello all. 

The subject line says it all.  I have a newly installed SME 8 server to which I restored the contents of my previous 7.5 server.  However, I cannot get the Backup to Workstation to work.  I've posted the information in the bug tracker already in Bug 6921.  But I really need help now to get the back up running.  If I can't backup the machine for more than a few days, I'm going to be forced to leave SME altogether and go with something simpler such as Ubuntu Server.  At least with it, there are many good, easy and reliable backup options I can use.  (As an aside, does anyone have a suggested alternative to the built-in backup function?  It has never been stable or reliable for me.

I have no idea why slapd not running should cause backup to fail.  This machine has no users other than admin.  It is a web application server only.  There are 85GB of web data on the machine that I need to backup.  Here are the entries from the log when a backup attempts to start:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Oct  1 16:15:01 www /sbin/e-smith/do_backupwk[2291]: /home/e-smith/db/backups: OLD 1349126101=(undefined)
Oct  1 16:15:01 www /sbin/e-smith/do_backupwk[2291]: /home/e-smith/db/backups: NEW 1349126101=backup_record
Oct  1 16:15:01 www /sbin/e-smith/do_backupwk[2291]: /home/e-smith/db/backups: OLD 1349126101=backup_record
Oct  1 16:15:01 www /sbin/e-smith/do_backupwk[2291]: /home/e-smith/db/backups: NEW 1349126101=backup_record|StartEpochTime|1349126101
Oct  1 16:15:01 www /sbin/e-smith/do_backupwk[2291]: /home/e-smith/db/backups: OLD 1349126101=backup_record|StartEpochTime|1349126101
Oct  1 16:15:01 www /sbin/e-smith/do_backupwk[2291]: /home/e-smith/db/backups: NEW 1349126101=backup_record|BackupType|workstation|StartEpochTime|1349126101
Oct  1 16:15:01 www esmith::event[2292]: Processing event: pre-backup 
Oct  1 16:15:01 www esmith::event[2292]: Running event handler: /etc/e-smith/events/actions/generic_template_expand
Oct  1 16:15:01 www esmith::event[2292]: expanding /etc/dar/DailyBackup.dcf 
Oct  1 16:15:01 www esmith::event[2292]: generic_template_expand=action|Event|pre-backup|Action|generic_template_expand|Start|1349126101 461432|End|1349126101 631538|Elapsed|0.170106
Oct  1 16:15:01 www esmith::event[2292]: Running event handler: /etc/e-smith/events/pre-backup/S10mysql-delete-dumped-tables
Oct  1 16:15:01 www esmith::event[2292]: S10mysql-delete-dumped-tables=action|Event|pre-backup|Action|S10mysql-delete-dumped-tables|Start|1349126101 631862|End|1349126101 646073|Elapsed|0.014211
Oct  1 16:15:01 www esmith::event[2292]: Running event handler: /etc/e-smith/events/pre-backup/S20mysql-dump-tables
Oct  1 16:15:03 www esmith::event[2292]: S20mysql-dump-tables=action|Event|pre-backup|Action|S20mysql-dump-tables|Start|1349126101 646651|End|1349126103 900740|Elapsed|2.254089
Oct  1 16:15:03 www esmith::event[2292]: Running event handler: /etc/e-smith/events/pre-backup/S30ldap-dump
Oct  1 16:15:04 www esmith::event[2292]: bdb_db_open: db_open(/var/lib/ldap/id2entry.bdb) failed: No such file or directory (2) 
Oct  1 16:15:04 www esmith::event[2292]: bdb(dc=pwarch,dc=com): Unknown locker ID: 0 
Oct  1 16:15:04 www esmith::event[2292]: backend_startup_one: bi_db_open failed! (2) 
Oct  1 16:15:04 www esmith::event[2292]: slap_startup failed 
Oct  1 16:15:04 www esmith::event[2292]: S30ldap-dump=action|Event|pre-backup|Action|S30ldap-dump|Start|1349126103 901282|End|1349126104 41283|Elapsed|0.140001|Status|256
Oct  1 16:15:04 www esmith::event[2292]: Running event handler: /etc/e-smith/events/pre-backup/S50rewind-tape
Oct  1 16:15:04 www esmith::event[2292]: S50rewind-tape=action|Event|pre-backup|Action|S50rewind-tape|Start|1349126104 41650|End|1349126104 126401|Elapsed|0.084751
Oct  1 16:15:04 www /sbin/e-smith/do_backupwk[2291]: /home/e-smith/db/backups: OLD 1349126101=backup_record|BackupType|workstation|StartEpochTime|1349126101
Oct  1 16:15:04 www /sbin/e-smith/do_backupwk[2291]: /home/e-smith/db/backups: NEW 1349126101=backup_record|BackupType|workstation|EndEpochTime|1349126104|StartEpochTime|1349126101
Oct  1 16:15:04 www /sbin/e-smith/do_backupwk[2291]: /home/e-smith/db/backups: OLD 1349126101=backup_record|BackupType|workstation|EndEpochTime|1349126104|StartEpochTime|1349126101
Oct  1 16:15:04 www /sbin/e-smith/do_backupwk[2291]: /home/e-smith/db/backups: NEW 1349126101=backup_record|BackupType|workstation|EndEpochTime|1349126104|Result|pre-backup:256|StartEpochTime|1349126101
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I have no idea how to restore/fix sladp.  Looking in the Bug report, I ran the following:
[root@www ~]# cd /service/ldap
[root@www ldap]# sv d .
[root@www ldap]# ./run
bdb_db_open: alock package is unstable
backend_startup_one: bi_db_open failed! (-1)
slap_startup failed
@(#) $OpenLDAP: slapd 2.3.43 (Jul 12 2012 04:02:16) $
        mockbuild@builder10.centos.org:/builddir/build/BUILD/openldap-2.3.43/openldap-2.3.43/build-servers/servers/slapd
bdb_db_open: alock package is unstable
backend_startup_one: bi_db_open failed! (-1)
slapd stopped.
connections_destroy: nothing to destroy.

I have no idea what this means or how to fix it.  Can anyone help me with this?

Thanks in advance for your help.

Re: Backup fails because slapd not running
« Reply #1 on: October 02, 2012, 03:01:00 AM »
I have no idea why slapd not running should cause backup to fail.

slapd must be running in order to dump the ldap content, and ldap content dump is necessary to backup the ldap data.

Offline janet

  • ****
  • 4,812
Re: Backup fails because slapd not running
« Reply #2 on: October 02, 2012, 04:41:32 AM »
ktenbrook2

Quote
I have no idea what this means or how to fix it.  Can anyone help me with this?

Readers should not really add comment here at this stage, as the matter is being actively followed up in bug report 6921 at http://bugs.contribs.org/show_bug.cgi?id=6921
Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.