On 11/01/06 10:24, Francis L Fabrizio wrote:
Found it finally!
2nd instance.
Haha, I'm glad the problem ended up being something that was not
actually impossible. :)
My successor at my former job here accidentally fired up our old VM some weeks ago.
Because of the way the mail flows around here and the DNS setup, it was not immediately
obvious that the mail was originating from a different server. The clue that tipped me
off to it was that when I looked deeper at the report, it showed one ticket still owned
by someone who no longer works here. I knew I reassigned all of his tickets elsewhere,
so it was then obvious that this was pulling from stale data. I should have caught this
much sooner, but it was a "can't see the forest for the trees" problem.
Thanks for all your help. At least the effort uncovered some other
opportunities for improvement. :-)
-Fran
Shawn
-----Original Message-----
From: Shawn M Moore [mailto:[email protected]]
Sent: Wednesday, December 22, 2010 2:31 PM
To: Francis L Fabrizio
Cc: [email protected]
Subject: Re: [rt-users] Tracking down rogue dashboard subscriptions
On 10/12/22 8:17, Francis L Fabrizio wrote:
I changed the subscription time to 7am (keeping the frequency at
never), and still got the mail... at 6am!
All signs point to you having another subscription (though we seem to
have ruled that out) or, like Ken Crocker guessed, a second RT instance
(or just rt-send-dashboards cronjob) running.
Not sure what to tell you, unfortunately. I don't see any way these
symptoms could be caused by an ordinary bug in the dashboard code.
If you do figure it out please follow up because I'm curious and would
like to better diagnose this situation in the future. This thread has
already prompted some improvements to dashboard diagnostics, so thanks.
:)
Shawn
