JobScheduler / Discussion / Early Warnings: The agent won't start

Maybe you can help me.
I'm using version 2.8.2.
The agents stopped running in my environment.
So I deleted all the journales. That didn't help.
I then deleted the controller in JOC Cockpit.
I added the controller again.
I added the agent and deployed it.
The agent remains in the “initialized” status.
The controller is "operational"

Agent Log

2026-03-18T16:06:44,982 info  js7.base.configutils.Configs - Reading configuration file C:\ProgramData\sos-berlin.com\js7\agent_4435\config\private\private.conf
2026-03-18T16:06:44,984 info  js7.base.configutils.Configs - Reading configuration file C:\ProgramData\sos-berlin.com\js7\agent_4435\config\agent.conf
2026-03-18T16:06:47,042 info  js7.common.pekkohttp.web.session.SessionRegister - Session:1 for User:System: Login (2.8.2 ✔) (eternal)
2026-03-18T16:06:47,994 info  js7.base.crypt.generic.DirectoryWatchingSignatureVerifier - Trusting signature keys:
2026-03-18T16:06:48,001 info  js7.base.crypt.generic.DirectoryWatchingSignatureVerifier -   X.509 origin=C:\ProgramData\sos-berlin.com\js7\agent_4435\config\private\trusted-x509-keys
2026-03-18T16:06:48,001 info  js7.base.crypt.generic.DirectoryWatchingSignatureVerifier -     X.509 certificate EMAILADDRESS=admin@sos-berlin.com, CN=SOS Intermediate CA, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE · CA 2020-06-17T23:49:14Z...2030-06-15T23:49:14Z fingerprint=d2689951 4827d60c 503001b8 0dc75024 e57b7de8 keyUsage=digitalSignature,keyCertSign,crlSign
2026-03-18T16:06:48,047 info  js7.subagent.Subagent - SIGNED SCRIPT INJECTION IS ALLOWED
2026-03-18T16:06:48,105 info  js7.subagent.Subagent - Subagent is ready to be dedicated
────────────────────────────────────────────────────────────────────────────────
2026-03-18T16:06:48,183 info  js7.common.pekkohttp.web.SinglePortPekkoWebServer - http://0.0.0.0:4435 Subagent web services are available - ACCESS IS PUBLIC - EVERYONE HAS ACCESS (public = true)
2026-03-18T16:06:48,234 info  js7.cluster.ClusterNode - Backup cluster Node:Backup, awaiting appointment from a primary node
2026-03-18T16:19:12,438 info  js7.common.pekkohttp.web.session.SessionRegister - Session:2 for User:Anonymous: Login (2.8.2 ✔)
2026-03-18T16:19:12,438 info  js7.common.pekkohttp.web.session.SessionRegister - Session:3 for User:Anonymous: Login (2.8.2 ✔)

Controller Log

2026-03-18T16:19:09,971 WARN  js7.common.pekkohttp.web.auth.GateKeeper - (http://0.0.0.0:4424) User 'JOC' logs in with credentials despite public=true
2026-03-18T16:19:09,971 WARN  js7.common.pekkohttp.web.auth.GateKeeper - (http://0.0.0.0:4424) User 'JOC' logs in with credentials despite public=true
2026-03-18T16:19:09,971 info  js7.common.pekkohttp.web.session.SessionRegister - Session:11 for User:JOC: Login (2.8.2 ✔)
2026-03-18T16:19:10,019 info  js7.journal.Journal - Event ⎛UnsignedSimpleItemAdded(AgentRef(Agent:TestAgent,Vector(Subagent:TestAgent),None,None,Some(ItemRevision(0))))
2026-03-18T16:19:10,019 info  js7.journal.Journal - Event ⎝UnsignedSimpleItemAdded(SubagentItem(Subagent:TestAgent,Agent:TestAgent,http://localhost:4425,false,Some(ItemRevision(0))))
2026-03-18T16:19:10,119 info  js7.cluster.watch.ClusterWatchService - ClusterWatchService(ClusterWatch:controller/Primary/TestAgent)(AgentClient(http://localhost:4425/agent)) started
2026-03-18T16:19:10,741 WARN  js7.controller.agent.AgentDriver - (TestAgent) Coupling failed: NoDirector: Agent Director is still not ready
2026-03-18T16:19:10,748 info  js7.journal.Journal - Event  Agent:TestAgent <-: AgentCouplingFailed(NoDirector: Agent Director is still not ready)
2026-03-18T16:19:12,145 info  js7.journal.Journal - Event ⎛UnsignedSimpleItemAdded(AgentRef(Agent:StandaloneAgent,Vector(Subagent:StandaloneAgent),None,None,Some(ItemRevision(0))))
2026-03-18T16:19:12,145 info  js7.journal.Journal - Event ⎝UnsignedSimpleItemAdded(SubagentItem(Subagent:StandaloneAgent,Agent:StandaloneAgent,http://localhost:4435,false,Some(ItemRevision(0))))
2026-03-18T16:19:12,164 info  js7.cluster.watch.ClusterWatchService - ClusterWatchService(ClusterWatch:controller/Primary/StandaloneAgent)(AgentClient(http://localhost:4435/agent)) started
2026-03-18T16:19:12,572 WARN  js7.controller.agent.AgentDriver - (StandaloneAgent) Coupling failed: NoDirector: Agent Director is still not ready
2026-03-18T16:19:12,575 info  js7.journal.Journal - Event  Agent:StandaloneAgent <-: AgentCouplingFailed(NoDirector: Agent Director is still not ready)

Hi John,

there are two prominent root causes for the issue:

You are trying to operate an Agent Cluster with the Open Souce License
- Clustering is not in scope of the Open Source License, see JS7 - License.
- The same will apply if you own a commercial license, but did not deploy the license key to the Primary and Secondary Director Agent.
- Check both Director Agent's ./logs/watchdog.log if it includes the information that a commercial license was identified.
When using a commercial license and setting up an Agent cluster, then for initial operation one of the Director Agents must be configured as the standby node.
- To this purpose the Standby Agent's ./config/agent.conf file has to include the setting: js7.journal.cluster.node.is-backup=yes
- The agent.log of your previous post suggests that this is the Standby Director Agent. There seems not to be a connection attempt from the Active Director Agent. In an Agent Cluster we find 1 Director Agent as the active node and 1 Director Agent as the standby node. The standby node is available. Please check the Active Director Agent's ./logs/agent.log file for reasons why it would not connect to the Standby Direcor Agent

The agent won't start

JobScheduler workload automation to execute jobs and workflows

Forums

Help

The agent won't start

The agent won't start

JobScheduler workload automation to execute jobs and workflows

Forums

Help

The agent won't start document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

The agent won't start