nesede

Absolutely will do. Though I don't expect it would be at all (based on prior research and other people's comments on this). I just ran a test on about 60 nzbs and they were all completed successfully.

So apparently binhex container has some sort of unresolved bug when it comes to unpacking - it just hangs at the unpack step. There are quite a few posts in the thread that mention it (example). Restarting either nzbget or the container gets it working again but it really messes things up (at least for me, downloads are incorrectly failed and need reprocessing, sometimes *arrs get confused, etc). It's happening very often right now and not sure what started triggering it. Prior to the past couple of months I've been running issue-free for at least 2-3 years.

Can confirm, no issue. I had to rework the paths a bit.

The binhex nzbget container somehow developed the unpack bug so I'm considering transitioning over to this one. Would there be any issues if I backed up settings in that copy of nzbget and restored them in this one?

You were right - and I am reporting back as promised to tell you so haha.

Hah really? I am only looking into this because my players told me it's a new thing haha. Must be some new update to the game then that borked something.

Will report back, my unraid is running a measly 3200G so perhaps even one core would make it stutter a bit if it's also doing nzbget actions, not sure. My server is very small in terms of population, 1-2 max players at a time but they have explored quite a bit so maybe that matters too. Backups are about 50MB now.

I'm too big of a noob when it comes to *nix to know how to even start troubleshooting this - my friends were complaining that they experienced some extreme chug at a particular time this past week in Valheim. The server does a ton of work (plex, extraction, copying, etc) but I don't know that anything was happening at that specific time (and I have no idea how to check). Is there a way to increase this docker's priority to prevent future chugs? Edit: you know what, I'm almost certain it was the auto backup function. I've disabled it to see what happens (as I already have a cronjob running nightly).

Hah... I foolishly realized that I was only keeping 1 backup, so that means it's already backed up the bad db. I presume if I delete the database file that's somewhere in appdata, it will get recreated upon container restart?

Ah thank you, you are correct - here is a snippet: Mar 15, 2021 05:05:10.394 [0x14fdec302200] ERROR - SQLITE3:(nil), 11, database corruption at line 66053 of [bf8c1b2b7a] Mar 15, 2021 05:05:10.394 [0x14fdec302200] ERROR - SQLITE3:(nil), 11, database disk image is malformed in "PRAGMA cache_size=2000" Mar 15, 2021 05:05:10.394 [0x14fdec302200] ERROR - Database corruption: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=2000 Mar 15, 2021 05:05:10.394 [0x14fdec302200] ERROR - Error: Unable to set up server: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=2000 Is there a way to get this running again without wiping everything and just starting over?

Wondering if anyone knows what is causing this. Plex was working perfectly until 1-2 days ago and unless things have updated automatically, I haven't made any changes. 2021-03-14 21:50:46.004088 [info] Host is running unRAID 2021-03-14 21:50:46.028864 [info] System information Linux NSD-Server 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux 2021-03-14 21:50:46.076928 [info] OS_ARCH defined as 'x86-64' 2021-03-14 21:50:46.102543 [info] PUID defined as '99' 2021-03-14 21:50:46.133587 [info] PGID defined as '100' 2021-03-14 21:50:46.316057 [info] UMASK defined as '000' 2021-03-14 21:50:46.342165 [info] Permissions already set for volume mappings 2021-03-14 21:50:46.370062 [info] Deleting files in /tmp (non recursive)... 2021-03-14 21:50:46.399759 [info] TRANS_DIR defined as '/config/transcode' 2021-03-14 21:50:46.424443 [info] Starting Supervisor... 2021-03-14 21:50:46,569 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2021-03-14 21:50:46,569 INFO Set uid to user 0 succeeded 2021-03-14 21:50:46,571 INFO supervisord started with pid 6 2021-03-14 21:50:47,574 INFO spawned: 'plexmediaserver' with pid 62 2021-03-14 21:50:47,577 INFO spawned: 'shutdown-script' with pid 63 2021-03-14 21:50:47,577 INFO reaped unknown pid 7 (exit status 0) 2021-03-14 21:50:47,602 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23296384629008 for <Subprocess at 23296384627952 with name plexmediaserver in state STARTING> (stderr)> 2021-03-14 21:50:47,602 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-03-14 21:50:47,602 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23296384154112 for <Subprocess at 23296384627952 with name plexmediaserver in state STARTING> (stdout)> 2021-03-14 21:50:47,602 INFO exited: plexmediaserver (exit status 255; not expected) 2021-03-14 21:50:47,602 DEBG received SIGCHLD indicating a child quit 2021-03-14 21:50:48,605 INFO spawned: 'plexmediaserver' with pid 69 2021-03-14 21:50:48,633 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23296384629152 for <Subprocess at 23296384627952 with name plexmediaserver in state STARTING> (stdout)> 2021-03-14 21:50:48,633 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23296384316224 for <Subprocess at 23296384627952 with name plexmediaserver in state STARTING> (stderr)> 2021-03-14 21:50:48,634 INFO exited: plexmediaserver (exit status 255; not expected) 2021-03-14 21:50:48,634 DEBG received SIGCHLD indicating a child quit 2021-03-14 21:50:50,638 INFO spawned: 'plexmediaserver' with pid 74 2021-03-14 21:50:50,667 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23296384154112 for <Subprocess at 23296384627952 with name plexmediaserver in state STARTING> (stdout)> 2021-03-14 21:50:50,667 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23296384316320 for <Subprocess at 23296384627952 with name plexmediaserver in state STARTING> (stderr)> 2021-03-14 21:50:50,668 INFO exited: plexmediaserver (exit status 255; not expected) 2021-03-14 21:50:50,668 DEBG received SIGCHLD indicating a child quit 2021-03-14 21:50:53,673 INFO spawned: 'plexmediaserver' with pid 79 2021-03-14 21:50:53,701 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23296384629152 for <Subprocess at 23296384627952 with name plexmediaserver in state STARTING> (stdout)> 2021-03-14 21:50:53,702 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23296384315984 for <Subprocess at 23296384627952 with name plexmediaserver in state STARTING> (stderr)> 2021-03-14 21:50:53,702 INFO exited: plexmediaserver (exit status 255; not expected) 2021-03-14 21:50:53,702 DEBG received SIGCHLD indicating a child quit 2021-03-14 21:50:54,703 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

From my local network but NAT reflection is turned on. Haha I wish, Bell Canada is complete garbage and utterly useless. No I hear you, and I appreciate your help. Might be SOL for now unfortunately.

I wish there was a way to check whether my ISP blocks this port or not. I only used the site to confirm that my open ports are actually open. When using my external IP in steam's server browser it still doesn't see the server. I've even tried changing the default port to something in the 60000s (which is where some of my other functional ports are) and still no luck. I made sure to delete "UDP - Game Port Range" and re-create it as per the instructions. So not really sure what to do at this point.

I read some stuff about my ISP's modem (Bell homehub 3000 in Canada) being trash/unreliable at port forwarding so I put the SFP module into an EdgeRouter X SFP but the issue remains unfortunately.

Maybe I am stupid but I can't seem to access the Valheim docker over the internet. Ports 2456, 2457, 2458 UDP have been forwarded in my router. I think I know how to port forward because my other dockers have no issues (deluge, plex, etc) and https://www.yougetsignal.com/tools/open-ports/ confirms this. The Valheim server is only accessible over LAN. Not sure what I am doing wrong, any thoughts would be greatly appreciated.

Any ideas on this? Or perhaps as an alternative, is it possible to port forward to unraid's 192.168.0.x ip and then inside unraid forward that to the VM's 192.168.122.x ip somehow?

Apologies in advance if this is a dumb question, noob here. I am basically just trying to use iMessage on android through AirMessage, and I'm running into one of the following 2 issues: 1. If I use the Catalina VM as configured out of the box by spaceinvaderone's docker, it has a 192.168.122.0/24 ip, and I can't port forward to it in my router. I can log in to iMessage and the store just fine though. 2. If I bridge my unraid adapter and get the Catalina VM a 192.168.0.0/24 ip, I am no longer able to log into iMessage. Any thoughts would be greatly appreciated, not sure how to go about this.