dirsrv error

Thu Nov 3 15:52:16 CET 2016

Hi Jan, hi guys, 

I am in need to increase the logs. 

I've found out this set of commands: 

ldapmodify -x -D "cn=directory manager" -w password 

dn: cn=config 

changetype: modify 

replace: nsslapd-errorlog-level 

nsslapd-errorlog-level:8192 

And, to get back: 

ldapmodify -x -D "cn=directory manager" -w password 

dn: cn=config 

changetype: modify 

replace: nsslapd-errorlog-level 

nsslapd-errorlog-level:0 

searching in the configuration files, I've found out that in my version
"nsslapd-errorlog-level" is not present. 

Can you tell me something more about that? 

Regards, 

Pietro 

Il 2016-10-31 16:00 Pietro Vassalli ha scritto: 

> Hi Jan, 
> 
> thank you for the quick response. 
> 
> Obviously I got an error on friday and so my idea of a cron.weekly error has gone. 
> 
> An excerpt from the logs is: 
> 
> /var/log/dirsrv/slapd-posta/access.20161028-135321 
> 
> [28/Oct/2016:17:14:33 +0200] conn=143825 op=6 RESULT err=0 tag=101 nentries=1 etime=0 notes=U
> [28/Oct/2016:17:14:34 +0200] conn=143844 fd=87 slot=87 connection from ::1 to ::1
> [28/Oct/2016:17:14:34 +0200] conn=143844 op=0 BIND dn="cn=Directory Manager" method=128 version=3
> [28/Oct/2016:17:14:34 +0200] conn=143844 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=directory manager"
> [28/Oct/2016:17:14:34 +0200] conn=143844 op=1 SRCH base="cn=kolab,cn=config" scope=2 filter="(&(associatedDomain=*))" attrs="associatedDomain"
> [28/Oct/2016:17:14:34 +0200] conn=143844 op=1 RESULT err=0 tag=101 nentries=1 etime=0
> [28/Oct/2016:17:14:34 +0200] conn=143844 op=2 BIND dn="cn=Directory Manager" method=128 version=3
> [28/Oct/2016:17:14:34 +0200] conn=143844 op=2 RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=directory manager"
> [28/Oct/2016:17:14:34 +0200] conn=143844 op=3 SRCH base="cn=kolab,cn=config" scope=2 filter="(&(associatedDomain=waterline.ch))" attrs=ALL
> [28/Oct/2016:17:14:34 +0200] conn=143844 op=3 RESULT err=0 tag=101 nentries=1 etime=0
> [28/Oct/2016:17:14:34 +0200] conn=143844 op=4 SRCH base="dc=mydomain,dc=mycountry" scope=2 filter="(&(|(|(objectClass=groupofuniquenames)(objectClass=groupofurls))(objectClass=kolabsharedfolder))(|(mail=name.surename at mydomain.mycountry)(alias=name.surename at mydomain.mycountry)(nsUniqueId=name.surename at mydomain.mycountry)))" attrs="mail alias nsUniqueId"
> [28/Oct/2016:17:14:34 +0200] conn=143844 op=4 RESULT err=0 tag=101 nentries=0 etime=0 notes=U
> [28/Oct/2016:17:14:34 +0200] conn=143845 fd=90 slot=90 connection from ::1 to ::1
> [28/Oct/2016:17:34:38 +0200] conn=1 fd=64 slot=64 connection from ::1 to ::1 
> 
> /var/log/dirsrv/slapd-posta/access.rotationinfo 
> 
> LOGINFO:Log file created at: 31/Oct/2016:12:53:49 (1477914829)
> LOGINFO:Previous Log File:/var/log/dirsrv/slapd-posta/access.20161030-125344 (1477828424) (15924249)
> LOGINFO:Previous Log File:/var/log/dirsrv/slapd-posta/access.20161029-135341 (1477742021) (6863423)
> LOGINFO:Previous Log File:/var/log/dirsrv/slapd-posta/access.20161028-135321 (1477655601) (21411212)
> LOGINFO:Previous Log File:/var/log/dirsrv/slapd-posta/access.20161023-135258 (1477223578) (25568945)
> LOGINFO:Previous Log File:/var/log/dirsrv/slapd-posta/access.20161022-135255 (1477137175) (8799991)
> LOGINFO:Previous Log File:/var/log/dirsrv/slapd-posta/access.20161024-135303 (1477309983) (35832211)
> LOGINFO:Previous Log File:/var/log/dirsrv/slapd-posta/access.20161025-135308 (1477396388) (41033258)
> LOGINFO:Previous Log File:/var/log/dirsrv/slapd-posta/access.20161026-135313 (1477482793) (35096679)
> LOGINFO:Previous Log File:/var/log/dirsrv/slapd-posta/access.20161027-135317 (1477569197) (35313186) 
> 
> /var/log/dirsrv/slapd-posta/errors 
> 
> [24/Oct/2016:14:32:34 +0200] - slapd started.  Listening on All Interfaces port 389 for LDAP requests
> [28/Oct/2016:17:34:38 +0200] - 389-Directory/1.3.2.16 B2014.098.2147 starting up
> [28/Oct/2016:17:34:38 +0200] - Detected Disorderly Shutdown last time Directory Server was running, recovering database.
> [28/Oct/2016:17:34:38 +0200] - slapd started.  Listening on All Interfaces port 389 for LDAP requests 
> 
> Note that I don't have any issue: how can I increase the logging for dirsrv? 
> 
> Regards, 
> 
> Pietro 
> 
> Il 2016-10-28 22:08 Jan Kowalsky ha scritto: 
> Hi Pietro,
> 
> Am 28.10.2016 um 15:50 schrieb Pietro Vassalli:  
> 
> Hi to everyone, 
> 
> every monday (don't laugh for that) almost about 3.00 p.m. dirsrv
> process hangs. 
> are there any other events on 3.00 p.m. - maybe cron weekly?
> 
> I try to stop it (service dirsrv stop) but no chance. I have to manually
> kill the process, use the recovery of ldap db and restart it (always
> manually). 
> 
> In the end the service restart but I have many problems with my users,
> who are complaining that (thunderbird requires the insertion of
> username/password...) and I'd like to be on holidays in some monday of
> the year... ;-) 
> only a idea ... could it be a logrotation script that removes / changes
> the dirsrv logfiles? 389-ds ships with it's own logrotation function -
> maybe it doesn't like if its logfiles are changed from outside?
> 
> regards
> jan
 CAUTION - This message may contain privileged and confidential
information intended only for the use of the addressee named above. If
you are not the intended recipient of this message you are hereby
notified that any use, dissemination, distribution or reproduction of
this message is prohibited. If you have received this message in error
please notify WATER-LINE SA immediately. Any views expressed in this
message are those of the individual sender and may not necessarily
reflect the views of WATER-LINE SA.

_______________________________________________
users mailing list
users at lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users CAUTION - This message
may contain privileged and confidential information intended only for
the use of the addressee named above. If you are not the intended
recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is
prohibited. If you have received this message in error please notify
WATER-LINE SA immediately. Any views expressed in this message are those
of the individual sender and may not necessarily reflect the views of
WATER-LINE SA. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20161103/0f60d640/attachment.html>