power probe unable to start

[Anon Anon]

Hi,

 

I would like to monitor APC ups, so I deployed on my hub server, the "power" probe....

Since it is deployed, I am not able to start this probe...

 

here is the log:

key    =  
port   =   
'java' is not recognized as an internal or external command,
operable program or batch file.
name   = power       
contip =     
cprid  = 4182641      
key    = sMAeyoEmnWDg9EZ2HFZ6vx1t5LT5qybaZl6aD7CQbgxG2YqOpO1EDnhIgIyfDHY 
port   = 48041  
cprid  = 4248339      
key    = WxlII05vZpvRMSqKqR7PHQdJrcPfg4GLRdNb4C2CWIM7jTCgqJSIitFcqnrmgA8 
cprid  = 4314055      
key    = qAdg1BspZA9R9YD6JvdiUfTZjNY3JVIDPHpuNLBVFCLbmJh0tpMVOJP4WUhhnnf 
Feb 28 17:56:40:495 [1608] Controller: Max. restarts reached for probe 'power' (command = runprobe.bat)
cprid  = 4366098      
key    = TZqjsKlPUKrk2Z3bzvdpxO9oiZj2k3742AWjrRyofglgCZsNz6m70upjBFVyRCk 
Mar  1 08:24:03:051 [1608] Controller: Max. restarts reached for probe 'power' (command = runprobe.bat)
cprid  = 4431912      
key    = uvqFuhgFFv9ZKZO5HeT7dLcxiUhMjLOgSjEAnyPKuHmik2hSatJZBPoo3nj3Ofq 
Mar  1 08:28:41:757 [1608] Controller: Max. restarts reached for probe 'power' (command = runprobe.bat)
cprid  = 4497469      
key    = hHPLassKhfu4JUlRIyQZVtFQo7YSrW30fEPrdTjDIERYDa2JWCGkZoMZl5QTPY1 
Mar  1 08:29:02:477 [1608] Controller: Max. restarts reached for probe 'power' (command = runprobe.bat)
cprid  = 4563369      
key    = ur6D8NrYJ0F2cGaIgTcaAkZH7s2MOF4rp6WsgoIHZJqRzjvIVml4UlC6UHsDbEs 
Mar  1 08:35:06:776 [1608] Controller: Max. restarts reached for probe 'power' (command = runprobe.bat)

 

Does anyone could help me?

 

regards

[Anon Anon]

I'd say that the critical message in there is:

'java' is not recognized...

 

Please check that a java virtual machine is installed and that the runprobe.bat file can find it. The easiest thing to do would probably be to download the java_jre package from the archive and drop it on the hub.

 

Cheers,

Stian

[Anon Anon]

Thanks, but Java is installed and it is used by some other probes....

 

I will check the BAT file ...

 

[Anon Anon]

Ok, I think I see the problem. The bat file calls 'java', but since it is started by the controller (which is started from a service as a system user) it probably does not have a path set that includes your Java's bin directory.

 

Double-click on the controller probe and click the 'Robot environment' button. Find the PATH variable in the list that shows up and see if your Java's bin directory is in that list. If it is not you can add it in the Setup->Environment tab.

 

Cheers,

Stian

[Anon Anon]

we had a similar issue with ecoMeter Probe 4.3 and it not starting.  Oddly enough it found the installed Java 32bit 1.8, but still wouldn't start.

 

We ended up deploying the java_jre package and that updated the Robot environment on the controller probe.  After that we restarted the probe and it started successfully!