Gateway crash, Gateway terminated, Gateway exited, core dump, coring.
- You have experienced a Geneos Gateway crash. This means that the Gateway has unexpectedly stopped running and may have generated a core dump.
- A Gateway process may terminate (commonly referred to as a crash, but this is not always the case) for a number of reasons, both expected and unexpected
- Either a user or another process may have sent a termination signal to the Gateway. This can be intentional, but sometimes be done by accident. Most signals are caught by the Gateway and logged before exiting. If you review the Gateway log file and see lines similar to either of these then this is the cause:
<Wed Aug 4 11:50:14> INFO: Gateway Signal TERM received - terminating
2021-08-04 11:51:56.076+0000 INFO: Gateway Signal TERM received - terminatingThe first line is from a GA4.x Gateway - the date format is the giveaway - and is almost certainly, regardless of the problem you are seeing, in need of upgrading.
- Other reasons for the Gateway terminating unexpectedly is a lack of system resources, which can be termed environmental factors, for example disk space or the process growing to a pre-imposed memory limit.
- Finally, you may have encountered a bug. The Geneos Gateway is a complex, multi-threaded application and there are a variety of reasons that it may encounter a problem that cannot be recovered from (or even logged as an error). Our Engineering teams work hard to address any reported bugs and to ensure that each release improves on the previous one, both in terms of quality but also new features - and sometimes these new features will introduce new, unexpected, failure modes.
- If the crash was not caused by an environmental factor, such as those listed above, then the first thing to check is the product Release Notes for similar symptoms. Geneos releases are continually improving and later releases from the version you have may have addressed the underlying cause of the problem.
- Check the Known Issues section in the Release Notes in case there is an identified defect that is being worked on. There may be documented workarounds while awaiting a fix.
- Review the Gateway log file at the time of the crash as there may be a descriptive entry just before the termination that would help explain the cause.
- Check to see if there is a core dump file in the working directory of the gateway. This will be called core.PID where PID was the process ID of the Gateway. You may not have core dumps enabled on your system in which case this file will not be created (check article in related articles).
- How to collect core dump file of a crashing program that is shipped in Red Hat Enterprise Linux 6/7/8?
If Issue Persists
- Please contact with our Client Services team via the chat service box available in any of our websites or via email to firstname.lastname@example.org
- Make sure you provide:
- Gateway Diagnostic File
- CoreDump File.
-Any troubleshooting step already verified from the ones described in this article.