Hexabot icon indicating copy to clipboard operation
Hexabot copied to clipboard

🤔 [ISSUE] - <container mongo is unhealthy error>

Open moaadzraig opened this issue 1 year ago • 12 comments

Description

i've installed ubunu 20.04, nodejs and docker and cloned the hexabox from github and followed the instructions mentioned in the installation guide of hexabox. everything worked. when i try to start hexabox using hexabot dev or start command, it starts pulling the container images and at the end it says "dependency failer to start: container mongo is unhealthy".

Error image:

Reproduction steps

1. sudo npm install -g hexabot-cli
2. hexabot create my-chatbot
3. cd my-chatbot/
4. npm i
5. hexabot init
6. sudo hexabot dev --services nlu,ollama

Logs

No response

Browsers

No response

OS

Linux

moaadzraig avatar Nov 02 '24 17:11 moaadzraig

err

moaadzraig avatar Nov 02 '24 17:11 moaadzraig

Hi @moaadzraig, thank you for reporting the issue. It will be helpful if you can provide the Hexabot Team with more details about the issue. For example, if you can share the container logs, OS version, node version ...

yassinedorbozgithub avatar Nov 02 '24 17:11 yassinedorbozgithub

hi yassine,

thanks for your quick response.

here's the details i got

node version: v20.18.0 npm version: 10.9.0 os: ubuntu 20.04.6 LTS

check two attachments one for mongo container created when running hexabot dev and one for hexabot start

looking forward to hear from you.

Regards.    

Sent from Outlookhttp://aka.ms/weboutlook


From: Yassine @.> Sent: Saturday, November 2, 2024 7:56 PM To: Hexastack/Hexabot @.> Cc: MOAAD ZRAIG @.>; Mention @.> Subject: Re: [Hexastack/Hexabot] 🤔 [ISSUE] - (Issue #310)

Hi @moaadzraighttps://github.com/moaadzraig, thank you for reporting the issue. It will be helpful if you can provide the Hexabot Team wih more details about the issue. For example, if you can share the container logs, OS version, node version ...

— Reply to this email directly, view it on GitHubhttps://github.com/Hexastack/Hexabot/issues/310#issuecomment-2453062795, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALJSWB37GUD53RNUDFL4D5TZ6UG4XAVCNFSM6AAAAABRB5LKACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGA3DENZZGU. You are receiving this because you were mentioned.Message ID: @.***>

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 25 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 25 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 25 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814 Could not connect to database using connectionString: @.***:27017/" /app/node_modules/mongodb/lib/sdam/topology.js:285 const timeoutError = new error_1.MongoServerSelectionError(Server selection timed out after ${serverSelectionTimeoutMS} ms, this.description); ^

MongoServerSelectionError: connect ECONNREFUSED 172.19.0.3:27017 at Timeout._onTimeout (/app/node_modules/mongodb/lib/sdam/topology.js:285:38) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { reason: TopologyDescription { type: 'Unknown', servers: Map(1) { 'mongo:27017' => ServerDescription { address: 'mongo:27017', type: 'Unknown', hosts: [], passives: [], arbiters: [], tags: {}, minWireVersion: 0, maxWireVersion: 0, roundTripTime: -1, lastUpdateTime: 13493369, lastWriteDate: 0, error: MongoNetworkError: connect ECONNREFUSED 172.19.0.3:27017 at connectionFailureError (/app/node_modules/mongodb/lib/cmap/connect.js:387:20) at Socket. (/app/node_modules/mongodb/lib/cmap/connect.js:310:22) at Object.onceWrapper (node:events:634:26) at Socket.emit (node:events:519:28) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { cause: Error: connect ECONNREFUSED 172.19.0.3:27017 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '172.19.0.3', port: 27017 }, [Symbol(errorLabels)]: Set(1) { 'ResetPool' } }, topologyVersion: null, setName: null, setVersion: null, electionId: null, logicalSessionTimeoutMinutes: null, primary: null, me: null, '$clusterTime': null } }, stale: false, compatible: true, heartbeatFrequencyMS: 10000, localThresholdMS: 15, setName: null, maxElectionId: null, maxSetVersion: null, commonWireVersion: 0, logicalSessionTimeoutMinutes: null }, code: undefined, [Symbol(errorLabels)]: Set(0) {} }

Node.js v20.13.1 /docker-entrypoint.sh: connect: Connection refused /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Connection refused Waiting for mongo:27017... Thu Oct 31 14:23:31 UTC 2024 retrying to connect to mongo:27017 (2/10) /docker-entrypoint.sh: connect: Connection refused /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Connection refused Thu Oct 31 14:23:32 UTC 2024 retrying to connect to mongo:27017 (3/10) /docker-entrypoint.sh: connect: Host is unreachable /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Host is unreachable Thu Oct 31 14:24:43 UTC 2024 retrying to connect to mongo:27017 (4/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:24:49 UTC 2024 retrying to connect to mongo:27017 (5/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:24:55 UTC 2024 retrying to connect to mongo:27017 (6/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:25:01 UTC 2024 retrying to connect to mongo:27017 (7/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:25:07 UTC 2024 retrying to connect to mongo:27017 (8/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:25:13 UTC 2024 retrying to connect to mongo:27017 (9/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:25:19 UTC 2024 retrying to connect to mongo:27017 (10/10) /docker-entrypoint.sh: connect: Host is unreachable /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Host is unreachable No custom config.js found, loading config.default.js Welcome to mongo-express 1.0.2

Could not connect to database using connectionString: @.***:27017/" /app/node_modules/mongodb/lib/sdam/topology.js:285 const timeoutError = new error_1.MongoServerSelectionError(Server selection timed out after ${serverSelectionTimeoutMS} ms, this.description); ^

MongoServerSelectionError: getaddrinfo EAI_AGAIN mongo at Timeout._onTimeout (/app/node_modules/mongodb/lib/sdam/topology.js:285:38) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { reason: TopologyDescription { type: 'Unknown', servers: Map(1) { 'mongo:27017' => ServerDescription { address: 'mongo:27017', type: 'Unknown', hosts: [], passives: [], arbiters: [], tags: {}, minWireVersion: 0, maxWireVersion: 0, roundTripTime: -1, lastUpdateTime: 13643795, lastWriteDate: 0, error: MongoNetworkError: getaddrinfo EAI_AGAIN mongo at connectionFailureError (/app/node_modules/mongodb/lib/cmap/connect.js:387:20) at Socket. (/app/node_modules/mongodb/lib/cmap/connect.js:310:22) at Object.onceWrapper (node:events:634:26) at Socket.emit (node:events:519:28) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { cause: Error: getaddrinfo EAI_AGAIN mongo at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) { errno: -3001, code: 'EAI_AGAIN', syscall: 'getaddrinfo', hostname: 'mongo' }, [Symbol(errorLabels)]: Set(1) { 'ResetPool' } }, topologyVersion: null, setName: null, setVersion: null, electionId: null, logicalSessionTimeoutMinutes: null, primary: null, me: null, '$clusterTime': null } }, stale: false, compatible: true, heartbeatFrequencyMS: 10000, localThresholdMS: 15, setName: null, maxElectionId: null, maxSetVersion: null, commonWireVersion: 0, logicalSessionTimeoutMinutes: null }, code: undefined, [Symbol(errorLabels)]: Set(0) {} }

Node.js v20.13.1 Waiting for mongo:27017... /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:26:06 UTC 2024 retrying to connect to mongo:27017 (2/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:26:12 UTC 2024 retrying to connect to mongo:27017 (3/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:26:18 UTC 2024 retrying to connect to mongo:27017 (4/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:26:24 UTC 2024 retrying to connect to mongo:27017 (5/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:26:30 UTC 2024 retrying to connect to mongo:27017 (6/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:26:36 UTC 2024 retrying to connect to mongo:27017 (7/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:26:42 UTC 2024 retrying to connect to mongo:27017 (8/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:26:48 UTC 2024 retrying to connect to mongo:27017 (9/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:26:54 UTC 2024 retrying to connect to mongo:27017 (10/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument No custom config.js found, loading config.default.js Welcome to mongo-express 1.0.2

Could not connect to database using connectionString: @.***:27017/" /app/node_modules/mongodb/lib/sdam/topology.js:285 const timeoutError = new error_1.MongoServerSelectionError(Server selection timed out after ${serverSelectionTimeoutMS} ms, this.description); ^

MongoServerSelectionError: getaddrinfo EAI_AGAIN mongo at Timeout._onTimeout (/app/node_modules/mongodb/lib/sdam/topology.js:285:38) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { reason: TopologyDescription { type: 'Unknown', servers: Map(1) { 'mongo:27017' => ServerDescription { address: 'mongo:27017', type: 'Unknown', hosts: [], passives: [], arbiters: [], tags: {}, minWireVersion: 0, maxWireVersion: 0, roundTripTime: -1, lastUpdateTime: 13738367, lastWriteDate: 0, error: MongoNetworkError: getaddrinfo EAI_AGAIN mongo at connectionFailureError (/app/node_modules/mongodb/lib/cmap/connect.js:387:20) at Socket. (/app/node_modules/mongodb/lib/cmap/connect.js:310:22) at Object.onceWrapper (node:events:634:26) at Socket.emit (node:events:519:28) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { cause: Error: getaddrinfo EAI_AGAIN mongo at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) { errno: -3001, code: 'EAI_AGAIN', syscall: 'getaddrinfo', hostname: 'mongo' }, [Symbol(errorLabels)]: Set(1) { 'ResetPool' } }, topologyVersion: null, setName: null, setVersion: null, electionId: null, logicalSessionTimeoutMinutes: null, primary: null, me: null, '$clusterTime': null } }, stale: false, compatible: true, heartbeatFrequencyMS: 10000, localThresholdMS: 15, setName: null, maxElectionId: null, maxSetVersion: null, commonWireVersion: 0, logicalSessionTimeoutMinutes: null }, code: undefined, [Symbol(errorLabels)]: Set(0) {} }

Node.js v20.13.1 Waiting for mongo:27017... /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:27:41 UTC 2024 retrying to connect to mongo:27017 (2/10) /docker-entrypoint.sh: line 15: mongo: Try again /docker-entrypoint.sh: line 15: /dev/tcp/mongo/27017: Invalid argument Thu Oct 31 14:27:47 UTC 2024 retrying to connect to mongo:27017 (3/10)

moaadzraig avatar Nov 02 '24 18:11 moaadzraig

Hello @moaadzraig Can you do docker logs -f mongo ? Do you have another mongo database installed on your machine or any other service that is using the port "27017" ?

marrouchi avatar Nov 02 '24 18:11 marrouchi

hello,

when i do docker logs -f mongo i get error log as in the attached file.

i will try a fresh ubuntu 20.04 installation and follow the steps again and let you know.

Regards,

Sent from Outlookhttp://aka.ms/weboutlook


From: Med Marrouchi @.> Sent: Saturday, November 2, 2024 8:37 PM To: Hexastack/Hexabot @.> Cc: MOAAD ZRAIG @.>; Mention @.> Subject: Re: [Hexastack/Hexabot] 🤔 [ISSUE] - (Issue #310)

Hello @moaadzraighttps://github.com/moaadzraig Can you do docker logs -f mongo ? Do you have another mongo database installed on your machine or any other service that is using the port "27017" ?

— Reply to this email directly, view it on GitHubhttps://github.com/Hexastack/Hexabot/issues/310#issuecomment-2453088695, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALJSWB3MMTJCLO6BY6V4VU3Z6ULV3AVCNFSM6AAAAABRB5LKACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGA4DQNRZGU. You are receiving this because you were mentioned.Message ID: @.***>

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 25 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 25 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 25 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

/usr/local/bin/docker-entrypoint.sh: line 416: 24 Illegal instruction (core dumped) "${mongodHackedArgs[@]}" --fork

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

moaadzraig avatar Nov 02 '24 18:11 moaadzraig

As it shows in the logs : WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!

Can I ask what CPU are you using ?

marrouchi avatar Nov 02 '24 19:11 marrouchi

hi,

i tried with another pc that has virtualbox and used the same iso image and it's starting fine but system is displaying error "network error please try again later" while browsing the web.

check attached.

Sent from Outlookhttp://aka.ms/weboutlook


From: Med Marrouchi @.> Sent: Saturday, November 2, 2024 9:34 PM To: Hexastack/Hexabot @.> Cc: MOAAD ZRAIG @.>; Mention @.> Subject: Re: [Hexastack/Hexabot] 🤔 [ISSUE] - (Issue #310)

As it shows in the logs : WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!

Can I ask what CPU are you using ?

— Reply to this email directly, view it on GitHubhttps://github.com/Hexastack/Hexabot/issues/310#issuecomment-2453105610, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALJSWBY3PXZ7JINJRCC33JLZ6USNRAVCNFSM6AAAAABRB5LKACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGEYDKNRRGA. You are receiving this because you were mentioned.Message ID: @.***>

moaadzraig avatar Nov 02 '24 22:11 moaadzraig

I cannot see the image you attachment, I guess you replied by email. Can you rather reply in github to upload the image?

Otherwise, if you are on Windows, I would advise to install Docker + WSL rather than using VirtualBox.

marrouchi avatar Nov 03 '24 09:11 marrouchi

img1 img2

moaadzraig avatar Nov 03 '24 09:11 moaadzraig

Hello @moaadzraig Any update on this issue? Were you able to resolve it?

marrouchi avatar Nov 30 '24 10:11 marrouchi

I am also getting same network error. is there a fix?

deepakitkar avatar Dec 19 '24 12:12 deepakitkar

Hi @deepakitkar, sorry for the delay Can you check if this command resolve the issue docker system prune

yassinedorbozgithub avatar Sep 16 '25 07:09 yassinedorbozgithub