On Tue, Nov 25, 2014 at 04:08:18PM +0000, Jona Joachim wrote: > On 2014-11-25, Landry Breuil <[email protected]> wrote: > > Hi, > > > > while setting up a prosody server, i noticed the default config is > > broken since it wants to use posix module (daemonize, syslog) but doesnt > > enable it by default.. also, since we make it depend on luaevent, maybe > > we should enable the libevent component by default too, or the > > dependency should be relaxed. > > Hi, > I had trouble with prosody in daemon mode in the past, in fact I could > never make it work even if I enable the posix module. > > joachim% sudo prosodyctl start > general info Hello and welcome to Prosody version 0.8.2 > general info Prosody is using the kqueue backend for > connection handling > WARNING: there is already a transaction in progress > Started > joachim% sudo prosodyctl status > Prosody is not running > joachim% pgrep prosody > joachim% pgrep lua > joachim% > > With daemonize = false it starts up without any trouble.
That seems to be because you enable libevent ? without it, i have no trouble with daemon mode on 5.6. Nov 25 16:45:55 general info Hello and welcome to Prosody version 0.9.4 Nov 25 16:45:55 general info Prosody is using the select backend for connection handling Nov 25 16:45:55 portmanager info Activated service 's2s' on [::]:5269, [*]:5269 Nov 25 16:45:55 portmanager info Activated service 'c2s' on [::]:5222, [*]:5222 Nov 25 16:45:55 portmanager info Activated service 'legacy_ssl' on no ports Nov 25 16:45:55 mod_posix info Prosody is about to detach from the console, disabling further console output Nov 25 16:45:55 mod_posix info Successfully daemonized to PID 20175 Landry
