leap_platform.git - [leap

Age	Commit message (Collapse)	Author
2014-12-17	Merge branch 'micah/platform-feature/6544' into develop	varac
	Conflicts: puppet/modules/site_check_mk/files/agent/logwatch/bigcouch.cfg Change-Id: I1646e49ffa5437a861b402b755bc15943c42ec4f
2014-12-16	Ignore "Generic server terminating" bigcouch message (Feature #6544)	Micah Anderson
	Change-Id: I73defd7964501e4eabe7dd05c02887e7aeb2f063
2014-12-16	ignore additional bigcouch error messages (#6512)	Micah Anderson
	Change-Id: Ie51fb485bcae9a9467c465bdd1b4a5785023db04
2014-12-09	Ignore rexi_EXIT bigcouch error (Bug #6512)	Micah Anderson
	Change-Id: I03842b65329aabb012cc2c7514007e174cbd8fc0
2014-12-02	Ignore bigcouch conflict errors, mainly coming from tapicero creating new ↵	varac
	users (Feature #6481) There are potentially many tapicero daemons running, and they all try to do the same thing at the same time. It is basically designed to create race conditions. All tapicero daemons try to create the user db at the same time. Only one of them wins the race and actually creates it. We need to fix this later (see https://leap.se/code/issues/6480) but for now, we ignore them because conflict errors should be handled by the applictation anyway. Change-Id: I91095b1901d238e3d199954ba3716023d3fd49c1
2014-03-04	ignore bigcouch 'Shutting down group server' error (#5246)	varac

2014-03-03	ignore "Uncaught error in HTTP request: {exit, normal}" error (#5226)	varac

2014-03-03	check syslog for bigcouch restarts	varac

2014-03-03	don't displa ycontext for errors in bigcouch.log (reported too many context ↵	varac
	lines), ignore patterns first
2014-02-27	ignore valid log patterns from bigcouch.log	varac

2014-02-27	renamed logwatch/couchdb.cfg to logwatch/bigcouch.cfg	varac