thr3ads.net - Fedora directory users - [Fedora-directory-users] FDS crashed, how to find out the reason? [Jun 2006]

If this information is useful, please help other people find it:
Share via:

Kimmo Koivisto

2006-Jun-25 18:09 UTC

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

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?

Best Regards
Kimmo Koivisto

Joe Sheehan

2006-Jun-26 14:23 UTC

head link

[Fedora-directory-users] Setting up multi-master via the command-line

Is there any utilities or instructions for setting up multi-master
via the command-line. The only ones I can find are
http://directory.fedora.redhat.com/wiki/Howto:MultiMasterReplication
but the mmr.pl doesn''t come by default.

Thanks

Joe

Richard Megginson

2006-Jun-26 15:23 UTC

head link

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

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@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

Kimmo Koivisto

2006-Jun-26 16:36 UTC

head link

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

Richard Megginson wrote ( sent Monday 26 June 2006
18:23):> 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.
>
> What are the access log entries from around the time of the crash?
>Hello

Access log is attached as access.log. 
My env is Server1, Server2.

Server1 in MMR is 192.168.71.25 and Server2 (the crashed one where this log is 
from) is 192.168.71.26. There is also Nagios monitoring system in 
192.168.71.30 which connects to the FDS to test that it is alive.

I did not see anything strange in access log during crash (happened 
22/Jun/2006/16:56) but maybe someone else is able to find something:

BR
Kimmo

Richard Megginson

2006-Jun-27 16:24 UTC

head link

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

Kimmo Koivisto wrote:> Richard Megginson wrote ( sent Monday 26 June 2006 18:23):
>   
>> 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.
>>>       
>> What are the access log entries from around the time of the crash?
>>
>>     
> Hello
>
> Access log is attached as access.log. 
> My env is Server1, Server2.
>
> Server1 in MMR is 192.168.71.25 and Server2 (the crashed one where this log
is
> from) is 192.168.71.26. There is also Nagios monitoring system in 
> 192.168.71.30 which connects to the FDS to test that it is alive.
>
> I did not see anything strange in access log during crash (happened 
> 22/Jun/2006/16:56) but maybe someone else is able to find something:
>   Hmm - I don''t know.  I would suggest that if you can find a
reproducible
test case, run the server that crashes with trace level debugging.
http://directory.fedora.redhat.com/wiki/FAQ#Troubleshooting> BR
> Kimmo
>   
> ------------------------------------------------------------------------
>
> [22/Jun/2006:16:53:34 +0300] conn=412 op=91982 SRCH base="dc=fi"
scope=2 filter="(NAI=user1@ton.fi)" attrs="mipKey mipAuthMethod
mipAuthorizedIpAddress mi
> pNotValidBefore mipNotValidAfter NAI"
> [22/Jun/2006:16:53:34 +0300] conn=412 op=91982 RESULT err=0 tag=101
nentries=1 etime=0
> [22/Jun/2006:16:53:34 +0300] conn=412 op=91983 MOD
dn="NAI=user1@ton.fi,o=TON MIP users,dc=fi"
> [22/Jun/2006:16:53:34 +0300] conn=412 op=91983 RESULT err=0 tag=103
nentries=0 etime=0 csn=449ab2cb000000020000
> [22/Jun/2006:16:53:34 +0300] conn=5708 op=7 EXT
oid="2.16.840.1.113730.3.5.5" name="Netscape Replication End
Session"
> [22/Jun/2006:16:53:34 +0300] conn=5708 op=7 RESULT err=0 tag=120 nentries=0
etime=0
> [22/Jun/2006:16:53:34 +0300] conn=5708 op=8 EXT
oid="2.16.840.1.113730.3.5.3" name="Netscape Replication Start
Session"
> [22/Jun/2006:16:53:34 +0300] conn=5708 op=8 RESULT err=0 tag=120 nentries=0
etime=0
> [22/Jun/2006:16:53:34 +0300] conn=5708 op=9 MOD
dn="nai=user1@ton.fi,o=ton mip users,dc=fi"
> [22/Jun/2006:16:53:34 +0300] conn=5708 op=9 RESULT err=0 tag=103 nentries=0
etime=0 csn=449ab2c9000200010000
> [22/Jun/2006:16:53:36 +0300] conn=5708 op=10 EXT
oid="2.16.840.1.113730.3.5.5" name="Netscape Replication End
Session"
> [22/Jun/2006:16:53:36 +0300] conn=5708 op=10 RESULT err=0 tag=120
nentries=0 etime=0
> [22/Jun/2006:16:53:38 +0300] conn=412 op=91984 SRCH base="dc=fi"
scope=2 filter="(NAI=user1@ton.fi)" attrs="mipKey mipAuthMethod
mipAuthorizedIpAddress mi
> pNotValidBefore mipNotValidAfter NAI"
> [22/Jun/2006:16:53:38 +0300] conn=412 op=91984 RESULT err=0 tag=101
nentries=1 etime=0
> [22/Jun/2006:16:53:38 +0300] conn=412 op=91985 MOD
dn="NAI=user1@ton.fi,o=TON MIP users,dc=fi"
> [22/Jun/2006:16:53:38 +0300] conn=412 op=91985 RESULT err=0 tag=103
nentries=0 etime=0 csn=449ab2cf000000020000
> [22/Jun/2006:16:53:38 +0300] conn=5708 op=11 EXT
oid="2.16.840.1.113730.3.5.3" name="Netscape Replication Start
Session"
> [22/Jun/2006:16:53:38 +0300] conn=5708 op=11 RESULT err=0 tag=120
nentries=0 etime=0
> [22/Jun/2006:16:53:38 +0300] conn=5708 op=12 EXT
oid="2.16.840.1.113730.3.5.5" name="Netscape Replication End
Session"
> [22/Jun/2006:16:53:38 +0300] conn=5708 op=12 RESULT err=0 tag=120
nentries=0 etime=0
> [22/Jun/2006:16:54:09 +0300] conn=5708 op=14 EXT
oid="2.16.840.1.113730.3.5.3" name="Netscape Replication Start
Session"
> [22/Jun/2006:16:54:09 +0300] conn=5708 op=14 RESULT err=0 tag=120
nentries=0 etime=0
> [22/Jun/2006:16:54:09 +0300] conn=5708 op=15 MOD
dn="nai=user1@ton.fi,o=ton mip users,dc=fi"
> [22/Jun/2006:16:54:09 +0300] conn=5708 op=15 RESULT err=0 tag=103
nentries=0 etime=0 csn=449ab2ee000000010000
> [22/Jun/2006:16:54:11 +0300] conn=5708 op=17 EXT
oid="2.16.840.1.113730.3.5.5" name="Netscape Replication End
Session"
> [22/Jun/2006:16:54:11 +0300] conn=5708 op=17 RESULT err=0 tag=120
nentries=0 etime=0
> [22/Jun/2006:16:54:11 +0300] conn=5708 op=18 EXT
oid="2.16.840.1.113730.3.5.3" name="Netscape Replication Start
Session"
> [22/Jun/2006:16:54:11 +0300] conn=5708 op=18 RESULT err=0 tag=120
nentries=0 etime=0
> [22/Jun/2006:16:54:11 +0300] conn=5708 op=19 MOD
dn="nai=user1@ton.fi,o=ton mip users,dc=fi"
> [22/Jun/2006:16:54:11 +0300] conn=5708 op=19 RESULT err=0 tag=103
nentries=0 etime=0 csn=449ab2ee000200010000
> [22/Jun/2006:16:54:11 +0300] conn=5708 op=20 MOD
dn="nai=user1@ton.fi,o=ton mip users,dc=fi"
> [22/Jun/2006:16:54:11 +0300] conn=5708 op=20 RESULT err=0 tag=103
nentries=0 etime=0 csn=449ab2ee000400010000
> [22/Jun/2006:16:54:14 +0300] conn=5708 op=21 EXT
oid="2.16.840.1.113730.3.5.5" name="Netscape Replication End
Session"
> [22/Jun/2006:16:54:14 +0300] conn=5708 op=21 RESULT err=0 tag=120
nentries=0 etime=0
> [22/Jun/2006:16:55:14 +0300] conn=5708 op=22 UNBIND
> [22/Jun/2006:16:55:14 +0300] conn=5708 op=22 fd=65 closed - U1
> [22/Jun/2006:16:55:19 +0300] conn=5709 fd=65 slot=65 connection from
192.168.71.25 to 192.168.71.26
> [22/Jun/2006:16:55:19 +0300] conn=5709 op=0 BIND
dn="cn=repman,cn=config" method=128 version=3
> [22/Jun/2006:16:55:19 +0300] conn=5709 op=0 RESULT err=0 tag=97 nentries=0
etime=0 dn="cn=repman,cn=config"
> [22/Jun/2006:16:55:19 +0300] conn=5709 op=1 SRCH base="" scope=0
filter="(objectClass=*)" attrs="supportedControl
supportedExtension"
> [22/Jun/2006:16:55:19 +0300] conn=5709 op=1 RESULT err=0 tag=101 nentries=1
etime=0
> [22/Jun/2006:16:55:19 +0300] conn=5709 op=2 SRCH base="" scope=0
filter="(objectClass=*)" attrs="supportedControl
supportedExtension"
> [22/Jun/2006:16:55:19 +0300] conn=5709 op=2 RESULT err=0 tag=101 nentries=1
etime=0
> [22/Jun/2006:16:55:19 +0300] conn=5709 op=3 EXT
oid="2.16.840.1.113730.3.5.3" name="Netscape Replication Start
Session"
> [22/Jun/2006:16:55:19 +0300] conn=5709 op=3 RESULT err=0 tag=120 nentries=0
etime=0
> [22/Jun/2006:16:55:19 +0300] conn=5709 op=4 MOD
dn="nai=user2@ton.fi,o=ton mip users,dc=fi"
> [22/Jun/2006:16:55:19 +0300] conn=5709 op=4 RESULT err=0 tag=103 nentries=0
etime=0 csn=449ab334000000010000
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=5 EXT
oid="2.16.840.1.113730.3.5.5" name="Netscape Replication End
Session"
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=5 RESULT err=0 tag=120 nentries=0
etime=0
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=6 EXT
oid="2.16.840.1.113730.3.5.3" name="Netscape Replication Start
Session"
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=6 RESULT err=0 tag=120 nentries=0
etime=0
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=7 MOD
dn="nai=user2@ton.fi,o=ton mip users,dc=fi"
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=7 RESULT err=0 tag=103 nentries=0
etime=0 csn=449ab334000100010000
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=8 MOD
dn="nai=user2@ton.fi,o=ton mip users,dc=fi"
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=8 RESULT err=0 tag=103 nentries=0
etime=0 csn=449ab335000000010000
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=9 MOD
dn="nai=user2@ton.fi,o=ton mip users,dc=fi"
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=9 RESULT err=0 tag=103 nentries=0
etime=0 csn=449ab335000100010000
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=10 MOD
dn="nai=user2@ton.fi,o=ton mip users,dc=fi"
> [22/Jun/2006:16:55:21 +0300] conn=5709 op=10 RESULT err=0 tag=103
nentries=0 etime=0 csn=449ab335000200010000
> [22/Jun/2006:16:55:23 +0300] conn=5709 op=11 EXT
oid="2.16.840.1.113730.3.5.5" name="Netscape Replication End
Session"
> [22/Jun/2006:16:55:23 +0300] conn=5709 op=11 RESULT err=0 tag=120
nentries=0 etime=0
> [22/Jun/2006:16:55:24 +0300] conn=5710 fd=66 slot=66 connection from
192.168.71.30 to 192.168.71.26
> [22/Jun/2006:16:55:24 +0300] conn=5710 op=0 BIND dn="" method=128
version=2
> [22/Jun/2006:16:55:24 +0300] conn=5710 op=0 RESULT err=0 tag=97 nentries=0
etime=0 dn=""
> [22/Jun/2006:16:55:24 +0300] conn=5710 op=1 SRCH base="dc=fi"
scope=0 filter="(objectClass=*)" attrs=ALL
> [22/Jun/2006:16:55:24 +0300] conn=5710 op=1 RESULT err=0 tag=101 nentries=1
etime=0
> [22/Jun/2006:16:55:24 +0300] conn=5710 op=2 UNBIND
> [22/Jun/2006:16:55:24 +0300] conn=5710 op=2 fd=66 closed - U1
> [22/Jun/2006:16:56:24 +0300] conn=5709 op=12 UNBIND
> [22/Jun/2006:16:56:24 +0300] conn=5709 op=12 fd=65 closed - U1
>         Fedora-Directory/1.0.2 B2006.060.1928
>         mip2.vn.fi:389 (/opt/fedora-ds/slapd-mip2.vn.fi)
>
> [25/Jun/2006:20:26:12 +0300] conn=0 fd=64 slot=64 connection from 127.0.0.1
to 127.0.0.1
> [25/Jun/2006:20:26:12 +0300] conn=0 op=0 BIND dn="" method=128
version=3
> [25/Jun/2006:20:26:12 +0300] conn=0 op=0 RESULT err=0 tag=97 nentries=0
etime=0 dn=""
> [25/Jun/2006:20:26:12 +0300] conn=0 op=1 SRCH base="dc=fi"
scope=2 filter="(objectClass=*)" attrs=ALL
> [25/Jun/2006:20:26:14 +0300] conn=0 op=1 RESULT err=0 tag=101 nentries=1
etime=2
> [25/Jun/2006:20:26:14 +0300] conn=0 op=2 UNBIND
> [25/Jun/2006:20:26:14 +0300] conn=0 op=2 fd=64 closed - U1
> [25/Jun/2006:20:26:20 +0300] conn=1 fd=64 slot=64 connection from 127.0.0.1
to 127.0.0.1
> [25/Jun/2006:20:26:20 +0300] conn=1 op=0 BIND dn="" method=128
version=3
> [25/Jun/2006:20:26:20 +0300] conn=1 op=0 RESULT err=0 tag=97 nentries=0
etime=0 dn=""
> [25/Jun/2006:20:26:20 +0300] conn=1 op=1 SRCH base="dc=fi"
scope=2 filter="(objectClass=*)" attrs=ALL
> [25/Jun/2006:20:26:20 +0300] conn=1 op=1 RESULT err=0 tag=101 nentries=1
etime=0
> [25/Jun/2006:20:26:20 +0300] conn=1 op=2 UNBIND
> [25/Jun/2006:20:26:20 +0300] conn=1 op=2 fd=64 closed - U1
> [25/Jun/2006:20:26:33 +0300] conn=2 fd=64 slot=64 connection from 127.0.0.1
to 127.0.0.1
> [25/Jun/2006:20:26:33 +0300] conn=2 op=0 BIND dn="cn=root"
method=128 version=3
> [25/Jun/2006:20:26:33 +0300] conn=2 op=0 RESULT err=0 tag=97 nentries=0
etime=0 dn="cn=root"
> [25/Jun/2006:20:26:33 +0300] conn=2 op=1 SRCH base="dc=fi"
scope=2 filter="(NAI=User3@ton.fi)" attrs="mipKey mipAuthMethod
mipAuthorizedIpAddress mipN
> otValidBefore mipNotValidAfter NAI"

Fedora directory users - Jun 2006 - FDS crashed, how to find out the reason?

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

[Fedora-directory-users] Setting up multi-master via the command-line

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

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

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