Validate_box not found

Hi @Rohit_84793,

You can refer to the following post to destroy vagrant environment:

To setup the vagrant environment from scratch in Windows, you can refer to VirtualBox&Vagrant_Windows doc in the Handouts section of the Lecture: Setting up the Vagrant Environment.

Please let me know, if you have any questions.

Thanks,
Sonali

C:\Users\Rohit\m103\m103-vagrant-env>vagrant up --provision

After this getting below error:—

mongod-m103: Waiting for machine to boot. This may take a few minutes…
mongod-m103: SSH address: 127.0.0.1:2222
mongod-m103: SSH username: vagrant
mongod-m103: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured (“config.vm.boot_timeout” value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you’re using a custom box, make sure that networking is properly
working and you’re able to connect to the machine. It is a common
problem that networking isn’t setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout (“config.vm.boot_timeout”) value.

C:\Users\Rohit\m103\m103-vagrant-env>vagrant up --provision

After this getting below error:—

mongod-m103: Waiting for machine to boot. This may take a few minutes…
mongod-m103: SSH address: 127.0.0.1:2222
mongod-m103: SSH username: vagrant
mongod-m103: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured (“config.vm.boot_timeout” value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you’re using a custom box, make sure that networking is properly
working and you’re able to connect to the machine. It is a common
problem that networking isn’t setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout (“config.vm.boot_timeout”) value.

Reply

again running same command:-

C:\Users\Rohit\m103\m103-vagrant-env>vagrant up --provision
Bringing machine ‘mongod-m103’ up with ‘virtualbox’ provider…
==> mongod-m103: Running provisioner: shell…
An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating

This worked to me:

File to edit: provision-mongod

Replace keyserver.ubuntu.com by public ip address:

sudo apt-key adv --keyserver 192.146.137.98 --recv …

1 Like

Hi @Rohit_84793,

I apologise for the late reply.
However, It is Great!! As I can check the issue has been resolved for you.

Can you please share what solution worked for you?

Kind Regards,
Sonali

validate_box not found.
Can you help me to fix this issue

Dear MongoDB Uni,

I was excited about starting the M103 course, however I am now writing to express my absolute disappointment in the courses that MongoDB provides.

Originally, I attempted to complete the M001 course, but due to issues with incorrect information for installation I deferred because the coursework deadlines are inflexible. I sat and completed the course at a later date.

Believing that installing environments was dealt with, I registered for another course. Again, I have invested more than double the hours required for the course for installing environments. The multiple links for the same environment are different, which was only discovered by downloading all of them. As my expectation is to learn the content of the course, which has not been possible with incorrect information and a lack of an environment being installed, I would like to cancel my registration.

Maybe, MongoDB will eventually provide correct installation information with adequate time, prior to the commencement of the course.

1 Like

Hi @Akhil_Kumar_Reddy_68114,

Can you please share the screenshot of the error that you are getting so that I can understand the issue better and help you with the appropriate solution?

Thanks,
Muskan
Curriculum Support Engineer

The same error with the validation commands…

image

I did use the:
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 2930ADAE8CAF5059EE73BB4B58712A2291FA4AD5

It went with no errors, much better than the previous one, but still no validation commands are available.

Hi @Ikrom_61557,

You probably need to download the validation scripts.
Please go through the following thread and follow the mentioned steps to do the same:

Please get back if the issue still persists.

Thanks,
Muskan
Curriculum Support Engineer

This command “download_validators” did not work even after a couple of provisions…
Downloaded the files (from here: Validation_BIn_Files) => moved to the VM => added to the PATH variable in .profile => and now it’s ok.

1 Like