-
-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sonarr requests - "message": "constraint failed\r\nNOT NULL constraint failed: Series.Images" #440
Comments
@godsplague If you are able to reproduce it and get the Something went wrong error. Can do please do the following: Open up the developers console (F12 on Chrome), go to the Network Tab Then press request to get the error message. (There should only be 1 red entry). @sch1308 I'll take a look at where that error is happening in the code and plug it. |
@sch1308 There should be more logs that I require, one with "Adding Series" and also "Seasons = X, out of X seasons" also "Sonarr API Options:" |
hopefully this is what you need. I clicked that error and here is the text it gave me |
Thanks that helped. It seems that it failed to send something to Sonarr (It was being Auto Approved). It tried to put the Sonarr error messages on screen for you but it didn't contain any error messages (which is really strange). I have fixed the exception being thrown, but I am not sure why Sonarr failed to accept the TV show (Anything in your Sonarr logs?). |
This happened to me once and it was due to Sonarr not being able to find the show, even when I searched for it by name inside sonarr. The only way I could add the show was by using the tvbd: prefix instead of the show name. |
Bizarre, checked the sonarr logs, which makes sense. Here is what I got (I cleared it and just did a request for a random title) http://pastebin.com/jyPPpdgh |
is there any way to see the full JSON payload for the add series request from PlexRequests? I'm working with sonarr support as well to see what's going on https://forums.sonarr.tv/t/sonarr-having-issues-adding-series-requested-from-other-programs/11497 |
Id have to give you a custom build so we can output it to the log. You okay with that?
|
I'd be willing to try it, this is the only break in the chain on my whole media operation. I'd hate to have to find an alternative for plexrequests.net or sonarr. Seems odd I'm the only one having this issue though. |
I agree, looking at the code, if you set your log level to Options is near the Response from Sonarr is near the |
does this shed any light? trace log on sonarr right after a request. http://pastebin.com/NBUKkKTE |
This is the issue: That's what we are getting back from Sonarr. I've updated the Sonarr thread post. Let's see if they are able to shed any light |
Issue raised on Sonarr Sonarr/Sonarr#1403 |
Thank you very much for your support, seems odd I'm the first to bring up this issue. Am I doing things in a weird way or what? hahah |
I don't think so. I think you are just on an earlier release than everyone else. Everyone will end up with this issue... Which sucks. |
Yeah, it's happening everytime for me now. I didn't realize it because most people were requesting movies, not tv shows. Plexrequests-meteor is also broke. |
Did it work previously? Wondering if going back one version would fix for the time being, or one version back on sonarr. You using sonarr too? |
Sonarr. I believe it's a change on Sonarr's end, as meteor plex requests has been rock solid for about 6 months until recently, and they haven't changed anything in a few months. |
Correct, it's an issue in Sonarr |
Makes sense, maybe I'll try going back one version on sonarr and see if it fixes when I have some more time. Not to sound rude at all but they have a lot going on I'm sure and who knows how long until it sees a fix |
Yeah, I raised a bug with them as I couldn't add an unmontiored series using the API (Which i need for the feature to request individual episodes). They fixed it but it could be a while until it's released (Since they have some big changes at the moment), then it could be even longer for people to update, so im working around it for now. |
I run sonarr on the development branch and that was already pushed, it doesn't fix the error that we are seeing in PlexRequests. |
I'm not aware of any change I can do to fix it. It's an internal Sonarr error. I'll speak to Markus (Sonarr Dev) at some point today. But I suggest you downgrade Sonarr for now. |
Thanks for your help Sent via the Samsung Galaxy S7 active, an AT&T 4G LTE smartphone -------- Original message -------- I'm not aware of any change I can do to fix it. It's an internal Sonarr error. I'll speak to Markus (Sonarr Dev) at some point today. But I suggest you downgrade Sonarr for now. You are receiving this because you were mentioned. |
@godsplague I have a potential workaround. Can you try out this build? https://ci.appveyor.com/project/tidusjar/requestplex/build/1.9.676/artifacts |
I'll give it a try as soon as I am able, thanks! Sent via the Samsung Galaxy S7 active, an AT&T 4G LTE smartphone -------- Original message -------- @godsplaguehttps://github.com/godsplague I have a potential workaround. Can you try out this build? https://ci.appveyor.com/project/tidusjar/requestplex/build/1.9.676/artifacts You are receiving this because you were mentioned. |
@godsplague That's cool, no rush. It should fix it, just want to confirm. @Collisionc this build should work around the issue: https://ci.appveyor.com/project/tidusjar/requestplex/build/1.9.676/artifacts |
I had to delete my sqlite file to get plexrequestsnet to startup without errors, but when I did that and re-setup sonarr it still gives me "Something went wrong" when requesting a tv show. |
You had to delete your database?!?! Can you please send me your latest backup (in the backup folder) at jamierees@outlook.com What error are you getting in the browsers console?
|
The database had been sitting at 364 MB for a few days (Somehow trace logging was enabled), but didn't seem to bother plexrequestsnet until this build. I had turned off trace logging, cleared the logs from the database, but it didn't automatically shrink it. I compacted/vacuumed the database down to 164 kb and was able to get plexrequestsnet to load it again. Object Is the error that is in the console. |
Ah ok strange... That's a new bug from the tv episode request work I am doing. It's not fully finished yet (as you can see). If I get time tomorrow I'll create a new branch off master (latest release) and add the fix into there.
|
No rush. Another thing that I've noticed, cpu usage and memory usage on the program have skyrocketed in the build you linked. On my ubuntu VPS it's currently using 2 GB of ram and sitting at 30% cpu usage, and the ram usage is slowly creeping up over time. Also, in the log this error message is being spammed: System.InvalidOperationException: There is an error in XML document (1, 2). ---> System.InvalidOperationException: was not expected. at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderPlexEpisodeMetadata.Read11_MediaContainer () <0x402af720 + 0x000b7> in :0 at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&) at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) <0x7f9335eef5d0 + 0x000a1> in :0 --- End of inner exception stack trace --- at System.Xml.Serialization.XmlSerializer.Deserialize (System.Xml.XmlReader xmlReader, System.String encodingStyle, XmlDeserializationEvents events) <0x41bf7ac0 + 0x00823> in :0 at System.Xml.Serialization.XmlSerializer.Deserialize (System.Xml.XmlReader xmlReader, System.String encodingStyle) <0x41bf7a20 + 0x0007f> in :0 at System.Xml.Serialization.XmlSerializer.Deserialize (System.IO.TextReader textReader) <0x41bf7600 + 0x00097> in :0 at PlexRequests.Api.ApiRequest.DeserializeXml[T](System.String input) <0x410de5f0 + 0x000c3> in :0 |
Ah ok interesting, That's to do with the new Episode cacher job I added in (I haven't fully tested that yet, so that's probably where the memory leak is coming from). What it does is goes through your Plex library and caches the episodes you have locally so we then know what to stop you from requesting in the UI. |
Here is a build that has been taken from Master (There is no new functionality) with the workaround https://ci.appveyor.com/project/tidusjar/requestplex/build/1.8.680/artifacts |
I pulled the latest dev commit and built it, it works fine on that branch too. I'm able to add series on sonarr with no issues so far. |
Awesome, I'll try it later today as well. Thanks! |
damn, no dice for me. http://pastebin.com/QKe8srwr Just tells me Something went wrong at the top right error. For the installation I just made a copy of the entire old plexrequest folder and then I copied in all the new files to overwrite. OOPS, my mistake, I forgot to handle the check box on the .rar file. Working fine now! |
Yeah the unblock is a PITA! |
Hey @tidusjar I've been having the same "Something went wrong" problem and that new build fixed it. Thanks! |
@cjdbury Yeah it's probably due to the bug in Sonarr |
If this is a bug report please make sure you have filled the following in:
(If it's not a bug and a feature request then just remove the below)
Plex Requests.Net Version: 1.8.4
Operating System: win 10 x64
Applicable Logs (from
/logs/
directory or the Admin page):Reproduction Steps:
Attempting to request tv series through sonarr. In the admin setup everything seems to be connected properly and test connectivity succeeds and is able to pull my unique quality profiles just fine. But when I go to request I get the oops something went wrong error. Tried showing you the debug log but it looks like everything is working ok though it is not. I have no issue accessing sonarr or plexrequests from inside my network or outside. Sorry if you need a different log just let me know. Thanks in advance
The text was updated successfully, but these errors were encountered: