Validate_lab_launch_mongod: command not found

I am very frustrated trying to get this to work. Can someone please help address this error. My validation directory seems to be empty. All labs so far have been working fine.

vagrant@m103:/var/m103/validation$ ll
total 8
drwxr-xr-x 2 root root 4096 Apr 13 02:43 ./
drwxr-xr-x 3 root root 4096 Apr 13 02:43 …/
vagrant@m103:/var/m103/validation$ mongo -u m103-admin -p m103-pass --authenticationDatabase admin --port 27000
MongoDB shell version v3.6.12
connecting to: mongodb://
Implicit session: session { “id” : UUID(“f2952521-d2d9-4830-8f18-34b0045cc564”) }
MongoDB server version: 3.6.12
Server has startup warnings:
2019-04-13T04:12:11.960+0000 I STORAGE [initandlisten]
2019-04-13T04:12:11.960+0000 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2019-04-13T04:12:11.960+0000 I STORAGE [initandlisten] ** See
2019-04-13T04:12:12.677+0000 I CONTROL [initandlisten]
2019-04-13T04:12:12.677+0000 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database.
2019-04-13T04:12:12.678+0000 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted.
2019-04-13T04:12:12.678+0000 I CONTROL [initandlisten]
MongoDB Enterprise >
MongoDB Enterprise > show dbs
admin 0.000GB
config 0.000GB
local 0.000GB
MongoDB Enterprise >

May be your vagrant provisioning did not happen properly
Try to search for that file
or is it attached in your course handouts

  1. I do not recall the directory containing the validation scripts being in /var.
  2. The script name in the title of this post has an uppercase V. It should be lowercase v. But the uppercase might be done automatically by this blog software.
  3. You can always look for the script with the following command:
find / -name validate_lab_launch_mongod

Thank you steevej for helping me here… Find command is not working. Seems like permissions issue. hmm… Any other pointers? Do MongoDB University folks help with such roadblocks?

I did enter lowercase ‘v’

vagrant@m103:~$ validate_box
validate_box: command not found

vagrant@m103:~ id uid=1000(vagrant) gid=1000(vagrant) groups=1000(vagrant) vagrant@m103:~ find / -name validate_lab_launch_mongod
find: /proc/tty/driver': Permission denied find:/proc/1/task/1/fd’: Permission denied
find: /proc/1/task/1/fdinfo': Permission denied find:/proc/1/task/1/ns’: Permission denied
find: /proc/1/fd': Permission denied find:/proc/1/map_files’: Permission denied
find: /proc/1/fdinfo': Permission denied find:/proc/1/ns’: Permission denied
find: /proc/2/task/2/fd': Permission denied find:/proc/2/task/2/fdinfo’: Permission denied

Thank you Ramachandran. Vagrant provisioning output was long. It did end oddly with a curl command failure which I ran manually after it. The course material does not indicate what a successful install would look like, so I have nothing to compare against, unless I am blatantly missing something here.

Here is the output. Any suggestions?

C02WT3B1HTD6MBP:/Users/axc08/university/m103/m103-vagrant-env> vagrant up --provision
Bringing machine ‘mongod-m103’ up with ‘virtualbox’ provider…
==> mongod-m103: Running provisioner: shell…
mongod-m103: Running: /var/folders/cc/ys93h08j16j7jz10h73j2l7c0000gn/T/vagrant-shell20190413-19937-eybuj1
mongod-m103: + config
mongod-m103: + sudo su
mongod-m103: + echo -e never
mongod-m103: + echo -e never
mongod-m103: + echo manual
mongod-m103: + sudo tee /etc/init/mongod.override
mongod-m103: manual
mongod-m103: + ip_config
mongod-m103: ++ ifconfig
mongod-m103: ++ tail -1
mongod-m103: ++ awk ‘{ print $1}’
mongod-m103: ++ grep -v
mongod-m103: ++ cut -d: -f2
mongod-m103: ++ grep ‘inet addr:’
mongod-m103: + export CLIENT_IP_ADDR=
mongod-m103: + CLIENT_IP_ADDR=
mongod-m103: ++ hostname
mongod-m103: + export CLIENT_FQDN=m103
mongod-m103: + CLIENT_FQDN=m103
mongod-m103: ++ hostname
mongod-m103: ++ tr ‘[:upper:]’ ‘[:lower:]’
mongod-m103: ++ cut -d. -f 1
mongod-m103: + export CLIENT_NAME=m103
mongod-m103: + CLIENT_NAME=m103
mongod-m103: + echo ‘Configuring /etc/hosts …’
mongod-m103: Configuring /etc/hosts …
mongod-m103: + echo ‘ localhost localhost.localdomain localhost4 localhost4.localdomain4 ’
mongod-m103: + echo ‘::1 localhost localhost.localdomain localhost6 localhost6.localdomain6’
mongod-m103: + echo ‘fe00::0 ip6-localnet’
mongod-m103: + echo ‘ff00::0 ip6-mcastprefix’
mongod-m103: + echo ‘ff02::1 ip6-allnodes’
mongod-m103: + echo ‘ff02::2 ip6-allrouters’
mongod-m103: + echo ‘ff02::3 ip6-allhosts’
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 hkp:// --recv 2930ADAE8CAF5059EE73BB4B58712A2291FA4AD5
mongod-m103: Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.O6YRhgJAex --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver hkp:// --recv 2930ADAE8CAF5059EE73BB4B58712A2291FA4AD5
mongod-m103: gpg:
mongod-m103: requesting key 91FA4AD5 from hkp server
mongod-m103: gpg:
mongod-m103: key 91FA4AD5: “MongoDB 3.6 Release Signing Key” not changed
mongod-m103: gpg:
mongod-m103: Total number processed: 1
mongod-m103: gpg:
mongod-m103: unchanged: 1
mongod-m103: + echo ‘Update Repositories’
mongod-m103: Update Repositories
mongod-m103: + sudo apt-get update -y
mongod-m103: Ign trusty/mongodb-enterprise/3.6 InRelease
mongod-m103: Hit trusty/mongodb-enterprise/3.6 Release.gpg
mongod-m103: Hit trusty/mongodb-enterprise/3.6 Release
mongod-m103: Hit trusty-security InRelease
mongod-m103: Ign trusty InRelease
mongod-m103: Hit trusty/mongodb-enterprise/3.6/multiverse amd64 Packages
mongod-m103: Hit trusty-security/main Sources
mongod-m103: Hit trusty-updates InRelease
mongod-m103: Hit trusty-security/universe Sources
mongod-m103: Hit trusty-backports InRelease
mongod-m103: Hit trusty-security/main amd64 Packages
mongod-m103: Hit trusty Release.gpg
mongod-m103: Hit trusty-security/universe amd64 Packages
mongod-m103: Hit trusty-updates/main Sources
mongod-m103: Hit trusty-security/main Translation-en
mongod-m103: Hit trusty-updates/restricted Sources
mongod-m103: Hit trusty-security/universe Translation-en
mongod-m103: Hit trusty-updates/universe Sources
mongod-m103: Ign trusty/mongodb-enterprise/3.6/multiverse Translation-en_US
mongod-m103: Ign trusty/mongodb-enterprise/3.6/multiverse Translation-en
mongod-m103: Hit trusty-updates/multiverse Sources
mongod-m103: Hit trusty-updates/main amd64 Packages
mongod-m103: Hit trusty-updates/restricted amd64 Packages
mongod-m103: Hit trusty-updates/universe amd64 Packages
mongod-m103: Hit trusty-updates/multiverse amd64 Packages
mongod-m103: Hit trusty-updates/main Translation-en
mongod-m103: Hit trusty-updates/multiverse Translation-en
mongod-m103: Hit trusty-updates/restricted Translation-en
mongod-m103: Hit trusty-updates/universe Translation-en
mongod-m103: Hit trusty-backports/main Sources
mongod-m103: Hit trusty-backports/restricted Sources
mongod-m103: Hit trusty-backports/universe Sources
mongod-m103: Hit trusty-backports/multiverse Sources
mongod-m103: Hit trusty-backports/main amd64 Packages
mongod-m103: Hit trusty-backports/restricted amd64 Packages
mongod-m103: Hit trusty-backports/universe amd64 Packages
mongod-m103: Hit trusty-backports/multiverse amd64 Packages
mongod-m103: Hit trusty-backports/main Translation-en
mongod-m103: Hit trusty-backports/multiverse Translation-en
mongod-m103: Hit trusty-backports/restricted Translation-en
mongod-m103: Hit trusty-backports/universe Translation-en
mongod-m103: Hit trusty Release
mongod-m103: Hit trusty/main Sources
mongod-m103: Hit trusty/restricted Sources
mongod-m103: Hit trusty/universe Sources
mongod-m103: Hit trusty/multiverse Sources
mongod-m103: Hit trusty/main amd64 Packages
mongod-m103: Hit trusty/restricted amd64 Packages
mongod-m103: Hit trusty/universe amd64 Packages
mongod-m103: Hit trusty/multiverse amd64 Packages
mongod-m103: Hit trusty/main Translation-en
mongod-m103: Hit trusty/multiverse Translation-en
mongod-m103: Hit trusty/restricted Translation-en
mongod-m103: Hit trusty/universe Translation-en
mongod-m103: Ign trusty/main Translation-en_US
mongod-m103: Ign trusty/multiverse Translation-en_US
mongod-m103: Ign trusty/restricted Translation-en_US
mongod-m103: Ign trusty/universe Translation-en_US
mongod-m103: Reading package lists…
mongod-m103: + echo ‘Installing MongoDB Enterprise Dependencies’
mongod-m103: Installing MongoDB Enterprise Dependencies
mongod-m103: + sudo apt-get install -y libgssapi-krb5-2 libsasl2-2 libssl1.0.0 libstdc++6 snmp
mongod-m103: Reading package lists…
mongod-m103: Building dependency tree…
mongod-m103: Reading state information…
mongod-m103: libsasl2-2 is already the newest version.
mongod-m103: libgssapi-krb5-2 is already the newest version.
mongod-m103: libssl1.0.0 is already the newest version.
mongod-m103: libstdc++6 is already the newest version.
mongod-m103: snmp is already the newest version.
mongod-m103: 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
mongod-m103: + install_mongod
mongod-m103: + echo ‘Install MongoDB Enterprise’
mongod-m103: Install MongoDB Enterprise
mongod-m103: + sudo apt-get install --force-yes -y mongodb-enterprise
mongod-m103: Reading package lists…
mongod-m103: Building dependency tree…
mongod-m103: Reading state information…
mongod-m103: mongodb-enterprise is already the newest version.
mongod-m103: 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
mongod-m103: + mkdir -p /var/log/mongodb/
mongod-m103: + sudo chown vagrant:vagrant -R /var/log/mongodb
mongod-m103: + sudo chown vagrant:vagrant -R /var/lib/mongodb
mongod-m103: + sudo echo ’
mongod-m103: security:
mongod-m103: + sudo tee -a /etc/mongod.conf
mongod-m103: authorization: enabled’
mongod-m103: security:
mongod-m103: authorization: enabled
mongod-m103: + echo ‘Done installing MongoDB Enterprise’
mongod-m103: Done installing MongoDB Enterprise
mongod-m103: + user_setup
mongod-m103: + sudo sh -c ‘killall mongod; true’
mongod-m103: mongod: no process found
mongod-m103: + sudo mkdir -p /data
mongod-m103: + sudo chmod -R 777 /data
mongod-m103: + mkdir -p /data/db
mongod-m103: + mkdir -p /home/vagrant/data
mongod-m103: + chmod -R 777 /home/vagrant/data
mongod-m103: + chown -R vagrant:vagrant /home/vagrant/data
mongod-m103: + mkdir -p /var/m103/validation
mongod-m103: + echo ‘Set LC_ALL=C to .profile’
mongod-m103: Set LC_ALL=C to .profile
mongod-m103: + sudo echo ‘export LC_ALL=C’
mongod-m103: + sudo echo PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/var/m103/validation
mongod-m103: + data_path
mongod-m103: + sudo mkdir -p /data
mongod-m103: + sudo chown -R vagrant:vagrant /data
mongod-m103: + install_pymongo
mongod-m103: + sudo apt-get -y install python-pip
mongod-m103: Reading package lists…
mongod-m103: Building dependency tree…
mongod-m103: Reading state information…
mongod-m103: python-pip is already the newest version.
mongod-m103: 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
mongod-m103: + sudo pip install pymongo
mongod-m103: Requirement already satisfied (use --upgrade to upgrade): pymongo in /usr/local/lib/python2.7/dist-packages
mongod-m103: Cleaning up…
mongod-m103: + download_dataset
mongod-m103: + echo ‘Downloading Dataset’
mongod-m103: Downloading Dataset
mongod-m103: + curl -s -o products.json.tgz
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.
C02WT3B1HTD6MBP:/Users/axc08/university/m103/m103-vagrant-env> curl -s -o products.json.tgz
C02WT3B1HTD6MBP:/Users/axc08/university/m103/m103-vagrant-env> ls -ltr
total 22696
-rw-r–r--@ 1 axc08 staff 811 Apr 12 22:08 Vagrantfile
-rw-r–r--@ 1 axc08 staff 4672 Apr 12 22:38 provision-mongod.orig
-rw-r–r--@ 1 axc08 staff 4783 Apr 12 22:39 provision-mongod
drwxr-xr-x 2 axc08 staff 64 Apr 12 22:42 shared
drwxr-xr-x 2 axc08 staff 64 Apr 12 22:42 dataset
-rw-r–r-- 1 axc08 staff 11314280 Apr 13 01:36 products.json.tgz
C02WT3B1HTD6MBP:/Users/axc08/university/m103/m103-vagrant-env> vagrant ssh
Welcome to Ubuntu 14.04.6 LTS (GNU/Linux 3.13.0-168-generic x86_64)

System information as of Sat Apr 13 05:36:06 UTC 2019

System load: 0.01 Processes: 84
Usage of /: 4.9% of 39.34GB Users logged in: 0
Memory usage: 8% IP address for eth0:
Swap usage: 0% IP address for eth1:

Graph this data and manage this system at:

New release ‘16.04.6 LTS’ available.
Run ‘do-release-upgrade’ to upgrade to it.

Last login: Sat Apr 13 05:32:09 2019 from

Thanks a lot.

Your find command did not fail
It just failing on those files on which you don’t have read permissions
In your find output do you see this particular command?

Try to stop and start vagrant
In my case i can see validation files when vagrant is started as below

mongod-m103: Downloading Validation Scripts
mongod-m103: + curl -s -o m103_validation.tgz
mongod-m103: + tar -xzvf m103_validation.tgz -C /var/m103/validation
mongod-m103: ./._validate_lab_change_dbpath
mongod-m103: validate_lab_change_dbpath

I searched through the entire screen output, no where do i see “Downloading Validation Scripts”.

Replied to you on the other thread

Thanks a ton :pray: