Home > database >  After start the mongo, mongo command not found
After start the mongo, mongo command not found

Time:09-18

I use the command/bin/mongo start later, the end tip is:
The NETWORK [initandlisten] waiting for connections on port 27017
And has been pause in the news,

I checked the relevant post, said the message, said the mongo server normal boot;
As long as the other one terminal, input $mongo can; But after I input the mongo command prompt command not found,

I am a Linux operating system, under the bin directory to find and found no mongo this command file, so prompt command not found.
And then searched the whole disk, did not find the mongo command file,

The following is my start directing a Log:
[oracle @ dbtest ~] $/bin/mongod
The 2019-08-23 T12: when. 706 + 0800 I CONTROL [main] Automatically disabling the TLS 1.0, to force - the enable TLS 1.0 specify - sslDisabledProtocols' none '
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] mongo starting: pid=41457 port=27017 dbpath=/data/db 64 - bit host=dbtest
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] db version v4.2.0
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] git version: a4b751dcf51dd249c5865812b390cfd1c0129c30
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1 e - fips 11 Feb 2013
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] allocator: tcmalloc
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] modules: none
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] build environment:
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] distmod: rhel70
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] distarch: x86_64
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] target_arch: x86_64
The 2019-08-23 T12: when. 710 + 0800 I CONTROL [initandlisten] options: {}
The 2019-08-23 T12: when. 712 + 0800 I STORAGE [initandlisten] Detected data files in/data/db created by the 'wiredTiger STORAGE engine, so setting the active STORAGE engine to' wiredTiger.
The 2019-08-23 T12: when. 712 + 0800 I STORAGE/initandlisten wiredtiger_open config: create, cache_size=2239 m, cache_overflow=(file_max=0 m), session_max=33000, eviction=(threads_min=4, threads_max=4), config_base=false, the statistics=(fast), log=(enabled=true, archive=true, path=journal, compressor=snappy), file_manager=(close_idle_time=100000), statistics_log=(wait=0), verbose=[recovery_progress checkpoint_progress],
"T12:2019-08-23. 500 + 0800 I STORAGE/initandlisten WiredTiger message (1566533417-500143) [41457:0 x7fe362b8bc00], TXN - recover: Recovering the log 4 through 5
"T12:2019-08-23. 574 + 0800 I STORAGE/initandlisten WiredTiger message (1566533417-574300) [41457:0 x7fe362b8bc00], TXN - recover: Recovering the log 5 through
The 2019-08-23 T12:10:17. 706 + 0800 I STORAGE/initandlisten WiredTiger message (1566533417-706771) [41457:0 x7fe362b8bc00], TXN - recover: the Main recovery loop: starting at 4/4480 to 5/256
"T12:2019-08-23. 707 + 0800 I STORAGE/initandlisten WiredTiger message (1566533417-707472) [41457:0 x7fe362b8bc00], TXN - recover: Recovering the log 4 through 5
"T12:2019-08-23. 826 + 0800 I STORAGE/initandlisten WiredTiger message (1566533417-826448) [41457:0 x7fe362b8bc00], TXN - recover: Recovering the log 5 through
"T12:2019-08-23. 911 + 0800 I STORAGE/initandlisten WiredTiger message (1566533417-911203) [41457:0 x7fe362b8bc00], TXN - recover: Set global recovery timestamp: (0, 0)
The 2019-08-23 T12:10:17. 955 + 0800 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp (0, 0)
The 2019-08-23 T12:10:17. 962 + 0800 I STORAGE/initandlisten Timestamp monitor starting
The 2019-08-23 T12:10:17. 967 + 0800 I CONTROL [initandlisten]
"T12:2019-08-23. 967 + 0800 I CONTROL [initandlisten] * * WARNING: Access CONTROL is not enabled for the database.
"T12:2019-08-23. 967 + 0800 I CONTROL [initandlisten] * * Read and write access to the data and the configuration is unrestricted.
The 2019-08-23 T12:10:17. 967 + 0800 I CONTROL [initandlisten]
"T12:2019-08-23. 967 + 0800 I CONTROL [initandlisten] * * WARNING: This server is bound to localhost.
"T12:2019-08-23. 967 + 0800 I CONTROL [initandlisten] * * Remote systems will be unable to connect to this server.
"T12:2019-08-23. 967 + 0800 I CONTROL [initandlisten] * * Start the server with - bind_ip & lt; address> To specify which IP
"T12:2019-08-23. 967 + 0800 I CONTROL [initandlisten] * * addresses it should serve responses from, or with - bind_ip_all to
"T12:2019-08-23. 967 + 0800 I CONTROL [initandlisten] * * bind to all interfaces. If this behaviors is desired, start the
"T12:2019-08-23. 967 + 0800 I CONTROL [initandlisten] * * server with - bind_ip 127.0.0.1 to disable this warning.
The 2019-08-23 T12:10:17. 967 + 0800 I CONTROL [initandlisten]
The 2019-08-23 T12:10:17. 967 + 0800 I CONTROL [initandlisten]
"T12:2019-08-23. 967 + 0800 I CONTROL [initandlisten] * * WARNING:/sys/kernel/mm/transparent_hugepage/enabled is' always'.
The 2019-08-23 T12:10:17. 967 + 0800 I CONTROL [initandlisten] * * We suggest setting it to 'never'
The 2019-08-23 T12:10:17. 967 + 0800 I CONTROL [initandlisten]
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
  • Related