Am 31.08.2015 um 00:13 schrieb Alan Hicks:
Keeping a connection open to LDAP allows much higher throughput so opening a new connection when needed would degrade the service.
but that's no reason DBMail dying when you reboot the LDAP server
LDAP is one of those services that should always be available because it is a core authentication service so don't understand why yours is disconnecting.
you really don't want to restart services left and right on other machines after you reboot the LDAP server after as example a kernel update
Monitoring CAN fix this, nagios is used here at Persistent Objects but any good monitoring software will work by checking if the service is running and restart if not. Completely automatic and transparent to users. Rarely kicks in as dbmail is so reliable. Not sure why you are getting annoyed at dbmail, I would be frustrated at LDAP as it is 100% reliable here.
as said: sometimes servers needs to be rebootet and stable services should just reconnect or *really* die not just stop working, if DBMail can't recover after lost of the LDAP connection it should just exit with a error-status when it no longer works at all
in that case at least supervisors like systemd could restart it automatically
On 30/08/2015 13:03, Matt . wrote:Hi, Anyone a clue about this ? I think some monitoring can't fix this. So I'm figuring out a solution. Cheers, Matthijs 2015-07-27 11:25 GMT+02:00 Matt . <yamakasi....@gmail.com>:Hi Guys, I'm wondering why DBmail needs a restart every time it's disconnected from the ldap server. This actually kinda annoys me because it should just do a lookup if needed and not have the connection open forever and die when it loses it. Anyone a clue why this happens and how to workaround it ? Thanks!
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
