Dgraph killed by OS configuration's OOM Killer policy
Last updated on JULY 07, 2017
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 5.1.0 and later
Information in this document applies to any platform.
A dgraph running from a shell script was running fine and then suddenly just die. The dgraph log (in verbose mode) just stopped writing and there was no error message. However, running the same process on a different machine it worked fine. Running the same process by command line and when the process died, it would come back saying killed. I could find no evidence of what killed it and no one claimed to be killing it.
dmesg and that showed what happened last. For example on:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms