Problem running vagrant up --provision

I need help, when I ran “vagrant up --provision”, I got the following error:

mongod-m103: + echo '    m103 m103'
mongod-m103: + update_repo
mongod-m103: + echo 'Install MongoDB Enterprise Repository'
mongod-m103: Install MongoDB Enterprise Repository
mongod-m103: + echo 'deb [ arch=amd64 ] trusty/mongodb-enterprise/3.6 multiverse'
mongod-m103: + sudo tee /etc/apt/sources.list.d/mongodb-enterprise.list
mongod-m103: deb [ arch=amd64 ] trusty/mongodb-enterprise/3.6 multiverse
mongod-m103: + sudo apt-key adv --keyserver --recv 0C49F3730359A14518585931BC711F9BA15703C6
mongod-m103: Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.f9LapUNxMU --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/ubuntu-advantage-esm-infra-trusty.gpg --keyserver --recv 0C49F3730359A14518585931BC711F9BA15703C6
mongod-m103: gpg:
mongod-m103: requesting key A15703C6 from hkp server
mongod-m103: gpg: keyserver timed out
mongod-m103: gpg: keyserver receive failed: keyserver error

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Please check this link

GPG: Keyserver timed out

Hi @Yook_20450,

In addition to @Ramachandra_37567,

If changing the network does not help then please refer this post and make the suggested modification to your provision-mongod file and see if that helps.

Shubham Ranjan
Curriculum Support Engineer

This is resolved now.
It was related to network/firewall issue.
I remove my laptop from the company network, login using public wi-fi and I was able to complete the step w/o error.
Thanks !


Hi @Yook_20450,

I’m glad your issue got resolved. If you have any other query then please feel free to get back to us.

Happy Learning!

Shubham Ranjan
Curriculum Support Engineer