You are not logged in.

#1 2011-01-24 18:24:43

maxi_jac
Member
From: France
Registered: 2008-08-02
Posts: 72

prosody config bug ?

Hi,

I updated my prosody package from community recently and now it won't work anymore.

It seems the config needs a pid_file variable the stock file does not have.
Setting it to /var/run/prosody/prosody.pid did not work for me.

It prevents the binary from complaining but never forks to background, "prosodyctl start" neither.

I did a clean install of course.

So, anything I missed ?

Offline

#2 2011-01-25 18:09:44

sergej
Package Maintainer (PM)
From: Russia, Voronezh
Registered: 2006-03-21
Posts: 69

Re: prosody config bug ?

You should add it after

admins = { }
pidfile = "/var/run/prosody/prosody.pid"

I'll try to fix it in package

Offline

#3 2015-02-12 06:34:48

schmodd
Member
Registered: 2015-02-12
Posts: 35

Re: prosody config bug ?

I am having a problem with prosody and its pidfile too.

I installed the package on a clean arch install (pacman -S prosody lua51-sec lua51-zlib).
If I try to start prosody via "systemctl start prosody.service" it fails.
Error:
mod_posix: Couldn't write pidfile at /run/prosody/prosody.pid; /run/prosody/prosody.pid: No such file or directory
general: Shutting down: Couldn't write pidfile

Arch wiki states that I should NOT alter anything regarding that pidfile (https://wiki.archlinux.org/index.php/pr … figuration).
So how is prosody supposed to work if it can't write its pidfile?

Offline

#4 2015-02-12 06:38:17

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: prosody config bug ?


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

Board footer

Powered by FluxBB