- Previous message: Igor Zhbanov: "Mail cluster with Murder or Perdition and MySQL: what is best and how to do?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
|
|
|
From: Konstantin V. Gavrilenko (no email)
Date: Mon Feb 12 2007 - 10:17:24 EST
Hi list,
I have a problem with my cyrus server that I managed to track to the
presence of the LDAP on the system.
The user and group information is obtained form the LDAP server.
When this functionality is enabled, when I start cyrus I get the
following error:
Feb 12 14:58:12 pingo master[22999]: about to exec /usr/lib/cyrus/idled
Feb 12 14:58:12 pingo master[22963]: ready for work
Feb 12 14:58:12 pingo master[22963]: process 23054 exited, signaled to
death by 13
Feb 12 14:58:12 pingo master[22963]: process 23055 exited, signaled to
death by 13
Feb 12 14:58:12 pingo master[22963]: process 23056 exited, signaled to
death by 13
Feb 12 14:58:14 pingo master[22963]: process 23057 exited, signaled to
death by 13
Feb 12 14:58:14 pingo master[22963]: service imaps pid 23057 in READY
If I change the nssswitch.conf to obtain the group information from
files, cyrus starts up fine.
passwd: files ldap
#group: files ldap
group: files
When I shut down ldap server, leave the nsswitch.conf to obtain the info
from "files ldap" and start cyrus, I get the following error for some
time, and them cyrus starts up normally.
Feb 12 15:13:07 pingo master[32551]: retrying with 1024 (current max)
Feb 12 15:13:07 pingo master[32551]: process started
Feb 12 15:13:07 pingo master[32554]: nss_ldap: failed to bind to LDAP
server ldaps://localhost/: Can't contact LDAP server
Feb 12 15:13:07 pingo master[32554]: nss_ldap: failed to bind to LDAP
server ldaps://localhost/: Can't contact LDAP server
Feb 12 15:13:07 pingo master[32554]: nss_ldap: reconnecting to LDAP
server (sleeping 1 seconds)...
Feb 12 15:13:08 pingo master[32554]: nss_ldap: failed to bind to LDAP
server ldaps://localhost/: Can't contact LDAP server
Feb 12 15:13:08 pingo master[32554]: nss_ldap: reconnecting to LDAP
server (sleeping 2 seconds)...
In both of last cases, I can turn on ldap after the cyrus has started,
and it does not affect its later functionality and works fine.
What can be the problem of initial start up of cyrus and signaled to
death by 13 (broken pipe) ? Has anyone experienced the same problem ?
-- Respectfully, Konstantin V. Gavrilenko Managing Director Arhont Ltd - Information Security web: http://www.arhont.com http://www.wi-foo.com e-mail: tel: +44 (0) 870 44 31337 fax: +44 (0) 117 969 0141 PGP: Key ID - 0xE81824F4 PGP: Server - keyserver.pgp.com ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
|
|
|