The init.d/ic-serviced does not start automatically after a Linux Server reboot

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:

• Rebooted the Linux Server and the sm_service commands do not work and the ic-serviced service did not start automatically. 
• Manually starting the ic-serviced works fine, however the expectation is that the service starts up after the Linux Host Server is rebooted

[root@<hostname>:/home/281973]# /etc/init.d/ic-serviced status
sm_serviced is not responding.
[root@<hostname>:/home/281973]# /etc/init.d/ic-serviced start
Starting sm_serviced ...
sm_serviced started
[root@<hostname>:/home/281973]# /etc/init.d/ic-serviced status
sm_serviced is responding.

 [root@<hostname>:/opt/InCharge/SAM/smarts/bin]# ./sm_service
[March 1, 2021 9:08:06 AM EST +609ms] t@3076089664 Primary Thread SMS-E-CLI_ENOACTION-You must supply exactly one action.

[root@<hostname>:/opt/InCharge/SAM/smarts/bin]# ./sm_service show
[March 1, 2021 9:08:08 AM EST +966ms] t@3012106048 Primary Thread CI-E-EFLOWID-For flow CI_FlowBufferedHead_U [Client Buffered Head] HEAD|BUFFERED @0x0000000000ed3ac0 . Read buffer, 0 bytes available of 2145 . ?3?0000000000000000 0000000000000000 ^|0000000000000000 0000000000000000 . Write buffer, 0 bytes written of 2048 . ?3?[^0000000000000000 0000000000000000 0000000000000000 0000000000000000 . -CI_FlowPipe_U IN_FLOW|PHYSICAL|LOCAL @0x0000000000ed3900 . sm_service CI-EWHILE-While executing function "open" SYS-ECONNREFUSED-Connection refused; in file "/work/redcurrent/DMT-10.1.2.0/11/smarts/clsapi/ci_flow.c" at line 3060

Environment

Smarts 10.1.X

Cause

During the Smarts install the ic-serviced is not set to automatically start up after Linux server reboot

Resolution

For RHEL 8.8 and 8.9 

1. Open file /usr/lib/systemd/system/ic-serviced.service
2. Edit below line and add "/bin/bash" before start of the service

             ExecStart=/bin/bash /etc/init.d/ic-serviced start

3. Save and reboot the VM.

For RHEL8.5 

1.  Determine runlevel

     runlevel

Note: runlevel can be either 3 or 5 generally 

2.  Edit ic-serviced startup script

     vi /etc/init.d/ic-serviced

3.    At the top of the file, replace 3 in the example below with the current runlevel if the runlevel is different than 3,

Also remove any blank lines if they are presented before or in between the following lines shown below.  For this to work, to these two lines need to be the first two lines in the file. 
Line 3 will be blank.

   #! /bin/sh
   #chkconfig: 3 90 98

This will use the systemctl commands to enable and start the ic-serviced and allow the service to be restarted upon System Reboot.

4.    Add the ic-serviced to systemctl.

       systemctl enable ic-serviced

5.    To manually start the ic-serviced daemon

     systemctl start ic-serviced

6.    To see the status of the ic-serviced daemon

      systemctl status ic-serviced

In the event that you want to stop and and disable the service and prevent it from restarting on System Reboot:
    
1.  To manually stop the ic-serviced daemon

    systemctl stop ic-serviced

    
2.  To disable the ic-serviced

    systemctl disable ic-serviced

For Linux Versions 8.4 or lower that use chkconfig 

1.  Determine runlevel

     runlevel

Note: runlevel can be either 3 or 5 generally 

2.  Edit ic-serviced startup script

     vi /etc/init.d/ic-serviced

3.    At the top of the file, replace 3 in the example below with the current runlevel if the runlevel is different than 3.

   #! /bin/sh
   #chkconfig: 3 90 98

4.    Add the ic-serviced script to chkconfig

       chkconfig --add ic-serviced

5.    Set the ic-serviced to autostart at the set run level

       chkconfig --level 3 ic-serviced on

6.   Verify the ic-serviced runlevels

       chkconfig|grep ic-serviced

7.   To manually start the ic-serviced daemon

      /etc/init.d/ic-serviced start

8.   To manually stop the ic-serviced daemon

      /etc/init.d/ic-serviced stop

9.   To see the status of the ic-serviced daemon

       /etc/init.d/ic-serviced status