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

    FusionAuth stops randomly, but nothing in the log

    Scheduled Pinned Locked Moved
    Q&A
    0
    2
    416
    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 use fusionauth on CentOS as an operating system service. Lately I often find that the service is up and running for a day or two, then randomly, it stops working.

      The problem is that I can't find anything in the log so I don't understand what's going on.

      Do you have any suggestions for identifying the problem?

      Originally posted here: https://github.com/FusionAuth/fusionauth-issues/issues/1048

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

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

        You could take a look at the system log. If the OOM killer ended a process due to memory constraints it will be logged there.

        You might see lines like:

        Dec 30 12:00:38 vps kernel: Out of memory: Kill process 30047 (java) score 98 or sacrifice child
        

        The OOM killer will begin killing services once the kernel runs out of memory. The solution will be to allocate less memory to FusionAuth or to increase the amount of RAM available to the host OS. You can do the former with the fusionauth-app.memory setting. See the configuration reference for more details.

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

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