[SERVER-7743] Print the low-level error when socket operations fail Created: 21/Nov/12 Updated: 29/Nov/16 Resolved: 29/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Usability |
| Affects Version/s: | 2.2.2, 2.3.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | William Zola | Assignee: | Jonathan Reams |
| Resolution: | Done | Votes: | 14 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | Platforms 2017-01-23 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When a low-level socket operation fails, the stack trace will only contain SOCKET_ERROR, RECV_ERROR or SEND_ERROR. Instead, the server should print out (at least) the errno from the underlying error, and ideally the error text corresponding to the errno. |
| Comments |
| Comment by Jonathan Reams [ 29/Nov/16 ] |
|
I just checked and by default we do log at log level zero by default in all the places I could find for the use of Socket. I'm going to close this as gone away. |
| Comment by Githook User [ 04/Dec/13 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by auto [ 02/Oct/13 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |
| Comment by auto [ 27/Sep/13 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: Revert " This reverts commit 86241d5da584018ef9bcfa779c1cc47459f2d155. |
| Comment by auto [ 26/Sep/13 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |