Menu

The agent treats Setup as a cluster

Help
2026-03-19
2026-03-26
  • John Baltimore

    John Baltimore - 2026-03-19

    I have installed an agent. I do not intend to run it in a cluster (I do not have a commercial license). However, the log shows that it is a cluster

    2026-03-18T16:06:48,234 info js7.cluster.ClusterNode - Backup cluster Node:Backup, awaiting appointment from a primary node

    How can I configure it for standalone operation?

     
  • Andreas

    Andreas - 2026-03-19

    Hi John,

    check your Agent's <agent-data>/config/agent.conf file if it holds the entry
    js7.journal.cluster.node.is-backup=yes

    If available, remove the setting. It makes an Agent the default standby node in an Agent Cluster. When using installer scripts such as js7_install_agent.sh (Install-JS7Agent.ps1) then the related command line switch that will create the setting is --Standby.

    After removal delete the <agent-data>/state directory as it persists the Agent's standby role. The directory will be recreated when you start the Agent.

     
  • John Baltimore

    John Baltimore - 2026-03-26

    Thank you very much for your help. The agent is working now.

    I found the cause of this incorrect configuration. In the Windows setup program for the agent, in step 6 of 12, you can select the checkbox "Installation as standby node for a cluster (requires commercial license)." That was the case for me. I think this option should not be selectable if you specified "GBU GPL v3.0 License" in step 2 of 12.

     

Log in to post a comment.

MongoDB Logo MongoDB