General discussion on installation and configuration of SOGo

Text archives Help


[SOGo] Error on sogo.log


Chronological Thread 
  • From: "Odhiambo Washington" ( ) < >
  • To:
  • Subject: [SOGo] Error on sogo.log
  • Date: Wed, 10 Apr 2019 18:10:00 +0300
  • Dmarc-filter: OpenDMARC Filter v1.2.0 mail.inverse.ca 1E5691DE522B

I am seeing this on sogo.log for v4.0.7 when a user is accessing their mail:

Apr 10 17:35:45 sogod [3631]: 41.90.4.204 "POST /SOGo/connect HTTP/1.1" 200 66/86 0.329 - - -
Apr 10 17:35:47 sogod [3631]: 41.90.4.204 "GET /SOGo/so/ HTTP/1.1" 302 0/0 0.023 - - -
Apr 10 17:35:47 sogod [3631]: 41.90.4.204 "GET /SOGo/so/ /view HTTP/1.1" 302 0/0 0.040 - - -
Apr 10 17:35:47 sogod [3631]: 41.90.4.204 "GET /SOGo/so/ /Mail HTTP/1.1" 302 0/0 0.003 - - -
Apr 10 17:35:47 sogod [3631]: 41.90.4.204 "GET /SOGo/so/ /Mail/view HTTP/1.1" 200 19085/0 0.095 82184 76% -
Apr 10 17:35:48 sogod [3631]: 41.90.4.204 "GET /SOGo/so/ /Calendar/alarmslist?browserTime=1554906941 HTTP/1.1" 200 63/0 0.088 - - -
Apr 10 17:35:49 sogod [5211]: 41.90.4.204 "GET /SOGo/so/ /Mail/0/view HTTP/1.1" 200 1135/0 0.690 - - -
2019-04-10 17:35:50.534 sogod[5211:101429] parseTimeZone: cannot parse time notation 'GMT'


Where could that be coming from? That time format is not consistent with the ones above it!
Then why is it talking about GMT when in my sogo.conf I have SOGoTimeZone = Africa/Nairobi;  ???

--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)


  • [SOGo] Error on sogo.log, Odhiambo Washington, 04/10/2019

Archive powered by MHonArc 2.6.18.

Top of page