[Freedombox-discuss] Tracking down the radicale problem.
jonas at jones.dk
Tue Apr 2 10:54:16 BST 2019
Quoting A. F. Cano (2019-04-01 22:51:46)
> On Mon, Apr 01, 2019 at 02:20:48AM +0200, Jonas Smedegaard wrote:
> > Quoting A. F. Cano (2019-04-01 00:11:58)
> > > On Wed, Mar 27, 2019 at 08:46:52AM +0100, Jonas Smedegaard wrote:
> > > > If you have configured Radicale to run with uWSGI (only, not also
> ps aux | grep radicale only shows the uwsgi processes, so that part
> should be ok.
Checking which processes listen on relevant tcp ports is more reliable.
> > > > itself listen on same port!) then you should first check the
> > > > Apache2 logs if it received the requests you expect it to. And
> > > > then check uWSGI logs if it received the requests Apache2 was
> > > > configured to proxy.
> Nothing shows up in the apache2 logs when I "fetch" while creating a
> DAV groupware calendar. Instead a get the HTTP error (0). This is
> with Korganizer on the same machine as the radicale server, Debian
Requests not in Apach2 access log most likely failed (check error log)
or did not reach apache2 at all (maybe sniff the network to compare the
REST requests from your client with the REST responses from apache2).
> Nothing shows up [in uwsgi log] either.
Requests not succesfully processed by Apache2 will not reach uwsgi.
> But I get different errors.
Please file bugreports: https://www.debian.org/Bugs/Reporting
Try isolate distinct bugs and file separate bugreports for each against
either Freedombox or Radicale as you suect is more suitable.
The better bugs are filed separately the easier they are to process.
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
More information about the Freedombox-discuss