Unknown instance

[Evan Huus]

Syslog-ng automatically forks into the background by default, so the
original process that upstart is looking for no longer exists. Either
pass the '--foreground' option to syslog-ng so it doesn't do that, or
add an 'expect fork' stanza to your configuration.

Cheers,
Evan

P.S. The 'expect fork' may need to be an 'expect daemon' depending on
the number of times syslog-ng forks. I believe it's only once (in
which case 'fork' is fine), but I could be wrong.

On Fri, Jan 27, 2012 at 7:13 PM, Chris Johnson <masterof0 at gmail.com> wrote:
> I am new to upstart and currently trying to set it up to launch syslog-ng on boot.  Based on the getting-started guide, I have come up with the following configuration:
>        start on runlevel [2345]
>        stop on runlevel [06]
>        exec /usr/local/sbin/syslog-ng
>
> Good part is that it appears to launch okay:
>        $ sudo start syslog-ng
>        syslog-ng start/running, process 25178
>
> Unfortunately when I run the status is shows 'stop/waiting' and when I try to stop, I get 'Unknown instance'
>        $ sudo stop syslog-ng
>        stop: Unknown instance:
>
> What am I missing?
>
> Thanks
> Chris
> --
> upstart-devel mailing list
> upstart-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel