No Gateway is active

RE: No Gateway is active

catalinp — Fri, 04 Aug 2017 08:48:38 GMT

In additions of what kondetiv ealier:
1.Stop Appian
2.Stop or kill any processes that are running on the ports reserved for the engines.
3.Start the engines.
4.Run checkengine.bat|sh to confirm that the engines have successfully started.

you can check:
1. the firewall to see if can communicate with DB
2. if have you a tool that restrict the environment like SeLinux, to check the audit file if it's blocking something
3. check if the DB isn't corrupted due a hard reset/shutdown

RE: No Gateway is active

abhinavg712 — Thu, 03 Aug 2017 18:11:58 GMT

There might be few scenarios

1. Latest running KDB's are corrupted, check {<Appian_Home>/server/process/exec/00/gw1 for exec-01 } and look for latest KDB size, workaround is to load the last check pointed KDB
2. Engines are not stopped properly ,resulted in check pointing not done.
3. As mentioned earlier in the post, check for disk space for your Appian Home

lastly check for failed engine logs as they will have detailed error trace for "FATAL" status

RE: No Gateway is active

Muneer Varma — Thu, 03 Aug 2017 16:02:30 GMT

The reasons for this issue are 1) The space available to store appian logs was 100% used and 2) /boot was 99%.
We cleaned up the space and server worked just fine.

RE: No Gateway is active

kondetiv — Wed, 26 Jul 2017 03:35:46 GMT

Muneer Varma Just apply our classic engineering solution that is not doing anything but only restarting engines.

1.Stop Appian
2.Stop or kill any processes that are running on the ports reserved for the engines.
3.Start the engines.
4.Run checkengine.bat|sh to confirm that the engines have successfully started.

RE: No Gateway is active

Eliot Gerson — Tue, 25 Jul 2017 20:38:53 GMT

Please take a look at community.appian.com/.../kb-1070-some-engines-are-unable-to-start-with-a-fatal-error-in-the-checkengine-script

Also, make sure you're waiting long enough; the engines might take a couple minutes to start.