Sonarr stopped working on localhost:8989

I was using Sonarr and it worked perfectly.
Suddenly it stopped working and i’m not so familiar with the Mac structue.
I have seen that the issue has been mentioned before but i didn’t understood how to fix this.
What should be really good for me was a step by step solution, f.e. click on this then do this or that.

When starting Sonarr i don’t get a confirmitation that it runs (but this is normal i believe).
Then i try to acces it by http://localhost:8989 but it doesn’t open at all.

i have seen that i should look at the log files but i don’t know where to find these.
If i go to Macintosh HD/My user name/ then i dont see a .config file .

Hope someone knows what i can do with above, I’m aware it’s pssible a noobies question
but i’m not too familiar yet with it,

Thanks in advance,

I’ve been experiencing similar issues. When i first try to load localhost:8989 it doesn’t display anything and 30 seconds later or so the screen refreshes and shows properly.I’m assuming it has something to do with Sonarr not running all the time like it once did, but I’ve only just started to investigate the problem.

Good evening,

Thanks for the reply.
I tried it for several days without luck.
I reinstalled Sonarr by downloading the file from the website and tried
local host again but still not working over here.

jasper

.config is a hidden folder, either use Go To Folder in finder or enable showing hidden files/folders in finder (there is a terminal command for it).

Thanks a lot Markus,

I first only tried in finder to show hidden files but now can see the log files.
i opened the last nzbdrone.txt file and i will paste down the last part of it.
It says :database disk image is malformed
database disk image is malformed

I think this is a clue to what is wrong ?
16-3-9 16:19:08.6|Info|Bootstrap|Starting Sonarr - /Applications/Sonarr.app/Contents/MacOS/NzbDrone.exe - Version 2.0.0.3732
16-3-9 16:19:11.5|Debug|ProcessProvider|Found 0 processes with the name: NzbDrone.Console
16-3-9 16:19:13.7|Debug|ProcessProvider|Found 0 processes with the name: NzbDrone
16-3-9 16:19:14.0|Info|MigrationLogger|*** Migrating data source=/Users/jaspergreevink/.config/NzbDrone/nzbdrone.db;cache size=-10485760;datetimekind=Utc;journal mode=Truncate;pooling=True;version=3;Full FSync=True ***
16-3-9 16:19:14.3|Debug|MigrationLogger|Took: 00:00:00.3310112
16-3-9 16:19:14.3|Info|MigrationLogger|*** Migrating data source=/Users/jaspergreevink/.config/NzbDrone/logs.db;cache size=-10485760;datetimekind=Utc;journal mode=Truncate;pooling=True;version=3;Full FSync=True ***
16-3-9 16:19:14.3|Fatal|ConsoleApp|EPIC FAIL!

System.Data.SQLite.SQLiteException: database disk image is malformed
database disk image is malformed
at System.Data.SQLite.SQLite3.Prepare (System.Data.SQLite.SQLiteConnection cnn, System.String strSql, System.Data.SQLite.SQLiteStatement previous, UInt32 timeoutMS, System.String& strRemain) <0x37337a0 + 0x00ac3> in :0
at System.Data.SQLite.SQLiteCommand.BuildNextCommand () <0x3733440 + 0x001a8> in :0

Thanks agin in advance,

I think your database is corrupt, you need to restore it from backup that sonarr takes automatically.

In this case only the logs database is corrupt, removing it will fix it.

@aser delete logs.db from /Users/jaspergreevink/.config/NzbDrone and any other logs.* files (not the logs folder though).

Good afternoon,

Thanks a lot for all assistance in this matter.
I copied the backup files and unzipped one where i was sure it was working.
Afterwards deleted the complete .config folder and installed sonarr again.
replaced the files for the ones from the backup and restarted my computer.

Now working perfectly again.

Thanks again and is there a way i can donate a little to the sonarr team?
really like to do so, cause the program is perfect as well the support and would
like to contribute to it.

Jasper

1 Like

Good afternoon again,

Just found the contribute button, only don’t have a credit card.
Will see how i can solve, possible by biitcoin, thanks again.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.