Highlighted
Vice Admiral Vice Admiral
Vice Admiral
301 views

opcmsga with pid 0 on solaris node

Jump to solution

Hi all,


on one node we got the message
(MS467) Message agent on node "node-name" is not running.
The Self Manager detected that the message agent on the managed node terminated unexpectedly.
Check the error logfile on that node for information about the cause of the problem.
To re-start the agents, run 'opcagt -start' on the managed node.

When I run opcragt “node-name” on OM server I get and realized opcmsga with PID 0
Node: “node-name”
HPOM Managed Node status :
-------------------------
OV Performance Core coda (3519) is running
OV Communication Broker ovbbccb (3501) is running
OV Control ovcd (3500) is running
OV Config and Deploy ovconfd (3502) is running

Subagent EA:
Action Agent opcacta (3541) is running
Logfile Encapsulator opcle (3517) is running
Monitor Agent opcmona (3545) is running
Message Agent opcmsga (0) is running
Message Interceptor opcmsgi (3515) is running

**************************************************
Remote administration completed successfully on all nodes.

How could this happen?

Agent is running on Solaris 10 as non-root user.

Many thanks

Tom

Labels (1)
Tags (2)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Vice Admiral Vice Admiral
Vice Admiral

Hi js_crc

Thanks for the answer.

We found that because filesystem /var/core run out of space the agent process could not restart even stopping the agent was a problem.

 After killing all agent processes on that node we could restart the agent correctly.

 many thanks and marry x-mas

View solution in original post

0 Likes
2 Replies
Highlighted
Captain
Captain

Hi Tom,

If you compare the PIDs, not only for opcmsga but for all the other agent processes listed in the result, against the output of ps -ef (executed locally) do you get the same values?

If you run ovdeploy -cmd "opcagt -restart" -node NameOfNode

Do you get the same 0 value for opcmsga or any other processes?

Thanks,

0 Likes
Highlighted
Vice Admiral Vice Admiral
Vice Admiral

Hi js_crc

Thanks for the answer.

We found that because filesystem /var/core run out of space the agent process could not restart even stopping the agent was a problem.

 After killing all agent processes on that node we could restart the agent correctly.

 many thanks and marry x-mas

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.