here is the log at startup
2018-04-17 06:13:59 InitParameterInteraction: parameter interaction: -connect set -> setting -dnsseed=0
2018-04-17 06:13:59 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-04-17 06:13:59 Assuming ancestors of block 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0 have valid signatures.
2018-04-17 06:13:59 Setting nMinimumChainWork=000000000000000000000000000000000000000000f91c579d57cad4bc5278cc
2018-04-17 06:13:59 Using the "sse4" SHA256 implementation
2018-04-17 06:13:59 Using RdRand as an additional entropy source
2018-04-17 06:13:59 Default data directory /root/.bitcoin
2018-04-17 06:13:59 Using data directory /root/.bitcoin/
2018-04-17 06:13:59 Using config file /root/.bitcoin/bitcoin.conf
2018-04-17 06:13:59 Using at most 125 automatic connections (1024 file descriptors available)
2018-04-17 06:13:59 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-04-17 06:13:59 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-04-17 06:13:59 Using 2 threads for script verification
2018-04-17 06:13:59 scheduler thread start
2018-04-17 06:13:59 Binding RPC on address 0.0.0.0 port 8332 failed.
2018-04-17 06:13:59 HTTP: creating work queue of depth 16
2018-04-17 06:13:59 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with
rpcauth. Please see share/rpcuser for rpcauth auth generation.
2018-04-17 06:13:59 HTTP: starting 4 worker threads
2018-04-17 06:13:59 Using wallet directory /root/.bitcoin/wallets
2018-04-17 06:13:59 init message: Verifying wallet(s)...in the log
2018-04-17 06:13:59 Binding RPC on address 0.0.0.0 port 8332 failed.failed to bind RPC? Does it mean that the RPC service is not up and cannot be provided?