1

Topic: fail log sogo after migration

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 9.6
- Linux/BSD distribution name and version: ubuntu 16.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): default
- Manage mail accounts with iRedAdmin-Pro? no
- Related log if you're reporting an issue:

Mar 24 16:35:03 sogod [2839]: |SOGo| starting method 'POST' on uri '/SOGo/connect'
Mar 24 16:35:03 sogod [2839]: <0x0x5599feaa03e0[SOGoCache]> Cache cleanup interval set every 300.000000 seconds
Mar 24 16:35:03 sogod [2839]: <0x0x5599feaa03e0[SOGoCache]> Using host(s) '127.0.0.1' as server(s)
Mar 24 16:35:03 sogod [2839]: [WARN] <0x0x7f3d2233dcc0[WOxElemBuilder]> could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder
Mar 24 16:35:03 sogod [2839]: <0x0x5599ff0ba680[NGLdapConnection]> Using ldap_initialize for LDAP URL: ldap://127.0.0.1:389
Mar 24 16:35:03 sogod [2839]: <0x0x5599ff10e960[NGLdapConnection]> Using ldap_initialize for LDAP URL: ldap://127.0.0.1:389
2017-03-24 16:35:03.429 sogod[2839] -[NGLdapConnection _searchAtBaseDN:qualifier:attributes:scope:]: search at base '' filter '(objectClass=*)' for attrs 'subschemaSubentry'
2017-03-24 16:35:03.430 sogod[2839] -[NGLdapConnection _searchAtBaseDN:qualifier:attributes:scope:]: search at base 'cn=Subschema' filter '(objectClass=*)' for attrs 'objectclasses'
2017-03-24 16:35:03.433 sogod[2839] -[NGLdapConnection _searchAtBaseDN:qualifier:attributes:scope:]: search at base 'o=domains,dc=xxx,dc=fr' filter '(&(mail=eric@xxx.fr)(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=sogo))' for attrs 'dn'
Mar 24 16:35:03 sogod [2839]: SOGoRootPage Login from '78.123.456.53' for user 'eric@xxx.fr' might not have worked - password policy: 65535  grace: -1  expire: -1  bound: 0
Mar 24 16:35:03 sogod [2839]: |SOGo| request took 0.016288 seconds to execute
====

hello
i just migrate old iredmail server many time upgrage to 9.5 to new one with 9.6

all find, i can login in roundcube, receive and send mail imap with password store in ldap.
But nope for Sogo  wrong credentials .

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: fail log sogo after migration

Try to reset its password.

3

Re: fail log sogo after migration

It is the same trouble after change password
no caldav and no webmail SOGo

all other ok
how sogo take auth ? in ldap or sync from ?

some idea to debug ?

regards

4

Re: fail log sogo after migration

SOGo authenticates user against LDAP. Please turn on debug mode in SOGo and try again.
FYI: http://www.iredmail.org/docs/debug.sogo.html

5 (edited by Tonton 2017-03-29 16:55:22)

Re: fail log sogo after migration

ZhangHuangbin wrote:

SOGo authenticates user against LDAP. Please turn on debug mode in SOGo and try again.
FYI: http://www.iredmail.org/docs/debug.sogo.html

Yes itis the log in my first post with
LDAPDebugEnabled = YES;

I will try the other

regards

    SOGoDebugRequests = YES;
    SOGoEASDebugEnabled = YES;
    //ImapDebugEnabled = YES;
    LDAPDebugEnabled = YES;
    //MySQL4DebugEnabled = YES;
    //PGDebugEnabled = YES;

i can login after update or not password for existing user but if i create new one it is working

Mar 29 04:45:11 sogod [17313]: |SOGo| starting method 'POST' on uri '/SOGo/connect'
Mar 29 04:45:11 sogod [17313]: <0x0x563f5a8be790[NGLdapConnection]> Using ldap_initialize for LDAP URL: ldap://127.0.0.1:389
Mar 29 04:45:11 sogod [17313]: <0x0x563f5acddff0[NGLdapConnection]> Using ldap_initialize for LDAP URL: ldap://127.0.0.1:389
2017-03-29 04:45:11.848 sogod[17313] -[NGLdapConnection _searchAtBaseDN:qualifier:attributes:scope:]: search at base 'o=domains,dc=XXX,dc=fr' filter '(&(mail=support@AAA.com)(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=sogo))' for attrs 'dn'
Mar 29 04:45:11 sogod [17313]: SOGoRootPage Login from '5.51.63.232' for user 'support@AAA.com' might not have worked - password policy: 65535  grace: -1  expire: -1  bound: 0
Mar 29 04:45:11 sogod [17313]: |SOGo| request took 0.057787 seconds to execute
Mar 29 04:45:11 sogod [17313]: 5.51.63.232 "POST /SOGo/connect HTTP/1.0" 403 34/76 0.059 - - 0
Mar 29 04:46:40 sogod [17313]: |SOGo| starting method 'POST' on uri '/SOGo/connect'
Mar 29 04:46:40 sogod [17313]: <0x0x563f5ac3c3c0[NGLdapConnection]> Using ldap_initialize for LDAP URL: ldap://127.0.0.1:389
Mar 29 04:46:40 sogod [17313]: <0x0x563f5a77ca40[NGLdapConnection]> Using ldap_initialize for LDAP URL: ldap://127.0.0.1:389
2017-03-29 04:46:40.986 sogod[17313] -[NGLdapConnection _searchAtBaseDN:qualifier:attributes:scope:]: search at base 'o=domains,dc=XXX,dc=fr' filter '(&(mail=newuser@AAA.com)(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=sogo))' for attrs 'dn'
Mar 29 04:46:41 sogod [17313]: SOGoRootPage successful login from '5.51.63.232' for user 'newuser@AAA.com' - expire = -1  grace = -1
Mar 29 04:46:41 sogod [17313]: <0x0x563f5a9f69f0[NGLdapConnection]> Using ldap_initialize for LDAP URL: ldap://127.0.0.1:389
2017-03-29 04:46:41.435 sogod[17313] -[NGLdapConnection _searchAtBaseDN:qualifier:attributes:scope:]: search at base 'o=domains,dc=XXX,dc=fr' filter '(&(|(mail=newuser@AAA.com)(mail=newuser@AAA.com))(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=sogo))' for attrs '*'
Mar 29 04:46:42 sogod [17313]: [WARN] <0x0x563f5ab96840[SOGoWebDAVAclManager]> entry '{DAV:}write' already exists in DAV permissions table
Mar 29 04:46:42 sogod [17313]: [WARN] <0x0x563f5ab96840[SOGoWebDAVAclManager]> entry '{DAV:}write-properties' already exists in DAV permissions table
Mar 29 04:46:42 sogod [17313]: [WARN] <0x0x563f5ab96840[SOGoWebDAVAclManager]> entry '{DAV:}write-content' already exists in DAV permissions table
Mar 29 04:46:42 sogod [17313]: |SOGo| request took 1.378530 seconds to execute

T.

6

Re: fail log sogo after migration

Similar issues were reported in this forum and SOGo mailing list before, but no clear answer from SOGo developers. SOGo log doesn't clearly tell you what the problem is. so i'm afraid that i don't have an answer for you in this case.

Usually account works after resetting password in this case.