After installing EEM and WCC on RHEL when we restart the server iGateway does not automatically start
Article ID: 281245
Updated On:
Products
Issue/Introduction
We have installed Autosys 12.1.X on RHEL.
EEM and WCC are on a dedicated machine.
When we restart the server the iGateway service does not automatically start.
We can go in and start it without error and everything works.
We see the iGwateway script in the /etc/init folder as well.
How can we get the service to start automatically
Environment
Autosys R12.1.X
EEM 12.X
RHEL 7.x 8.x
Cause
The OS Did not have the igateway service set to start.
Resolution
Run "chkconfig"
do you see the services configured/listed to start at any of the run levels?
The client could see the following from the chkconfig command:
CA-wcc 0:off 1:off 2:off 3:on 4:off 5:on 6:off
CA-wcc-services 0:off 1:off 2:off 3:on 4:off 5:on 6:off
dxserver 0:off 1:off 2:on 3:on 4:on 5:on 6:off
This is what the chkconfig should show:
CA-wcc 0:off 1:off 2:off 3:on 4:off 5:on 6:off
CA-wcc-services 0:off 1:off 2:off 3:on 4:off 5:on 6:off
dxserver 0:off 1:off 2:on 3:on 4:on 5:on 6:off
igatewayd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
We use the chkconfig to set the startup run levels.
Please run the belowchkconfig <service_name> on --level runlevels
example:chkconfig igatewayd on --level 2345
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/s2-services-chkconfig
Then run the chkconfig command to validate the changes
If you now see what is expected go ahead and do a reboot.
Additional Information
Also run "systemctl list-unit-files"
Services that will start at boot will be listed as enabled.
If you need to enable one run: systemctl enable <service name>
Also "journalctl -b" should show you what actions were attempted during boot-up regarding systemd.
Note: Please verify this with your system admin as depending on the version of your OS it might be something slightly different.
Feedback
