Arch Linux

schmodd

Member

Registered: 2015-02-12

Posts: 35

[SOLVED] prosody not able to create pidfile

I am having a problem with prosody and its pidfile.

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?

Update:

I checked  "systemctl -t service" which showed me:

● systemd-tmpfiles-setup.service                  loaded failed failed  Create Volatile Files and Directories

a closer look at "systemctl status systemd-tmpfiles-setup.service" shows:

● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
   Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Do 2015-02-12 08:40:00 CET; 1min 44s ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 164 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
 Main PID: 164 (code=exited, status=1/FAILURE)

Feb 12 08:40:00 upbox systemd-tmpfiles[164]: [/usr/lib/tmpfiles.d/prosody.conf:1] Unknown user '412'.
Feb 12 08:40:00 upbox systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Feb 12 08:40:00 upbox systemd[1]: Failed to start Create Volatile Files and Directories.
Feb 12 08:40:00 upbox systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Feb 12 08:40:00 upbox systemd[1]: systemd-tmpfiles-setup.service failed.

Solution:
I corrected the id of user prosody in /usr/lib/tmpfiles.d/prosody.conf. For some reason "412" was mistakenly put as userid of prosody.
Prosody is starting now!

Last edited by schmodd (2015-03-02 08:39:03)

Issa

Member

From: Berlin

Registered: 2014-12-14

Posts: 19

Re: [SOLVED] prosody not able to create pidfile

I encountered a similar problem. My solution:

I used 'grpck' and 'pwck" to check for problems with existing users. -> I found that I still had a user 'ejabber' who was not removed when I removed 'ejabberd'-package.

I checked the details for the user prosody (seemed to be correct)

I uncommented settings for log files (to be able to check the log)

I configured prosody to use port 5222 and 5269

Then, after restarting prosody using 'systemctl restart prosody' it worked.

Please excuse poor formatting. I'm just really relieved that it's working now and I can take a break.

Good luck!

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: [SOLVED] prosody not able to create pidfile

The correct solution is to update the prosody package. This was fixed a few days ago.