Kbase P128458: Fathom container is Offline (remote monitoring) when remote AdminServer is started as non-root accou
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/07/2008 |
|
Status: Verified
SYMPTOM(s):
Remote Fathom container remains Offline when remote AdminServer is started as non-root account
fmconfig -enable -host <host_Fathom_is_running_on> has been run sucessfully on the remote server
fmconfig has been executed within proenv as root user
fmconfig -update -host <host_Fathom_is_running_on> has been run sucessfully on the remote server
Service pack levels are the same on the OE Management AdminServer and Remote AdminServer
DLC/properties/management.properties and MFConfigurationElements.xsd created and correct
tcp/ip between Fathom machine and remote console working
correct java version in use on both machines for OpenEdge product
ContainerOffline, Resource Name: Server, Severity: 4, Message: Container has shut down. (11224)
The Fathom Management Console shows that all remote monitored servers (containers) are not active:
Contain Offline: <container_name>
The container is offline. If the container is no longer to be monitored you can delete it from Fathom with the "delete Container" button below. Deleting the container will delete all resource-definitions in Fathom for the container.
The "Fathom1.<hostname>.cache" directory from Progress working directory on remotely monitored machine has been deleted
remote adminserver has been restarted
remote databases start under the remote AdminServer
Remote containers are online when remote AdminServer is started as root account
write permission in Fathom1.P125P21E1.cache/content directory needed to be changed for Remote AdminServer to start under non-root account
Remote admserv.log shows System Plugin is not started
Plugin.System not installed: (7439)
Failed to install plugin Plugin.System. (7433)
DLC/properties/AdminServerPlugins.properties does not have 'commented out' plugins
FACT(s) (Environment):
All Supported Operating Systems
Fathom Management 3.x
CAUSE:
This is a permissions issue. There is an absolute requirement that fmconfig -enable -host must be run as root. When the remoted adminsever is started as non root account, the System plugin cannot load.
FIX:
The System plugin that requires root priv is _amspriv. This executable must (1) be owned by root and (2) must have the set user id bit set.
remote AdminServer machine do:
$ su
$ cd $DLC/bin
$ chown root _amspriv
$ chmod u+s _amspriv
The Remote AdminServer will now start as a non-root user at this point and be able to load the System plugin.
If the log files and property files were initially created as root, verify that these files have world read/write privs. The files are located in:
- $DLC/properties
- $WRKDIR