Closed Bug 867305 Opened 11 years ago Closed 11 years ago

Webpay prod celery tasks are not logging to syslog

Categories

(Cloud Services :: Operations: Marketplace, task, P1)

x86
macOS
task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kumar, Assigned: oremj)

References

Details

I was looking for log messages about postbacks which run in a celery task but it looks like we stopped getting them in the syslog files after April 2. This is the last log message:

2013-04-02.bz2:Apr  2 15:30:53 web24.addons.phx1.mozilla.com: [] w.pay.utils:INFO about to notify http://mozpay-catalog.paas.allizom.org/mozpay/postback of notice type 0 :/data/www/marketplace.firefox.com-webpay/webpay/webpay/pay/utils.py:56

I ran the code successfully which would otherwise generate that log message but I see nothing.

Any ideas why the celery daemon is not doing logging? 

Notice how the message above is not actually running on celery. I think celery logging never went to syslog because we activated celery here:
Summary: Webpay prod celery logging disappeared → Webpay prod celery tasks are not logging to syslog
Priority: -- → P1
Assignee: server-ops-amo → jthomas
Rob tried to log a bunch of stuff on -dev's celery today and didn't see anything come through either.  If that's totally unrelated you can ignore, but thought it might help.
Jeremy found rsyslog was having trouble resolving hostnames or something on -dev.  He fixed it last night, could also be the same issue here?
https://github.com/mozilla/funfactory/pull/51

kumar | oremj: I pulled it in but I don't want to deal with upgrading funfactory in webpay. I'll patch our local LOGGING to fix it.
Assignee: jthomas → oremj
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Does this fix sending logs to celery? I thought it only fixed putting the right hostname in the log file? I couldn't easily hotfix webpay so this is not applied yet. It will be in bug 871860
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
The problems with syslog were fixed by oremj in Bug 868210 and logs in comment 0 started to reappear in logs.

The log hotfix does just fix the hostname in the logs, but without it is hard to differentiate where the logs are originating from.

[root@syslog1.addons.phx1 05]# bzgrep 'w.pay.utils' *
2013-05-03.bz2:May  3 14:59:12 localhost6.localdomain: [] w.pay.utils:INFO about to notify https://marketplace-dev.allizom.org/services/webpay/postback of notice type 0 :/data/www/marketplace-dev.allizom.org-webpay/webpay/webpay/pay/utils.py:56
2013-05-03.bz2:May  3 14:59:13 localhost6.localdomain: [] w.pay.utils:DEBUG URL https://marketplace-dev.allizom.org/services/webpay/postback responded OK for transaction webpay:307797c9-b03d-4c14-91e5-c1e0de310f32 notification :/data/www/marketplace-dev.allizom.org-webpay/webpay/webpay/pay/utils.py:94
2013-05-03.bz2:May  3 15:06:36 localhost6.localdomain: [] w.pay.utils:INFO about to notify https://marketplace-dev.allizom.org/services/webpay/postback of notice type 0 :/data/www/marketplace-dev.allizom.org-webpay/webpay/webpay/pay/utils.py:56
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
ok, thanks. When will this be applied to webpay production? I don't see a commit in Bug 868210 but I just reproduced the problem in prod and I still do not see celery log notices.

To reproduce, you can load this in a browser on a Firefox OS phone (or Firefox OS Simulator) http://mozpay-catalog.paas.allizom.org/ Tap Buy and tap Continue to simulate.
re-opening since the original problem for us was on prod only, not dev
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: oremj → jthomas
webpay -dev and stage celery logs are reaching syslog, but prod is only writing to console. I am still investigating.
Assignee: jthomas → oremj
Should be fixed in https://github.com/mozilla/webpay/commit/767cf680b51d6a574ce4f9a14572b0024df70db9
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Component: Server Operations: AMO Operations → Operations: Marketplace
Product: mozilla.org → Mozilla Services
You need to log in before you can comment on or make changes to this bug.