Details
-
Fix
-
Status: Released (View Workflow)
-
Blocker
-
Resolution: Fixed
-
1.12
-
None
-
Tested on Linux (Ubuntu)
Description
Current Situation
The Agent is terminated immediately after starting as shown:
sos@lubuntu-vm:~/sos-berlin.com/jobscheduler_agent/bin$ ./jobscheduler_agent.sh start sos@lubuntu-vm:~/sos-berlin.com/jobscheduler_agent/bin$ ...JobScheduler Agent(4445) is started with pid=2574! ...see log file /home/sos/sos-berlin.com/jobscheduler_agent/var_4445/logs/jobscheduler_agent_4445.log ...watchdog for pid 2574 is started Hit ENTER to return to your command prompt. Error: Could not find or load main class com.sos.scheduler.engine.agent.main.AgentMain
The log file reads:
2017-10-10 14:46:36,000 +0200 [info] JobScheduler Agent terminated abnormal 2017-10-10 14:46:36,005 +0200 [info] Watchdog calls "/home/sos/sos-berlin.com/jobscheduler_agent/var_4445/tmp/kill_tasks_after_crash.sh" 2017-10-10 14:46:36,012 +0200 [info] "/home/sos/sos-berlin.com/jobscheduler_agent/var_4445/tmp/kill_tasks_after_crash.sh" doesn't exist or is empty. Nothing to do.
Desired Behaviour
The Agent should work as documented.