dirtysanchez

Radarr stopped working. From what I can tell from the logs it appears Radarr updated to v3 but blew up in the migration process. Any help would be appreciated. Relevant log section below. EDIT: Rolled back to v0.2 and container starts but has no config (no indexers, no movies, etc). Tried restoring db from backups and container fails with “corrupted db”. Long story short, there doesn’t appear to be much support for all the v3 upgrade failures (not throwing shade, I understand you all do this for nothing but the love of the platform and the community), so I started from scratch and reconfigured a fresh v3 from the ground up. All good now. [Info] Bootstrap: Starting Radarr - /app/radarr/bin/Radarr.dll - Version 3.0.0.4204 [Info] AppFolderInfo: Data directory is being overridden to [/config] [Info] Router: Application mode: Interactive [Info] MigrationController: *** Migrating data source=/config/radarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** [Info] MigrationLoggerProvider: *** 165: remove_custom_formats_from_quality_model migrating *** [Info] remove_custom_formats_from_quality_model: Starting migration to 165 [Error] MigrationLoggerProvider: Newtonsoft.Json.JsonReaderException: Unterminated string. Expected delimiter: ". Path 'protocol', line 16, position 1. at NzbDrone.Common.Serializer.Json.Deserialize[T](String json) in D:\a\1\s\src\NzbDrone.Common\Serializer\Json.cs:line 48 at NzbDrone.Core.Datastore.Migration.remove_custom_formats_from_quality_model.AddIndexerFlagsToBlacklist(IDbConnection conn, IDbTransaction tran) in D:\a\1\s\src\NzbDrone.Core\Datastore\Migration\165_remove_custom_formats_from_quality_model.cs:line 102 at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor.Process(PerformDBOperationExpression expression) at FluentMigrator.Expressions.PerformDBOperationExpression.ExecuteWith(IMigrationProcessor processor) at FluentMigrator.Runner.MigrationRunner.<>c__DisplayClass70_0.<ExecuteExpressions>b__1() at FluentMigrator.Runner.StopWatch.Time(Action action) at FluentMigrator.Runner.MigrationRunner.ExecuteExpressions(ICollection`1 expressions) [v3.0.0.4204] Newtonsoft.Json.JsonReaderException: Unterminated string. Expected delimiter: ". Path 'protocol', line 16, position 1. at NzbDrone.Common.Serializer.Json.Deserialize[T](String json) in D:\a\1\s\src\NzbDrone.Common\Serializer\Json.cs:line 48 at NzbDrone.Core.Datastore.Migration.remove_custom_formats_from_quality_model.AddIndexerFlagsToBlacklist(IDbConnection conn, IDbTransaction tran) in D:\a\1\s\src\NzbDrone.Core\Datastore\Migration\165_remove_custom_formats_from_quality_model.cs:line 102 at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor.Process(PerformDBOperationExpression expression) at FluentMigrator.Expressions.PerformDBOperationExpression.ExecuteWith(IMigrationProcessor processor) at FluentMigrator.Runner.MigrationRunner.<>c__DisplayClass70_0.<ExecuteExpressions>b__1() at FluentMigrator.Runner.StopWatch.Time(Action action) at FluentMigrator.Runner.MigrationRunner.ExecuteExpressions(ICollection`1 expressions) [Fatal] ConsoleApp: EPIC FAIL! [v3.0.0.4204] NzbDrone.Common.Exceptions.RadarrStartupException: Radarr failed to start: Error creating main database ---> Newtonsoft.Json.JsonReaderException: Unterminated string. Expected delimiter: ". Path 'protocol', line 16, position 1. at NzbDrone.Common.Serializer.Json.Deserialize[T](String json) in D:\a\1\s\src\NzbDrone.Common\Serializer\Json.cs:line 48 at NzbDrone.Core.Datastore.Migration.remove_custom_formats_from_quality_model.AddIndexerFlagsToBlacklist(IDbConnection conn, IDbTransaction tran) in D:\a\1\s\src\NzbDrone.Core\Datastore\Migration\165_remove_custom_formats_from_quality_model.cs:line 102 at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor.Process(PerformDBOperationExpression expression) at FluentMigrator.Expressions.PerformDBOperationExpression.ExecuteWith(IMigrationProcessor processor) at FluentMigrator.Runner.MigrationRunner.<>c__DisplayClass70_0.<ExecuteExpressions>b__1() at FluentMigrator.Runner.StopWatch.Time(Action action) at FluentMigrator.Runner.MigrationRunner.ExecuteExpressions(ICollection`1 expressions) at FluentMigrator.Runner.MigrationRunner.ExecuteMigration(IMigration migration, Action`2 getExpressions) at FluentMigrator.Runner.MigrationRunner.ApplyMigrationUp(IMigrationInfo migrationInfo, Boolean useTransaction) at FluentMigrator.Runner.MigrationRunner.MigrateUp(Int64 targetVersion, Boolean useAutomaticTransactionManagement) at FluentMigrator.Runner.MigrationRunner.MigrateUp(Boolean useAutomaticTransactionManagement) at FluentMigrator.Runner.MigrationRunner.MigrateUp() at NzbDrone.Core.Datastore.Migration.Framework.MigrationController.Migrate(String connectionString, MigrationContext migrationContext) in D:\a\1\s\src\NzbDrone.Core\Datastore\Migration\Framework\MigrationController.cs:line 67 at NzbDrone.Core.Datastore.DbFactory.CreateMain(String connectionString, MigrationContext migrationContext) in D:\a\1\s\src\NzbDrone.Core\Datastore\DbFactory.cs:line 115 --- End of inner exception stack trace --- at NzbDrone.Core.Datastore.DbFactory.CreateMain(String connectionString, MigrationContext migrationContext) in D:\a\1\s\src\NzbDrone.Core\Datastore\DbFactory.cs:line 130 at NzbDrone.Core.Datastore.DbFactory.Create(MigrationContext migrationContext) in D:\a\1\s\src\NzbDrone.Core\Datastore\DbFactory.cs:line 79 at NzbDrone.Core.Datastore.DbFactory.Create(MigrationType migrationType) in D:\a\1\s\src\NzbDrone.Core\Datastore\DbFactory.cs:line 67 at NzbDrone.Core.Datastore.DbFactory.RegisterDatabase(IContainer container) in D:\a\1\s\src\NzbDrone.Core\Datastore\DbFactory.cs:line 45 at Radarr.Host.NzbDroneConsoleFactory.Start() in D:\a\1\s\src\NzbDrone.Host\ApplicationServer.cs:line 95 at Radarr.Host.Router.Route(ApplicationModes applicationModes) in D:\a\1\s\src\NzbDrone.Host\Router.cs:line 56 at Radarr.Host.Bootstrap.Start(ApplicationModes applicationModes, StartupContext startupContext) in D:\a\1\s\src\NzbDrone.Host\Bootstrap.cs:line 77 at Radarr.Host.Bootstrap.Start(StartupContext startupContext, IUserAlert userAlert, Action`1 startCallback) in D:\a\1\s\src\NzbDrone.Host\Bootstrap.cs:line 40 at NzbDrone.Console.ConsoleApp.Main(String[] args) in D:\a\1\s\src\NzbDrone.Console\ConsoleApp.cs:line 41 Press enter to exit... Non-recoverable failure, waiting for user intervention...

Everything working as it should. Marking this as solved.

Nuked the docker.img and recreated containers from my templates. So far so good. I am able to stop containers successfully. I'll marked this solved in another 24 hours if all is still working. Thanks again for the help.

Thanks for taking a look Squid. Yes, plex crashed a few days ago (first time in years if I recall correctly) and that is what lead to the discovery of the issue as I was unable to get it running again without a hard reset that caused an unclean shutdown. The following day I discovered it went beyond the plex container when I was attempting to stop some containers to prepare for migrating all my drives to xfs. As for the current container refusing to stop (not the docker system per se), even if you turn Docker off it doesn't kill the running containers. You can change Settings > Docker > Enable Docker to no and the containers don't die nor does Docker itself stop. docker ps still shows them running. Once the migrations are complete (tomorrow morning) I'll nuke the docker.img and reinstall all dockers per your suggestion and report back. Thank you for the assistance.

Hello all, Recently starting having an issue, unsure when exactly it started as I don't often have a reason to stop a docker container. Issue exists on 6.6.6 as well as 6.6.5. Unknown if it existed in prior versions or if it is even unRAID OS version related. I run the following containers. All containers are the linuxserver.io version with the exception of UniFi Video which is pducharme: Plex UniFi UniFi Video Radarr Sonarr Sabnzbd Tautulli Transmission Problem is as follows. If you attempt to stop a running container, it does not stop. The GUI shows the spinning arrows forever and once you finally refresh it still shows it running. The container is in fact dead at that point and the container WebGUI does not respond, but it does not finish exiting correctly. Issuing a docker stop containername or a docker kill containername from cmd line does nothing and hangs until you ctrl-c out. I have not found a way to kill and/or restart the container successfully. Some of the container logs appear as if the container exited successfully, while others the last line in the logs is "[s6-finish] syncing disks". At this point the only way to get the container running again is to restart unRAID. Problem is unRAID is now unable to stop the docker service, and therefore unable to stop the array. The only way to restart the server is a hard power cycle, and hence an unclean shutdown. In limited testing I have found that if only Plex and UniFi Video are running you can stop the array and the containers will successfully stop and the array successfully stops. I have yet to start the containers one by one and find which ones are causing the issue. I am currently in the process of migrating all drives to xfs and so have not yet had the time to test further. All that said, it appears when the containers are automatically stopped/restarted weekly to update via CA Auto Update settings, they do stop and start correctly. I have searched the forums and have not found a similar issue with resolution. Attached are diags from when the containers were hung. Any assistance would be appreciated. landfill-diagnostics-20190102-1851.zip

Hello all, Updated to 6.6.6 from 6.6.5. I am now unable to stop dockers. Most containers are linuxserver.io. Have also tried to stop from cmd line and it does not stop. Also rolled back to 6.6.5 and no change. It is possible this started before the upgrade and I just haven't had to manually stop a docker in a month or two. Did some searching and didn't find much. Not sure this is related to the unRAID version or some other issue. Diags attached. Many thanks for any assistance. landfill-diagnostics-20190102-1851.zip

Good to know. Thank you.

There was, at least on mine (default admin/pass), but that may have been a remnant from a previous docker as I migrated to the Linuxserver docker from another one. Anyway, I figured out how to disable it. Stop the docker, change the rpc-authentication-required setting to false in the settings.json file in the docker appdata directory. It will no longer prompt for a password.

Any way to remove the username and password for the webGUI? Environment variable or via the settings.json file?

Thank you!

Any thoughts on creating a Ubiquiti UniFi controller docker? I know one already exists by pducharme, but he doesn't seem to be around much and the UniFi controller was updated to 4.7.5 almost a month ago and his docker is still at 4.6.6.

Er may or may not be working on souch a thing, but consensus in the group is that sonarr is better Yes, I've seen the same mentioned by others as well. I guess I just haven't tried to migrate to Sonarr yet as it's quite a bit more difficult to get setup and working properly (or so I've heard), but once running it puts SickBeard to shame. Maybe I'll bite the bullet this weekend and give it a shot.

Any chance of a linuxserver.io SickBeard Docker? I've migrated all of my Dockers to the linuxserver.io Dockers where possible, but no Docker for SickBeard makes me sad...

I did similar to jumperalex. I remapped /transcode in the Docker config from /tmp to /mnt/cache/apps/plex/Library/Application Support/Plex Media Server/Cache/Transcode. I didn't change the path inside Plex itself as I mapped the full path to the transcode directory to /transcode in the Docker.

hex, you are correct about Plex's behavior and it is why I advocated against moving transcoding to RAM in the past. I had the same problem as dirtysanchez, but it was only on long high bit rate videos (movie BD rips). All other stuff ran fine. When I dug into it I was basically juuuuuust not hitting the wall with the shorter lower bit rate stuff but the BD movie rips, at full bit rate, would fill /tmp in about 30-45 min. Crash. flush. restart. rinse. repeat. Frankly the concern over SSD wear is misplaced given all current evidence and most plex / unraid implementations I can guess at. Even with 24/7 streaming of a reasonable number of 20mbit streams the SSD will outlive most people, no less its likely useful life. Hex, they are approx 1.5GB 720p mkv files. It is palying on a Roku, and so is resulting in only the audio being remuxed, therefore the transcoded file size should be approx 1.5GB. It's certainly filling up /tmp before the play completes. I'm going to have to agree with jumperalex here. While transcoding to RAM can save a bit of wear and tear on the cache drive (assuming SSD) it's likely not something that is going to make a significant difference in the life of the SSD, assuming newer-gen SSD's. They have proven to have significantly longer endurance than even the manufacturer ratings in most cases, and even with the added writes of transcoding to the SSD will likely outlast their useful life. I have moved transcoding back to the SSD and will leave it there. If you can transcode to RAM without issues, then I see no point in not doing so. But if you have issues with /tmp filling up, it's probably best to just move transcoding back to cache and be done with it.