shikinami

Members
 View Profile  See their activity

  • Posts

    6

  • Joined

  • Last visited

 Content Type 

Everything posted by shikinami

  1. shikinami
    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.
  2. shikinami
    Thanks. Yeah, one got up to 23GB before I noticed what was happening!
  3. shikinami
    Yes I think there was, but haven't been able to find anyone with the same problem - did your log files also balloon in size?
  4. shikinami
    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!)
  5. shikinami
    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.
  6. shikinami
    I also recently have had issues with this container: 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?