Mongo error when `bin/up` on Ubuntu 16.04
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, mongodb, shell
- Domain
- databases, infrastructure
Research direction
Start by reproducing the failure with bin/up on Ubuntu 16.04 and inspect the Mongo replica-set startup output around the mongosh assertion. Compare the Docker and Mongo setup behavior with the expected successful startup; done means bin/up completes without the mongosh error and the services run.
Written by the indexing model from the issue text.
Description
Steps to Reproduce
- clone toolkit
- run
bin/up
Expected Behaviour
Everything runs OK.
Observed Behaviour
Initiating Mongo replica set...
Creating mongo ... done
# mongosh[25]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
# Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
----- Native stack trace -----
1: 0xd5a347 node::Assert(node::AssertionInfo const&) [mongosh]
2: 0xdcde28 node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [mongosh]
3: 0xdcdf11 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [mongosh]
4: 0xc784ab node::MultiIsolatePlatform::Create(int, v8::TracingController*, v8::PageAllocator*) [mongosh]
5: 0xc684ae main [mongosh]
6: 0x7f5a046ffd90 [/lib/x86_64-linux-gnu/libc.so.6]
7: 0x7f5a046ffe40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
8: 0xc7135e [mongosh]
Context
I try to update docker, but it doesn't work.
Technical Info
- URL:
- Browser Name and version: Edge
- Operating System and version (desktop or mobile): Ubuntu 16.04
- Signed in as:
- Project and/or file:
Analysis
It seems like a docker error, but I have no idea.
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 310
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from overleaf/toolkit
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in overleaf/toolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ll7/robot_sf_ll7#9560 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100