View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004329||SOGo||with SOGo||public||2017-11-01 09:50||2017-11-10 14:34|
|Platform||[Server] Linux||OS||RHEL/CentOS||OS Version||7|
|Fixed in Version||4.0.0|
|Summary||0004329: "ERROR(-[NSNull(misc) forwardInvocation:]): called selector stringByTrimmingSpaces on NSNull !" filling sogo.log|
This seems just a warning (despite the "ERROR" at the beginning...) but at about 5 to 15 messages / minute, the log grows, and it complicates really all searches and debug with it !!
But I see today that the messages are logged also when no web clients are connected (no "POST..." message), but also when activesync ping :
2017-11-01 10:33:17.358 sogod ERROR(-[NSNull(misc) forwardInvocation:]): called selector stringByTrimmingSpaces on NSNull !
But, NOT when the devices refresh themselves by activesync (messages "POST /SOGo/Microsoft-Server-ActiveSync?User=xxxxxx&DeviceId=XXXXXXXXXX&DeviceType=iPhone&Cmd=Ping HTTP/1.1" 200 13/0 10.582 - - -8K" generate no "stringByTrimmingSpaces..." error)
What is the reason of this message and what can be done to avoid it ?
|Tags||No tags attached.|
You can try to find a possible cause by enabling verbose logging:
SOGoDebugRequests = YES;
LDAPDebugEnabled = YES;
Check sogo.log for the first occurrence of "NSNull(misc) forwardInvocation:" after starting sogod with above parameters.
Well : I can't for now restart sogo on prod server, but I activate debug on a test server.
which result is:
the "NULL" results are mail4 and mail5 (the user as only 3 aliases), I guess this is the problem : here the ERROR appears 2 times, when on the prod server, the users have no aliases, and it appears 5 times. I suppose you must test the field before pass it to stringByTrimmingSpaces ?
Unfortunatly, I couldn't reproduce the problem with EAS. Connecting a device with activesync on the test server does not produce errors as on the prod server. To be confirmed later if the error is fixed for the imap fetch.
Please try the latest nightly build and let me know if it solves the issue.
And can you tell us when the version 3.2.11 will be available in the repos ?
You can install the latest nightly RPM builds.
Oh sorry, I forgot to make a difference between "last version" and "last nightly build" :) so I was waiting for 3.2.11.
Well, it seems good ! I continue to check the log for some days.
Just, the log being more clear now, I noticed a message "parseTimeZone: cannot parse time notation 'GMT'", I think that it is not in relation with this last built but since last update (3.2.9 -> 3.2.10) but had not seen it before (message hidden into all this stringByTrimmingSpaces...) May I open a new ticket, as I didn't found reference of this error in bug reports since v1.3.xx ? Or would you have a (quick) solution ?
If you isolate the event that causes the error, than please open an ticket and attached the event source (vCalendar).
|2017-11-01 09:50||fsoyer||New Issue|
|2017-11-02 06:38||tfu||Note Added: 0012406|
|2017-11-02 09:00||fsoyer||Note Added: 0012407|
|2017-11-09 02:41||francis||Changeset attached||=> sogo master 38d4a268|
|2017-11-09 02:41||francis||Assigned To||=> francis|
|2017-11-09 02:41||francis||Resolution||open => fixed|
|2017-11-09 23:19||francis||Note Added: 0012420|
|2017-11-10 13:54||fsoyer||Note Added: 0012421|
|2017-11-10 13:57||francis||Note Added: 0012422|
|2017-11-10 14:04||fsoyer||Note Added: 0012423|
|2017-11-10 14:30||fsoyer||Note Added: 0012424|
|2017-11-10 14:34||francis||Note Added: 0012425|
|2017-11-10 14:34||francis||Status||new => resolved|
|2017-11-10 14:34||francis||Fixed in Version||=> 4.0.0|