Andrey,
This just isn't enough information to diagnose. Do you have a core
file? If not, please enable core files:
Hopefully you can catch it again and get a core, and then we can work on it.
Regards,
Mark
On 01/07/2015 11:07 AM, Ivanov Andrey (M.) wrote:
We've just had a crash of one of 3 multi-master replicated 389ds
(v1.3.2 latest patch from GIT). The only interesting message is in the
error log:
[07/Jan/2015:15:33:42 +0100] - entry2str_internal_ext: array boundary
wrote: bufsize=17001 wrote=17226
audit log and access log show nothing particular at the same moment.
last record in audit log before the crash:
time: 20150107153340
dn:
uid=some_login,ou=Etudiants,ou=Utilisateurs,dc=id,dc=polytechnique,dc=edu
changetype: modify
replace: lastLoginTime
lastLoginTime: 20150107143336Z
-
replace: entryusn
entryusn: 457510
-
in access log nothing special either:
[07/Jan/2015:15:33:33 +0100] conn=75663 op=10512 SRCH
base="ou=utilisateurs,dc=id,dc=polytechnique,dc=edu" scope=2
filter="(&(uid=...)(objectClass=inetOrgPerson)(objectClass=X-Misc))"
attrs="X-Vlan-WiFi X-Vlan-WiFi"
[07/Jan/2015:15:33:33 +0100] conn=75663 op=10512 RESULT err=0 tag=101
nentries=1 etime=0.001000
[07/Jan/2015:15:33:33 +0100] conn=86232 fd=275 slot=275 connection
from 129.104.69.16 to 129.104.247.8
[07/Jan/2015:15:33:33 +0100] conn=86232 op=0 EXT
oid="1.3.6.1.4.1.1466.20037" name="startTLS"
[07/Jan/2015:15:33:33 +0100] conn=86232 op=0 RESULT err=0 tag=120
nentries=0 etime=0.000000
[07/Jan/2015:15:33:33 +0100] conn=86232 SSL 128-bit AES
[07/Jan/2015:15:33:33 +0100] conn=86232 op=1 BIND
dn="uid=...,ou=Etudiants,ou=Utilisateurs,dc=id,dc=polytechnique,dc=edu"
method=128
version=3
[07/Jan/2015:15:33:33 +0100] conn=86232 op=1 RESULT err=0 tag=97
nentries=0 etime=0.027000
dn="uid=...,ou=Etudiants,ou=Utilisateurs,dc=id,dc=polytechnique,dc=edu"
[07/Jan/2015:15:33:33 +0100] conn=86232 op=2 UNBIND
[07/Jan/2015:15:33:33 +0100] conn=86232 op=2 fd=275 closed - U1
Nothing unusual in the logs of the other two replicas either. No
special charge, nothing unusual...
I am unable to reproduce the crash. It looks like the bug
https://fedorahosted.org/389/ticket/47360. However, this bug was fixed
an anyway no attributes were deleted at this moment.on any replica
(audit.log is active everywhere)
Any ideas?
Thanks!
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users