Hey,

I have installed supervisor from pip, how does this have an effect? What
are the steps to fix the issue?

Here is the journalctl output after an attempted install:

alex@tapandcork:~$ journalctl -xn
No journal files were found.
alex@tapandcork:~$ journalctl
No journal files were found.
alex@tapandcork:~$

Thanks for looking into this!

On Sun, 21 Feb 2016 11:04:23 +0100 Orestis Ioannou
<[email protected]> wrote:
> Hello,
>
> I can't reproduce this on my machine. Just a wild guess, had you
> installed before supervisor from pip ??
>
>
> On Sat, 20 Feb 2016 13:23:49 -0700 Alexander <[email protected]> wrote:
> >
> > Also here is the systemd output:
> >
> > alex@tapandcork:~$ sudo systemctl start supervisor
> > Job for supervisor.service failed. See 'systemctl status
> > supervisor.service' and 'journalctl -xn' for details.
> > alex@tapandcork:~$ ^C
> > alex@tapandcork:~$ systemctl status supervisor.service
> > ● supervisor.service - LSB: Start/stop supervisor
> > Loaded: loaded (/etc/init.d/supervisor)
> > Active: failed (Result: exit-code) since Sat 2016-02-20 12:49:21
> > MST; 18s ago
> > Process: 21786 ExecStart=/etc/init.d/supervisor start (code=exited,
> > status=2)
>
>
> The status doesn't give much details here. Maybe journalctl will provide
> some more info so please provide me with an output.
>
> Cheers,
>
> Orestis
>
>

Reply via email to