[SERVER-25036] Solaris 11.3 x86 Failed to inizialize JSContext Created: 13/Jul/16 Updated: 13/Aug/16 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 3.3.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Heitepriem | Assignee: | Jonathan Reams |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Install MongoDB 3.3.9 on fresh Solaris installation |
||||||||
| Sprint: | Platforms 17 (07/15/16), Platforms 18 (08/05/16) | ||||||||
| Participants: | |||||||||
| Description |
|
I downloaded the latest Development version (3.3.9) because it says that the Bug So I tried to connect to the console using this command: */opt/mongo/bin/mongo --port 27017* and got this error:
A few information regarding my setup: |
| Comments |
| Comment by Daniel Heitepriem [ 28/Jul/16 ] | ||||||||||||||||||||||||||||||||||||||||||
|
Alright, everything is now working as it should, using version 3.3.10
Regards, | ||||||||||||||||||||||||||||||||||||||||||
| Comment by Daniel Heitepriem [ 27/Jul/16 ] | ||||||||||||||||||||||||||||||||||||||||||
|
Hi acm, Regards, | ||||||||||||||||||||||||||||||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 27/Jul/16 ] | ||||||||||||||||||||||||||||||||||||||||||
|
The fix version is indeed wrong:
| ||||||||||||||||||||||||||||||||||||||||||
| Comment by Jonathan Reams [ 27/Jul/16 ] | ||||||||||||||||||||||||||||||||||||||||||
|
Actually looking at this again, I think the fix made it into 3.3.10 and not 3.3.9. When I run with 3.3.9, I see the JSContext failure you reported, but not in 3.3.10 - I think our fixVersion is just wrong for | ||||||||||||||||||||||||||||||||||||||||||
| Comment by Jonathan Reams [ 27/Jul/16 ] | ||||||||||||||||||||||||||||||||||||||||||
|
semirben, I'm having trouble reproducing this. I'm running on stock Oracle Solaris 11.3 for x86_64:
Are you running Oracle Solaris 11.3? What version of the kernel are you running? What's the output of pkg info kernel? We'd tested the fix in | ||||||||||||||||||||||||||||||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 15/Jul/16 ] | ||||||||||||||||||||||||||||||||||||||||||
|
Thanks for the additional information, we will investigate. | ||||||||||||||||||||||||||||||||||||||||||
| Comment by Daniel Heitepriem [ 15/Jul/16 ] | ||||||||||||||||||||||||||||||||||||||||||
|
Hi acm, I neither got a stack trace nor any other error. After installing MongoDB I tried to connect to the console and almost instantly got this error. Here are the steps after installing MongoDB
And the output of the logfile:
| ||||||||||||||||||||||||||||||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 15/Jul/16 ] | ||||||||||||||||||||||||||||||||||||||||||
|
Is there any other information printed? Do you get a stack trace? Can you provide the entire output, including the invocation of the shell, until it terminates? |