Thanks.
It seems like that call to zookeeper lib API is causing this exit with 251 and hence it is most likely in zookeeper lib code.
Regards
On Mon, Mar 4, 2019 at 5:26 PM Lennart Poettering <lennart@xxxxxxxxxxxxxx> wrote:
On Mo, 04.03.19 16:58, prashantkumar dhotre (prashantkumardhotre@xxxxxxxxx) wrote:
> Hi,
>
> In my journal log, I see ;
>
> 1199473 Mar 01 15:46:03 evo-qfx-01 systemd[1]: ifmand.service: Main process
> exited, code=exited, status=251/n/a
>
>
> I want to know what does 251 means.
>
> Can you please let me know where can I see the exit-code to meaning mapping
This depends on the program you are invoking as a service. i.e. ask
the folks who wrote "ifmand" about this, or consult the documentation
for that program.
When systemd cannot invoke a program you configured it will generate a
couple of error codes on its own. These are documented here:
https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Process%20exit%20codes
But as you can see there 251 is none of the exit codes systemd itself
defines, hence it must come from your own app.
Lennart
--
Lennart Poettering, Red Hat
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
