Hi Paul,

here's a few hints:

2013-06-26 16:30:54.652 sogod[68616] -[NGLdapConnection 
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base ��N filter 
��N for attrs �OM
2013-06-26 16:30:54.653 sogod[68616] -[NGLdapConnection 
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base  filter ��N 
for attrs �OM
2013-06-26 16:30:54.656 sogod[68616] -[NGLdapConnection 
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base ��N filter 
��N for attrs �OM

Don't mind those, the ldap debugging code in SOPE doesn't work too well as you can see.


Jun 26 16:30:54 sogod [68616]: <0x09DF6EC8[SOGoUserFolder]:sogo> baseURL: 
name=sogo (container=SOGo)
  container: /SOGo -- http://team.atlantisservices.net/SOGo/so/sogo/Mail/view
  own: /SOGo/so/sogo
Jun 26 16:30:54 sogod [68616]: <0x0x80c171568[NGLdapConnection]> Using 
ldap_initialize for LDAP URL: ldap://<LDAP IP>:389
2013-06-26 16:30:54.727 sogod[68616] -[NGLdapConnection 
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base ��N filter 
��N for attrs �OM
2013-06-26 16:30:54.729 sogod[68616] WARNING: IMAP4 connection pooling is 
disabled!
Jun 26 16:31:54 sogod [68615]: [WARN] <0x0x809cc3568[WOWatchDogChild]> pid 
68616 has been hanging in the same request for 1 minutes
Jun 26 16:32:54 sogod [68615]: [WARN] <0x0x809cc3568[WOWatchDogChild]> pid 
68616 has been hanging in the same request for 2 minutes

From this, I would say that the LDAP requests worked, but that SOGo is somehow waiting for the imap server. One thing you could do is looking at the LDAP queries to make sure that they return the expected results. You can do this by either dumpimg the ldap traffic using tcpdump/wireshark, or by enabling query logging on the LDAP side (olcLogLevel: stats).

Is there any relevant information in the imap server logs? You could also try to dump the imap traffic to see what is going on.

You could also attach to the "hanging" process using a process tracer (ktrace, truss) and see which system call it is blocking on. If the process blocks while doing operations on a filedescriptor, you'll need to use lsof to map the fd the a real file (or socket).




--
[email protected]
https://inverse.ca/sogo/lists

Reply via email to