[SERVER-9313] Mongodb segfaults Created: 10/Apr/13 Updated: 10/Dec/14 Resolved: 28/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.2.2, 2.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Luciano Issoe | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Upgrading ReplicaSet from 2.2.2 to 2.4.1 on Ubuntu 12.04_LTS. Upgrading one secondary at a time and then stepDown primary and upgrade it. After upgrading one of the secondaries, the other secondary (2.2.2) became the primary. So far so good. At the same time the one just upgraded to 2.4.1 crashed and asked for a forced restart. The forced restart made the server come back. Here´s the trace log: Wed Apr 10 19:13:42.892 [conn11018514] authenticate db: mobile-ads { authenticate: 1, user: "heroku_app", nonce: "c4f142c96e76b192", key: "e3da736a5915cc8fd221c9f0e1055f88" }Wed Apr 10 19:13:42.961 Wed Apr 10 19:13:42.961 Invalid access at address: 0x7ed6ab13bff0 from thread: conn11018521 Wed Apr 10 19:13:42.961 Wed Apr 10 19:13:42.961 Wed Apr 10 19:13:42.961 Invalid access at address: 0x7ed6b088bff0 from thread: conn11018532 Invalid access at address: 0x7ed6aec76ff0 from thread: conn11018530 Wed Apr 10 19:13:42.961 Wed Apr 10 19:13:42.961 Invalid access at address: 0x7ed6af57fff0 from thread: conn11018531 Invalid access at address: 0x7ed6ae46eff0 from thread: conn11018520 Invalid access at address: 0x7ed6b0689ff0 from thread: conn11018529 Wed Apr 10 19:13:42.961 Wed Apr 10 19:13:42.961 Got signal: 11 (Segmentation fault). Invalid access at address: 0x7ed6aea74ff0 from thread: conn11018522 Wed Apr 10 19:13:42.961 Got signal: 11 (Segmentation fault). Wed Apr 10 19:13:42.961 Got signal: 11 (Segmentation fault). Got signal: 11 (Segmentation fault). Got signal: 11 (Segmentation fault). Wed Apr 10 19:13:42.961 |
||
| Operating System: | ALL |
| Participants: |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 28/Oct/13 ] |
|
Hi Luciano, I'm closing this issue due to inactivity. As Eric noted, this may be related to If you've upgrade to 2.4.2 or newer and are still experiencing this issue please feel free to reopen with additional details. Thanks, |
| Comment by Eric Milkie [ 11/Apr/13 ] |
|
We fixed a segfault that might be your issue, in 2.4.2: |
| Comment by Luciano Issoe [ 11/Apr/13 ] |
|
It happened again. Third time in two days! Three different instances, same error. Rolling back to 2.2;... |
| Comment by Luciano Issoe [ 11/Apr/13 ] |
|
It happened again, Primary crashed right now. Thu Apr 11 15:10:12.016 Invalid access at address: 0x7dd936ac1ff0 from thread: conn24344468 Thu Apr 11 15:10:12.036 [conn24344471] authenticate db: mobile-ads { authenticate: 1, user: "heroku_app", nonce: "cdf74ad518fe62a6", key: "4ad17b691330d66715cf7fc22baacb70" }Thu Apr 11 15:10:12.047 [conn24344472] authenticate db: web-ads { authenticate: 1, user: "heroku_app", nonce: "d813c9227661b1ad", key: "f53f4b2582892832459e0017c320ec19" }Thu Apr 11 15:10:12.068 [conn24344473] authenticate db: web-ads { authenticate: 1, user: "heroku_app", nonce: "321849d76d43b3a5", key: "df43e4139fb8af8cef140d430f0e72b1" }Thu Apr 11 15:10:12.069 [conn24344474] authenticate db: web-ads { authenticate: 1, user: "heroku_app", nonce: "eb14c1794b943d2b", key: "ba2ed3fe327d2c80dcee0d8e399c71d2" }Thu Apr 11 15:10:12.078 [conn24344476] authenticate db: mobile-ads { authenticate: 1, user: "heroku_app", nonce: "ade8bfe21ac6eac9", key: "e3b4215ce260a54ee45bf224db9020b0" }Thu Apr 11 15:10:12.078 [conn24344475] authenticate db: mobile-ads { authenticate: 1, user: "heroku_app", nonce: "e239c13063ea6bbb", key: "ac6510baf61def9fc17c9c5fa5b57783" }Thu Apr 11 15:10:12.086 [conn24344477] authenticate db: mobile-ads { authenticate: 1, user: "heroku_app", nonce: "d4471c9b812dbb57", key: "dbf832eda0911b5f7634c9adbcf29d6f" }Thu Apr 11 15:10:12.087 [conn24344478] authenticate db: mobile-ads { authenticate: 1, user: "heroku_app", nonce: "7ac86afe69ed14c1", key: "c55bb0c8f30b3dcfa280abdbb92c7d0a" }Thu Apr 11 15:10:12.094 Got signal: 11 (Segmentation fault). Here´s whats logged on dmesg: [13252333.794369] mongod D ffff880f22dd3700 0 914 1 0x00000000 |