View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004739||SOGo||Backend Calendar||public||2019-04-23 20:18||2019-04-27 20:51|
|Platform||[Server] Linux||OS||Debian||OS Version||8 (Jessie)|
|Summary||0004739: Calendar made public unreachable once access to DB tears down|
Afer activating public calendars and doing some testing to load the exported ics onto a website, it works for the first few minutes and then Sogo starts giving 404.
Activating debug, I can only see that sogo triggers the 404 without attempting to connect to the DB, even when there are connections established.
To get it working again I need to reconnect to the website with that particular user.
I am using LDAP auth + MySQL DB.
Problem happens both with memcached running or stopped.
|Steps To Reproduce|
Create a public calendar, curl it to verify you can download it from wherever.
Wait about 5-10 minutes, the curl command now fails and return 404.
Check Sogo logs, it returns 404 and no request is made to the database.
If I (re)initiate a connection to the website with the account of the user sharing the calendar, my curl requests are working again for few minutes.
On success, when access to the user sharing the calendar is fresh:
Apr 23 20:58:13 sogod : |SOGo| starting method 'GET' on uri '/SOGo/dav/public/contact/Calendar/602B-5CBDED80-1-73939F80.ics'
When it fails:
Apr 23 21:08:23 sogod : |SOGo| starting method 'GET' on uri '/SOGo/dav/public/contact/Calendar/602B-5CBDED80-1-73939F80.ics'
Testing locally against sogo port directly gives same results:
Apr 23 21:13:45 sogod : |SOGo| starting method 'GET' on uri '/SOGo/dav/public/contact/Calendar/602B-5CBDED80-1-73939F80.ics'
|Tags||No tags attached.|
Sorry I forgot to amend the title. I thought it was related to DB connection, but I could reproduce the error with active established links to the DB, so I don't think it's related any more.
Also almost everytime when attempting to reconnect with the user sharing the calendar I get:
An error occurred during object publishing
tried to access private object (0x0x563e667b4eb0, SoClass=SOGoContactFolders)
I can reproduce this on a fresh install with restore, after switching to Postgres.
I got another instance running elsewhere without this issue.
Ok, I eventually figured it out. Problem was coming from the use of 'bindAsCurrentUser = YES;' in my configuration. This will partially break access to SOGo when trying to access a public calendar of another user after few minutes.