mongodump dose not work on remote host

148 views
Skip to first unread message

Zhen Cao

unread,
Mar 1, 2018, 1:24:13 AM3/1/18
to mongodb-user
hi,

i use command mongodump to backup mongodb instance:

mongodump -h 192.168.150.101 --username ira.cao --password ira.cao -d udisk -o temp

its output:
connected to: 192.168.150.101
2018-03-01T11:52:34.035+0800 DATABASE: udisk to temp/udisk

but temp/udisk is a empty dir

run the same command on host 192.168.150.101, it works well locally
its output:
2018-03-01T11:53:22.322+0800 writing udisk.t_lc_id_pool to
2018-03-01T11:53:22.322+0800 writing udisk.t_lc_info to
2018-03-01T11:53:22.322+0800 writing udisk.t_pg_info to
2018-03-01T11:53:22.322+0800 writing udisk.t_chunk_info to
2018-03-01T11:53:22.323+0800 done dumping udisk.t_lc_info (1 document)
2018-03-01T11:53:22.324+0800 writing udisk.t_gray_gate_info to
2018-03-01T11:53:22.324+0800 done dumping udisk.t_lc_id_pool (20 documents)
2018-03-01T11:53:22.324+0800 writing udisk.t_cluster_info to
2018-03-01T11:53:22.325+0800 done dumping udisk.t_cluster_info (1 document)
2018-03-01T11:53:22.325+0800 writing udisk.t_chunk_repair_task to
2018-03-01T11:53:22.325+0800 done dumping udisk.t_gray_gate_info (1 document)
2018-03-01T11:53:22.325+0800 writing udisk.t_chunk_repair_task_job to
2018-03-01T11:53:22.325+0800 done dumping udisk.t_chunk_repair_task (0 documents)
2018-03-01T11:53:22.325+0800 done dumping udisk.t_chunk_repair_task_job (0 documents)
2018-03-01T11:53:22.348+0800 done dumping udisk.t_pg_info (12 documents)
2018-03-01T11:53:22.351+0800 done dumping udisk.t_chunk_info (5 documents)

am i wrong somewhere? Thranks for your help !

Kevin Adistambha

unread,
Mar 4, 2018, 7:30:13 PM3/4/18
to mongodb-user

Hi

Did you see any error message? Could you try running mongodump with the --verbose option and see if there’s any error message? Please also post the complete output of the remote mongodump command.

It will also be helpful if you can provide your exact MongoDB version (e.g. 3.6.3) along with some relevant information about your deployment (e.g. is it a replica set, is it MongoDB Atlas, what OS are you using, etc.)

Best regards
Kevin

Zhen Cao

unread,
Mar 6, 2018, 10:41:44 PM3/6/18
to mongodb-user
Thanks!

mongo version:

db version v3.4.3
git version: f07437fb5a6cca07c10bafa78365456eb1d6d5e1
OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
allocator: tcmalloc
modules: enterprise
build environment:
    distmod: rhel62
    distarch: x86_64
    target_arch: x86_64

mongodump version of the remote host:
version 2.6.11

mongodump version of the local host:
mongodump version: r3.4.3
git version: f07437fb5a6cca07c10bafa78365456eb1d6d5e1
Go version: go1.7
   os: linux
   arch: amd64
   compiler: gc
OpenSSL version: OpenSSL 1.0.1e 11 Feb 2013

os:
mongod server: CentOS release 6.3 (Final)
mongodump : CentOS release 6.7 (Final)

mongodump with verbose option:

2018-03-07T11:28:15.475+0800 creating new connection to:192.168.150.101:27017
2018-03-07T11:28:15.475+0800 [ConnectBG] BackgroundJob starting: ConnectBG
2018-03-07T11:28:15.476+0800 connected to server 192.168.150.101:27017 (192.168.150.101)
2018-03-07T11:28:15.476+0800 connected connection!
connected to: 192.168.150.101
2018-03-07T11:28:15.478+0800 DATABASE: udisk to temp/udisk

mongodump of the remote host is not incompatible with mongod server?
i will search for this point

Thanks!
zhen Cao

在 2018年3月5日星期一 UTC+8上午8:30:13,Kevin Adistambha写道:
Reply all
Reply to author
Forward
0 new messages