Hi,
exit status 9 menas "SIGKILL", so someone (that also includes some process)
sent a kill signal to arangod.
Because an explicit kill signal was sent, arangod is intentionally not
restarted by the supervisor process.
A kill signal may be sent by the operating system (e.g. OOM killer) or some
other resource management tool.
In case of the OOM killer you should see some messages in syslog about the
OOM killer choosing and killing arangod.
Is there anything obvious in the system logs around the time it happened?
Best regards
Jan
Am Freitag, 10. März 2017 07:10:59 UTC+1 schrieb Ilkka Huotari:
>
> Hi, I have encountered this a couple of times now:
>
> In */var/log/arangodb3/arangod.log.supervisor* there is this:
>
> *2017-03-07T09:12:08Z [1322] INFO {startup} child 1323 died of natural
> causes, exit status 9*
>
> Any ideas what might be causing this? Arangodb does not restart on its own
> after this, it stays down. The latest crash was on 3.1.11.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
