USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND It quickly got above my skill level, but I don't think they got to the bottom of it either, if it is the same underlying problem. It seems SAB had a similar issue when using Direct Unpack, I didn't test running the exact same unrar command outside of the docker, but will next time the unpacking hangs. This is consistent with the docker restart workaround. If I kill the main nzbget process, it restart itself and spawns a new unrar process that finishes quickly. During this statem, Sys load in TOP is consistently high (4+) and so is CPU usage for both nzbget and unrar. When a file is stuck in unpacking, the docker console shows an unrar process running for a few seconds, then re-spawning with a new PID.
I've been seeing more than usual of the unrar hanging lately, so I thought I'd try to get to the bottom of it again.īut just in case it gives you any new ideas, here's what I found.
0 kommentar(er)
