search

CompoUK / MediaBrowser.Plugins.VuPlus

MediaBrowser Vu+ Plugin
3 stars 13 forks source link

Error retrieving recordings #1

Open imp1sh opened 7 years ago

imp1sh commented 7 years ago

When I try to retrieve recordings it just doesn't work and I get an error in the logs, see below. There will be special characters in the recordings list, like ä or ß JFYI. emby server Version 3.2.36.0 FreeBSD 11.0 (jail) Plugin Version 3.1.0.0

2017-11-17 17:05:04.022 Info App: [VuPlus] Start GetRecordingsAsync, retrieve all 'Inprogress' and 'Completed' recordings 
2017-11-17 17:05:04.022 Info App: [VuPlus] Start EnsureConnectionAsync
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync HostName: 10.10.10.10
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync StreamingPort: 8001
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync WebInterfacePort: 80
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync WebInterfaceUsername: 
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync WebInterfacePassword: 
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync UseSecureHTTPS: False
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync OnlyOneBouquet: True
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync TVBouquet: Favourites (TV)
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync ZapToChannel: True
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync FetchPiconsFromWebInterface: True
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync PiconsPath: 
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync RecordingPath: /hdd/movie
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync EnableDebugLogging: True
2017-11-17 17:05:04.022 Info App: [VuPlus] EnsureConnectionAsync Validation of config parameters completed
2017-11-17 17:05:04.022 Info App: [VuPlus] Start InitiateSession, validates connection and returns Bouquet reference if required
2017-11-17 17:05:05.389 Error App: [VuPlus] Failed to parse timer information.
2017-11-17 17:05:05.389 Error App: [VuPlus] GetRecordingsAsync error: Input string was not in a correct format.
2017-11-17 17:05:05.389 Error App: Error getting recordings
        *** Error Report ***
        Version: 3.2.36.0
        Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server
        Operating system: Unix 11.0.0.0
        64-Bit OS: True
        64-Bit Process: True
        User Interactive: False
        Mono: 4.8.1 (4.8.1.0 Sat Nov  4 02:41:58 UTC 2017)
        Processor count: 4
        Program data path: /var/db/emby-server
        Application directory: /usr/local/lib/emby-server
        System.ApplicationException: Failed to parse timer information.
          at MediaBrowser.Plugins.VuPlus.LiveTvService+<GetRecordingsAsync>d__12.MoveNext () [0x006d0] in <1d084dc5d0084964993b673f93dce71a>:0 
        --- End of stack trace from previous location where exception was thrown ---
          at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
          at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
          at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
          at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
          at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
          at Emby.Server.Implementations.LiveTv.LiveTvManager+<RefreshRecordings>c__asyncD+<RefreshRecordings>c__AnonStorey35+<RefreshRecordings>c__async34.MoveNext () [0x000e0] in <ed9d9a739e4b4dd69dd175646f337511>:0 
        System.ApplicationException
          at MediaBrowser.Plugins.VuPlus.LiveTvService+<GetRecordingsAsync>d__12.MoveNext () [0x006d0] in <1d084dc5d0084964993b673f93dce71a>:0 
        --- End of stack trace from previous location where exception was thrown ---
          at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
          at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
          at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
          at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
          at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
          at Emby.Server.Implementations.LiveTv.LiveTvManager+<RefreshRecordings>c__asyncD+<RefreshRecordings>c__AnonStorey35+<RefreshRecordings>c__async34.MoveNext () [0x000e0] in <ed9d9a739e4b4dd69dd175646f337511>:0 

2017-11-17 17:05:05.391 Info HttpServer: HTTP Response 200 to 2a00:fefe:0101:0101::1000. Time: 1371ms (slow). https://my.f.q.dn:8920/LiveTv/Recordings?UserId=715f2f78d3b148f1974f272e9083d595&Limit=8&Fields=CanDelete%2CPrimaryImageAspectRatio%2CBasicSyncInfo&EnableTotalRecordCount=false&EnableImageTypes=Primary%2CThumb%2CBackdrop 
2017-11-17 17:05:05.392 Info HttpServer: HTTP Response 200 to 2a00:fefe:0101:0101::1000. Time: 1360ms (slow). https://my.f.q.dn:8920/LiveTv/Recordings/Groups?userId=715f2f78d3b148f1974f272e9083d595
FredFrin commented 6 years ago

I found what looks like exactly the same issue & reported it in what seems to be a fork of this project - see Issue#2: https://github.com/chlorm-forks/Emby.Plugins.VuPlus/issues

I also have german recordings, so non-Ascii or non-Utf-8 characters may well be the cause even though the error message is complaining about:

Failed to parse timer information.