Re: [systemd-devel] Prosody Failed on start

[Tomasz Torcz]

On Sat, Aug 12, 2017 at 01:08:08AM +0530, Sabir Mohammed wrote:
> Hi,
> 
> I am installed prosody successfully and it worked without any problem at
> first. After that I reboot the server and again started prosody. But at
> this time, it shows failed message.
> 
> 
> * prosody.service - LSB: Flexible communications server for Jabber/XMPP

  First, this is completely wrong. Prosody has system support 
(https://github.com/daurnimator/mod_systemd),
you should be using normal systemd unit. Here you use init.d SYSV script
via the compatibility layer.
  Probably your distribution shipped something wrong, please open a bug
with them.

> Aug 11 22:35:08 server prosody[1384]: Prosody is still not running. Please
> give it some time or check your log files for errors.
> 
> What is the solution.? Anyone help..

  Do as the message say and check the log files. Those should be
in /var/log/prosody/ IIRC.  

-- 
Tomasz Torcz  ,,If you try to upissue this patchset I shall be 
seeking
xmpp: zdzich...@chrome.pl   an IP-routable hand grenade.'' -- Andrew Morton 
(LKML)

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Prosody Failed on start

[Sabir Mohammed]

Hi,

I am installed prosody successfully and it worked without any problem at
first. After that I reboot the server and again started prosody. But at
this time, it shows failed message.


[root@server ~]# service prosody restart
Restarting prosody (via systemctl):  Job for prosody.service failed because
the control process exited with error code. See "systemctl status
prosody.service" and "journalctl -xe" for details.
   [FAILED]
[root@server ~]# systemctl status prosody.service
* prosody.service - LSB: Flexible communications server for Jabber/XMPP
   Loaded: loaded (/etc/rc.d/init.d/prosody; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2017-08-11 22:35:08 UTC;
12s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 1384 ExecStart=/etc/rc.d/init.d/prosody start (code=exited,
status=1/FAILURE)

Aug 11 22:35:01 server systemd[1]: Starting LSB: Flexible communications
server for Jabber/XMPP...
Aug 11 22:35:01 server runuser[1386]: pam_unix(runuser:session): session
opened for user prosody by (uid=0)
Aug 11 22:35:08 server systemd[1]: prosody.service: control process exited,
code=exited status=1
Aug 11 22:35:08 server prosody[1384]: Starting Prosody XMPP (Jabber)
server: Still waiting...
Aug 11 22:35:08 server prosody[1384]: Prosody is still not running. Please
give it some time or check your log files for errors.
Aug 11 22:35:08 server prosody[1384]: [FAILED]
Aug 11 22:35:08 server systemd[1]: *Failed to start LSB: Flexible
communications server for Jabber/XMPP.*
Aug 11 22:35:08 server systemd[1]: Unit prosody.service entered failed
state.
Aug 11 22:35:08 server systemd[1]: prosody.service failed.
[root@server ~]#

What is the solution.? Anyone help..

-- 
*Thanks & Regards*
*Sabir S M*
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

[vcaputo]

This is not recommended.  Forwarding is currently implemented
synchronously in journald, and can have a very substantial negative
impact on journald performance in general as a result.

BTW: are we not averse to top-posting on systemd-devel?

Regards,
Vito Caputo


On Fri, Aug 11, 2017 at 05:47:15AM +, Zhujiafa wrote:
> add
> " systemd.journald.forward_to_console=1 "
>  to your kernel  parameters.
> 
> 
> 
> 
> ZhuJiafa
> email: zhuji...@huawei.com
> tel: +86 18651652661
> 
> From: Reindl Harald
> Date: 2017-08-11 13:37
> To: 
> systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY
> 
> 
> 
> Am 11.08.2017 um 04:29 schrieb Sergei Franco:
> > I am trying to retain behaviour of the startup scripts the same as sysvinit.
> > For example, on sysv the script outputs feedback to the console when the
> > stopping and starting is done via console.
> > With systemd all output is "hidden", and to see the output you need to
> > check the journal (or syslog if configured). There is no feedback.
> >
> > Is it possible to configure StandardOutput=tty (and StandardErrror)
> > where TTYPath= is set to current $SSH_TTY env (be that
> > /devpts/0,/dev/pts/1 or /dev/pts/n)?
> 
> no, because PID1 is a completly different process than any TTY
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel

> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

[Mantas Mikulėnas]

Doing that directly makes little sense. The terminal will eventually go
away, and your service will start getting write errors for stdout.

Instead it would be better if systemctl could spawn `journalctl --follow
--unit=`... I remember it used to have a follow option for status.

On Fri, Aug 11, 2017, 05:29 Sergei Franco  wrote:

> Hi,
>
> I am trying to retain behaviour of the startup scripts the same as
> sysvinit.
> For example, on sysv the script outputs feedback to the console when the
> stopping and starting is done via console.
> With systemd all output is "hidden", and to see the output you need to
> check the journal (or syslog if configured). There is no feedback.
>
> Is it possible to configure StandardOutput=tty (and StandardErrror) where
> TTYPath= is set to current $SSH_TTY env (be that /devpts/0,/dev/pts/1 or
> /dev/pts/n)?
>
> Regards.
>
> Sergei.
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
-- 

Mantas Mikulėnas 
Sent from my phone
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel