Darcalen

SONARR plugin, "Installed Version Unknown" error. Is anyone else having this issue? Attached is a snip of the plugin web interface. The installed version (according to Sonarr->System->About) is 2.0.0.4472. I'm betting the "unknown" version is prompting the update Sonarr button, but what is causing the unRAID interface for the plugin to not recognize the version in the first place? Is this something wrong with the plugin or is it a problem with Sonarr itself? And, how can I fix this? I have already completely removed Sonarr and reinstalled, I have tried to "update Sonarr" using the button and from the CLI, and I have also tried a fresh install of unRAID on a clean thumb drive and installed the plugin from scratch. All efforts end with the same results (see attached). Thanks in advance for any assistance.

PhAzE, hope you are doing better after your surgery. Having an issue with FileBot. I get the following message when trying to upgrade from 4.7.2 to 4.7.5 from the CLI: Get well and I hope you get enjoy the holidays. Thanks for your hard work on these, it's really appreciated.

I have been looking for this as well. If the majority don't care then I will have to live with it, but I've been trying to turn it off since it started showing up.

Yes, but it's the brand new fresh install that is showing to be 117MB, and not working. EDIT: Sonarr works on the 6.1.9 build I have. So is this a result of 32 bit Sonarr, on 32 bit unRAID, on a 64 bit HW platform? Or is the SuperMicro X11SSL-CF, with Intel® Pentium® CPU G4400 @ 3.30GHz, with a 32 bit unRAID the problem? Anyone else have issues with this particular MB? It's the first one I have come across, as I usually order a 10 series.

I'm going to test that next, however, a friend of mine and I were noticing that the size of the installation is is significantly different on a couple of matched system builds. 5.0.6 on a system with Sonarr running (no problem): install=19MB, config=35 ~ 54MB 5.0.6 on this system, sonar INOP: install=117MB, config=8MB Comparing directories on all 3 systems shows this system has 2 additional files that the working systems do not have. core @ 110MB libmediainfo.0.dylib @ 14MB may be nothing, but I found it odd that the installs were done within minutes of each other, and the files are not the same. I get that the configs may be different and grow, but I figured the install directories should be about the same. Thoughts? Red Herring? I'm gonn try the unRAID 6.1.9 on this server and will get back to you

Manually starting the plugin from the CLI gets this output: root@Tower:/boot/config/plugins# /usr/local/emhttp/plugins/Sonarr/scripts/rc.Sonarr buttonstart Starting Sonarr... /usr/local/emhttp/plugins/Sonarr/scripts/rc.Sonarr: line 206: 7493 Segmentation fault (core dumped) mono /usr/lib/mono/4.5/mozroots.exe --import --sync > /dev/null 2>&1 Start failed: PID created but no process exists unRAID 6 is great, but for what I am doing it adds a level of complexity that I can't afford right now. I will test it on unRAID 6 shortly, however, if the Sonarr app files are the same for both (since they are the same plugin) I will expect to get the same result, since I do not get this result by moving the "failed" install to a different server and booting there. I'm afraid I may have a hardware problem with this particular system. That's what I am trying to verify before I contact the company I bought the SM from.

Stop all my plugins and then delete the /usr/local/PhAzE-Common directory. Then empty the install directory. Leave your config directory alone. Start them up and see if sonarr works. Same error "Start Failed: PID created but no process exists" Stop it again, move your config folder a somewhere else for now and see if it starts fresh (possible db corruption). Same error "Start Failed: PID created but no process exists" set your config and install directories to /mnt/disk1/... instead of/mnt/user and see if that helps. Do that if the other fixes don't work. Same error "Start Failed: PID created but no process exists" This was all done with Sonarr being the only app I was restarting. I left the others off.

Originally it was not a fresh install, it was a ghosted copy, but when it failed, I uninstalled and removed files manually to be sure, then did a fresh install.

Not using cache. /mnt/user/appdata/install/Sonarr /mnt/user/appdata/config/Sonarr/config

And thanks for the super fast response.

Sonarr-env mono -V Mono JIT compiler version 4.2.3 (Stable 4.2.3.4/832de4b Thu Apr 21 10:37:54 EDT 2016) Copyright © 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com TLS: __thread SIGSEGV: altstack Notifications: epoll Architecture: x86 Disabled: none Misc: softdebug LLVM: supported, not enabled. GC: sgen

PhAzE, Been using your plugins on unRAID 5 for a couple of years (and unRAID 6), and have never had issue until now. I'm trying to figure out if this is a hardware issue, if there is a setting I missed, or is there something else amiss. PROBLEM Sonarr - I prepped the drives, and built it out as a media server (including CP, SAB, Plex.. (your plugins)), but the Sonarr app fails to start, and throws the error "Start Failed: PID created but no process exists." The app updated fine, but still fails to start (2.0.0.3### and 2.0.0.4###) On CLI, I get a "Line 1: ###### Segmentation fault (core dumped) mono /mnt/user/appdata/install/Sonarr/NzbDrone.exe" along with an error about line 206 in /usr/local/emhttp/plugins/Sonarr/scripts/rc.Sonarr. I'm running unRAID 5.0.6 on a SuperMicro X11SSL-CF MB with Intel Pent proc, 4GB RAM, SanDisk 8GB Boot, 2x HGST 4TB NAS drive (removed the other 4 drives to narrow troubleshooting). This is a first, and searching for the PID error on this site (and others) didn't reveal anything helpful. The same drives work fine in a different chassis (all plugins/apps start), and all the other services/plugins/apps are working fine, but Sonarr is failing on this system only. Can you (or anyone) throw me a bone?