[Fedora-directory-users] FDS crashed, how to find out the reason?

[Richard Megginson]

Kimmo Koivisto wrote:
> Hello
>
> I have MMR environment, 2x FDS, version 1.0.2, Red Hat Enterprise 4 ES 32bit 
> x86. My servers are server1.ton.fi and server2.ton.fi. 
>
> Server2 died couple of days ago (friday I think) and I restarted it today. 
> Everything seems to be okay, but I need to provide some reasons why this 
> happened.
>
> My /opt/fedora-ds/slapd-server2/logs/error shows the following:
> <error log>     
>        Fedora-Directory/1.0.2 B2006.060.1928
>         server2.ton.fi:389 (/opt/fedora-ds/slapd-server2.ton.fi)
>
> [17/Jun/2006:00:00:00 +0300] NSMMReplicationPlugin - agmt="cn="Replication to 
> server1.ton.fi"" (server1:389): Incremental protocol: event 
> update_window_opened should no
> t occur in state wait_for_changes
> [18/Jun/2006:00:00:00 +0300] NSMMReplicationPlugin - agmt="cn="Replication to 
> server1.ton.fi"" (server1:389): Incremental protocol: event 
> update_window_opened should no
> t occur in state wait_for_changes
>         Fedora-Directory/1.0.2 B2006.060.1928
>         server2.ton.fi:389 (/opt/fedora-ds/slapd-server2.ton.fi)
>
> [18/Jun/2006:04:23:11 +0300] - Backing up file 1 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/sn.db4)
> [18/Jun/2006:04:23:11 +0300] - Backing up file 2 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/entrydn.db4)
> [18/Jun/2006:04:23:11 +0300] - Backing up file 3 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/parentid.db4)
> [18/Jun/2006:04:23:11 +0300] - Backing up file 4 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/objectclass.db4)
> [18/Jun/2006:04:23:11 +0300] - Backing up file 5 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/aci.db4)
> [18/Jun/2006:04:23:11 +0300] - Backing up file 6 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/cn.db4)
> [18/Jun/2006:04:23:11 +0300] - Backing up file 7 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/givenName.db4)
> [18/Jun/2006:04:23:12 +0300] - Backing up file 8 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/nsUniqueId.db4)
> [18/Jun/2006:04:23:12 +0300] - Backing up file 9 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/numsubordinates.db4)
> [18/Jun/2006:04:23:12 +0300] - Backing up file 10 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/DBVERSION)
> [18/Jun/2006:04:23:12 +0300] - Backing up file 11 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/ancestorid.db4)
> [18/Jun/2006:04:23:12 +0300] - Backing up file 12 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/uid.db4)
> [18/Jun/2006:04:23:12 +0300] - Backing up file 13 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/nscpEntryDN.db4)
> [18/Jun/2006:04:23:12 +0300] - Backing up file 14 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/id2entry.db4)
> [18/Jun/2006:04:23:12 +0300] - Backing up file 15 
> (/tmp/tmp.dJIDpX3348/fdsbackup/userRoot/nsds5ReplConflict.db4)
> [18/Jun/2006:04:23:12 +0300] - Backing up file 16 
> (/tmp/tmp.dJIDpX3348/fdsbackup/log.0000002860)
> [18/Jun/2006:04:23:12 +0300] - Backing up file 17 
> (/tmp/tmp.dJIDpX3348/fdsbackup/DBVERSION)
> [19/Jun/2006:00:00:00 +0300] NSMMReplicationPlugin - agmt="cn="Replication to 
> server1.ton.fi"" (server1:389): Incremental protocol: event 
> update_window_opened should no
> t occur in state wait_for_changes
> [20/Jun/2006:00:00:00 +0300] NSMMReplicationPlugin - agmt="cn="Replication to 
> server1.ton.fi"" (server1:389): Incremental protocol: event 
> update_window_opened should no
> t occur in state wait_for_changes
> [21/Jun/2006:00:00:00 +0300] NSMMReplicationPlugin - agmt="cn="Replication to 
> server1.ton.fi"" (server1:389): Incremental protocol: event 
> update_window_opened should no
> t occur in state wait_for_changes
> [22/Jun/2006:00:00:00 +0300] NSMMReplicationPlugin - agmt="cn="Replication to 
> server1.ton.fi"" (server1:389): Incremental protocol: event 
> update_window_opened should no
> t occur in state wait_for_changes
>         Fedora-Directory/1.0.2 B2006.060.1928
>         server2.ton.fi:389 (/opt/fedora-ds/slapd-server2.ton.fi)
>
> [22/Jun/2006:17:01:10 +0300] - Fedora-Directory/1.0.2 B2006.060.1928 starting 
> up
>         Fedora-Directory/1.0.2 B2006.060.1928
>         server2.ton.fi:389 (/opt/fedora-ds/slapd-server2.ton.fi)
>
> [25/Jun/2006:20:25:48 +0300] - Fedora-Directory/1.0.2 B2006.060.1928 starting 
> up
> [25/Jun/2006:20:25:48 +0300] - Detected Disorderly Shutdown last time 
> Directory Server was running, recovering database.
> [25/Jun/2006:20:26:06 +0300] - slapd started.  Listening on All Interfaces 
> port 389 for LDAP requests
> [25/Jun/2006:20:27:05 +0300] NSMMReplicationPlugin - agmt="cn="Replication to 
> server1.ton.fi"" (server1:389): Unable to receive the response for a 
> startReplication exte
> nded operation to consumer (Can't contact LDAP server). Will retry later.
> [25/Jun/2006:20:27:09 +0300] NSMMReplicationPlugin - agmt="cn="Replication to 
> server1.ton.fi"" (server1:389): Simple bind resumed
> </error log>
>
> Any ideas?
>   
What are the access log entries from around the time of the crash?
> Best Regards
> Kimmo Koivisto
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3178 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-directory-users/attachments/20060626/602e3653/attachment.bin>