Welcome to the PufferPanel community forums! If you need help please register an account and post in the Support category.

Random stop without crash reports



  • Hello , my servers have random stop without any bukkit crash report
    only in scales logs

    [2016-02-19 20:11:42] [WARN] Server process detected as crashed and container was stopped (pid: 30252) for server 25ce9bd0-3ab6-40ce-be70-b35014393db9
    [2016-02-19 20:11:42] [WARN] Server process for 25ce9bd0-3ab6-40ce-be70-b35014393db9 killed after crash, server is now rebooting...
    

    I updated pufferpanel and scales to the last version at 19/2 and the error persists.

    How i can desactivate auto kill server when Server process detected as crashed and container was stopped?



  • Unfortunately, that is not something you can disable, because it is how Scales was designed (I disagree with it, and the new daemon will not be relying on that). But for most servers, it means that something is causing the process to report as not running, or it never specified a specific output.

    Do you think you can provide the complete Scales logs and the server's logs?



  • This is happening to me too.
    The server logs just end abruptly and restart.

    Scales log:
    http://i.imgur.com/JPKkLxJ.png



  • It's probably because your memory was too low, I had the same issue as yours, and after changing the memory so that it was higher, it worked and it didn't auto kill the server. I hope this fixes your issue.



  • Mc logs:
    http://pastebin.com/sffuepfx
    (last minutes before kill) any crash report

    Scales:
    http://pastebin.com/PHeyrd5k

    [2016-02-23 17:48:09] [WARN] Server process detected as crashed and container was stopped (pid: 687) for server 25ce9bd0-3ab6-40ce-be70-b35014393db9
    [2016-02-23 17:48:09] [WARN] Server process for 25ce9bd0-3ab6-40ce-be70-b35014393db9 killed after crash, server is now rebooting...

    Are constants

    I tryed changing the memory for the mc server and the problem continues..

    I have 3 nodes , only this error is occurring in a single node with 4gb ram .
    I checked at the used memory and does not exceed 70%. I have another node with 2gb ram and this problem not exist. I've tried reinstalling scales and can not find solution.



  • Open your system logs and see what is happening around those times. Scales is not killing the server, so it sounds like either docker is killing them due to OOM, or something on the system is killing it.



  • @AwesomePinch said:

    It's probably because your memory was too low, I had the same issue as yours, and after changing the memory so that it was higher, it worked and it didn't auto kill the server. I hope this fixes your issue.

    @LordRalex said:

    Open your system logs and see what is happening around those times. Scales is not killing the server, so it sounds like either docker is killing them due to OOM, or something on the system is killing it.

    Thanks! After looking at the logs usingdmesg I realised it was killed because of running out of memory.


Log in to reply
 

3
Online

666
Users

708
Topics

3.2k
Posts

Looks like your connection to PufferPanel Community was lost, please wait while we try to reconnect.