I did an upgrade from 1.2.2 to 1.3.0, and after restarting the service, with the same configuration .GNUstepDefaults that has been working fine, I now get unable to bind errors in /var/log/sogod/sogo.log file, for the bindDN user that I have been using fine for the last year or so.
System is a VM (ESXi 4.0 U2) running Centos 5.5, just did a yum update, using as the repo:
[sogo-nightly-rhel5]
name=Inverse SOGo nightly-build Repository
baseurl=http://inverse.ca/downloads/SOGo/RHEL5/nightly/$basearch
gpgcheck=0
Did see the "known" error about memcached:
memcached-1.4.2-1.el5.i386 from installed has depsolving problems
--> Missing Dependency: libevent-1.1a.so.1 is needed by package memcached-1.4.2-1.el5.i386 (installed)
But I don't think this is related.
Using an LDAP browser like jxplorer, I am able to connect to the window AD tree with that bindDN and password, so I know it's not a problem with the bindDN and bindPassword/bindFields.
FYI my SOGoUserSources looks something like this (sanitized):
SOGoUserSources = (
{
CNFieldName = displayname;
IDFieldName = cn;
IMAPHostFieldName = mailHost;
UIDFieldName = sAMAccountName;
baseDN = "dc=test,dc=internal";
bindDN = "[email protected]";
bindFields = sAMAccountName;
bindPassword = testpassword;
canAuthenticate = YES;
displayName = "Active Directory";
hostname = "IPAddress";
id = directory;
isAddressBook = YES;
port = 389;
}
)
Since I am running this in a VM, I had taken a snapshot before, so did a rollback to 1.2.2, and everything is fine again. So must be something related to the 1.3.0 update.
Any idea what went wrong? Or have others done the update without any problems?
Thanks.
System is a VM (ESXi 4.0 U2) running Centos 5.5, just did a yum update, using as the repo:
[sogo-nightly-rhel5]
name=Inverse SOGo nightly-build Repository
baseurl=http://inverse.ca/downloads/SOGo/RHEL5/nightly/$basearch
gpgcheck=0
Did see the "known" error about memcached:
memcached-1.4.2-1.el5.i386 from installed has depsolving problems
--> Missing Dependency: libevent-1.1a.so.1 is needed by package memcached-1.4.2-1.el5.i386 (installed)
But I don't think this is related.
Using an LDAP browser like jxplorer, I am able to connect to the window AD tree with that bindDN and password, so I know it's not a problem with the bindDN and bindPassword/bindFields.
FYI my SOGoUserSources looks something like this (sanitized):
SOGoUserSources = (
{
CNFieldName = displayname;
IDFieldName = cn;
IMAPHostFieldName = mailHost;
UIDFieldName = sAMAccountName;
baseDN = "dc=test,dc=internal";
bindDN = "[email protected]";
bindFields = sAMAccountName;
bindPassword = testpassword;
canAuthenticate = YES;
displayName = "Active Directory";
hostname = "IPAddress";
id = directory;
isAddressBook = YES;
port = 389;
}
)
Since I am running this in a VM, I had taken a snapshot before, so did a rollback to 1.2.2, and everything is fine again. So must be something related to the 1.3.0 update.
Any idea what went wrong? Or have others done the update without any problems?
Thanks.
-- [email protected] https://inverse.ca/sogo/lists
