Return
-
Title
Authentication Services heartbeat errors. /var/opt/quest/home/questusr/.quest_autoqasstatus/./notify.sh: line 96: kill: (10397) - No such process -
Description
Showing up in the log file of the clients: Cron /bin/sh '/var/opt/quest/home/questusr/.quest_autoqasstatus/./notify.sh' 'heartbeat' # auto-qas-status service job /var/opt/quest/home/questusr/.quest_autoqasstatus/./notify.sh: line 96: kill: (10397) - No such process -
Cause
MCU product defects:
28641 - notify.sh script doesn't handle HTTP 202 or 208 cases28644 - output run_qas_status_check.sh error output to another log besides status result file.These are fixed in MCU 2.5.2 version.
-
Resolution
RESOLUTION:
Upgrade to MCU version 2.5.2.
WORKAROUND:
1. Download the MCU patch attached to this article and uncompress the file.
The attached patch for Management Console for Unix (MCU) contains the following files:The files in the patch are:bullseye-model-2.5.1.jarbullseye-server-2.5.1.jarbullseye-sugi-2.5.1.jarsugi-core-2.5.1.jar2. Install the files on the MCU server by following these steps:
1. Stop the MCU service
Quest One Management Console for Unix2. Backup the existing files (make sure they are moved and not kept in the same path) The files can be found here:Windows 2008:C:\Program Files (x86)\Quest Software\Management Console for Unix\webapps\ROOT\WEB-INF\libLinux/Unix:/opt/quest/mcu/webapps/ROOT/WEB-INF/lib/3. Extract the new jar files and move them into the same location that the originals were in.4. Restart MCU service.Then try to reproduce the issue with the error message appearing on your monitoring application.E.g. the error message was:cat: 0652-050 Cannot open ./.auto_qas_status_results.3. The new updated script still needs to be properly pushed out via the MCU. In order for that to occur you will need to delete the heartbeat policy within MCU and configure it freshly.1.Right click the host in question and select details you will get a new screen and in the upper right hand corner is an 'Options' drop down menu. I've included a screenshot to show what this looks like.2. Select the Check QAS agent status automatically....which opens another window.3. At this time you need to uncheck "Check Status Automatically", click ok, which will then configure the client to stop doing the checks.Once complete you can configure it again in the timeline you prefer and that should solve the issue. -
Change Request
28644 -
Attachments