Hi,
thx for the replies so far.
- "sogo-tool checkup" does not identify misconstructed events
- fortunately no data loss found yet
- could not construct synthetic data for the reproduction until now
But I could identify something odd about the log format on that specific
kinds of entries.
The "invalid day given" entries have a prefix like
2023-10-12 10:55:19.204 sogod[1335:1335] File NSCalendarDate.m: 1553. In ...
The standard log entries have a prefix like
Oct 12 10:55:20 sogod [1337]: IP "GET /SOGo/so/..."
=> the way the date is written differs.
No special debug log setting is active in /etc/sogo/sogo.conf
GCSFolderDebugEnabled = NO;
GCSFolderStoreDebugEnabled = NO;
LDAPDebugEnabled = NO;
MySQL4DebugEnabled = NO;
ImapDebugEnabled = NO;
SMTPDebugEnabled = NO;
OCSFolderManagerSQLDebugEnabled = NO;
SOGoDebugRequests = NO;
SOGoUIxDebugEnabled = NO;
SoDebugBaseURL = NO;
SoDebugObjectTraversal = NO;
SoSecurityManagerDebugEnabled = NO;
WODebugZipResponse = NO;
SOGoDebugLeaks = NO;
SOGoTnefDecoderDebugEnabled = NO;
WODebugHttpTransaction = NO;
WOPageRequestHandlerDebugEnabled = NO;
SoObjectRequestHandlerDebugEnabled = NO;
Hopefully these kind of log messages are only "warnings".
Dirk
Am 11.10.23 um 14:29 schrieb francis ([email protected]):
Hi Dirk
On Oct 11, 2023, at 04:56, Dirk Schäfer ([email protected]) <[email protected]>
wrote:
since updating SOGo to version 5.9.0 we have MANY entries in sogo.log of the
form:
"sogod[2741:2741] File NSCalendarDate.m: 1553. In -[NSCalendarDate
initWithYear:month:day:hour:minute:second:timeZone:] invalid day given - 0"
Do you have an idea?
Does a "sogo-tool checkup" identify misconstructed events?
Francis
