Hi Daniel,

On Thu, Nov 22, 2018 at 12:35:59PM +0100, Daniel Pocock wrote:
> Warning: CalDAV: No response status doing webdav sync for calendar foo
> Warning: CalDAV: Error doing webdav sync: undefined
> Warning: There has been an error reading data for calendar: foo.
> However, this error is believed to be minor, so the program will attempt
> to continue. Error code: DAV_REPORT_ERROR. Description: There has been
> an error reading data for calendar:
> https://foo.example.org/davical/caldav.php/foo/home/. It has been
> disabled until it is safe to use it.
> Warning: There has been an error reading data for calendar: foo.
> However, this error is believed to be minor, so the program will attempt
> to continue. Error code: READ_FAILED. Description:

I don't remember ever seeing this from Thunderbird for calendars on a
DAViCal server.

> Simply logging into the web server and doing
> 
>   systemctl restart apache2
> 
> resolves the issue and all the clients work again for another week or so.
> 
> Has anybody else observed this?
> 
> Where should I look for additional logging or clues next time this
> happens?  Should I enable any extra logging options in DAViCal, Apache
> or PostgreSQL?

Well I'd start with the Apache logs: when TB says "no response status",
what does Apache think happened with the request, which status did it
log, anything in the error log?

A default install of the davical package pulls in mod_php, which AFAIK
doesn't keep state between requests; do you use a different PHP
interpreter, or something like a Zend server or memcached? Nothing in
the way davical processes or responds to a request should change from a
webserver restart, really...

If you still think davical may be at fault and want to dig deeper, have
a look at https://wiki.davical.org/index.php/Debugging - I'd recommend
setting $c->dbg["ALL"] = 1; and perhaps limiting things to a single
remote IP. The result is fairly verbose but should show you what the
requests and responses look like, and will provide enough detail to pin
down where things go south on the server side.

Florian

Reply via email to