Jump to content

shikinami

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by shikinami

  1. On 1/30/2021 at 1:51 AM, ich777 said:

    I have implemented a quick fix for now and disabled the log to prevent the logfile from ballooning.

    Please grafik.png.be300c2cfa00ab726a0de71a751fef3f.png the container.

    Sorry to be a bother again! 

    The log fix seems to work for the huge files inside /logs/. I also read the replies to the github issue you opened and your fix based on that info seems to be working. However, I've noticed there's now a 'masterLog.0' file within the root directory that is also getting huge within just a few minutes. 

    We're still experiencing similar random crashes, so I'm unsure of if these 'logs' are the root problem or are just symptoms of something else.

    Screenshot 2021-02-07 012947.png

    • Thanks 1
  2. 27 minutes ago, ich777 said:

    I will try to replicate the issue, are you talking about a complete fresh installation with nothing changed in the template?

    Thank you - yes, I deleted the docker, image, and the folder inside /appdata/. Then reinstalled from community apps and left everything default.

    (The server ran perfectly fine for many months up until recently, so thanks for all the fun times we've had so far!)

  3. If anyone knows a solution or is able to replicate this issue: the SCP Secret Laboratory docker is generating absolutely huge log files within a few minutes of running, and I can't find a way to disable or prevent it from happening. It looks like the log file is corrupting since there are only a few lines (no garbage characters, all file readers show nothing). A fresh install with all default settings has the same issue. 

    Screenshot 2021-01-29 235955.png

    unknown.png

  4. I also recently have had issues with this container:

     image.png.2d00f4ed36b87d31451f5c8c9c88130f.png

     

    I haven't changed anything about the server (I might've updated the container, don't remember when it started). Changing ports with "WebUI" "WEBUI_PORT" etc etc doesn't fix it. All other containers are running smoothly still.

    `netstat -plnt | grep :8090` reveals that the address should definitely be available. Anyone have any ideas?

     

×
×
  • Create New...