[SERVER-3496] file/io warning on some numa system WAS - Got signal: 11 (Segmentation fault) Created: 27/Jul/11  Updated: 12/Jul/16  Resolved: 28/Sep/11

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: 1.8.1
Fix Version/s: 1.8.4, 2.0.1, 2.1.0

Type: Bug Priority: Critical - P2
Reporter: Paul Gao Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Centos 5 64bit


Attachments: File mongod-jeeves.strace     File numa_maps     File numa_maps_mongodb     File numa_maps_mongodb     File numa_maps_mongodb    
Issue Links:
Depends
Related
is related to SERVER-3212 Got signal: 11 (Segmentation fault) Closed
Operating System: Linux
Participants:

 Description   
    • WARNING: cannot parse numa_maps

Wed Sep 7 22:44:28 [initandlisten] File I/O errno:29 Illegal seek

[edited to show correct warning]



 Comments   
Comment by Eliot Horowitz (Inactive) [ 17/Oct/11 ]

No - this is just a cosmetic issue.

Comment by Jason Koppe [ 17/Oct/11 ]

To be clear, if this is the only issue in the logs, should seeing this warning prevent an upgrade?

Comment by auto [ 26/Sep/11 ]

Author:

{u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: Correctly check return value of read() SERVER-3496
Branch: master
https://github.com/mongodb/mongo/commit/5b39cc6b52893b54d021e3014380b6d9cf9f9eed

Comment by auto [ 26/Sep/11 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: fix numa parsing issue SERVER-3496
Branch: v1.8
https://github.com/mongodb/mongo/commit/b09007c96bafb185374ccd5ab68fba5e8362017f

Comment by auto [ 26/Sep/11 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: fix numa parsing issue SERVER-3496
Branch: v2.0
https://github.com/mongodb/mongo/commit/2c34a826b61921c1635d83bf726e38acd76c2d7a

Comment by auto [ 26/Sep/11 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: fix numa parsing issue SERVER-3496
Branch: master
https://github.com/mongodb/mongo/commit/299620984586bdb497342d7ba60a4fb967e4ccb3

Comment by Mathias Stearn [ 13/Sep/11 ]

@Stefan, I just noticed that the wrong error was shown in the description. It's been fixed now.

Comment by Stefan Huber [ 13/Sep/11 ]

sure thing, totally missed the NUMA bit (sorry for that - quite late here)
The error just looked way to similar

Comment by Mathias Stearn [ 13/Sep/11 ]

@Stefan: I don't think that strace is from a NUMA machine. Could you open a different ticket with the log where you first saw it?

Comment by Stefan Huber [ 13/Sep/11 ]

Got the same problem using Mongodb 2.0.0 on CentOS 5.6 64bit.
I attached my strace.

Comment by Mathias Stearn [ 12/Sep/11 ]

It should be run somewhere that is exciting the error. However you don't need to bring down anything. The --port and --dbpath are specified to (hopefully) not conflict with your existing deployment. It should try to start up, fail (because dbpath doesn't exist) and shut down right away.

Comment by Joseph Hammerman [ 12/Sep/11 ]

To be clear, this command shoudl be run on one of our prod servers (which are displaying the error)?

We will have to schedule a time to bring down the daemon on one of our Replica Sets, if so.

Comment by Mathias Stearn [ 12/Sep/11 ]

Could you run the following and attach mongod.strace?

strace -s 100 mongod --port 9999 --dbpath /tmp/does_not_exist 2>mongod.strace

Generated at Thu Feb 08 03:03:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.