docker compose;no connect Mongodb;ERROR:2024-11-19T02:20:17.982Z: INFO [jobs:manager] Cancelling 0 jobs { MongoNetworkError: failed to connect to server [localhost:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker-compose, javascript, mongodb
Research direction
Start by reproducing the failure with Docker Compose and inspect the MongoDB connection configuration indicated by the ECONNREFUSED localhost:27017 log. Done means the Countly jobs manager connects to MongoDB successfully without the reported network error.
Written by the indexing model from the issue text.
Description
2024-11-19T02:20:17.982Z: INFO [jobs:manager] Cancelling 0 jobs { MongoNetworkError: failed to connect to server [localhost:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017] at Pool. (/opt/countly/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:431:11) at emitOne (events.js:116:13) at Pool.emit (events.js:211:7) at connect (/opt/countly/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:557:14) at makeConnection (/opt/countly/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:39:11) at callback (/opt/countly/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:261:5) at Socket.err (/opt/countly/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:286:7) at Object.onceWrapper (events.js:315:30) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at emitErrorNT (internal/streams/destroy.js:66:8) at _combinedTickCallback (internal/process/next_tick.js:139:11) at process._tickCallback (internal/process/next_tick.js:181:9) name: 'MongoNetworkError', errorLabels: [ 'TransientTransactionError' ], [Symbol(mongoErrorContextSymbol)]: {} } { MongoNetworkError: failed to connect to server [localhost:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017] at Pool. (/opt/countly/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:431:11) at emitOne (events.js:116:13) at Pool.emit (events.js:211:7) at connect (/opt/countly/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:557:14) at makeConnection (/opt/countly/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:39:11) at callback (/opt/countly/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:261:5) at Socket.err (/opt/countly/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:286:7) at Object.onceWrapper (events.js:315:30) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at emitErrorNT (internal/streams/destroy.js:66:8) at _combinedTickCallback (internal/process/next_tick.js:139:11) at process._tickCallback (internal/process/next_tick.js:181:9) name: 'MongoNetworkError', errorLabels: [ 'TransientTransactionError' ],
This is a problem,i do not handle it
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 980
- Avg merge
- 17h 54m
- Merged PRs (30d)
- 59
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 Countly/countly-server
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Countly/countly-server#7775 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Countly/countly-server#6891 · 1 comment ·
Maintainers usually reply within 1 day
-
Hardware specsOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Countly/countly-server#5665 ·
Maintainers usually reply within 1 day
-
ARM64 SupportPossibly taken @andreialecu claimed this 254 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
Countly/countly-server#5421 · 10 comments · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Countly/countly-server#4900 · 1 comment ·
Maintainers usually reply within 1 day
All issues in Countly/countly-server
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
apache/rocketmq-dashboard#6896 ·
Maintainers usually reply within 3 days
-
bug engine
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
frostney/GocciaScript#1746 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SasanLabs/VulnerableApp#836 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
keyxmakerx/Chronicle#1469 ·
Maintainers usually reply within 1 day