Sonarr Hangs due to DB File

Help & Support
1

Sonarr version: 2.0.0.4409
Mono version: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 14 12:30:00 UTC 2016)
OS: Ubuntu 16.04.1 LTS (Xenial Xerus)
Debug Logs
Trace Logs
Description of issue:

Ive been getting a handful of errors, but most of them look like they are associated with the database files not opening. Here are a few of the error codes im looking at here:

Message:
Task Error: unable to open database file
unable to open database file
System.Data.SQLite.SQLiteException (0x80004005): unable to open database file unable to open database file at System.Data.SQLite.SQLite3.Prepare (System.Data.SQLite.SQLiteConnection cnn, System.String strSql, System.Data.SQLite.SQLiteStatement previous, System.UInt32 timeoutMS, System.String& strRemain) [0x0033c] in <61a20cde294d4a3eb43b9d9f6284613b>:0 at System.Data.SQLite.SQLiteCommand.BuildNextCommand () [0x00068] in <61a20cde294d4a3eb43b9d9f6284613b>:0

Message:
Failed to connect to qBitTorrent, please check your settings.: Failed to connect to qBitTorrent, please check your settings.
NzbDrone.Core.Download.Clients.DownloadClientException: Failed to connect to qBitTorrent, please check your settings. —> System.Net.WebException: Error: NameResolutionFailure (Too many open files) —> System.Net.Sockets.SocketException: Too many open files at System.Net.Sockets.Socket…ctor (System.Net.Sockets.AddressFamily addressFamily, System.Net.Sockets.SocketType socketType, System.Net.Sockets.ProtocolType protocolType) [0x0005d] in :0 at System.Net.WebConnection.Connect (System.Net.HttpWebRequest request) [0x000d6] in :0 — End of inner exception stack trace — at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in :0 at System.Net.HttpWebRequest.GetResponse () [0x0000e] in :0 at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x000fe] in <72ef4295e48b4c9093ad258ad9c4a51f>:0 — End of inner exception stack trace — at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxy.ProcessRequest[TResult] (NzbDrone.Common.Http.HttpRequestBuilder requestBuilder, NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings) [0x0007b] in :0 at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxy.GetConfig (NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings) [0x00012] in :0 at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrent.GetItems () [0x0000c] in :0

These has happened multiple times this week. Seems to be resolved by restarting the service, but then eventually hangs again. I do have quite a good bit of stuff being downloaded.

Anyways, let me know if you need any additional information.
Thanks,
SilverSix311

2

These logs are months old, you need to enable ((trace logging in general settings)).[quote=“SilverSix311, post:1, topic:12990”]
System.Net.WebException: Error: NameResolutionFailure (Too many open files)
[/quote]

Too Many Open files for a DNS request is a bit unexpected, I wonder if something else is afoot.

Are you using a proxy with Sonarr?
Is this a new issue?
Have you been running mono 4.6.2 for a while?

3

It is running on OpenFlixr so there is a Proxy setup with nginx I do believe. I’ve been running 4.6.2 for like a week or 2? I saw the message on sonarr telling me my Mono version was to old and would cause some kinda issues. I can’t remember exactly what the message was. I’m trying to get more recent Trace and Debug logs for ya. This issue just started this week I do believe.

4

I meant the proxy feature in Sonarr (I believe it’s set in general settings), which would be for outbound requests. I ask because we’ve seen some issues with it recently and could be at play here if you’re using it.

5

Oh, No I am not using the proxy settings inside sonarr. I’ll wait for it to crash again tonight with the new logs and Ill get those uploaded as soon as I can. Thanks for the help so far! Wasn’t expecting any responses this fast.

1 Like
6

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