Quoting James Valleroy (2019-01-15 02:18:37) > Package: radicale > Version: 2.1.11-2 > Severity: normal > > I enabled the radicale config for uwsgi, and then restarted uwsgi, > which failed to start. > > # cat /var/log/uwsgi/app/radicale.log > Mon Jan 14 20:03:06 2019 - *** Starting uWSGI 2.0.17.1-debian (64bit) on [Mon > Jan 14 20:03:06 2019] *** > Mon Jan 14 20:03:06 2019 - compiled with version: 8.2.0 on 27 December 2018 > 16:37:18 > Mon Jan 14 20:03:06 2019 - os: Linux-4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 > (2018-12-22) > Mon Jan 14 20:03:06 2019 - nodename: compbook > Mon Jan 14 20:03:06 2019 - machine: x86_64 > Mon Jan 14 20:03:06 2019 - clock source: unix > Mon Jan 14 20:03:06 2019 - pcre jit disabled > Mon Jan 14 20:03:06 2019 - detected number of CPU cores: 4 > Mon Jan 14 20:03:06 2019 - current working directory: / > Mon Jan 14 20:03:06 2019 - writing pidfile to /run/uwsgi/app/radicale/pid > Mon Jan 14 20:03:06 2019 - detected binary path: /usr/bin/uwsgi-core > Mon Jan 14 20:03:06 2019 - chdir() to /var/lib/radicale/collections > Mon Jan 14 20:03:06 2019 - chdir(): No such file or directory [core/uwsgi.c > line 2631] > > > The uwsgi config shipped in radicale 2.x package tries to chdir to > /var/lib/radicale/collections. > > There is a step to create /var/lib/radicale, but I think it needs to > be moved before the chdir, and to also create the collections > directory.
Ohh, good catch! I remember adjusting that chdir was one of the last adjustments I did - but clearly was too focused on handling migrations carefully and forgot to take new installations into account. New fixed release should be on its way now... - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
