Closed
Bug 1193037
Opened 9 years ago
Closed 9 years ago
hgweb1 isn't logging to /var/log/hg.log
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gps, Assigned: gps)
Details
Attachments
(1 file)
hgweb1.dmz.scl3 isn't logging to /var/log/hg.log. I'm not sure what is or isn't going on. The serverlog extension is installed and should be producing syslog messages to local2. Not sure why /var/log/hg.log isn't being updated. FWIW, I touched /var/log/hg.log a few minutes ago to see if the missing file was the cause of the problem. It obviously wasn't.
|
||
Comment 1•9 years ago
|
||
weird. I tried HUP'ing rsyslogd, but that didn't appear to do anything though it should have. 'service rsyslogd restart' and it's logging now.
|
Assignee | |
Comment 2•9 years ago
|
||
I should have tried that. Doh. I guess we should modify Ansible to restart rsyslogd when it touches rsyslog config files. I'll code this up real quick.
Assignee: nobody → gps
|
|
Assignee | |
Comment 3•9 years ago
|
||
ansible: restart rsyslogd when modifying config files (bug 1193037); r?fubar hgweb1 wasn't logging to hg.log after it was freshly provisioned. It appears rsyslogd needs to be restarted to pick up new config files. Sending a SIGHUP doesn't appear to work :/
Attachment #8646490 -
Flags: review?(klibby)
|
|
||
Comment 4•9 years ago
|
||
Comment on attachment 8646490 [details] MozReview Request: ansible: restart rsyslogd when modifying config files (bug 1193037); r?fubar https://reviewboard.mozilla.org/r/15785/#review14043 Ship It!
Attachment #8646490 -
Flags: review?(klibby) → review+
|
|
Assignee | |
Comment 5•9 years ago
|
||
url: https://hg.mozilla.org/hgcustom/version-control-tools/rev/1af450383ad064d9b07ba0f6b9d27307e4b5338d changeset: 1af450383ad064d9b07ba0f6b9d27307e4b5338d user: Gregory Szorc <gps@mozilla.com> date: Tue Aug 11 11:18:49 2015 -0700 description: ansible: restart rsyslogd when modifying config files (bug 1193037); r=fubar hgweb1 wasn't logging to hg.log after it was freshly provisioned. It appears rsyslogd needs to be restarted to pick up new config files. Sending a SIGHUP doesn't appear to work :/
|
|
Assignee | |
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•