Sonarr using 100% CPU after nzbGet failure

Sonarr version: 2.0.0.4427
Mono version: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 21 12:08:40 UTC 2016)
OS: Ubuntu 16.0.4
Debug logs: http://pastebin.com/G3PZGUXa

On startup, Sonarr begins a scan of all series, then at some point in the process sees a couple errors.

One error: Can’t retrieve history from nzbGet.
NzbGet is running on the same machine, and “test” in the Sonarr downloader configuration works all the time. nzbGet web UI is responsive and it’s idle [nothing currently downloading].

Other error: Can’t find some torrent file; Sonarr is looking in a nonexistent directory. Not sure where it’s getting that directory path, as there is nothing configured in Sonarr or Transmission with that path.

Coincident with one of those errors, CPU usage stays at 100% and the scan apparently aborts. The Web UI continues to show the scan message “[refreshseries] Scanning disk for Jon Glaser Loves Gear”.

If I stop Sonarr and restart it, the same behavior will repeat every time.

That doesn’t appears to be an issue with NZBGet, but possibly an issue with mono (we saw a similar issue with mono 4.4 and this is the second time I’ve seen that error with 4.6.2 (at least it looks the same).

Sonarr gets the download paths from the download client, sounds like an item I. Transmission is using that path.

Is it always at the same series?
Is the Sonarr UI still operational?

Sonarr gets the download paths from the download client, sounds like an item I. Transmission is using that path.

I’ve deleted all torrents from Transmission and have rechecked the settings file for that path. I’ve restarted Tranmission and Sonarr, watching the log again and don’t see that error. Maybe cleared that one.

Is it always at the same series?

It is always that series, but I don’t know if that’s just due to timing. Like it takes X minutes to get that far in the scan and the first attempt to contact nzbGet happens X minutes after startup? That particular series is fully downloaded. The two episodes that are still marked as “monitored” are present on disk at highest quality.

Is the Sonarr UI still operational?

Yes, it is. If I go into the detail page for any series, the refresh arrows are spinning, but the UI is functional otherwise.

I just clicked the refresh button in the next alphabetical series:

16-12-29 14:02:27.2|Info|SceneMappingService|Updating Scene mappings
16-12-29 14:02:28.6|Info|RefreshSeriesService|Updating Info for Jonathan Creek
16-12-29 14:02:29.4|Info|RefreshEpisodeService|Starting episode info refresh for: [75033][Jonathan Creek]
16-12-29 14:02:29.6|Info|RefreshEpisodeService|Finished episode refresh for series: [75033][Jonathan Creek].
16-12-29 14:02:29.6|Info|DiskScanService|Scanning disk for Jonathan Creek
16-12-29 14:02:30.3|Info|DiskScanService|Completed scanning disk for Jonathan Creek
16-12-29 14:02:30.6|Info|ExistingMetadataImporter|Found 0 existing metadata files
16-12-29 14:02:30.7|Info|ExistingSubtitleImporter|Found 0 existing subtitle files
16-12-29 14:02:30.7|Info|ExistingOtherExtraImporter|Found 0 existing other extra files
16-12-29 14:02:30.7|Info|ExistingExtraFileService|Found 0 extra files

Now the arrows are no longer spinning, but the “Scanning disk for Jon Glaser Loves Gear” is still there. It closes when I click the X.

Weird. I disabled both download clients so it wouldn’t try to contact either of them, then restarted. Watching the log, it gets to “16-12-29 14:11:36.4|Info|DiskScanService|Completed scanning disk for Jon Glaser Loves Gear” and then stops with the CPU at 100%.

All these series are on the same mounted UNRAID share. Ownership details between “Jon Glaser Loves Gear” and “Join or Die with Craig Ferguson” [which precedes JGLG in the log look the same. No invisible files in the JGLG directory.

The next series in line is “Jonathon Creek”, which I’ve established scans fine on it’s own, so it doesn’t seem like a problem with it.

Looks like something with that particular series [JGLG], but what?

I’ll turn up the logging and see what it reveals.

Seems like maybe a file that’s broken somehow? I started a run a little while ago, and the debug go shows this:

16-12-29 14:29:07.1|Info|DiskScanService|Scanning disk for Jon Glaser Loves Gear
16-12-29 14:29:07.1|Debug|DiskScanService|Scanning ‘/mnt/nas/tv-nfs/Jon Glaser Loves Gear’ for video files
16-12-29 14:29:07.1|Debug|DiskScanService|10 video files were found in /mnt/nas/tv-nfs/Jon Glaser Loves Gear
16-12-29 14:29:07.1|Debug|DiskScanService|[317900][Jon Glaser Loves Gear] Cleaning up media files in DB
16-12-29 14:29:07.1|Debug|ImportDecisionMaker|Analyzing 0/10 files.
16-12-29 14:29:07.1|Info|DiskScanService|Completed scanning disk for Jon Glaser Loves Gear
16-12-29 14:29:07.1|Debug|VideoFileInfoReader|Getting media info from /mnt/nas/tv-nfs/Jon Glaser Loves Gear/Season 01/Jon Glaser Loves Gear - S01E10 - Sailing WEBDL-1080p.m4v
16-12-29 14:29:09.6|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (2 ms)
16-12-29 14:30:33.2|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (2 ms)
16-12-29 14:32:03.2|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (1 ms)
16-12-29 14:33:33.2|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (1 ms)
16-12-29 14:35:03.2|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (1 ms)
16-12-29 14:36:33.2|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (1 ms)
16-12-29 14:38:03.3|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (5 ms)
16-12-29 14:39:33.2|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (1 ms)
16-12-29 14:41:03.3|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (1 ms)

An RSS Sync started right then, but that “/api/queue” notification repeats in the log every couple minutes for the next hour and a quarter.

mediainfo returns valid information on the file.

I moved it out of the season directory and started Sonarr again. Sails right through all series, no errors.

Reenabled the downloaders and restarted. Now that the scan has completed successfully, it starts up and just sits, virtually no CPU.

Any interest in seeing the video file and the logs from all these runs?

Which version of libmediainfo do you have installed? We’ve seen a few issues with files recently and older versions of media info, but previous versions of media info didn’t have issues (and the issue has been fixed in newer versions, but not released in the Ubuntu repo).

Not sure that having the file will tell me much, but PM me a link and I can at try to verify if it works with newer versions.

chaz@brand:~$ mediainfo --Version
MediaInfo Command line,
MediaInfoLib - v0.7.82

I’ll put the file somewhere and send you a link. Just thought if it was failing in some weird way that you could trap and deal with it might be useful.

1 Like

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