search cancel

Harvest Broker Won't Auto-Restart

book

Article ID: 254200

calendar_today

Updated On:

Products

CA Harvest Software Change Manager

Issue/Introduction

We used the article Install SCM Server component v13.0.3 and v13.0.4 on Redhat Linux 8.x to install SCM Server on our Redhat Linux server and used the included instructions to configure so that it would run as a service and automatically restart if the server was rebooted.  We are finding out that the configuration to auto-restart does not work.

- We double-checked permissions on the startup.sh and shutdown.sh scripts to ensure that all users had permission to read and execute the scripts

- We ensured the scripts had "#!/bin/bash" as the first line of the script

- We tested the scripts to ensure they worked as expected when run from a command prompt window.

- When executing "systemctl status cascm" we got the following response:

  cascm.service - CA Harvest SCM server
   Loaded: loaded (/etc/systemd/system/cascm.service; enabled/ vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2022-11-03 20:06:44 UTC; 2 mins 4s ago
  Process: 940 ExecStart=/home/cascm/scripts/startup.sh (code=exited, status=203/EXEC)

Nov 03 20:06:43 *********.***.****.*** systemd[1]: Starting CA Harvest SCM server...
Nov 03 20:06:44 *********.***.****.*** systemd[1]: cascm.service: Control process exited, code=exited status=203
Nov 03 20:06:44 *********.***.****.*** systemd[1]: cascm.service: Failed with result 'exit-code'.
Nov 03 20:06:44 *********.***.****.*** systemd[1]: Failed to start CA Harvest SCM server.

Environment

Release : 13.0.3

Cause

The Unix forums indicated the 203/EXEC error code indicated a SELinux permission problem.  

Resolution

The Linux system administrator copied the /home/cascm/scripts/startup.sh and /home/cascm/scripts/shutdown.sh scripts into a different directory (/usr/local/scripts) and edited the /etc/systemd/system/cascm.service file to point there.  After this the automated startup worked as expected.