-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Empy newsletter after PlexMediaServer update #1117
Comments
Hi! |
Do you have logs after sending the newsletter? |
Can you trying again with trace logs on? |
These are all the logs from midnight to 7.30 am when the newsletter is posted. I have done a test right now:
|
|
@tidusjar This same problem happened with myself before. I suspect that the API has changed with the latest update last night for Plex Pass subscribers. If you need me to send you the exe for the newest version like I did last time, I'd be happy to. I can also confirm this is happening to me as well. I've listed my specs below. Thanks. Ombi Version: Update Branch: OS: |
I am also experiencing this. Ombi Version: 2.1.0 Update brach: Stable OS: Windows 10 Pro x64 Plex: 1.4.1.3362 on Plex Pass |
I'm getting empty newsletters as well. Plex server version 1.4.2.3400 on Plex Pass |
Can you guys give the EAP branch a try? |
Just did last night. Is there a way to force a newsletter email to go out?
Or just change the chron job temporarily?
Thanks for adding mass email by the way 😀
…On Tue, Feb 28, 2017, 3:01 AM Jamie ***@***.***> wrote:
Can you guys give the EAP branch a try?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1117 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AYw2GBJM-XIWkZyEAJgmZY2pO_5W1TT8ks5rg9RfgaJpZM4MAOU5>
.
|
You can simply hit "send test email to admin" in the newsletter settings page |
Not sure if this has to do with the Newsletter generation but I have a ton of these in my log:
|
Looks like a bug with the new changes...
…On Tue, 28 Feb 2017 at 14:49 rynh ***@***.***> wrote:
[image: image]
<https://cloud.githubusercontent.com/assets/25966104/23409861/27be769a-fd9b-11e6-83f8-ee2383a3b5cd.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1117 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGVaLFtqSS6jHLFFQGYWaLIq2nlqKfetks5rhDPqgaJpZM4MAOU5>
.
|
I am getting the error to on the dev build just updated today. Exception when calling GetMetadata for Plex, Retrying 00:00:10 Ombi.Api.PlexApi Error 2/28/2017 5:39:33 PM |
UPDATE: @SuperPotatoMen with trace I did not see any other errors. I just added a lot of media so it takes a while to error out completely.
|
same issue here. everything is on latest versions. disabled news letter for now until a fixed. |
I have this issue but I don't see any errors when I turn logs up to trace. I see a lot of descriptions of episodes in log. The "Deserialzing Object" is filled with metadata. |
Hello, I installed early access version 2.1.1496 and the newsletter is working perfectly now, thank you! |
I'd like some clarification on this issue. I seem to be having the same issue as the OP but there are a number of people here that seem to be having a different issue and it's causing confusion, at least to me. I am having an issue with the newsletter being empty but like the OP, there are no errors in the logs or anything to even indicate there is a problem. There seems to be a lot of others saying they have the same problem but their logs and very different and seem to indicate a different issue with the same outcome of an empty newsletter. gadgetusaf, diedrichg, and rynh all seem to be having different issues than the OP and I. |
My problem was fixed by following the instructions to clear the table.
The other error was resolve by restarting my rocket container again.
|
Right. It seems there are multiple issues here. I think the original issue was overlooked when others started chiming in and adding their logs, mistakenly thinking their issue is the same as the original one. |
@bobbintb I agree this issue is now a bit of a confusing mess. The original issue should be fixed now? I changed the way we query Plex. |
Do we need to what for a commit or something? What do we need to do to get the fix? |
Wondering also....do we need to switch to the dev branch or the EAP branch for now? |
Pleas stay on the EAP branch, dev branch is buggy and untested ;) It can break your whole ombi configuration |
@SuperPotatoMen It's not buggy! Just some of the code is untested 😆 |
So, this is fixed in the EAP branch? It seems more broken than before. Before I set the logs to trace and it would show that it was getting the information from Plex, it just wasn't in the email. Now the trace logs don't show any information from Plex. I make sure the token was up to date as well. tidusjar said he changed the way Plex is queried to fix this but was that even the issue? It seems to be querying the information just fine before, it just wasn't being put in the email. Anyone gotten the fix to work? |
We no longer use the plex Recently Added API since it didn't really make much sense, it would show duplicates and there was no way to tell how far back it was going. Are you running EAP? Since this will be resolved in that branch now. |
That's what I'm saying, I'm using EAP and it's still not working. It seems to be working less than it did before. Before the trace log would show the API request from Plex with all the recently added shows in json format or whatever format is was. Now it doesn't show the API request results at all. The email before would have a section for new movies and new tv shows but those sections would be empty. Now the section titles aren't there either. |
I upgraded to EAP 2.1.1538 and ran OS: Window 10 |
I didn't change anything but something must have changed. I left the email option activated and I got one this morning. I think it's because of it no longer using the recently added api. Maybe I was working once I switched to the EAP branch but nothing qualified as "new" and I didn't understand how it measured that. So then, how does it determine what is "new" now that it no longer uses the "recently added" category from Plex? |
New stuff is newly added, so the newsletter will run, and check for new content. It will then add that to the "sent" list, then the next run we check the sent list for things that are not on there, so they must be new |
I get that if it showed up between newsletters it is "newly added" but according to what? Ombi? Plex? If it was newly added to Plex but was not an Ombi request will it still show up? My question really has more to do with the source of the information it uses to evaluate what is "new", not how it evaluates it. |
Can you guys upgrade to the last eap, we fixed this issue |
Just updated to the new EAP. |
Newsletter works for me but just for movies? |
I'm on Application Version: 2.1.1554 eap. |
@GilbN pleas open a new issue for that :) |
Will do ;) |
Any update guys? |
Seems to work for movies, I have not checked with TV shows yet. |
I can't get new TV episodes in the newsletter.
|
That means that the episode cacher is not being able to cache any episodes... Can you raise a new bug for that and include your Plex version? |
Ok, I willl do it |
Ombi Version:
V 2.1.0
Update Branch:
Stable
Operating System:
Ubuntu Server 16.10
Mono Version (only if your not on windows)
Stable 4.2.3.4/832de4b
Applicable Logs (from
/logs/
directory or the Admin page):Problem Description:
Newsletter is empty after plex update to version 1.4.1.3362-77c6a4f80_amd64
No errors in logs
Reproduction Steps:
Send newsletter
The text was updated successfully, but these errors were encountered: