Highlighted
Absent Member.
Absent Member.
471 views

Probe JMX requesting restart on receiving robeUpdate10.01.CUP2.zip

Jump to solution

Back again, experts

 

In the course of attemping to fix the invalid content pack, we cleared the probe DB. Now none of our probes are able to fully go back to functioning. When rebuilding their DB, the probe calls for the JVM to restart and redo the probe. In the worst cases, this cycle of restarting causes the probes to eventually run out of memory.

 

This happens right when the probe receives the request to upload the CUP2 update. This happened on an older probe and a new one installed. We have also tried increasing the heap size to allow the probe to last a little longer, but to no avail.

 

jvm 1    | <2013-08-12 17:26:42,489> 1727508 [INFO ] [ProbeGW: DB Tasks Distributor] (DiscoveryClient.java:710) - ProbeGW: Downloading file from server: discoveryResources/probeUpdate10.01.CUP2.zip
jvm 1    | <2013-08-12 17:27:04,864> 1749883 [INFO ] [ProbeGW: DB Tasks Distributor] (DownloadsManager.java:84) - Save file: download required:discoveryResources/probeUpdate10.01.CUP2.zip 1374806463451 time1376346424864
jvm 1    | <2013-08-12 17:27:05,060> 1750079 [INFO ] [ProbeGW: DB Tasks Distributor] (LocalDownLoader.java:140) - ProbeMgr: received new server data fileName=discoveryResources/probeUpdate10.01.CUP2.zip
jvm 1    | <2013-08-12 17:27:05,841> 1750860 [INFO ] [ProbeGW: DB Tasks Distributor] (DiscoveryClient.java:906) - ProbeGW: sending probe status to the server: Disconnected_Being_Restarted
jvm 1    | <2013-08-12 17:27:06,832> 1751851 [INFO ] [ProbeGW: DB Tasks Distributor] (ProbeRestartHandler.java:130) - >>>>> Schedule Restart in 0 msec
jvm 1    | <2013-08-12 17:27:06,902> 1751921 [WARN ] [Probe Schedule Restart] (ProbeRestartHandler.java:55) - >>>>>>>>>>>>>>>> Restart is scheduled in 0 milli-seconds
jvm 1    | <2013-08-12 17:27:06,903> 1751922 [WARN ] [Probe Schedule Restart] (ProbeRestartHandler.java:57) - >>>>>>>>>>>>>>>> Probe is being Restarted!!!!!!!!!
jvm 1    | <2013-08-12 17:27:06,965> 1751984 [INFO ] [ProbeGW: DB Tasks Distributor] (DiscoveryClient.java:906) - ProbeGW: sending probe status to the server: Disconnected_Being_Restarted
wrapper  | JVM requested a restart.

 Checking both the gateway and manager (we're running a single installation), the offending file has made it onto the Probe Server and is fully present. We are running the probe without the console. This occurs both before and after a probe update is manually issued in uCMDB.

 

Would uninstalling CUP2 alleviate this issue?

0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.
Absent Member.

Re: Probe JMX requesting restart on receiving robeUpdate10.01.CUP2.zip

Jump to solution
By running the probe in console mode, it was able to push the CUP update through and finish rebuilding the database.

I'm curious, is there a timeout setting for the Probe or JVM Wrapper that's different between a standard start and a console mode start? It took almost a minute and a half for the console to push the cup update through, would that cause the Probe/JVM to request a restart because it suspected hanging?

View solution in original post

0 Likes
2 Replies
Highlighted
Absent Member.
Absent Member.

Re: Probe JMX requesting restart on receiving robeUpdate10.01.CUP2.zip

Jump to solution
By running the probe in console mode, it was able to push the CUP update through and finish rebuilding the database.

I'm curious, is there a timeout setting for the Probe or JVM Wrapper that's different between a standard start and a console mode start? It took almost a minute and a half for the console to push the cup update through, would that cause the Probe/JVM to request a restart because it suspected hanging?

View solution in original post

0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Probe JMX requesting restart on receiving robeUpdate10.01.CUP2.zip

Jump to solution

Please be aware that any jar related upgrade (CUP is an example) is scheduled to be restartarted with the delay. It's stated in documentation.

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
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.