ldap.log has grown too large

digitolx · 05-25-2010, 08:51 AM

I've noticed my ldap.log file has grown to 30GB and has filled / to 86%..

1. I want to know if I zero out the logfile will this cause any issues while ldap is up and running?

# > ldap.log

2. I will be changing the log file settings in slapd.conf. I will then need to restart slapd.. Will restarting impact existing connections at all?

Thank you

druuna · 05-26-2010, 02:00 AM

Hi,

T1) his: > ldap.log should work while ldap is running. Any other command will disconnect the running ldap instance from the log (restart will be needed).

2) Restarting ldap will:
- gracefully terminate all the connections,
- stop the ldap core,
- start the ldap core,
- wait for connections and serve them if needed.

Do change the log settings. Logfiles this big are not workable in the long run.

Hope this helps.

selestin Mathew · 05-26-2010, 02:48 AM

Hi,

you can use command "> ldap.log" in the running environment. Why don't you implement log rotate for ldap logs and check the 'loglevel' value. Do not use level 4 without any reason in production which is heavy trace debugging mode.