EXAOperation stuck in initialization
Details
| Detail name | Value |
|---|---|
| Changelog Number | 10589 |
| Type | Bug |
| Status | Open |
| Affected Versions | Exasol 6.1.0, Exasol 6.2.0, Exasol 7.0.rc2 |
Description:
Under rare circumstances, EXAOperation may not start because of a deadlock caused by an underlying library. In this case, the EXAOperation website will become unresponsive and will not load on further browser requests.
Workaround:
EXAoperation can be restarted by running the following command on the management node.
killall appserverd
If EXAoperation still does not come up, then a reboot of the node which is running EXAoperation is recommended (in most cases, this is the management node).