Ombi
Ombi copied to clipboard
Ombi-app
Duplicate Notifications to Users
Describe the bug Duplicate email notifications to users at every touch point.
To Reproduce
- Request a movie to tv series with an account that requires approval
- Approve (duplicates sent to user here here)
- Download complete -> movie available (another duplicate notification sent to user here)
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):
- OS: unraid linux docker
Ombi Version (please complete the following information):
- Version 4.0.533.0
- Media Server Plex
- Database Type: SQLite
Additional context looks very similar to issue #2998 which closed due to innactivity.
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.
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:
https://pastebin.com/P0b5gWiC
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?
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:
https://controlc.com/e28e1131
Sorry the 1 minute of logs was too long/large for pastebin or github's limits.