Re: [SOGo] object not found: SOGo = UID
Hello MJ Am 2014-11-26 um 15:29 schrieb heupink: We've upgraded to 2.2.10 yesterday. Today I created a new user, and tried logging on. Did not work due to object not found: SOGo = UID. Tried logging on in roundcube: no problem. Searched the mailinglist, and found some causes / solutions, none of which applied to us. Then I found a suggestion to restart memcached, and that solved the issue immediately. Can we agree that this is a bug? Worth submitting a bugreport for this? Yes, please submit a bug report. This should not happen. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
[SOGo] object not found: SOGo = UID
Hi, We've upgraded to 2.2.10 yesterday. Today I created a new user, and tried logging on. Did not work due to object not found: SOGo = UID. Tried logging on in roundcube: no problem. Searched the mailinglist, and found some causes / solutions, none of which applied to us. Then I found a suggestion to restart memcached, and that solved the issue immediately. Can we agree that this is a bug? Worth submitting a bugreport for this? MJ -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] object not found: SOGo = UID [revisited, SOLVED (at least for me)]
Whenever you play with sogo (or its configuration), always restart memcached as well, i.e. every time you restart sogod restart also memcached. Marcel Waldvogel wrote, On 10/09/2013 16:51: Hello [This is in case anyone is running into the problem in the future. Maybe the friendly guys at inverse will also fix the root cause of this problem.] After a restart of my database server, trying to login resulted in the 404 error object not found: username, where username was the user's login name. Trying to restart sogod did not help, neither did another restart of postgresql. The log did not show new error messages, either (see below), the LDAP solution from the object not found thread in January did not help either.. Looking at the log, it seemed that some users could still log in. After some playing around, restarting memcached brought the solution, the system is running fine as ever. @inverse: Could it be that if some requests are aborted due the DB shutdown, an invalid value is stored in memcached? -Marcel 2013-09-10 16:27:35.259 sogod[24674] WARNING(-[NSNull(misc) count]): called NSNull -count (returns 0) !!! 111.111.111.111 - - [10/Sep/2013:16:27:35 GMT] GET /SOGo/so/ HTTP/1.1 200 4438/0 0.021 12450 64% 0 2013-09-10 16:27:39.257 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): called selector objectForKey: on NSNull ! 2013-09-10 16:27:39.259 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): called selector setObject:forKey: on NSNull ! 2013-09-10 16:27:39.259 sogod[24674] didn't set return value for type 'v' Sep 10 16:27:39 sogod [24674]: SOGoRootPage successful login from '111.111.111.111' for user 'username' - expire = -1 grace = -1 111.111.111.111 - - [10/Sep/2013:16:27:39 GMT] POST /SOGo/connect HTTP/1.1 200 27/47 0.049 - - 0 2013-09-10 16:27:39.549 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): called selector objectForKey: on NSNull ! 2013-09-10 16:27:39.551 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): called selector setObject:forKey: on NSNull ! 2013-09-10 16:27:39.551 sogod[24674] didn't set return value for type 'v' 111.111.111.111 - - [10/Sep/2013:16:27:39 GMT] GET /SOGo/so/username HTTP/1.1 404 24/0 0.006 - - 0 2013-09-10 16:33:23.476 sogod[24674] File NSKeyValueCoding.m: 913. In -[NSObject(KeyValueCoding) valuesForKeys:] This method is deprecated, use -dictionaryWithValuesForKeys: -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] object not found: SOGo = UID [revisited, SOLVED (at least for me)]
Hello [This is in case anyone is running into the problem in the future. Maybe the friendly guys at inverse will also fix the root cause of this problem.] After a restart of my database server, trying to login resulted in the 404 error object not found: username, where username was the user's login name. Trying to restart sogod did not help, neither did another restart of postgresql. The log did not show new error messages, either (see below), the LDAP solution from the object not found thread in January did not help either.. Looking at the log, it seemed that some users could still log in. After some playing around, restarting memcached brought the solution, the system is running fine as ever. @inverse: Could it be that if some requests are aborted due the DB shutdown, an invalid value is stored in memcached? -Marcel 2013-09-10 16:27:35.259 sogod[24674] WARNING(-[NSNull(misc) count]): called NSNull -count (returns 0) !!! 111.111.111.111 - - [10/Sep/2013:16:27:35 GMT] GET /SOGo/so/ HTTP/1.1 200 4438/0 0.021 12450 64% 0 2013-09-10 16:27:39.257 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): called selector objectForKey: on NSNull ! 2013-09-10 16:27:39.259 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): called selector setObject:forKey: on NSNull ! 2013-09-10 16:27:39.259 sogod[24674] didn't set return value for type 'v' Sep 10 16:27:39 sogod [24674]: SOGoRootPage successful login from '111.111.111.111' for user 'username' - expire = -1 grace = -1 111.111.111.111 - - [10/Sep/2013:16:27:39 GMT] POST /SOGo/connect HTTP/1.1 200 27/47 0.049 - - 0 2013-09-10 16:27:39.549 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): called selector objectForKey: on NSNull ! 2013-09-10 16:27:39.551 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): called selector setObject:forKey: on NSNull ! 2013-09-10 16:27:39.551 sogod[24674] didn't set return value for type 'v' 111.111.111.111 - - [10/Sep/2013:16:27:39 GMT] GET /SOGo/so/username HTTP/1.1 404 24/0 0.006 - - 0 2013-09-10 16:33:23.476 sogod[24674] File NSKeyValueCoding.m: 913. In -[NSObject(KeyValueCoding) valuesForKeys:] This method is deprecated, use -dictionaryWithValuesForKeys: smime.p7s Description: S/MIME cryptographic signature
Re: [SOGo] object not found: SOGo = UID
Hi, Do you have imap Pooling enabled ? Disabling this helps me out. Reloading the site without username after failed login can also be a quick help. Perhaps the Cache Time Parameter can also help, but this ist not tested. Hope this can help Best Philipp v. Strobl-Albeg - PILARKTO.NET - Am 24.01.2013 um 17:11 schrieb Ronald J. Yacketta yacke...@potsdam.edu: Donny, Thanks for the reply! Wish this was the case, but we have been running SOGo in production for 2+ weeks without any configuration changes. Everything has been fine until this week when SOGo usage increased due to students and faculty returning from break. A restored of SOGo and memcached seems to have resolved the issue for the time being, a bit worried that this issue will creep up over the next few days of usage. -Ron On Thursday, 24 January, 2013 11:06 EST, Donny Brooks dbro...@mdah.state.ms.us wrote: On 01/24/2013 07:57 AM, Ronald J. Yacketta wrote: We have been running SOGo in production mode for 2 without any configuration changes to SOGo, Mail or LDAP. This week have been receiving reports of user getting error 'object not found: SOGo = username' when accessing the calendar tab. Log shows the following: Jan 24 08:46:55 sogod [9353]: SOGoRootPage successful login for user 'UID' - expire = -1 grace = -1 137.143.160.6 - - [24/Jan/2013:08:46:55 GMT] POST /SOGo/connect HTTP/1.1 200 27/43 0.076 - - 688K 2013-01-24 08:46:55.636 sogod[9310] ERROR(-[NSNull(misc) forwardInvocation:]): called selector objectForKey: on NSNull ! 2013-01-24 08:46:55.662 sogod[9310] ERROR(-[NSNull(misc) forwardInvocation:]): called selector setObject:forKey: on NSNull ! 2013-01-24 08:46:55.662 sogod[9310] didn't set return value for type 'v' 137.143.160.6 - - [24/Jan/2013:08:46:55 GMT] GET /SOGo/UIDHTTP/1.1 404 36/0 0.028 - - 1M Searching list archives returns results indicating that the user does not exist, but in this case the user is one of the first to use SOGo in production and has been doing all of our campus training. I had a similar issue yesterday but it was on our new machine. Ludovic sent this in reply to my message: That means your SOGoUserSources is wrong. Correctly set IDFieldName and UIDFieldName. -- Ludovic Marcotte +1.514.755.3630 ::www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] object not found: SOGo = UID aka SOLVED: Thunderbird ESR 10.0.7 (+ Lightning 1.2.3) and SOGo 1.3.18a/2.0.2 (which is in fact not solved) aka missing VCALENDAR component
Hi, i have to confess, that the imap pooling isn't the problem. After having (imap pooling disabled) the object not found failure again, i checked the sogo config for ldap auth, which Ludovic and other recommended. For testing purpose do a ldapsearch with the exact (copy paste) paramteres from the sogo-config. For me the problem seems a additional ldap-filter that was wrongly interpreted by a update-script or else: businessCategory= pro to apos;proapos; Testing with ldapsearch gives no result with the old filter. (CentOS5) ldapsearch -x -D uid=UID,BASEDN from sogo-config -b BASEDN from sogo-config -w - ((objectClass=*)(businessCategory=apos;proapos;)) Now it does. ldapsearch -x -D uid=UID,BASEDN from sogo-config -b BASEDN from sogo-config -w - ((objectClass=*)(businessCategory=pro)) Or do you have aonther solution found for this ? Also check the bindAsCurrentUser and canAuthenticate Parameter (look also at the lists for [SOGo] object not found after login) Best regards to Potsdam from Stuttgart ;-) Philipp Philipp v. Strobl.-Albeg - PILAKRTO.NET - Am 24.01.2013 17:11, schrieb Ronald J. Yacketta: Donny, Thanks for the reply! Wish this was the case, but we have been running SOGo in production for 2+ weeks without any configuration changes. Everything has been fine until this week when SOGo usage increased due to students and faculty returning from break. A restored of SOGo and memcached seems to have resolved the issue for the time being, a bit worried that this issue will creep up over the next few days of usage. -Ron On Thursday, 24 January, 2013 11:06 EST, Donny Brooksdbro...@mdah.state.ms.us wrote: On 01/24/2013 07:57 AM, Ronald J. Yacketta wrote: We have been running SOGo in production mode for 2 without any configuration changes to SOGo, Mail or LDAP. This week have been receiving reports of user getting error 'object not found: SOGo = username' when accessing the calendar tab. Log shows the following: Jan 24 08:46:55 sogod [9353]: SOGoRootPage successful login for user 'UID' - expire = -1 grace = -1 137.143.160.6 - - [24/Jan/2013:08:46:55 GMT] POST /SOGo/connect HTTP/1.1 200 27/43 0.076 - - 688K 2013-01-24 08:46:55.636 sogod[9310] ERROR(-[NSNull(misc) forwardInvocation:]): called selector objectForKey: on NSNull ! 2013-01-24 08:46:55.662 sogod[9310] ERROR(-[NSNull(misc) forwardInvocation:]): called selector setObject:forKey: on NSNull ! 2013-01-24 08:46:55.662 sogod[9310] didn't set return value for type 'v' 137.143.160.6 - - [24/Jan/2013:08:46:55 GMT] GET /SOGo/UIDHTTP/1.1 404 36/0 0.028 - - 1M Searching list archives returns results indicating that the user does not exist, but in this case the user is one of the first to use SOGo in production and has been doing all of our campus training. I had a similar issue yesterday but it was on our new machine. Ludovic sent this in reply to my message: That means your SOGoUserSources is wrong. Correctly set IDFieldName and UIDFieldName. -- Ludovic Marcotte +1.514.755.3630 ::www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] object not found: SOGo = UID
We have been running SOGo in production mode for 2 without any configuration changes to SOGo, Mail or LDAP. This week have been receiving reports of user getting error 'object not found: SOGo = username' when accessing the calendar tab. Log shows the following: Jan 24 08:46:55 sogod [9353]: SOGoRootPage successful login for user 'UID' - expire = -1 grace = -1 137.143.160.6 - - [24/Jan/2013:08:46:55 GMT] POST /SOGo/connect HTTP/1.1 200 27/43 0.076 - - 688K 2013-01-24 08:46:55.636 sogod[9310] ERROR(-[NSNull(misc) forwardInvocation:]): called selector objectForKey: on NSNull ! 2013-01-24 08:46:55.662 sogod[9310] ERROR(-[NSNull(misc) forwardInvocation:]): called selector setObject:forKey: on NSNull ! 2013-01-24 08:46:55.662 sogod[9310] didn't set return value for type 'v' 137.143.160.6 - - [24/Jan/2013:08:46:55 GMT] GET /SOGo/UIDHTTP/1.1 404 36/0 0.028 - - 1M Searching list archives returns results indicating that the user does not exist, but in this case the user is one of the first to use SOGo in production and has been doing all of our campus training. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] object not found: SOGo = UID
On 01/24/2013 07:57 AM, Ronald J. Yacketta wrote: We have been running SOGo in production mode for 2 without any configuration changes to SOGo, Mail or LDAP. This week have been receiving reports of user getting error 'object not found: SOGo = username' when accessing the calendar tab. Log shows the following: Jan 24 08:46:55 sogod [9353]: SOGoRootPage successful login for user 'UID' - expire = -1 grace = -1 137.143.160.6 - - [24/Jan/2013:08:46:55 GMT] POST /SOGo/connect HTTP/1.1 200 27/43 0.076 - - 688K 2013-01-24 08:46:55.636 sogod[9310] ERROR(-[NSNull(misc) forwardInvocation:]): called selector objectForKey: on NSNull ! 2013-01-24 08:46:55.662 sogod[9310] ERROR(-[NSNull(misc) forwardInvocation:]): called selector setObject:forKey: on NSNull ! 2013-01-24 08:46:55.662 sogod[9310] didn't set return value for type 'v' 137.143.160.6 - - [24/Jan/2013:08:46:55 GMT] GET /SOGo/UIDHTTP/1.1 404 36/0 0.028 - - 1M Searching list archives returns results indicating that the user does not exist, but in this case the user is one of the first to use SOGo in production and has been doing all of our campus training. I had a similar issue yesterday but it was on our new machine. Ludovic sent this in reply to my message: That means your SOGoUserSources is wrong. Correctly set IDFieldName and UIDFieldName. -- Ludovic Marcotte +1.514.755.3630 ::www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] object not found: SOGo = UID
Donny, Thanks for the reply! Wish this was the case, but we have been running SOGo in production for 2+ weeks without any configuration changes. Everything has been fine until this week when SOGo usage increased due to students and faculty returning from break. A restored of SOGo and memcached seems to have resolved the issue for the time being, a bit worried that this issue will creep up over the next few days of usage. -Ron On Thursday, 24 January, 2013 11:06 EST, Donny Brooks dbro...@mdah.state.ms.us wrote: On 01/24/2013 07:57 AM, Ronald J. Yacketta wrote: We have been running SOGo in production mode for 2 without any configuration changes to SOGo, Mail or LDAP. This week have been receiving reports of user getting error 'object not found: SOGo = username' when accessing the calendar tab. Log shows the following: Jan 24 08:46:55 sogod [9353]: SOGoRootPage successful login for user 'UID' - expire = -1 grace = -1 137.143.160.6 - - [24/Jan/2013:08:46:55 GMT] POST /SOGo/connect HTTP/1.1 200 27/43 0.076 - - 688K 2013-01-24 08:46:55.636 sogod[9310] ERROR(-[NSNull(misc) forwardInvocation:]): called selector objectForKey: on NSNull ! 2013-01-24 08:46:55.662 sogod[9310] ERROR(-[NSNull(misc) forwardInvocation:]): called selector setObject:forKey: on NSNull ! 2013-01-24 08:46:55.662 sogod[9310] didn't set return value for type 'v' 137.143.160.6 - - [24/Jan/2013:08:46:55 GMT] GET /SOGo/UIDHTTP/1.1 404 36/0 0.028 - - 1M Searching list archives returns results indicating that the user does not exist, but in this case the user is one of the first to use SOGo in production and has been doing all of our campus training. I had a similar issue yesterday but it was on our new machine. Ludovic sent this in reply to my message: That means your SOGoUserSources is wrong. Correctly set IDFieldName and UIDFieldName. -- Ludovic Marcotte +1.514.755.3630 ::www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
