Summary
Question
Configuring anubis setup in sm.ini file does not seem to be working and there aren't any error messages displayed in sm.log file. Restarting the system didn’t make any difference.
The Anubis configuration is done on the loadbalancer server not on applicationserver.
Environment specification:
- SM version – 9.31.1046 build 1046
- Sm.ini configuration:
## System Settings ##
shared_memory:32000000
log:../logs/sm.log
maxlogsize:5000000
numberoflogfiles:10
enableAnubisMonitor:1
anubisPollInterval:15
……………
There are no anubis schedulers defined so this is not in conflict with new setup.
The following instructions are used:
enableAnubisMonitor
This parameter starts the anubis monitor to check the status of background scheduler threads.
Note: The ThreadControllerId-background thread, which can be started no matter whether enableAnubisMonitor is enabled or not, has been modified to additionally include the anubis monitor functionality and thus eliminated the need for the anubis process.
Location:
sm.ini
Server’s OS command prompt
Default value:
0 (Disabled)
Possible values:
0: Disabled (when this parameter is not present in sm.ini or the command prompt)
1: Enabled
For more information, see QCCR1E72028.
Note: If an anubis agent record and anubis schedule record, which were used to restart stopped background processes automatically, already exist in your system, before enabling enableAnubisMonitor you need to disable the original anubis RAD applications as follows:
1 Delete the existing anubis agent record.
a Type info on the Service Manager command line, and click Search.
b Delete the anubis agent record.
2 Delete the existing anubis schedule record.
a Type sch on the Service Manager command line, and click Search.
b Delete the anubis schedule record.
anubisPollInterval
This parameter specifies the time interval (in seconds) at which the anubis monitor checks to see if any registered scheduler is alive.
Location:
sm.ini
Server’s OS command prompt
Default value:
15 (seconds)
Possible values:
Any time interval (in seconds)
For more information, see QCCR1E72028.
How to test:
Edit sm.ini file and add setting for Anubis. Kill one of the processes through system status and verify that the process is not starting.
Answer
Unlike the previous Anubis method If the admin has killed the thread it will be removed from the thread manager, so that it will not restart. Hence the reason that it appears not to work.
Here is how to test on Windows.
1. Kill agent scheduler by using Process Explorer (available here http://technet.microsoft.com/en-gb/sysinternals/bb896653.aspx)
a. In system status you can see the PID and TID for agent (or other process).
b. Search for it in Process Explorer and kill only this thread.
2. Wait for 15 seconds and then check system status and sm.log.
3. You will see the process appear again and the one you killed disappears.
4. If you repeat these steps without configuring Anubis you will see the process does not run again.
Other Operating Systems have applications similar to Process Explorer which can be used for testing in step 1. For example for Linux the Linux Process Explorer http://sourceforge.net/projects/procexp/ will work.