I really need help here please. Does anyone have these problems I'm having where file access from Docker containers is stalling? I had this in another post, but apparently it's buried. Drive spindown is not enabled. I have tried with only one container running (Plex, or any other), I have limited CPU & memory on the containers, I have left them completely open on CPU & RAM. No change, and no indication (to me) of what needs to be fixed. Thank you.

 

 

Edited August 14, 20187 yr by zippyd00

Why did you start another thread? It isn't obvious where to reply now.

 

Did you fix the OOMs? Try shutting down some of your containers while you troubleshoot so as to break the problem up into smaller ones. It looks as though resilio-sync is the process that's being reaped so that's where I'd start looking.

No one responded to the original thread in six weeks, that's why.

 

I paid $150 for two licenses on two servers, only have this forum for support and can't get this resolved.

 

Like I said in both, Resilio can be completely stopped, and only one container running (doesn't matter which), and no change to the performance. Random I/O stalls.

 

I deleted the docker img and rebuilt only Plex once, only another a different time, and same on both.

 

I can give all the data you want, logs, etc. Willing to try anything. Just need some assistance.

Edited August 14, 20187 yr by zippyd00

4 hours ago, John_M said:

Did you fix the OOMs?

 

that @1812 pointed out to you on 1 July? 

 

 

As I responded also on July 1, I had not only limited the memory on that container, but I also simply disable the Resilio container. As of right now after the rebuild of the Docker image, Resilio isn't even installed.

That doesn't answer the question as to whether the OOMs and subsequent call traces are still happening. Diagnostics covering a period when you are experiencing your issue would be useful.

 

And relax, I'm trying to help you. I'm just a user too.