Sonar will not import, spins foever

Sonarr version (exact version): 3.0.3.653
Mono version (if Sonarr is not running on Windows): ubuntu - 6.4.0.198
OS: ubuntu 18.04

Sonarr will not import items… It just spins forever. I have legit started import before work at 6:50am, get HOME from work at 7pm and just spins.

sonarr, and files are chown/chgrp to the SAME user, all are on SAME harddrive.

trace log - http://paste.ubuntu.com/p/XFQYWvGncH/

debug log - http://paste.ubuntu.com/p/RDHMDSRVxq/

edited:
19-11-6 01:46:11.1|Trace|Owin|SQLite error (5): database is locked
19-11-6 01:46:11.1|Trace|Owin|

I have remade the database multiple times, AS soon as its done making the database it gets database is locked…

One or two here and there isn’t a problem, just means it was retried again and was successful. Unless you’re seeing tons of these in a really short span this isn’t a problem.

It looks like Sonarr is restarting often. Grabbing the standard output/error to a file would be a good start as that’ll capture logs that Sonarr was unable to write to the log file due to mono crashing, which it could be given the number of restarts.

sonar.txt - http://paste.ubuntu.com/p/pmM4T45YDc/

That shows the same thing, you need to redirect standard output and error to a file, not grab the existing Sonarr log file.

would u like to explain how??

since i have sonarr on trace logs and i have uploaded all 3…

I have reinstalled/deleted folders/files and made a fresh install when i made this post, so i can try everything u all ask on a new slate

Redirect to a file:

Upload that file after a few minutes.

Also worth trying to run Sonarr directly instead of a startup script.

can’t run directly I just get segmentation fault

[cyber@box]:(10.2Mb)~$ /usr/bin/mono --debug /usr/lib/sonarr/bin/Sonarr.exe -nobrowser -data=/var/lib/sonarr > /home/cyber/sonarr/1.txt 2 > /home/cyber/sonarr/2.txt
Segmentation fault
[cyber@box]:(10.2Mb)~$ cd /home/cyber/sonarr
[cyber@box]:(677b)~/sonarr$ ls
1.txt 2.txt
[cyber@box]:(677b)~/sonarr$ tail 2.txt
[Info] Bootstrap: Starting Sonarr - /usr/lib/sonarr/bin/Sonarr.exe - Version 3.0.3.653
[Info] AppFolderInfo: Data directory is being overridden to [/var/lib/sonarr]
[Info] Router: Application mode: Interactive
[Info] MigrationLogger: *** Migrating data source=/var/lib/sonarr/sonarr.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
[Info] MigrationLogger: *** Migrating data source=/var/lib/sonarr/logs.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
[Info] OwinHostController: Listening on the following URLs:
[Info] OwinHostController: http://*:8989/
[Info] SonarrBootstrapper: Starting Web Server

hello? no response after that?

Hi. Missed the reply…

Well that would explain why Sonarr is restarting constantly…

You didn’t include the fault, but start there, it’s the problem.

Well sonarr use to work with that problem… and how to fix?? i google and google at first and gave up bc no one ever fixed it for ubuntu 18.04 with mono

That’s going to depend on the exact error. Likely an issue with mono or a dependency of it, but not sure what it could be.

well i have followed all sonarr’s instructions… without futher instructions this issue isn’t going to get resolved.

got any ideas?

None without seeing the segfault and we’ll have to see.

[cyber@box]:(10.2Mb)~$ /usr/bin/mono --debug /usr/lib/sonarr/bin/Sonarr.exe -nobrowser -data=/var/lib/sonarr
[Info] Bootstrap: Starting Sonarr - /usr/lib/sonarr/bin/Sonarr.exe - Version 3.0.2.529
[Info] AppFolderInfo: Data directory is being overridden to [/var/lib/sonarr]
[Info] Router: Application mode: Interactive
[Info] MigrationLogger: *** Migrating data source=/var/lib/sonarr/sonarr.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
[Info] MigrationLogger: *** Migrating data source=/var/lib/sonarr/logs.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
[Info] OwinHostController: Listening on the following URLs:
[Info] OwinHostController: http://*:8989/
[Info] SonarrBootstrapper: Starting Web Server
Segmentation fault

Segmentation fault happens as soon as i hit f5 on website.

That’s it? Nothing logged to console or the log file after that?

It sounds similar to this thread:

But beyond that I have no idea, segmentation fault could be tons of things, possibly hardware related too.

[cyber@box]:(28.5Mb)/var/lib/sonarr/logs$ pastebinit sonarr.debug.txt
http://paste.ubuntu.com/p/cBCSv5zNR9/
[cyber@box]:(28.5Mb)/var/lib/sonarr/logs$ pastebinit sonarr.txt
http://paste.ubuntu.com/p/4x8MZxB9zr/

i tried to look for things with Vivaldi but couldn’t find anything but a 500.
so just gonna blame it on the hardware is the reason I can’t use your software?? since mono is working fine for other things…

No, I said it’s a possibility. We’ve seen bad RAM cause all sorts of issues before, but there is not much for us to go on, essentially we know there was an error. We can’t make mono tell us more about that error if it’s taking Sonarr down.

It could be mono 6, who knows, given the information I have no idea, grasping at straws.

Does the same thing happen when you try to load the UI in another browser?

Sonarr’s log files aren’t useful if mono crashes as Sonarr has no way to write to the log file. Capturing the standard output and error to a file is the only way to get a log of it, outside of a screenshot of the console output (which is worse than a text file of it).

Things to try:

  • Another browser
  • Downgrading mono to 5.20
  • Running Sonarr on another system
  • docker?

FIXED

docker create
–name=sonarr
-e PUID=1000
-e PGID=1000
-e user=cyber
-e TZ=Europe/London
-e UMASK_SET=0002
-p 8989:8989
-v /home/cyber/sonarr:/home/cyber/sonarr
-v /home/cyber/torrents/data/anime:/home/cyber/torrents/data/anime
-v /home/cyber/torrents/data/tvshows:/home/cyber/torrents/data/tvshows
-v /home/cyber/torrents/data/yen:/home/cyber/torrents/data/yen
-v /home/cyber/torrents/data/movies:/home/cyber/torrents/data/movies
–restart unless-stopped
linuxserver/sonarr

if other ppl are having problems, i set the actual user aswell and that was the ticket :smiley: