Hi Jon, Quoting Jon Kristensen (2016-06-21 20:51:58) > I noticed that Radicale failed to start when I installed it using > "apt-get install radicale". > > The reason turned out to be that the /var/log/radicale directory was > missing. > > "mkdir /var/log/radicale" made it possible for me to start Radicale. I > realized that this was a problem when running the radicale program > failed with a Python stack trace (which I, unfortunately, don't have > access to now). > > Could this be a bug in the Debian installation script, perhaps? > > I was using a fully upgraded Debian 8 in a VPS. > > Output of "uname -a": > > Linux Debian-85-jessie-64-minimal 3.16.0-4-amd64 #1 SMP Debian > 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux
Thanks for the bugreport, and the additional, valuable details. Radicale should be usable in multiple ways. Upstream by default has it setup to run by a regular user inside $HOME, but Debian package offers to run it as a sysV daemon. As a system-wide daemon the Debian way, the following should work: 1) Enable daemon in /etc/default/radicale 2) Start daemon with "service radicale start" Logdir should then be created if missing. If above failed, then it is a bug in the package, but if you chose to use Radicale in different ways than offered by the Debian package then it is on you to make it work. Therefore: How did you try to start Radicale which failed for you but succeeded by creating that logdir? Regards, - 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
