[Freedombox-discuss] Tracking down the radicale problem.

[Jonas Smedegaard]

Quoting A. F. Cano (2019-03-27 04:18:32)
> chown radicale.radicale /var/lib/radicale
> chown radicale.radicale /var/lib/radicale/collections
> chown radicale.radicale /var/lib/radicale/collections/afc

Safer to delimit user and group with ":" - e.g. like this:

  chown radicale:radicale /var/lib/radicale


> And no wonder, I also have to change /etc/radicale/logging per
> 
> https://wiki.debian.org/Radicale

Please notice that above wiki page documents a different "more 
lightweight serving directly by Radicale [...] discouraged and not well 
tested".

You should probably _not_ follow that guide if you want Radicale run 
(not directly but) with uWSGI proxied with Apache2 - as is the 
recommended in the radicale package and as far as I know the way it is 
setup in FreedomBox.


> install uwsgi-plugin-psgi, libapache2-mod-authnz-external
> 
> (uwsgi, apache2 were already installed)

[...]

> Then I realized that the radicae log file is actually at
> 
> /var/log/uwsgi/app/radicale.log
> 
> but the only warning I found there was:
> 
> Fri Mar 22 16:58:25 2019 - !!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!
> Fri Mar 22 16:58:25 2019 - no request plugin is loaded, you will not be able to manage requests.
> Fri Mar 22 16:58:25 2019 - you may need to install the package for your language of choice, or simply load it with --plugin.
> Fri Mar 22 16:58:25 2019 - !!!!!!!!!!! END OF WARNING !!!!!!!!!!
> 
> Went looking and found this:
> 
> https://stackoverflow.com/questions/20176959/uwsgi-no-request-plugin-is-loaded-you-will-not-be-able-to-manage-requests
> 
> so installed uwsgi-plugins-all.  This pulled 47 dependencies and
> 8 suggestions.

You needed only uwsgi-plugin-python3 (instead of uwsgi-plugin-psgi).

Sorry, that information was wrong in the radicale package documentation 
and has now been corrected for the next release: 
https://salsa.debian.org/debian/radicale/commit/8a1c3db


> And now I'm out of ideas.  I set up a DAV groupware resource calendar 
> from Korganizer on the same computer with login credentials as myself 
> (regular user, existing user account), configure the resource 
> manually, added the resource, with remote URL https://<computer 
> name>/radicale/afc/calendar.ics (the same as used to work in the 
> FreedomBox before it stopped working) but when I "fetch" it comes back 
> with an "There was a problem with the request. HTTP error (0).

If you have configured Radicale to run with uWSGI (only, not also 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.


> Does anyone have any idea what I'm missing? Somewhere I read that the 
> data needed to be migrated in the upgrade from radicale 1.x to 2.x but 
> it didn't say how.

It is mentioned in /usr/share/doc/radicale/NEWS.Debian.gz

Where did you try look for the information?


 - Jonas

-- 
 * 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...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/freedombox-discuss/attachments/20190327/b16f085b/attachment.sig>