Unraid, intermittent startup fail. PID file not writable

v2.0.0.5085 (binhex):
Mono version : Unknown:
Unraid 6.3.2, Docker:
https://hastebin.com/xapeqipoco.cs:

https://imgur.com/yAYX43u

Sonarr sometimes decides to start working for a day or a few weeks. It’s web page won’t load and the log file complains about the disk being full, so it can’t write the PID file. All four mechanical disks in the array have space, the cache has space and so does the flash key Unraid runs from. So this message is bogus.

Should I go in and just delete the PID file?

What is this about, I would like to understand.

Where does /config actually exist? Can you check the free space there when it happens?

The error comes from mono, I doubt it’s a mono bug, but something with mono telling the system to create the file is leading to the out of space error.

Mono? I though docker used python.

Anyway, the nzbdrone.pid file lives on the cache drive.

The cache drive has 641mb free right now, but the Sonarr image won’t start. Same error.

Could this be a virtual filesystem thing?

Mono? I though docker used python.

No, Sonarr is written in C# for .net), mono is an interpretation of .net for Linux/macOS. Python would require the entirety of Sonarr to be rewritten.

Could this be a virtual filesystem thing?

Sounds like it, but not sure if it’s an issue with the contain filesystem being full or with the mapping to the host.
Have you mapped /config for the container to the unRAID cache drive?

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.