Error connecting to db:27017 (172.18.0.3:27017) :: caused by :: Connection refused
dasaradhan opened this issue · 9 comments
MongoDB shell version v4.2.0
connecting to: mongodb://db:27017/admin?compressors=disabled&gssapiServiceName=mongodb
2019-10-17T05:43:53.180+0000 E QUERY [js] Error: couldn't connect to server db:27017, connection attempt failed: SocketException: Error connecting to db:27017 (172.18.0.3:27017) :: caused by :: Connection refused :
connect@src/mongo/shell/mongo.js:341:17
@(connect):2:6
2019-10-17T05:43:53.186+0000 F - [main] exception: connect failed
2019-10-17T05:43:53.186+0000 E - [main] exiting with code 1
Currently v4.x is not tested with Hygieia please downgrade version to 3.6 and retry
2019-10-17T12:25:18.498+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=29384c25b3c9
2019-10-17T12:25:18.499+0000 I CONTROL [initandlisten] db version v3.6.14
2019-10-17T12:25:18.499+0000 I CONTROL [initandlisten] git version: cbef87692475857c7ee6e764c8f5104b39c342a1
2019-10-17T12:25:18.499+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
2019-10-17T12:25:18.499+0000 I CONTROL [initandlisten] allocator: tcmalloc
2019-10-17T12:25:18.499+0000 I CONTROL [initandlisten] modules: none
2019-10-17T12:25:18.499+0000 I CONTROL [initandlisten] build environment:
2019-10-17T12:25:18.499+0000 I CONTROL [initandlisten] distmod: ubuntu1604
2019-10-17T12:25:18.499+0000 I CONTROL [initandlisten] distarch: x86_64
2019-10-17T12:25:18.499+0000 I CONTROL [initandlisten] target_arch: x86_64
2019-10-17T12:25:18.499+0000 I CONTROL [initandlisten] options: { net: { bindIpAll: true } }
2019-10-17T12:25:18.499+0000 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-10-17T12:25:18.499+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=256M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),compatibility=(release="3.0",require_max="3.0"),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2019-10-17T12:25:21.079+0000 E STORAGE [initandlisten] WiredTiger error (-31802) [1571315121:79464][1:0x7fc36743da40], connection: __log_open_verify, 1028: Version incompatibility detected: unsupported WiredTiger file version: this build requires a maximum version of 2, and the file is version 3: WT_ERROR: non-specific WiredTiger error
2019-10-17T12:25:21.081+0000 E - [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 486
2019-10-17T12:25:21.092+0000 I STORAGE [initandlisten] exception in initAndListen: Location28595: -31802: WT_ERROR: non-specific WiredTiger error, terminating
2019-10-17T12:25:21.092+0000 I NETWORK [initandlisten] shutdown: going to close listening sockets...
2019-10-17T12:25:21.092+0000 I NETWORK [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2019-10-17T12:25:21.092+0000 I CONTROL [initandlisten] now exiting
2019-10-17T12:25:21.092+0000 I CONTROL [initandlisten] shutting down with code:100
[ec2-user@ip-172-31-16-167 Hygieia]$
After degrading .I'm facing the following issue now
seems to be an issue bringing up mongo 3.6
can you check if the database is up?
Containers are going to exited state:
Error log for :db-setup_1
Error log for:mongo:3.6
Error log for hygieia collector:
Docker.compose.yml:
version: '3'
services:
db:
image: mongo:3.6
ports:
- "27017:27017"
volumes:
- "db-data:/data/db_1"
db-setup:
build: db
depends_on:
- db
api:
image: hygieia-api
depends_on:
- db
environment:
- AUTH_EXPIRATION_TIME= 36000
- AUTH_SECRET= secret
ui:
build: UI
image: hygieia-ui
stdin_open: true
tty: true
depends_on:
- api
ports:
- "8000:80"
hygieia-build-jenkins-collector:
build: hygieia-build-jenkins-collector
image: hygieia-build-jenkins-collector
depends_on:
- db-setup
volumes:
db-data:
certs:
docker-compose.override.yml:
version: '3'
services:
hygieia-build-jenkins-collector:
environment:
- JENKINS_CRON= 0 * * * * *
- JENKINS_MASTER= http://3.16.22.132:8080
- JENKINS_USERNAME= Dragon
- JENKINS_API_KEY= 11df470af887b7e5051d7d22a79943ae59
- MONGO_PORT= 27017
- MONGO_HOST= 27017
hygieia-build-jenkins-collector:
FROM openjdk:8-jre
VOLUME ["/hygieia/logs"]
RUN mkdir /hygieia/config
EXPOSE 8080
ENV PROP_FILE /hygieia/config/application.properties
RUN chmod -R a+x /hygieia
WORKDIR /hygieia
COPY target/*.jar /hygieia
COPY docker/properties-builder.sh /hygieia/
RUN sed -i -e 's/\r$//' ./properties-builder.sh
CMD ./properties-builder.sh &&
java -Djava.security.egd=file:/dev/./urandom -jar *.jar --spring.config.location=$PROP_FILE
after changing to mongo:3.6 below error in mongo:
can someone please help here
C:\Program Files\MongoDB\Server\4.2\bin>mongo mongo.exe
MongoDB shell version v4.2.5
connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
2020-04-15T22:22:07.772+0530 E QUERY [js] Error: couldn't connect to server 127.0.0.1:27017, connection attempt failed: NetworkTimeout: Error connecting to 127.0.0.1:27017 :: caused by :: Socket operation timed out :
connect@src/mongo/shell/mongo.js:341:17
@(connect):2:6
2020-04-15T22:22:07.775+0530 F - [main] exception: connect failed
2020-04-15T22:22:07.775+0530 E - [main] exiting with code 1
can someone help
2020-04-15T22:17:30.958+0530 I CONTROL [initandlisten]
2020-04-15T22:17:31.033+0530 I SHARDING [initandlisten] Marking collection local.system.replset as collection version:
2020-04-15T22:17:31.117+0530 I STORAGE [initandlisten] Flow Control is enabled on this deployment.
2020-04-15T22:17:31.117+0530 I SHARDING [initandlisten] Marking collection admin.system.roles as collection version:
2020-04-15T22:17:31.119+0530 I SHARDING [initandlisten] Marking collection admin.system.version as collection version:
2020-04-15T22:17:31.196+0530 I SHARDING [initandlisten] Marking collection local.startup_log as collection version:
2020-04-15T22:17:32.495+0530 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory 'C:/data/db/diagnostic.data'
2020-04-15T22:17:32.499+0530 I SHARDING [LogicalSessionCacheRefresh] Marking collection config.system.sessions as collection version:
2020-04-15T22:17:32.500+0530 I SHARDING [LogicalSessionCacheReap] Marking collection config.transactions as collection version:
2020-04-15T22:17:32.501+0530 I NETWORK [listener] Listening on 127.0.0.1
2020-04-15T22:17:32.503+0530 I NETWORK [listener] waiting for connections on port 27017
2020-04-15T22:17:33.003+0530 I SHARDING [ftdc] Marking collection local.oplog.rs as collection version:
mongodb is started