On Tue, 2017-05-16 at 20:00 +0200, Hanspeter Kunz wrote: > On Tue, 2017-05-16 at 13:00 -0400, Ludovic Marcotte wrote: > > On 2017-05-16 12:09 PM, Hanspeter Kunz ([email protected]) wrote: > > > > > has somebody an idea what is causing those errors? > > > > Look at sogo.log to see if a worker raised an exception and > > restarted. > > yes, that is what I suspected too. but at the time of the proxy > errors > I see absolutely nothing in the logs (sogo, syslog). Sorry, I forgot > to > mention that.
the only errors I see in sogo.log are of the form:
May 16 22:47:03 sogod [15081]: [ERROR]
<0x7f693aa3f130[SOGoAppointmentFolder]:personal> DAV property
'{urn:ietf:params:xml:ns:caldav}schedule-tag' has no matching SQL
field, response could be incomplete
and
May 16 22:48:17 sogod [15081]: [ERROR]
<0x7f693ae56ae0[SOGoAppointmentInboxFolder]:inbox> (-[SOGoGCSFolder
toOneRelationshipKeys]): fetch failed!
but they occur independent of the proxy error.
Best,
Hp
smime.p7s
Description: S/MIME cryptographic signature
