Closed Bug 493282 Opened 15 years ago Closed 15 years ago

Need to check logs for emails sent out on stage vs prod

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: paulc, Assigned: aravind)

References

()

Details

This is related to bug 454629. We likely need IT to check the logs for the two and compare. 
We have user watches on the Forum that let users know when a new post has been posted in threads. The Contributors forum watches work for staging but not production. Perhaps looking at the logs would help us understand why this happens.
Please file these bugs against IT, not SUMO.
Assignee: nobody → server-ops
Component: General → Server Operations
Product: support.mozilla.com → mozilla.org
QA Contact: general → mrz
Version: unspecified → other
Are you looking for the apache error logs?
I'm looking for the logs that show when php tries to send out emails. We have an inconsistency between stage and production for the Contributors/OT forums. Lucy or Chris could say more about it. I'm trying to see if there's a difference between stage and production in relation to bug 454629.
Mail logs rather than apache logs would be what you want.
Assignee: server-ops → oremj
Did this bug need more info, or is it just waiting for time to grab the logs?

I would think we just need to set aside a specific time to try and trigger sending emails from all the different forums. Then we only need to grab the logs from a small window. I'd be available to help with this, if so.
Aravind or Dave, will you take a look at the mail logs for this.
Assignee: oremj → server-ops
Assignee: server-ops → aravind
What kind of logs are you looking for?  The mail servers only log from and to addresses.  All of the servers in the app cluster are configured to send mail out directly to the internet and not through our mail relays.  So if you need specific mail logs, I'd need to know the time and date around which you want me to look.  This would involve combing multiple servers for your messages, so please be as specific as you can.
Is it easier if we try to send these messages while you're watching or is it the same as if we just give you some timestamps? Also, would it help the search to have a specific keyword in the message? 

If it doesn't matter when the messages were from I should have received notification for any of the posts here https://support.mozilla.com/tiki-view_forum_thread.php?forumId=3&comments_threshold=0&comments_parentId=270707&comments_offset=20&comments_per_page=20&thread_style=commentStyle_plain (sorry, can't find a way to link to specific posts).

I *did* receive notification for the Cww's "another post" reply in this thread https://support.mozilla.com/tiki-view_forum_thread.php?comments_parentId=330915&forumId=4
Lucy: We will not be able to see the comments (or text) in the e-mails, no matter how we slice this.  The best I can do is tell you if a mail was sent to someone from our servers.  It would be easiest if we can schedule this for sometime later this week, and test while we are watching.  How does sometime in the AM on Thursday sound?
Aravind, sounds good. You're PDT? Drop a time in here, or feel free to find me on IRC (Lucy) to sort out when.
Thanks for helping on this Lucy.
Okay, so I was watching the mail logs on the webheads when Lucy was testing.  I was able to see the app servers generate mails for the foums that were working.  For the forums that weren't, the app servers did not even generate e-mails.  So, this doesn't seem to be a case of mail getting lost or rejected on the gateways etc.  The application itself doesn't seem to be generating e-mails for some forums.  Also, I did not notice any errors from the application when this happened.  At this point, I'd say this may be an application/code issue..
Please re-open if you need any more help from us.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.