Open Shadow229 opened 4 years ago
Hi!
Thanks for the issue report. Before a real human comes by, please make sure you used our bug report format.
Have you looked at the wiki yet? https://github.com/tidusjar/ombi/wiki/
Before posting make sure you also read our FAQ.
Make the title describe your issue. Having 'not working' or 'I get this bug' for 100 issues, isn't really helpful.
If we need more information or there is some progress we tag the issue or update the tag and keep you updated.
Thanks!
Ombi Bot.
Same issue here, brand new install, first set of requests by a user and sent out 2 emails per show once approved.
I had this issue on win10/v3 and it turned out it's cause I had Ombi running as a service and starting up in normal mode on boot.
In my case I'm running as a docker container. Sometimes even more than two notifications are sent, up to 4! Hopefully the developer will still look at backporting fixes to v3 if the fix is ever known.
To keep this updated - I'm currently running 4.0.748.0 (unraid OS - linuxserver/ombi:v4-preview repo) and still receiving duplicate emails. As an addition (not mentioned in the reproduction steps above), I also receive duplication completion notifications when I request my own movies (without the need for approval)
For me personally its only ever duplicated. @mapleleafs89 is there any pattern you've spotted when yours sends 2 or 4?
I updated to v4 and am still seeing duplicate notifications. No root cause, work arounds, or fixes anyone is aware of yet?
Still duplicate emails for me. Everything works perfectly except for that and I’ve been unable to find a cause/fix yet! If anyone does I’d love to hear it
Yeah same here it seems to be always 2 emails sent to everyone at every step its quite annoying, its sending from O365
i had this issue on v3 and now upgraded but still have the issue on v4. the newsletter emails does not seem to send duplicates nor do emails pertaining to the "issues" plugin section of Ombi ("Issue has been resolved for...."). the test email is also just one but all notifications double up. the v3 had vote or follow or something and that feature didnt send the other person duplicates, only the original requester
Yeah same here it seems to be always 2 emails sent to everyone at every step its quite annoying, its sending from O365
I'm using gmail, so its not email account type specific at least.
Still seeing duplicates only on items that are now marked as available. Approved items seem to send single emails.
Version: v4.0.1336
I'm also seeing this issue.
Running Ombi on Unraid via Docker as well. Could that somehow be the key?
Just to keep you in the loop, I couldn't work out what was causing this, but I'm going to be re-investigating again soon
Running version 4.0.1342 (i did saw there is a new version out) i am getting duplicate emails.
I did want to add that I am also seeing duplicate notifications in the app as well, not just email.
Thanks for the report.
soon there will be more information in the log files for me to help pinpoint this issue.
Just to save this from being stale, issue still persist. Getting duplicate emails/notifications from Ombi each time.
Yep still happening on 4.9.0
Confirmed, still bugged.
Yeah, still aware, if you could start uploading a log file when this happens it should help or at least point me in the correct direction. It's not something I've been able to reproduce so it's been difficult to pinpoint the issue, especially since it doesn't happen to everyone
Just happened to be searching through the logs to see what happens and I got a duplicate email notification. Found the section in question:
This is 4.10.2 on Ubuntu 18.04 for what it's worth.
In that log, is that the same time you got a duplicate notification? Also what type of notification?
That is indeed the same time that I received 2 email notifications.
i am also having the same issue 2 emails at the same time
If someone else is experiencing this issue, can you please provide the information im asking a above
If someone else is experiencing this issue, can you please provide the information im asking a above
Also here's a screenshot of my email settings in Ombi:
@tidusjar Hey Jamie; this just happened to me for the last 3 nights in a row (Sometimes multiple times a day as found below)
The lastest one was just a few minutes ago at 2:00AM on the dot.
Here's my logs:
2022-03-06 01:30:51.238 -05:00 [Information] Default Quartz.NET properties loaded from embedded resource file
2022-03-06 01:30:51.280 -05:00 [Debug] TaskSchedulingThreadPool configured with max concurrency of 10 and TaskScheduler ThreadPoolTaskScheduler.
2022-03-06 01:30:51.285 -05:00 [Information] Initialized Scheduler Signaller of type: Quartz.Core.SchedulerSignalerImpl
2022-03-06 01:30:51.286 -05:00 [Information] Quartz Scheduler v."3.1.0.0" created.
2022-03-06 01:30:51.287 -05:00 [Information] RAMJobStore initialized.
2022-03-06 01:30:51.288 -05:00 [Information] Scheduler meta-data: Quartz Scheduler (v3.1.0.0) 'DefaultQuartzScheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'Quartz.Core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'Quartz.Simpl.DefaultThreadPool' - with 10 threads.
Using job-store 'Quartz.Simpl.RAMJobStore' - which does not support persistence. and is not clustered.
2022-03-06 01:30:51.288 -05:00 [Information] Quartz scheduler 'DefaultQuartzScheduler' initialized
2022-03-06 01:30:51.288 -05:00 [Information] Quartz scheduler version: 3.1.0.0
2022-03-06 01:30:51.289 -05:00 [Information] JobFactory set to: Ombi.Schedule.IoCJobFactory
2022-03-06 01:30:51.331 -05:00 [Information] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
2022-03-06 01:30:51.335 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:31:17.655 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:31:46.522 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:32:14.974 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:32:43.038 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:33:12.266 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:33:38.718 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:34:04.526 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:34:33.463 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 01:35:00.007 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:35:00.027 -05:00 [Debug] Calling Execute on job DVR.ISickRageSync
2022-03-06 01:35:00.038 -05:00 [Debug] Trigger instruction : NoInstruction
2022-03-06 01:35:24.305 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:35:53.741 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:36:18.717 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:36:48.660 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:37:14.158 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:37:38.746 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:38:04.953 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:38:34.902 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:39:01.828 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:39:25.735 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:39:55.500 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 01:40:00.000 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:40:00.001 -05:00 [Debug] Calling Execute on job DVR.ILidarrArtistSync
2022-03-06 01:40:00.269 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 01:40:00.270 -05:00 [Debug] Trigger instruction : NoInstruction
2022-03-06 01:40:00.270 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:40:00.270 -05:00 [Debug] Calling Execute on job DVR.ILidarrAlbumSync
2022-03-06 01:40:04.081 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 01:40:04.081 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:40:04.081 -05:00 [Debug] Calling Execute on job DVR.ILidarrAvailabilityChecker
2022-03-06 01:40:04.081 -05:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-06 01:40:04.081 -05:00 [Debug] Deleting trigger
2022-03-06 01:40:04.095 -05:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-06 01:40:04.096 -05:00 [Debug] Deleting trigger
2022-03-06 01:40:31.300 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:40:55.489 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:41:22.898 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:41:48.333 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:42:15.808 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:42:45.055 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:43:13.678 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:43:38.275 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:44:01.908 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:44:30.471 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:44:56.198 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:45:19.480 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:45:44.331 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:46:13.847 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:46:42.920 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:47:09.144 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:47:38.393 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:48:02.734 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:48:30.361 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:48:55.695 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:49:19.276 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:49:44.713 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:50:10.084 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:50:36.953 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:51:05.895 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:51:32.530 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:52:00.209 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:52:23.337 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:52:48.497 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:53:18.091 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:53:41.121 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:54:06.063 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:54:33.936 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:55:03.351 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:55:26.852 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:55:52.892 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:56:19.812 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:56:44.116 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:57:11.778 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:57:37.152 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:58:05.420 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:58:35.299 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:59:03.497 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:59:27.676 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 01:59:57.093 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 02:00:00.002 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 02:00:00.002 -05:00 [Debug] Calling Execute on job Emby.IEmbyContentSync
2022-03-06 02:00:00.002 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 02:00:00.003 -05:00 [Debug] Calling Execute on job Plex.IPlexContentSyncRecentlyAdded
2022-03-06 02:00:00.003 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 02:00:00.003 -05:00 [Debug] Calling Execute on job Plex.IPlexContentSync
2022-03-06 02:00:00.011 -05:00 [Debug] Trigger instruction : NoInstruction
2022-03-06 02:00:00.969 -05:00 [Debug] Trigger instruction : NoInstruction
2022-03-06 02:00:06.350 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 02:00:06.350 -05:00 [Debug] Trigger instruction : NoInstruction
2022-03-06 02:00:06.350 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 02:00:06.350 -05:00 [Debug] Calling Execute on job Plex.IPlexEpisodeSync
2022-03-06 02:00:08.153 -05:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-06 02:00:08.153 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 02:00:08.153 -05:00 [Debug] Deleting trigger
2022-03-06 02:00:08.153 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 02:00:08.153 -05:00 [Debug] Calling Execute on job System.IRefreshMetadata
2022-03-06 02:00:08.273 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 02:00:08.273 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 02:00:08.273 -05:00 [Debug] Calling Execute on job Plex.IPlexAvailabilityChecker
2022-03-06 02:00:08.275 -05:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-06 02:00:08.275 -05:00 [Debug] Deleting trigger
2022-03-06 02:00:08.300 -05:00 [Debug] Batch acquisition of 1 triggers
2022-03-06 02:00:08.300 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 02:00:08.300 -05:00 [Debug] Calling Execute on job Notifications.INotificationService
2022-03-06 02:00:08.342 -05:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-06 02:00:08.342 -05:00 [Debug] Deleting trigger
2022-03-06 02:00:11.213 -05:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-06 02:00:11.213 -05:00 [Debug] Deleting trigger
2022-03-06 02:00:37.855 -05:00 [Debug] Batch acquisition of 0 triggers
2022-03-06 02:01:01.619 -05:00 [Debug] Batch acquisition of 0 triggers
Are you guys on the develop version? You did make some changes in the laster versions
Are you guys on the develop version? You did make some changes in the laster versions
Yep! I am on developer version. Just updated to 4.14.2 to resolve the other issue I reported with "Intervention".
I have made no changes to the configuration at all since the upgrade; I did the update to that build around 1:30AM; got the email notification at 2AM; I should mention again that I had the spammy emails a few days prior as you can see by the screenshot so we can rule out anything specific to that update. :) In the time I've had those notifications I've made no changes to the configuration except whatever updates was available on the developer branch.
Hello, I'm having the exact same issue as everybody above. I have Plex sync set up every 4 hours and when I run it manually it triggers these notification (Plex recently added wont).
Here is a log 10 min before and 10min after 8:00am https://pastebin.com/HQqZ6tTf.
Ombi version: 4.14.2 OS: Debian 5.10.92-1
Just happened to me again 5 minutes ago at noon on the dot, got 2 more of the same movie today:
Logs are below:
Sorry the 1 minute of logs was too long/large for pastebin or github's limits.
@tidusjar I updated to v4.14.3 and for the first time in multiple days; I have not had any notifications today at 2AM at all about the Blacklight movie being available.
I'll keep an eye for the notifications around the time of noon; but so far waking up without 2 or 3 emails in my inbox seems extremely promising! :)
As always your hard work and dedication is appreciated on this fantastic project.
I also updated to 4.14.3 and no emails were sent so far! Awesome thanks!
Thanks for the feedback guys! :)
Nothing at noon today either today; which is one of the 2 usual times I'd get spammed with notifications. And no worries at all; seeing the OP opened this in 2020 I'm not sure if they will provide feedback for you to close it.
I think it's safe for me to say in my situation anyways it looks to be resolved. I'll update again if I notice it again but I'd consider this a huge improvement already.
Evening all, OP here, been catching these emails in passing and semi-keeping up with the notifications.
I was getting duplicate emails for requests last week. I’ve been messing about with my server this week, but I’ll check my ombi version and run a request this evening to provide feedback on the duplications!
Thanks for keeping on top of this!
On 7 Mar 2022, at 18:13, Joel Samson @.***> wrote:
Nothing at noon today either today; which is one of the 2 usual times I'd get spammed with notifications. And no worries at all; seeing the OP opened this in 2020 I'm not sure if they will provide feedback for you to close it.
I think it's safe for me to say in my situation anyways it looks to be resolved. I'll update again if I notice it again but I'd consider this a huge improvement already.
— Reply to this email directly, view it on GitHubhttps://github.com/Ombi-app/Ombi/issues/3825#issuecomment-1060982244, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANKBTFFLSVI3GLXSITW5TWTU6ZBMZANCNFSM4SZ22X6A. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
@tidusjar I'm afraid I'm now getting this error while syncing Plex.
2022-03-08 12:00:03.176 +01:00 [Warning] Exception thrown when attempting to cache the Plex Content in server "Reinflix"
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: PlexServerContent.Key'.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
Morning, sorry was having some connection issues with my dockers I needed to fix. Back up and running now.
Looks like I’m still getting duplications for things on 4.13.0:
Strangely, no duplication for an item added to retry, but dupe on a decline.
Also getting duplicate notifications in the Ombi app (iOS)
Todays log attached below.
Will run an update on my container now and retest
edit: cropped the log to the bit thats relevant:
2022-03-08 14:03:19.040 +00:00 [Error] Error when sending movie to DVR app, added to the request queue Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0. at Newtonsoft.Json.JsonTextReader.ParseValue() at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent) at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType) at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings) at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings) at Ombi.Api.Api.Request[T](Request request, CancellationToken cancellationToken) in /home/runner/work/Ombi/Ombi/src/Ombi.Api/Api.cs:line 90 at Ombi.Api.Radarr.RadarrV3Api.GetMovies(String apiKey, String baseUrl) in /home/runner/work/Ombi/Ombi/src/Ombi.Api.Radarr/RadarrV3Api.cs:line 55 at Ombi.Core.Senders.MovieSender.SendToRadarr(MovieRequests model, Boolean is4K, RadarrSettings settings) in /home/runner/work/Ombi/Ombi/src/Ombi.Core/Senders/MovieSender.cs:line 170 at Ombi.Core.Senders.MovieSender.Send(MovieRequests model, Boolean is4K) in /home/runner/work/Ombi/Ombi/src/Ombi.Core/Senders/MovieSender.cs:line 70 2022-03-08 14:03:19.074 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:03:19.076 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:03:19.076 +00:00 [Debug] Calling Execute on job Notifications.INotificationService 2022-03-08 14:03:21.678 +00:00 [Debug] Trigger instruction : DeleteTrigger 2022-03-08 14:03:21.678 +00:00 [Debug] Deleting trigger 2022-03-08 14:03:42.792 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:04:08.445 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:04:34.491 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:04:38.813 +00:00 [Error] Could not test Radarr Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0. at Newtonsoft.Json.JsonTextReader.ParseValue() at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent) at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType) at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings) at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings) at Ombi.Api.Api.Request[T](Request request, CancellationToken cancellationToken) in /home/runner/work/Ombi/Ombi/src/Ombi.Api/Api.cs:line 90 at Ombi.Api.Radarr.RadarrV3Api.SystemStatus(String apiKey, String baseUrl) in /home/runner/work/Ombi/Ombi/src/Ombi.Api.Radarr/RadarrV3Api.cs:line 47 at Ombi.Controllers.V1.External.TesterController.Radarr(RadarrSettings settings) in /home/runner/work/Ombi/Ombi/src/Ombi/Controllers/V1/External/TesterController.cs:line 382 2022-03-08 14:04:44.364 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:04:44.364 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:04:44.364 +00:00 [Debug] Calling Execute on job DVR.IRadarrSync 2022-03-08 14:04:45.342 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:04:45.343 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:04:45.343 +00:00 [Debug] Calling Execute on job DVR.IArrAvailabilityChecker 2022-03-08 14:04:45.343 +00:00 [Debug] Trigger instruction : DeleteTrigger 2022-03-08 14:04:45.343 +00:00 [Debug] Deleting trigger 2022-03-08 14:04:45.349 +00:00 [Debug] Trigger instruction : DeleteTrigger 2022-03-08 14:04:45.349 +00:00 [Debug] Deleting trigger 2022-03-08 14:04:54.625 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:04:54.625 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:04:54.625 +00:00 [Debug] Calling Execute on job DVR.ISonarrSync 2022-03-08 14:04:59.754 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:04:59.754 +00:00 [Debug] Trigger instruction : DeleteTrigger 2022-03-08 14:04:59.754 +00:00 [Debug] Deleting trigger 2022-03-08 14:04:59.754 +00:00 [Debug] Calling Execute on job DVR.IArrAvailabilityChecker 2022-03-08 14:04:59.754 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:04:59.755 +00:00 [Debug] Trigger instruction : DeleteTrigger 2022-03-08 14:04:59.755 +00:00 [Debug] Deleting trigger 2022-03-08 14:05:00.000 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:05:00.000 +00:00 [Debug] Calling Execute on job Jellyfin.IJellyfinContentSync 2022-03-08 14:05:00.006 +00:00 [Debug] Trigger instruction : NoInstruction 2022-03-08 14:05:27.925 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:05:53.231 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:06:12.432 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:06:12.433 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:06:12.433 +00:00 [Debug] Calling Execute on job Notifications.INotificationService 2022-03-08 14:06:15.113 +00:00 [Debug] Trigger instruction : DeleteTrigger 2022-03-08 14:06:15.113 +00:00 [Debug] Deleting trigger 2022-03-08 14:06:35.924 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:07:05.845 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:07:34.867 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:07:59.111 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:08:23.933 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:08:53.462 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:09:21.486 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:09:45.995 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:10:00.000 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:10:00.000 +00:00 [Debug] Calling Execute on job DVR.ISonarrSync 2022-03-08 14:10:05.161 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 14:10:05.161 +00:00 [Debug] Trigger instruction : NoInstruction 2022-03-08 14:10:05.161 +00:00 [Debug] Calling Execute on job DVR.IArrAvailabilityChecker 2022-03-08 14:10:05.161 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:10:05.163 +00:00 [Debug] Trigger instruction : DeleteTrigger 2022-03-08 14:10:05.163 +00:00 [Debug] Deleting trigger 2022-03-08 14:10:33.691 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:11:01.954 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:11:26.775 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:11:56.060 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:12:19.590 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:12:45.711 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:13:14.996 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:13:38.054 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:14:03.633 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 14:14:31.820 +00:00 [Debug] Batch acquisition of 1 triggers
Follow on from previous post - updated to 4.14.3 and still receiving duplicate notifications. Log below:
2022-03-08 15:00:00.004 +00:00 [Debug] Calling Execute on job Plex.IPlexContentSyncRecentlyAdded 2022-03-08 15:00:01.500 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 15:00:01.500 +00:00 [Debug] Trigger instruction : NoInstruction 2022-03-08 15:00:01.501 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 15:00:01.501 +00:00 [Debug] Calling Execute on job Plex.IPlexAvailabilityChecker 2022-03-08 15:00:01.574 +00:00 [Debug] Batch acquisition of 1 triggers 2022-03-08 15:00:01.574 +00:00 [Debug] Batch acquisition of 0 triggers 2022-03-08 15:00:01.574 +00:00 [Debug] Calling Execute on job Notifications.INotificationService 2022-03-08 15:00:01.592 +00:00 [Debug] Trigger instruction : DeleteTrigger 2022-03-08 15:00:01.592 +00:00 [Debug] Deleting trigger 2022-03-08 15:00:04.988 +00:00 [Debug] Trigger instruction : DeleteTrigger 2022-03-08 15:00:04.988 +00:00 [Debug] Deleting trigger 2022-03-08 15:00:30.820 +00:00 [Debug] Batch acquisition of 0 triggers
Hi, I'm running 4.14.4 in Docker through Kubernetes with MariaDB on Linux x86_64.
I also get duplicate emails, and possibly related, I also get some "Duplicate entry ... for key 'AK_PlexServerContent_Key'" messages.
This is the show I added:
mysql> select Id,Title,ReleaseYear,ImdbId,TvDbId,TheMovieDbId,Type,AddedAt,Has4K from PlexServerContent where title="No Exit";
+----------+---------+-------------+-----------+--------+--------------+------+----------------------------+-------+
| Id | Title | ReleaseYear | ImdbId | TvDbId | TheMovieDbId | Type | AddedAt | Has4K |
+----------+---------+-------------+-----------+--------+--------------+------+----------------------------+-------+
| 21275004 | No Exit | 2022 | tt7550014 | 290120 | 833425 | 0 | 2022-03-17 13:40:08.895331 | 1 |
+----------+---------+-------------+-----------+--------+--------------+------+----------------------------+-------+
1 row in set (0.00 sec)
mysql>
Below is the log for the time period when I received the duplicate email notifications.
2022-03-17 13:25:00.000 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:00.000 +11:00 [Debug] Calling Execute on job DVR.ICouchPotatoSync
2022-03-17 13:25:00.000 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:00.000 +11:00 [Debug] Calling Execute on job DVR.ILidarrArtistSync
2022-03-17 13:25:00.000 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:00.000 +11:00 [Debug] Calling Execute on job DVR.IRadarrSync
2022-03-17 13:25:00.000 +11:00 [Debug] Calling Execute on job DVR.ISickRageSync
2022-03-17 13:25:00.000 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:00.000 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:00.000 +11:00 [Debug] Calling Execute on job DVR.ISonarrSync
2022-03-17 13:25:00.001 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:00.001 +11:00 [Debug] Calling Execute on job Emby.IEmbyContentSync
2022-03-17 13:25:00.001 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:00.001 +11:00 [Debug] Calling Execute on job Plex.IPlexContentSyncRecentlyAdded
2022-03-17 13:25:00.001 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:00.001 +11:00 [Debug] Calling Execute on job Plex.IPlexContentSync
2022-03-17 13:25:00.001 +11:00 [Debug] Trigger instruction : NoInstruction
2022-03-17 13:25:00.001 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:00.001 +11:00 [Debug] Calling Execute on job System.IMediaDatabaseRefresh
2022-03-17 13:25:00.002 +11:00 [Debug] Calling Execute on job System.IResendFailedRequests
2022-03-17 13:25:00.002 +11:00 [Debug] Trigger instruction : NoInstruction
2022-03-17 13:25:00.002 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:00.003 +11:00 [Debug] Trigger instruction : NoInstruction
2022-03-17 13:25:00.003 +11:00 [Debug] Trigger instruction : NoInstruction
2022-03-17 13:25:00.361 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:00.361 +11:00 [Debug] Trigger instruction : NoInstruction
2022-03-17 13:25:00.362 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:00.362 +11:00 [Debug] Calling Execute on job Plex.IPlexContentSync
2022-03-17 13:25:00.363 +11:00 [Error] Exception when adding new Movie "Scream"
Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException: The database operation was expected to affect 1 row(s), but actually affected 0 row(s); data may have been modified or deleted since entities were loaded. See http://go.microsoft.com/fwlink/?LinkId=527962 for information on understanding and handling optimist
ic concurrency exceptions.
at Microsoft.EntityFrameworkCore.Update.AffectedCountModificationCommandBatch.ThrowAggregateUpdateConcurrencyException(Int32 commandIndex, Int32 expectedRowsAffected, Int32 rowsAffected)
at Microsoft.EntityFrameworkCore.Update.AffectedCountModificationCommandBatch.ConsumeResultSetWithoutPropagationAsync(Int32 commandIndex, RelationalDataReader reader, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.AffectedCountModificationCommandBatch.ConsumeAsync(RelationalDataReader reader, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.<>c__DisplayClass33_0`2.<<ExecuteAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.ExecuteImplementationAsync[TState,TResult](Func`4 operation, Func`4 verifySucceeded, TState state, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.ExecuteImplementationAsync[TState,TResult](Func`4 operation, Func`4 verifySucceeded, TState state, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func`4 operation, Func`4 verifySucceeded, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Ombi.Store.Repository.BaseRepository`2.InternalSaveChanges() in /home/runner/work/Ombi/Ombi/src/Ombi.Store/Repository/BaseRepository.cs:line 96
at Ombi.Store.Repository.PlexServerContentRepository.Update(IMediaServerContent existingContent) in /home/runner/work/Ombi/Ombi/src/Ombi.Store/Repository/PlexContentRepository.cs:line 117
at Ombi.Schedule.Jobs.Plex.PlexContentSync.MovieLoop(PlexServers servers, Mediacontainer content, HashSet`1 contentToAdd, Dictionary`2 contentProcessed) in /home/runner/work/Ombi/Ombi/src/Ombi.Schedule/Jobs/Plex/PlexContentSync.cs:line 328
2022-03-17 13:25:00.828 +11:00 [Warning] Exception thrown when attempting to cache the Plex Content in server "stuff.example.com"
Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException: The database operation was expected to affect 1 row(s), but actually affected 0 row(s); data may have been modified or deleted since entities were loaded. See http://go.microsoft.com/fwlink/?LinkId=527962 for information on understanding and handling optimist
ic concurrency exceptions.
at Microsoft.EntityFrameworkCore.Update.AffectedCountModificationCommandBatch.ThrowAggregateUpdateConcurrencyException(Int32 commandIndex, Int32 expectedRowsAffected, Int32 rowsAffected)
at Microsoft.EntityFrameworkCore.Update.AffectedCountModificationCommandBatch.ConsumeResultSetWithoutPropagationAsync(Int32 commandIndex, RelationalDataReader reader, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.AffectedCountModificationCommandBatch.ConsumeAsync(RelationalDataReader reader, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.<>c__DisplayClass33_0`2.<<ExecuteAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.ExecuteImplementationAsync[TState,TResult](Func`4 operation, Func`4 verifySucceeded, TState state, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.ExecuteImplementationAsync[TState,TResult](Func`4 operation, Func`4 verifySucceeded, TState state, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func`4 operation, Func`4 verifySucceeded, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Ombi.Store.Repository.BaseRepository`2.InternalSaveChanges() in /home/runner/work/Ombi/Ombi/src/Ombi.Store/Repository/BaseRepository.cs:line 96
at Ombi.Store.Repository.BaseRepository`2.AddRange(IEnumerable`1 content, Boolean save) in /home/runner/work/Ombi/Ombi/src/Ombi.Store/Repository/BaseRepository.cs:line 54
at Ombi.Schedule.Jobs.Plex.PlexContentSync.ProcessServer(PlexServers servers, Boolean recentlyAddedSearch) in /home/runner/work/Ombi/Ombi/src/Ombi.Schedule/Jobs/Plex/PlexContentSync.cs:line 204
at Ombi.Schedule.Jobs.Plex.PlexContentSync.StartTheCache(PlexSettings plexSettings, Boolean recentlyAddedSearch) in /home/runner/work/Ombi/Ombi/src/Ombi.Schedule/Jobs/Plex/PlexContentSync.cs:line 151
2022-03-17 13:25:00.829 +11:00 [Debug] Trigger instruction : NoInstruction
2022-03-17 13:25:01.299 +11:00 [Error] Exception thrown when attempting to send series over to Sonarr
System.Exception: TVDBID is missing
at Ombi.Core.Senders.TvSender.SendToSonarr(ChildRequests model, SonarrSettings s) in /home/runner/work/Ombi/Ombi/src/Ombi.Core/Senders/TvSender.cs:line 308
2022-03-17 13:25:01.302 +11:00 [Error] Exception thrown when sending a movie to DVR app, added to the request queue
System.Exception: TVDBID is missing
at Ombi.Core.Senders.TvSender.SendToSonarr(ChildRequests model, SonarrSettings s) in /home/runner/work/Ombi/Ombi/src/Ombi.Core/Senders/TvSender.cs:line 308
at Ombi.Core.Senders.TvSender.Send(ChildRequests model) in /home/runner/work/Ombi/Ombi/src/Ombi.Core/Senders/TvSender.cs:line 139
2022-03-17 13:25:01.582 +11:00 [Error] Exception thrown when attempting to send series over to Sonarr
System.Exception: TVDBID is missing
at Ombi.Core.Senders.TvSender.SendToSonarr(ChildRequests model, SonarrSettings s) in /home/runner/work/Ombi/Ombi/src/Ombi.Core/Senders/TvSender.cs:line 308
2022-03-17 13:25:01.582 +11:00 [Error] Exception thrown when sending a movie to DVR app, added to the request queue
System.Exception: TVDBID is missing
at Ombi.Core.Senders.TvSender.SendToSonarr(ChildRequests model, SonarrSettings s) in /home/runner/work/Ombi/Ombi/src/Ombi.Core/Senders/TvSender.cs:line 308
at Ombi.Core.Senders.TvSender.Send(ChildRequests model) in /home/runner/work/Ombi/Ombi/src/Ombi.Core/Senders/TvSender.cs:line 139
2022-03-17 13:25:01.636 +11:00 [Debug] Trigger instruction : NoInstruction
2022-03-17 13:25:01.997 +11:00 [Warning] Exception thrown when attempting to cache the Plex Content in server "stuff.example.com"
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
---> MySqlConnector.MySqlException (0x80004005): Duplicate entry '48230' for key 'AK_PlexServerContent_Key'
at MySqlConnector.Core.ServerSession.ReceiveReplyAsyncAwaited(ValueTask`1 task) in /_/src/MySqlConnector/Core/ServerSession.cs:line 910
at MySqlConnector.Core.ResultSet.ReadResultSetHeaderAsync(IOBehavior ioBehavior) in /_/src/MySqlConnector/Core/ResultSet.cs:line 44
at MySqlConnector.MySqlDataReader.ActivateResultSet(CancellationToken cancellationToken) in /_/src/MySqlConnector/MySqlDataReader.cs:line 107
at MySqlConnector.MySqlDataReader.CreateAsync(CommandListPosition commandListPosition, ICommandPayloadCreator payloadCreator, IDictionary`2 cachedProcedures, IMySqlCommand command, CommandBehavior behavior, Activity activity, IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/MySql
DataReader.cs:line 450
at MySqlConnector.Core.CommandExecutor.ExecuteReaderAsync(IReadOnlyList`1 commands, ICommandPayloadCreator payloadCreator, CommandBehavior behavior, Activity activity, IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/Core/CommandExecutor.cs:line 56
at MySqlConnector.MySqlCommand.ExecuteReaderAsync(CommandBehavior behavior, IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/MySqlCommand.cs:line 313
at MySqlConnector.MySqlCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/MySqlCommand.cs:line 305
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.<>c__DisplayClass33_0`2.<<ExecuteAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.ExecuteImplementationAsync[TState,TResult](Func`4 operation, Func`4 verifySucceeded, TState state, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.ExecuteImplementationAsync[TState,TResult](Func`4 operation, Func`4 verifySucceeded, TState state, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.ExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func`4 operation, Func`4 verifySucceeded, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Ombi.Store.Repository.BaseRepository`2.InternalSaveChanges() in /home/runner/work/Ombi/Ombi/src/Ombi.Store/Repository/BaseRepository.cs:line 96
at Ombi.Store.Repository.BaseRepository`2.SaveChangesAsync() in /home/runner/work/Ombi/Ombi/src/Ombi.Store/Repository/BaseRepository.cs:line 78
at Ombi.Schedule.Jobs.Plex.PlexContentSync.ProcessServer(PlexServers servers, Boolean recentlyAddedSearch) in /home/runner/work/Ombi/Ombi/src/Ombi.Schedule/Jobs/Plex/PlexContentSync.cs:line 257
at Ombi.Schedule.Jobs.Plex.PlexContentSync.StartTheCache(PlexSettings plexSettings, Boolean recentlyAddedSearch) in /home/runner/work/Ombi/Ombi/src/Ombi.Schedule/Jobs/Plex/PlexContentSync.cs:line 155
2022-03-17 13:25:01.999 +11:00 [Debug] Trigger instruction : NoInstruction
2022-03-17 13:25:01.999 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:01.999 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:01.999 +11:00 [Debug] Calling Execute on job Plex.IPlexEpisodeSync
2022-03-17 13:25:09.697 +11:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-17 13:25:09.697 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:09.697 +11:00 [Debug] Deleting trigger
2022-03-17 13:25:09.697 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:09.697 +11:00 [Debug] Calling Execute on job System.IRefreshMetadata
2022-03-17 13:25:11.643 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:11.643 +11:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-17 13:25:11.643 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:11.643 +11:00 [Debug] Deleting trigger
2022-03-17 13:25:11.643 +11:00 [Debug] Calling Execute on job Plex.IPlexAvailabilityChecker
2022-03-17 13:25:12.438 +11:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-17 13:25:12.438 +11:00 [Debug] Deleting trigger
2022-03-17 13:25:13.963 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:13.963 +11:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-17 13:25:13.963 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:13.963 +11:00 [Debug] Deleting trigger
2022-03-17 13:25:13.963 +11:00 [Debug] Calling Execute on job Plex.IPlexEpisodeSync
2022-03-17 13:25:15.977 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:15.977 +11:00 [Debug] Trigger instruction : NoInstruction
2022-03-17 13:25:15.977 +11:00 [Debug] Calling Execute on job DVR.IArrAvailabilityChecker
2022-03-17 13:25:15.977 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:16.090 +11:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-17 13:25:16.090 +11:00 [Debug] Deleting trigger
2022-03-17 13:25:17.298 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:17.298 +11:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-17 13:25:17.298 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:17.298 +11:00 [Debug] Deleting trigger
2022-03-17 13:25:17.298 +11:00 [Debug] Calling Execute on job System.IRefreshMetadata
2022-03-17 13:25:18.337 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:18.337 +11:00 [Debug] Trigger instruction : NoInstruction
2022-03-17 13:25:18.337 +11:00 [Debug] Calling Execute on job DVR.IArrAvailabilityChecker
2022-03-17 13:25:18.337 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:18.420 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:18.420 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:18.420 +11:00 [Debug] Calling Execute on job Notifications.INotificationService
2022-03-17 13:25:18.452 +11:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-17 13:25:18.452 +11:00 [Debug] Deleting trigger
2022-03-17 13:25:22.141 +11:00 [Debug] Batch acquisition of 1 triggers
2022-03-17 13:25:22.141 +11:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-17 13:25:22.141 +11:00 [Debug] Batch acquisition of 0 triggers
2022-03-17 13:25:22.141 +11:00 [Debug] Calling Execute on job Plex.IPlexAvailabilityChecker
2022-03-17 13:25:22.141 +11:00 [Debug] Deleting trigger
2022-03-17 13:25:23.167 +11:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-17 13:25:23.167 +11:00 [Debug] Deleting trigger
2022-03-17 13:25:28.855 +11:00 [Debug] Trigger instruction : DeleteTrigger
2022-03-17 13:25:28.855 +11:00 [Debug] Deleting trigger
2022-03-17 13:25:46.468 +11:00 [Debug] Batch acquisition of 0 triggers
Can someone check how they configured Ombi:
Is this enabled or disabled?
And if enabled are you also syncing with your Media Server?
Can someone check how they configured Ombi:
- Settings -> Configuration -> Movies -> Radarr -> Scan for availability
Is this enabled or disabled?
And if enabled are you also syncing with your Media Server?
My Radarr "Scan for availability" is enabled, and my Ombi is syncing with Plex. My scheduled jobs are 0 0/5 * 1/1 * ? *
for both "Plex Sync", and "Plex Recently Added Sync".
Maybe having both at the same interval is causing duplicate email send triggers? I'll change my Plex Sync
to something less frequent.
Can someone check how they configured Ombi:
- Settings -> Configuration -> Movies -> Radarr -> Scan for availability
Is this enabled or disabled? And if enabled are you also syncing with your Media Server?
My Radarr "Scan for availability" is enabled, and my Ombi is syncing with Plex. My scheduled jobs are
0 0/5 * 1/1 * ? *
for both "Plex Sync", and "Plex Recently Added Sync".Maybe having both at the same interval is causing duplicate email send triggers? I'll change my
Plex Sync
to something less frequent.
That could cause issues yes. Why do you have them running at the same CRON?
Plex Sync: a full sync to get all media (without checking for deletion) Plex Recently added: sync which fetched the recently added media from Plex (without removing deletion) Media Data Refresh: Full deletion of Ombi Cache with a full sync with the Media Server (which causes deleted media to be unavailable in Ombi)
Can you try and uncheck the Radarr "Scan for Availability" and see if the issue persists?
That could cause issues yes. Why do you have them running at the same CRON?
I never even thought of looking at the CRON jobs let alone modify them...
Will try to modify the CRONs and uncheck the scan for availability.
I thought I also had the same CRONs at the same time, but I was wrong; I was looking at the same box lol.
Plex Recently added: 0 0/30 1/1 ? Plex Sync: 0 0 2 1/1 ? Media Data Refresh: 0 0 12 1/5 ? *
So in short; my Crons weren't all at the same time and the issue was still happening; but I will try to disable the "Scan for Availability" in Radarr settings anyways.
Can you try and uncheck the Radarr "Scan for Availability" and see if the issue persists?
My ‘scan for availability’ was never checked and I still have the problem.
Never messed about with cron jobs tho - interested in hearing if anyone has any success with changing these.
I get duplicate push notifications in the app every single time someone requests anything. It is always exactly 2 push notifications.
After updating to 4.16.11 I started getting two notifications/emails of the same media being available every 30 minutes. Ive updated to 4.16.12 and this is down to one, but I'm still getting the same notification every 30 mins. I can disable Email notifications, but the slider for Mobile/App notifications doesn't seem to stop them.
I'm also having this problem, exactly 2 notifications with exactly 5 minutes between them.
I'm also having this problem. New install. I get every mobile notification twice.
Describe the bug Duplicate email notifications to users at every touch point.
To Reproduce
Expected behaviour Only a single email notification per step to be sent to users
Screenshots N/A
Logs (Logs directory where Ombi is located) latest log: log-20201021.txt
Desktop (please complete the following information):
Ombi Version (please complete the following information):
Additional context looks very similar to issue #2998 which closed due to innactivity.