Highlighted
Bano Absent Member.
Absent Member.
949 views

(ctrl-45) Component 'opcmona' with pid 12459 exited. Restarting component.

Jump to solution

I often got this kind of alarm "(ctrl-45) Component 'opcmona' with pid 12459 exited. Restarting component."

But when I checking by use opcragt -status, all services are showing running status. What does that alert mean? Should I ignore it?

0 Likes
1 Solution

Accepted Solutions
Ram_21 Contributor.
Contributor.

Re: (ctrl-45) Component 'opcmona' with pid 12459 exited. Restarting component.

Jump to solution

Hello

 

The error is suggesting that you may have a problem with one of the measurement threshold policies that is deployed on the node where you see this issue. Verify that all the measurement threshold policies are doing what they are supposed to be doing. Also look in the System.txt file to see if there are any more details or other errors that may point to why opcmona is behaving this way.

 

If you consistently see the issue you may want to trace opcmona and see what the logs show when the error occur and also track down the policy that could be causing this.

 

Hope this helps.

Regards

Ram

 

0 Likes
4 Replies
Ram_21 Contributor.
Contributor.

Re: (ctrl-45) Component 'opcmona' with pid 12459 exited. Restarting component.

Jump to solution

Hello

 

The error is suggesting that you may have a problem with one of the measurement threshold policies that is deployed on the node where you see this issue. Verify that all the measurement threshold policies are doing what they are supposed to be doing. Also look in the System.txt file to see if there are any more details or other errors that may point to why opcmona is behaving this way.

 

If you consistently see the issue you may want to trace opcmona and see what the logs show when the error occur and also track down the policy that could be causing this.

 

Hope this helps.

Regards

Ram

 

0 Likes
Bano Absent Member.
Absent Member.

Re: (ctrl-45) Component 'opcmona' with pid 12459 exited. Restarting component.

Jump to solution

May I ask what's location of System.txt? I'm new to HPOV. thanks.

0 Likes
Bano Absent Member.
Absent Member.

Re: (ctrl-45) Component 'opcmona' with pid 12459 exited. Restarting component.

Jump to solution

I've found it in /var/opt/OV/log, thanks!

0 Likes
Jiban Absent Member.
Absent Member.

Re: (ctrl-45) Component 'opcmona' with pid 12459 exited. Restarting component.

Jump to solution

Hello,

 

I have the same issue, I have this 'System.txt' file with the below error log:

0: ERR: Mon May 9 19:45:15 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 5533 exited. Restarting component.
0: ERR: Mon May 9 20:00:21 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 23666 exited. Restarting component.
0: ERR: Mon May 9 20:15:27 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 9720 exited. Restarting component.
0: ERR: Mon May 9 20:30:33 2016: ovcd (23983/1108449600): (ctrl-95) Component 'opcmona' exceeded the automatic restart limit. Use 'ovc -start opcmona'.
0: ERR: Mon May 9 22:33:58 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 26591 exited. Restarting component.
0: ERR: Mon May 9 22:49:04 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 11830 exited. Restarting component.
0: ERR: Mon May 9 23:04:10 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 29055 exited. Restarting component.
0: ERR: Mon May 9 23:05:27 2016: ovcd (23983/1074792768): (ctrl-43) No such target 'coda'.
0: ERR: Mon May 9 23:19:16 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 14271 exited. Restarting component.
0: ERR: Mon May 9 23:24:30 2016: ovcd (23983/1094764864): (ctrl-43) No such target 'coda'.
0: ERR: Mon May 9 23:24:49 2016: ovcd (23983/1074792768): (ctrl-43) No such target 'coda'.
0: ERR: Mon May 9 23:34:22 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 31754 exited. Restarting component.
0: ERR: Mon May 9 23:49:28 2016: ovcd (23983/1108449600): (ctrl-95) Component 'opcmona' exceeded the automatic restart limit. Use 'ovc -start opcmona'.
0: ERR: Tue May 10 00:06:51 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 4622 exited. Restarting component.
0: ERR: Tue May 10 00:21:57 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 21930 exited. Restarting component.
0: ERR: Tue May 10 00:37:03 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 7172 exited. Restarting component.
0: ERR: Tue May 10 00:52:09 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 24937 exited. Restarting component.
0: ERR: Tue May 10 01:07:15 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 9633 exited. Restarting component.
0: ERR: Tue May 10 01:22:21 2016: ovcd (23983/1108449600): (ctrl-95) Component 'opcmona' exceeded the automatic restart limit. Use 'ovc -start opcmona'.
0: ERR: Tue May 10 01:26:57 2016: ovcd (23983/1091606848): (ctrl-43) No such target 'coda'.
0: ERR: Tue May 10 01:27:19 2016: ovcd (23983/1092659520): (ctrl-43) No such target 'coda'.
0: ERR: Tue May 10 01:27:28 2016: ovcd (23983/1094764864): (ctrl-43) No such target 'coda'.
0: ERR: Tue May 10 01:27:34 2016: ovcd (23983/1095817536): (ctrl-43) No such target 'coda'.
0: ERR: Tue May 10 01:42:29 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 17617 exited. Restarting component.
0: ERR: Tue May 10 01:57:35 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 2386 exited. Restarting component.
0: ERR: Tue May 10 02:12:41 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 20112 exited. Restarting component.
0: ERR: Tue May 10 02:27:47 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 4883 exited. Restarting component.
0: ERR: Tue May 10 02:42:53 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 22660 exited. Restarting component.
0: ERR: Tue May 10 02:57:59 2016: ovcd (23983/1108449600): (ctrl-95) Component 'opcmona' exceeded the automatic restart limit. Use 'ovc -start opcmona'.
0: ERR: Tue May 10 03:11:49 2016: ovcd (23983/1094764864): (ctrl-43) No such target 'coda'.
0: ERR: Tue May 10 03:11:56 2016: ovcd (23983/1074792768): (ctrl-43) No such target 'coda'.
0: ERR: Tue May 10 03:12:02 2016: ovcd (23983/1093712192): (ctrl-43) No such target 'coda'.
0: ERR: Tue May 10 03:26:58 2016: ovcd (23983/1108449600): (ctrl-45) Component 'opcmona' with pid 7222 exited. Restarting component.
0: ERR: Tue May 10 03:33:09 2016: ovcd (23983/1095817536): (ctrl-43) No such target 'coda'.
0: ERR: Tue May 10 03:33:29 2016: ovcd (23983/1093712192): (ctrl-43) No such target 'coda'.
0: ERR: Tue May 10 03:33:51 2016: ovcd (23983/1074792768): (ctrl-43) No such target 'coda'.
0: WRN: Tue May 10 03:34:17 2016: opcmsga (378/47529728592144): [genmsga.c:2042]: Warnings occurred during the read of the
OVO responsible manager configuration. (OpC30-1203)
line 24 WARNING: Could not get IP-address (OpC20-1511)
line 37 WARNING: Could not get IP-address (OpC20-1511)
Configuration file 'OVO authorization' contains warning or syntax errors. (OpC20-208)
0: WRN: Tue May 10 03:34:24 2016: opcmsga (378/47529728592144): [genmsga.c:2042]: Warnings occurred during the read of the
OVO responsible manager configuration. (OpC30-1203)
line 24 WARNING: Could not get IP-address (OpC20-1511)
line 37 WARNING: Could not get IP-address (OpC20-1511)
Configuration file 'OVO authorization' contains warning or syntax errors. (OpC20-208)
0: ERR: Tue May 10 03:45:34 2016: ovcd (23983/1094764864): (ctrl-43) No such target 'coda'.
0: ERR: Tue May 10 03:49:24 2016: ovcd (23983/1107396928): (ctrl-45) Component 'opcmona' with pid 464 exited. Restarting component.
0: ERR: Tue May 10 04:04:30 2016: ovcd (23983/1107396928): (ctrl-45) Component 'opcmona' with pid 17869 exited. Restarting component.
0: ERR: Tue May 10 04:19:36 2016: ovcd (23983/1107396928): (ctrl-45) Component 'opcmona' with pid 3197 exited. Restarting component.
0: ERR: Tue May 10 04:19:51 2016: ovcd (23983/1074792768): (ctrl-43) No such target 'coda'.

 

And below policies are deployed on that node:

 


Version Status
--------------------------------------------------------------------
configsettings "OVO settings" enabled 1
le "LOG_APP_ListeJournauxAPP" enabled 0001.0001
le "Lnx_Msg_Log" enabled 0001.0000
mgrconf "OVO authorization" enabled 1
monitor "Boo_Stat" enabled 0001.0001
monitor "Cor_Stat" enabled 0001.0001
monitor "Crn_Proc" enabled 0001.0001
monitor "Ito_Stat" enabled 0001.0001
monitor "MON_APP_VerifAppli" enabled 0001.0008
monitor "MON_OS_VerifDisque" enabled 0001.0002
monitor "NFS_mount_sur" enabled 0001.0001
monitor "Ntp_Stat" enabled 0001.0001
monitor "Os_Stat_10m" enabled 0001.0001
monitor "Slg_Proc" enabled 0001.0001
monitor "Swp_Stat" enabled 0001.0002
msgi "Ito_Msg" enabled 0001.0116
sched "Ito_Msg_24h" enabled 0001.0000

 

Could you please check and suggest me to solve the issue.

 

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.