[SERVER-25562] Archive stdout.log with mongod.log for Jepsen task Created: 11/Aug/16 Updated: 13/Aug/16 Resolved: 11/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | Jonathan Abrahams |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | TIG 2016-08-29 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
When mongod is started up by the Jepsen client, it logs to stdout.log. The conf file also logs to mongod.log. Sometimes mongod will fail to start and having this exrta log file maybe helpful in determining the cause. |
| Comments |
| Comment by Githook User [ 11/Aug/16 ] |
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: |