Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Facing issue when tiledesk server connect to mongo db #94

Open
shikhil-gupta opened this issue Apr 26, 2023 · 7 comments
Open

Facing issue when tiledesk server connect to mongo db #94

shikhil-gupta opened this issue Apr 26, 2023 · 7 comments

Comments

@shikhil-gupta
Copy link

shikhil-gupta commented Apr 26, 2023

Hi Tiledesk Team, I have followed these two steps only on Mac laptop,

curl https://raw.githubusercontent.com/Tiledesk/tiledesk-deployment/master/docker-compose/docker-compose.yml --output docker-compose.yml

docker-compose up

I am seeing following error consistently.

tiledesk-server  | (node:25) [MONGODB DRIVER] Warning: Current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor.
tiledesk-server  | (Use `node --trace-warnings ...` to show where the warning was created)
tiledesk-server  | (node:25) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
tiledesk-server  | (node:25) [MONGOOSE] DeprecationWarning: Mongoose: the `strictQuery` option will be switched back to `false` by default in Mongoose 7. Use `mongoose.set('strictQuery', false);` if you want to prepare for this change. Or use `mongoose.set('strictQuery', true);` to suppress this warning.
tiledesk-server  | Listening tiledesk-server ver:2.4.3 on port 3000
tiledesk-server  | error: Failed to connect to MongoDB on mongodb://mongo/tiledesk  failed to connect to server [mongo:27017] on first connect [MongoNetworkTimeoutError: connection timed out
tiledesk-server  |     at connectionFailureError (/usr/src/app/node_modules/mongodb/lib/core/connection/connect.js:362:14)
tiledesk-server  |     at Socket.<anonymous> (/usr/src/app/node_modules/mongodb/lib/core/connection/connect.js:330:16)
tiledesk-server  |     at Object.onceWrapper (node:events:627:28)
tiledesk-server  |     at Socket.emit (node:events:513:28)
tiledesk-server  |     at Socket._onTimeout (node:net:550:8)
tiledesk-server  |     at listOnTimeout (node:internal/timers:559:17)
tiledesk-server  |     at processTimers (node:internal/timers:502:7)] {"name":"MongoNetworkError","stack":"MongoNetworkError: failed to connect to server [mongo:27017] on first connect [MongoNetworkTimeoutError: connection timed out\n    at connectionFailureError (/usr/src/app/node_modules/mongodb/lib/core/connection/connect.js:362:14)\n    at Socket.<anonymous> (/usr/src/app/node_modules/mongodb/lib/core/connection/connect.js:330:16)\n    at Object.onceWrapper (node:events:627:28)\n    at Socket.emit (node:events:513:28)\n    at Socket._onTimeout (node:net:550:8)\n    at listOnTimeout (node:internal/timers:559:17)\n    at processTimers (node:internal/timers:502:7)]\n    at Pool.<anonymous> (/usr/src/app/node_modules/mongodb/lib/core/topologies/server.js:441:11)\n    at Pool.emit (node:events:513:28)\n    at /usr/src/app/node_modules/mongodb/lib/core/connection/pool.js:564:14\n    at /usr/src/app/node_modules/mongodb/lib/core/connection/pool.js:1000:11\n    at /usr/src/app/node_modules/mongodb/lib/core/connection/connect.js:32:7\n    at callback (/usr/src/app/node_modules/mongodb/lib/core/connection/connect.js:300:5)\n    at Socket.<anonymous> (/usr/src/app/node_modules/mongodb/lib/core/connection/connect.js:330:7)\n    at Object.onceWrapper (node:events:627:28)\n    at Socket.emit (node:events:513:28)\n    at Socket._onTimeout (node:net:550:8)\n    at listOnTimeout (node:internal/timers:559:17)\n    at processTimers (node:internal/timers:502:7)"}

@andrealeo83 @nicolan74 @sponzillo @JohnnyUB

@sponzillo
Copy link
Contributor

Please be more clear in your error description.

What distribution are you using?
Where are you installing/trying the Tiledesk software stack?
Did you modify the original stack components?

Please follow our community guidelines:

https://developer.tiledesk.com/support#i-need-help-but-its-not-so-urgent

@shikhil-gupta
Copy link
Author

Thanks for the response @sponzillo

I am running the docker installation and followed the following steps only

curl https://raw.githubusercontent.com/Tiledesk/tiledesk-deployment/master/docker-compose/docker-compose.yml --output docker-compose.yml

docker-compose up

And I am seeing tiledesk server keep restarting due to connection error with mongo.

@gab-95
Copy link
Contributor

gab-95 commented Apr 27, 2023

Hi @shikhil-gupta!!
Just one question: have you an arm64 ( apple chip) processor?

@shikhil-gupta
Copy link
Author

shikhil-gupta commented Apr 27, 2023

Hi @gab-95 Yes it is arm64

Screenshot 2023-04-27 at 10 44 18 PM

@gab-95
Copy link
Contributor

gab-95 commented Apr 28, 2023

Hi @shikhil-gupta!
unfortunately arm64 processors are not supported by tiledesk yet. we're working on it .

the valid alternative could be to use helm ( https://github.com/Tiledesk/tiledesk/blob/master/helm/README.md )

@shikhil-gupta
Copy link
Author

Hi @gab-95 I have tried Kubernetes and Helm, facing same issue that tiledesk-server pod is failed to connect with mongodb pod.

@shikhil-gupta
Copy link
Author

HI @gab-95 Could you please respond on why I am facing same issue with helm deployment also?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants