[ldap:error] [pid 1491] AH01323: Purge of LDAP cache failed
Seems that thisx problem hangs up a machine within 3-4 hours resulting a lot of apache scripts running at 2-3% cpu bringing everything else offline.
Thanks!
EDIT:
I just had a problem again, but this time i did not see the warning in the log. I just saw a lot of requests from z-push and my android-Outlook raising the processcount of apache. I just shut down the Outlook on Android. I do not see any hanging inctances for apache coming up until now. I’ll keep you updated.
Looks like this bug in Apache. The bug doesn’t mention a workaround, unfortunately. Possible ways to deal with it are:
Rebuild the Apache Debian package and modify the build process to apply the patch from that bug. Drawback: each time Apache is updated from Univention you’ll have to rebuild that new version with your patch.
File a bug in Univention’s bug tracker and ask them to do 1. with their official package. This would benefit all Univention users, but it wouldn’t be an immediate solution to your problem.
Write a script that monitors Apache’s error log and restarts it as soon as the message is encountered.
I have the same issue… time to time i get a lot of apache process the server completly lagged.
After restart the apache service is stay ok for more some days… i suspected from ucs dashboard… so i think this is a confirmation.
I want to open a bug, but i just wanted to get further informations. I want to wait some 24h more to get shure if it could be the admin dashbord - on the other hand i am not shure and just do not what to throw bug like “Here is the error - go for it”
@codedmind - Do you also have Kopano or anything else installed? I have an installation where i moved Kopano to a seperate Domain Member - and i do not see the error here. Since what time do you see the error?
@chackl nop, basic installation, only samba for windows domain and ucs dashboard, with the latest update of ucs dashboard and ucs 4.4 this behaviour appear
Ok - Just testing around a little here.
I saw also no problems coming up using the default prometheus config - i added some custom scripts to fetch some extra metrics i got the error again.
Did you also modify the prometheus config with extra jobs to get other metrics into the dashboard?
Ok - Me too. So i think it is Prometheus.
What interval do you check the custom metrics and are they using apache for their communication? (Something like RevereProxy / ProxyPass?)
I have some PHP scripts fetching me data with fping each 5 secs. The PHP script is executed by apache somewhere on /var/www