[Pkg-xmpp-devel] Bug#900146: prosody fails to write pid file

[Tobias Frost]

On Sat, 26 May 2018 19:52:26 +0000 cloos at jhcloos.com wrote:
> Package: prosody
> Version: 0.10.1-1~bpo9+2
> Severity: important
> 
> ** I'm reporting this from a different box than where it occurrs. **
> 
> My xmpp box runs stretch.  After I added stretch-backports, which
> upgraded prosody to 0.10.1-1~bpo9+2, it would not run.
> 
> The systemd file tried to use /var/run/prosody/prosody.pid for the
pid.
> That matched what the cfg file specified.
> 
> But the directory /var/run/prosody does not exist.
> 
> The systemd file has:
> 
>   RuntimeDirectory=prosody
> 
> but that did not create a usable directory.
> 
> I had to switch both files to put the pid elsewhere (in a permanent
> directory to which the prosody uid has write permission) in order to
> get prosody to start.
> 
> This did not occur with stretch's 0.9.12-2.

As I had the same issue: The cause at my side was that after update I
did not merge the configuration files, as prosody.cfg.lua refers to the
pid file location as well. So the lua file wanted /var/run, while the
init.d file created /run/prosody. 

The fix is to "merge" prosody.cfg.lua.dpkg-dist with prosody.cfg.lua..

--
tobi



>