A freshly installed agent on Windows Vista produce this log output (the error is at the end)
2010-04-13 16:01:18,241 INFO ProActiveAgent.WindowsService - Starting ProActive Agent service
2010-04-13 16:01:18,491 INFO ProActiveAgent.CommonStartInfo - Selected action RMAction
2010-04-13 16:01:18,507 INFO ProActiveAgent.CommonStartInfo - The initial java heap size is -Xms64M and maximum java heap size is -Xmx64M
2010-04-13 16:01:18,507 INFO ProActiveAgent.ExecutorsManager - Creating 1 executors.
2010-04-13 16:01:18,600 DEBUG ProActiveAgent.ExecutorsManager - Loading events in the Executors Manager.
2010-04-13 16:01:18,600 DEBUG ProActiveAgent.ExecutorsManager - Loading CalendardEvent 4/12/2010 12:00:00 AM -> 4/18/2010 11:59:59 PM
2010-04-13 16:01:18,600 DEBUG ProActiveAgent.ProActiveRuntimeExecutor0 - Received start action request from AgentScheduler
2010-04-13 16:01:18,631 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - Started ProActive Runtime process (link: pid:4292)
CLASSPATH=.;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\script-js.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\jruby-engine.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\jython-engine.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\commons-logging-1.0.4.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_SRM-common.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_ResourceManager.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_Scheduler-core.jar
Command-line: C:\Program Files\Java\jre6\bin\java.exe -Dproactive.communication.protocol=rmi -Dproactive.rmi.port=1099 -Dproactive.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Dproactive.configuration="file:C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\proactive\ProActiveConfiguration.xml" -Djava.security.manager -Dpa.scheduler.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Dpa.rm.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Djava.security.policy="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\security.java.policy" -Dlog4j.configuration="file:///C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\log4j\log4j-client" -Dproactive.net.interface=eth3 -Xms64M -Xmx64M org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter -r rmi://pataud:1099 -n sed -s Agents
2010-04-13 16:01:18,631 DEBUG ProActiveAgent.ProActiveRuntimeExecutor0 - Setting process priority to Normal and max cpu usage to 100%
2010-04-13 16:01:18,631 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - Adding new process java (link: pid:4292) to the cpu limiter
2010-04-13 16:01:18,819 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - The ProActive Runtime process has exited for unknown reason
2010-04-13 16:01:19,833 DEBUG ProActiveAgent.ProActiveRuntimeExecutor0 - The ProActive Runtime process restart delay is 0 ms (link: barrier is 4/18/2010 11:59:44 PM)
2010-04-13 16:01:19,833 DEBUG ProActiveAgent.ProActiveRuntimeExecutor0 - Restart delay is now set to 5000 ms
2010-04-13 16:01:19,833 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - Started ProActive Runtime process (link: pid:7084)
CLASSPATH=.;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\script-js.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\jruby-engine.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\jython-engine.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\commons-logging-1.0.4.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_SRM-common.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_ResourceManager.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_Scheduler-core.jar
Command-line: C:\Program Files\Java\jre6\bin\java.exe -Dproactive.communication.protocol=rmi -Dproactive.rmi.port=1099 -Dproactive.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Dproactive.configuration="file:C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\proactive\ProActiveConfiguration.xml" -Djava.security.manager -Dpa.scheduler.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Dpa.rm.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Djava.security.policy="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\security.java.policy" -Dlog4j.configuration="file:///C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\log4j\log4j-client" -Dproactive.net.interface=eth3 -Xms64M -Xmx64M org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter -r rmi://pataud:1099 -n sed -s Agents
2010-04-13 16:01:20,035 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - The ProActive Runtime process has exited for unknown reason
2010-04-13 16:01:20,082 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - An error occured in Events_OnNewProcess incrminatedProcess System.Diagnostics.Process (java)
System.InvalidOperationException: Instance 'java' does not exist in the specified Category.
at System.Diagnostics.CounterDefinitionSample.GetInstanceValue(String instanceName)
at System.Diagnostics.PerformanceCounter.NextSample()
at System.Diagnostics.PerformanceCounter.get_RawValue()
at ProActiveAgent.CPULimiter.ProcessWatcher.GetProcessInstanceName(Int32 pid)
at ProActiveAgent.CPULimiter.ProcessWatcher..ctor(Process processToWatch)
at ProActiveAgent.CPULimiter.addProcessToWatchList(Process processToWatch)
at ProActiveAgent.ProActiveRuntimeExecutor.Events_OnNewProcess(Object sender, NewProcessEventArgs args)
2010-04-13 16:01:20,082 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - An error occured in Events_OnNewProcess incrminatedProcess
System.NullReferenceException: Object reference not set to an instance of an object.
at ProActiveAgent.ProActiveRuntimeExecutor.Events_OnNewProcess(Object sender, NewProcessEventArgs args)
2010-04-13 16:01:21,049 DEBUG ProActiveAgent.ProActiveRuntimeExecutor0 - The ProActive Runtime process restart delay is 5000 ms (link: barrier is 4/18/2010 11:59:44 PM)
activeeon-bot
commented
14 years ago
Original issue created by Cédric Dalmasso on 13, Apr 2010 at 16:16 PM - AGENT-59
A freshly installed agent on Windows Vista produce this log output (the error is at the end)
2010-04-13 16:01:18,241 INFO ProActiveAgent.WindowsService - Starting ProActive Agent service 2010-04-13 16:01:18,491 INFO ProActiveAgent.CommonStartInfo - Selected action RMAction 2010-04-13 16:01:18,507 INFO ProActiveAgent.CommonStartInfo - The initial java heap size is -Xms64M and maximum java heap size is -Xmx64M 2010-04-13 16:01:18,507 INFO ProActiveAgent.ExecutorsManager - Creating 1 executors. 2010-04-13 16:01:18,600 DEBUG ProActiveAgent.ExecutorsManager - Loading events in the Executors Manager. 2010-04-13 16:01:18,600 DEBUG ProActiveAgent.ExecutorsManager - Loading CalendardEvent 4/12/2010 12:00:00 AM -> 4/18/2010 11:59:59 PM 2010-04-13 16:01:18,600 DEBUG ProActiveAgent.ProActiveRuntimeExecutor0 - Received start action request from AgentScheduler 2010-04-13 16:01:18,631 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - Started ProActive Runtime process (link: pid:4292) CLASSPATH=.;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\script-js.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\jruby-engine.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\jython-engine.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\commons-logging-1.0.4.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_SRM-common.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_ResourceManager.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_Scheduler-core.jar Command-line: C:\Program Files\Java\jre6\bin\java.exe -Dproactive.communication.protocol=rmi -Dproactive.rmi.port=1099 -Dproactive.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Dproactive.configuration="file:C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\proactive\ProActiveConfiguration.xml" -Djava.security.manager -Dpa.scheduler.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Dpa.rm.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Djava.security.policy="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\security.java.policy" -Dlog4j.configuration="file:///C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\log4j\log4j-client" -Dproactive.net.interface=eth3 -Xms64M -Xmx64M org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter -r rmi://pataud:1099 -n sed -s Agents 2010-04-13 16:01:18,631 DEBUG ProActiveAgent.ProActiveRuntimeExecutor0 - Setting process priority to Normal and max cpu usage to 100% 2010-04-13 16:01:18,631 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - Adding new process java (link: pid:4292) to the cpu limiter 2010-04-13 16:01:18,819 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - The ProActive Runtime process has exited for unknown reason 2010-04-13 16:01:19,833 DEBUG ProActiveAgent.ProActiveRuntimeExecutor0 - The ProActive Runtime process restart delay is 0 ms (link: barrier is 4/18/2010 11:59:44 PM) 2010-04-13 16:01:19,833 DEBUG ProActiveAgent.ProActiveRuntimeExecutor0 - Restart delay is now set to 5000 ms 2010-04-13 16:01:19,833 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - Started ProActive Runtime process (link: pid:7084) CLASSPATH=.;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\script-js.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\jruby-engine.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\jython-engine.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\commons-logging-1.0.4.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_SRM-common.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_ResourceManager.jar;C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\dist\lib\ProActive_Scheduler-core.jar Command-line: C:\Program Files\Java\jre6\bin\java.exe -Dproactive.communication.protocol=rmi -Dproactive.rmi.port=1099 -Dproactive.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Dproactive.configuration="file:C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\proactive\ProActiveConfiguration.xml" -Djava.security.manager -Dpa.scheduler.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Dpa.rm.home="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core" -Djava.security.policy="C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\security.java.policy" -Dlog4j.configuration="file:///C:\Users\Public\PPS\ProActiveScheduling-2.0.0_core\config\log4j\log4j-client" -Dproactive.net.interface=eth3 -Xms64M -Xmx64M org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter -r rmi://pataud:1099 -n sed -s Agents 2010-04-13 16:01:20,035 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - The ProActive Runtime process has exited for unknown reason 2010-04-13 16:01:20,082 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - An error occured in Events_OnNewProcess incrminatedProcess System.Diagnostics.Process (java) System.InvalidOperationException: Instance 'java' does not exist in the specified Category. at System.Diagnostics.CounterDefinitionSample.GetInstanceValue(String instanceName) at System.Diagnostics.PerformanceCounter.NextSample() at System.Diagnostics.PerformanceCounter.get_RawValue() at ProActiveAgent.CPULimiter.ProcessWatcher.GetProcessInstanceName(Int32 pid) at ProActiveAgent.CPULimiter.ProcessWatcher..ctor(Process processToWatch) at ProActiveAgent.CPULimiter.addProcessToWatchList(Process processToWatch) at ProActiveAgent.ProActiveRuntimeExecutor.Events_OnNewProcess(Object sender, NewProcessEventArgs args) 2010-04-13 16:01:20,082 INFO ProActiveAgent.ProActiveRuntimeExecutor0 - An error occured in Events_OnNewProcess incrminatedProcess System.NullReferenceException: Object reference not set to an instance of an object. at ProActiveAgent.ProActiveRuntimeExecutor.Events_OnNewProcess(Object sender, NewProcessEventArgs args) 2010-04-13 16:01:21,049 DEBUG ProActiveAgent.ProActiveRuntimeExecutor0 - The ProActive Runtime process restart delay is 5000 ms (link: barrier is 4/18/2010 11:59:44 PM)