Last modified: 2014-02-03 22:56:43 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T62772, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 60772 - Logstash stopped recording apache2 events (fatalmonitor) at 2014-02-01
Logstash stopped recording apache2 events (fatalmonitor) at 2014-02-01
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Logstash (Other open bugs)
wmf-deployment
All All
: High normal (vote)
: ---
Assigned To: Bryan Davis
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-02-03 18:03 UTC by Bryan Davis
Modified: 2014-02-03 22:56 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bryan Davis 2014-02-03 18:03:02 UTC 
It appears that no events of the "apache2" type have been stored in logstash since 2014-01-31T23:59:59.000Z. These events are used to drive the fatalmonitor dashboard.

I tried restarting the logstash instance on logstash1001 but this did not seem to restore the event stream. Events of other types are being recorded which are delivered via the udp2log transport stream. fluorine.eqiad.wmnet is still adding new lines to /a/mw-log/apache2.log.
Comment 1 Bryan Davis 2014-02-03 18:43:42 UTC 
The root cause seems to be a bad grok parse pattern. See https://gerrit.wikimedia.org/r/#/c/110971 for a fix that matches config that I have manually deployed on logstash1001.
Comment 2 MZMcBride 2014-02-03 22:55:06 UTC 
https://gerrit.wikimedia.org/r/110971 has now been merged. Is this bug resolved/fixed?
Comment 3 Bryan Davis 2014-02-03 22:56:43 UTC 
I forced a puppet run after the merge and was able to verify the fix.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links