Troubleshooting
Problem
An EGO service's configuration changes after EGO on the primary host is restarted. The problem is more likely to be encountered after changes to the underlying file system hosting the $EGO_COFNDIR directory.
Symptom
- It can appear that an EGO service reverted to a previous configuration.
- A setting that was enabled in the EGO service's profile is no longer enabled.
- The configuration in the service profile XML file $EGO_CONFDIR/../../eservice/esc/conf/services/<service_name>.xml does not match the configuration of the service according to the output of the "egosh service view <service_name>" command.
- The EGO Service Controller log $EGO_CONFDIR/../../eservice/esc/log/esc.log.<hostname> contains the following error message.
-
2020-08-28 21:29:40.000 UTC ERROR [6650:139704168625984] loadServices(): Service <service_name> has already existed, ignoring
-
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSZUMP","label":"IBM Spectrum Symphony"},"ARM Category":[{"code":"a8m50000000CeTuAAK","label":"EGOSC"}],"ARM Case Number":"TS009497552","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
14 June 2022
UID
ibm16594547