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
Email Reports being sent out twice #5300
Comments
As also stated at the Forum (http://forum.piwik.org/read.php?2,116654) we got a similiar Problem - E-Mail Reports are sent out twice to our Customers. It's a productive System. Booth Mails are sent out identically at the same Time! Within DB: http://temp.in.futureweb.at/piwik/db.jpg - 2 Reports created If you need any further Information don't hesitate to contact me - will try to provide any needed Information ... Andreas Schnederle-Wagner |
Since you have moved things around I have now had to setup here to post. As I had posted above on the port of here, when is some one going to look into the problem. I have updated on every update it now has "2.4.1" on it but still having the same problem. As I Posted above:As I have stated on the Forum at: For some reason my system is sending out reports twice, this has been happening since using 2.2.0, it was a complete fresh install (Eg Last weeks one was, Week 19 May - 25 May 2014 PDF) It is the same size attachment with the same info. There is only one cronjob at 1min past every Hr OS Debian Wheezy This system is a production machine and most software (MySQL/PHP/Apache) can not be upgraded with out braking a lot of other sites. Is there any other info you need, and from where it is... I need to get this fixed, as my customers are complying about receiving the same email twice a week. |
I have the same problem, except that the delay between the two identical mails is 1 day... |
Thanks guys for the reports, it's appreciated. The issue is experienced by a lot of users who have a standard configuration, we must investigate this issue. We surely will find a solution. If we can't find the root cause which I hope we will, then we could at least implement a safety net in before sending email to check the same email has not already been sent. If you have any more information please post, such as the exact times with seconds at which reports were received? |
Here are more reports of the issue. Email reports will send out multiple emails (most times 5) of the same report. Also, the report is sending at 3am instead of the set time of 8am. Expectation: The report only needs to send once and if it could send at the designated time, that would be great. To recreate:
Sometime, we received another report three times:
Another report: I always get the emails in duplicate each time they come out and occasionally, like today, there are 4 or 5 of them. Do you know why that is or how I can fix it? |
Possible fix in #6392, feel free to review. |
Fix for #5300: prevent email reports from being sent twice
The fix has been merged. When trying to send again a report that was already sent, a warning is now logged in the logs, but the report is not sent. Manually triggering a report through the admin is not affected (report always sent). |
As I have stated on the Forum at:
http://forum.piwik.org/read.php?2,115952,page=1#msg-115952
For some reason my system is sending out reports twice, this has been happening since using 2.2.0, it was a complete fresh install
(Eg Last weeks one was, Week 19 May - 25 May 2014 PDF)
Monday sent 26 May 2014 at 23:01 Subject; (Report Website **** - Week 19 May - 25 May 2014)
Sunday sent 01 June 2014 23:01 Subject; (Report Website **** - Week 19 May - 25 May 2014)
It is the same size attachment with the same info.
There is only one cronjob at 1min past every Hr
"/usr/bin/php5 /web/piwik_2/console core:archive --url=http://stats2/ > /web/piwik_2/archive/piwik-archive.log"
OS Debian Wheezy
MySQL version 5.5.31
PHP version 5.4.4-14+deb7u2
Apache version 2.2.22
This system is a production machine and most software (MySQL/PHP/Apache) can not be upgraded with out braking a lot of other sites.
Is there any other info you need, and from where it is...
The text was updated successfully, but these errors were encountered: