Kbase P16104: Monitoring agent does not autostart after applying 91C patch
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/03/2003 |
|
Status: Unverified
FACT(s) (Environment):
Fathom 1.0A
FACT(s) (Environment):
Progress 9.1C
SYMPTOM(s):
AgentIdle: Database Agent, <agent name>, is not running. (9743)
AgentIdle: Database Agent, FathomTrendDatabase, is not running. (9743)
Getting alert within Fathom "* Alert! Alert Name: AgentIdle, Resource Name: FathomTrendDatabase, Severity: 3, Message: Database Agent, FathomTrendDatabase, is not running. (9743)"
Fathom patch 1.0A01 has been installed
Monitoring agent is not autostarting within the AdminServer
CHANGE:
Applied latest 9.1C patch
CAUSE:
BUG# 20021216-018
CAUSE:
From Donna Henning: This behavior results from the fact that there is no support for the Database Connection Adapter license in Fathom 1.0a, however, the license is enforced (with a default of false) in core 9.1c and 9.1d. Since there are no further plans to patch Fathom 1.0a, the workaround is to (1) set "monitorlicensed=true" for each database configuration in conmgr.properties, or (2) upgrade to Fathom 2.0a.
CAUSE:
This is a known issue
FIX:
Put a line "monitorlicensed=true" without "" into your $DLC/properties/conmgr.properties and restart your monitored databases as well as AdminServer.
The property must be added under the [database...] group for each of the databases in the conmgr.properties file.
Backup of conmgr.properties is recommended.