Prowl and Sonarr

Bjorn_Eriksson · October 3, 2016, 12:49pm

Hi,
I dont really know when but Prowl seems to fail after sonarr has been running for awhile on my system…
Log says: Invalid API Key: "mylongboringapikey"
When I get this problem I just restart sonarr and Prowl messeges start sending out again fine.
I use Prowl for many services and in my own scripts and its only through sonarr Im experiencing this weird behaviour.

I have a friend who is also using Prowl with Sonarr and he started experience this issue around the same time as me.
Thanks for a great piece of software!

markus101 · October 3, 2016, 4:24pm

AN invalid API comes from Prowl’s API, either they are actually returning that or the Library Sonarr uses to connect to Prowl (Prowlin) is misinterpreting the response, that library hasn’t changed in years, but AFAIK the API hasn’t either.

We’ll need ((trace logs)) that include the failure and the version or Sonarr, operating system and mono version (if applicable) to investigate further.

Bjorn_Eriksson · October 4, 2016, 7:05am

Here is my log with tracelog enabled:
Component Message Time
NzbDroneErrorPipeline Invalid request Validation failed:
– Unable to send test message 08:33
ProwlService Unable to send test message: API Key: "myboringapikey"is invalid: API Key: “myboringapikey” is invalid 08:33
ProwlService Invalid API Key: “myboringapikey” 08:33

I can clearly read that it says my api key is invalid but the key isnt invalid, I use it for other programs/script and it always work if I just restart Sonarr.
Mono version:
mono version is 3.2 or better: 4.2.2
Sonarr version:
Latest 2.0.0.4326 - Sep 13 2016
OS: Synology DSM Latest.

Its not permitted to upload .txt logs to the forum so here it is in raw text, tried to remove my api key from below text.

[v2.0.0.4326] System.Net.WebException: The request timed out
at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00065] in /home/bean/spksrc/native/mono/work-native/mono-4.2.2/mcs/class/System/System.Net/HttpWebRequest.cs:946
at System.Net.HttpWebRequest.GetResponse () [0x0000e] in /home/bean/spksrc/native/mono/work-native/mono-4.2.2/mcs/class/System/System.Net/HttpWebRequest.cs:958
at Prowlin.HttpInterface.GetResultDocument (System.Collections.Generic.Dictionary`2 parameters, System.String method, Prowlin.ResultBase resultBase) <0x41aea2b0 + 0x00047> in :0
at Prowlin.HttpInterface.SendVerification (IVerification verification) <0x41aea130 + 0x00067> in :0
at Prowlin.ProwlClient.SendVerification (IVerification verification) <0x41ae3040 + 0x00031> in :0
at NzbDrone.Core.Notifications.Prowl.ProwlService.Verify (System.String apiKey) [0x00023] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Prowl\ProwlService.cs:68

[v2.0.0.4326] NzbDrone.Core.Notifications.Prowl.InvalidApiKeyException: API Key: “myboringapikey” is invalid
at NzbDrone.Core.Notifications.Prowl.ProwlService.Verify (System.String apiKey) [0x0008b] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Prowl\ProwlService.cs:80
at NzbDrone.Core.Notifications.Prowl.ProwlService.Test (NzbDrone.Core.Notifications.Prowl.ProwlSettings settings) [0x00000] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Prowl\ProwlService.cs:88

16-10-4 08:48:22.4|Trace|NzbDroneErrorPipeline|Handling Exception
16-10-4 08:48:22.4|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:
– Unable to send test message
16-10-4 08:48:22.4|Trace|Http|Res: 1482 [POST] /api/notification/test: 400.BadRequest (100167 ms)
16-10-4 08:48:22.4|Debug|Api|[POST] /api/notification/test: 400.BadRequest (100167 ms)
16-10-4 08:48:39.6|Trace|Scheduler|Pending Tasks: 1
16-10-4 08:48:39.6|Trace|CommandQueueManager|Publishing MessagingCleanup
16-10-4 08:48:39.6|Trace|CommandQueueManager|Checking if command is queued or started: MessagingCleanup
16-10-4 08:48:39.6|Trace|CommandQueueManager|Inserting new command: MessagingCleanup
16-10-4 08:48:39.7|Trace|CommandExecutor|MessagingCleanupCommand -> CleanupCommandMessagingService
16-10-4 08:48:39.7|Trace|CommandQueueManager|Marking command as started: MessagingCleanup
16-10-4 08:48:39.8|Trace|CommandQueueManager|Cleaning up old commands
16-10-4 08:48:39.8|Trace|CommandQueueManager|Updating command status
16-10-4 08:48:39.9|Trace|EventAggregator|Publishing CommandExecutedEvent
16-10-4 08:48:39.9|Trace|EventAggregator|CommandExecutedEvent -> TaskManager
16-10-4 08:48:39.9|Trace|TaskManager|Updating last run time for: NzbDrone.Core.Messaging.Commands.MessagingCleanupCommand
16-10-4 08:48:39.9|Trace|EventAggregator|CommandExecutedEvent <- TaskManager
16-10-4 08:48:39.9|Trace|EventAggregator|CommandExecutedEvent -> TaskModule
16-10-4 08:48:39.9|Trace|EventAggregator|CommandExecutedEvent <- TaskModule
16-10-4 08:48:39.9|Trace|CommandExecutor|MessagingCleanupCommand <- CleanupCommandMessagingService [00:00:00.0988520]
16-10-4 08:48:46.9|Trace|Http|Req: 1495 [GET] /api/health
16-10-4 08:48:46.9|Trace|Http|Req: 1496 [GET] /api/diskspace
16-10-4 08:48:47.0|Trace|Http|Res: 1495 [GET] /api/health: 200.OK (17 ms)
16-10-4 08:48:47.0|Debug|Api|[GET] /api/health: 200.OK (17 ms)
16-10-4 08:48:47.0|Trace|Http|Req: 1497 [GET] /api/health
16-10-4 08:48:47.0|Trace|Http|Res: 1497 [GET] /api/health: 200.OK (10 ms)
16-10-4 08:48:47.0|Debug|Api|[GET] /api/health: 200.OK (10 ms)
16-10-4 08:48:47.3|Trace|Http|Res: 1496 [GET] /api/diskspace: 200.OK (319 ms)
16-10-4 08:48:47.3|Debug|Api|[GET] /api/diskspace: 200.OK (319 ms)
16-10-4 08:48:47.3|Trace|Http|Req: 1498 [GET] /api/diskspace
16-10-4 08:48:47.6|Trace|Http|Res: 1498 [GET] /api/diskspace: 200.OK (260 ms)
16-10-4 08:48:47.6|Debug|Api|[GET] /api/diskspace: 200.OK (260 ms)
16-10-4 08:48:50.2|Trace|Http|Req: 1499 [POST] /api/system/restart
16-10-4 08:48:50.2|Info|LifecycleService|Restart requested.
16-10-4 08:48:50.2|Trace|EventAggregator|Publishing ApplicationShutdownRequested
16-10-4 08:48:50.3|Trace|EventAggregator|ApplicationShutdownRequested -> NzbDroneServiceFactory
16-10-4 08:48:56.4|Debug|ProcessProvider|Found 0 processes with the name: NzbDrone.Console
16-10-4 08:48:56.7|Debug|ProcessProvider|Found 1 processes with the name: NzbDrone
16-10-4 08:48:56.7|Debug|ProcessProvider| - [14426] NzbDrone
16-10-4 08:48:57.3|Info|MigrationLogger|*** Migrating data source=/usr/local/nzbdrone/var/.config/NzbDrone/nzbdrone.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
16-10-4 08:48:57.9|Debug|MigrationLogger|Took: 00:00:00.6648492
16-10-4 08:48:57.9|Info|MigrationLogger|*** Migrating data source=/usr/local/nzbdrone/var/.config/NzbDrone/logs.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
16-10-4 08:48:58.0|Debug|MigrationLogger|Took: 00:00:00.0444068
16-10-4 08:48:58.0|Info|Router|Application mode: Interactive
16-10-4 08:48:58.0|Debug|Router|Console selected
16-10-4 08:48:58.1|Info|OwinHostController|Listening on the following URLs:
16-10-4 08:48:58.1|Info|OwinHostController| http://*:8989/

nicheplayer · October 25, 2016, 10:42pm

Been having the same issue since sometime this summer. Assume the logfile above will provide the lead you need, but I can run one too if you like. Thanks.

system · December 24, 2016, 10:42pm

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