FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    runtime mode differences mean that FusionAuth won't start

    Scheduled Pinned Locked Moved
    Q&A
    logs nodes startup
    0
    2
    1.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • danD
      dan
      last edited by

      I see this message in my log file:

      2020-12-15 9:20:23.203 AM ERROR io.fusionauth.api.service.system.NodeService - Node [1bdcee86-5568-48cc-b680-9e39532bdd6c] cannot be added. The runtime mode is [Production] and this node in [Development] mode.
      

      What does this mean? FusionAuth doesn't start, how can I fix this?

      --
      FusionAuth - Auth for devs, built by devs.
      https://fusionauth.io

      1 Reply Last reply Reply Quote 0
      • danD
        dan
        last edited by

        It looks like you switched to development mode from production mode, possibly to run some migrations automatically.

        This message means that FusionAuth sees an entry in its node records that would lead to an incompatible configuration. What we really want to avoid is a cluster of FusionAuth instances with some in development and others in production, as that might lead to some confusing behavior.

        If you are running a single node, you can try restarting FusionAuth a few times and that node record should be reset. You can also switch the node back to production and make sure it shuts down cleanly, which should remove the node record.

        --
        FusionAuth - Auth for devs, built by devs.
        https://fusionauth.io

        1 Reply Last reply Reply Quote 0
        • First post
          Last post