Hanging on "Clearing any previously set network interfaces"

MongoDB University M310: MongoDB Security
#1

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\ARUL>cd C:\Users\ARUL\Desktop\MongoDB_Course_Material\M310

C:\Users\ARUL\Desktop\MongoDB_Course_Material\M310>vagrant up
Bringing machine ‘database’ up with ‘virtualbox’ provider…
Bringing machine ‘infrastructure’ up with ‘virtualbox’ provider…
==> database: Checking if box ‘ubuntu/trusty64’ version ‘20190429.0.1’ is up to
date…
==> database: Fixed port collision for 22 => 2222. Now on port 2200.
==> database: Clearing any previously set network interfaces… (Hanging)

#2

Hi @ARULAMUTHAN_97759,

In this course, you have two boxes (database and infrastructure) to provision. Suggest you do it one by one:

  1. First you need to destroy any M310 boxes that were started up:
    i. Run vagrant destroy database, then type y and hit Enter
    i. Run vagrant destroy infrastructure, then type y and hit Enter
  2. Create the machines:
    i. vagrant up database
    ii. vagrant up infrastructure
#3

Hi @ARULAMUTHAN_97759,

If the problem still persists for you, please share the versions of virtualbox and vagrant. You can find the same using the following command in the terminal:

vboxmanage --version
vagrant --version

Thanks,
Sonali

#4

hi,

Now I am grrting below error

.
database: WARNING: The following packages cannot be authenticated!
database: mongodb-enterprise-shell mongodb-enterprise-server mongodb-enter
prise-mongos
database: mongodb-enterprise-tools mongodb-enterprise
database: E
database: :
database: There are problems and -y was used without --force-yes
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.

C:\Users\ARUL\Desktop\MongoDB_Course_Material\M310>vagrant ssh database
Welcome to Ubuntu 14.04.6 LTS (GNU/Linux 3.13.0-170-generic x86_64)

#5

Ok, that’s progress. For this specific error, here’s the fix: