Database: There are problems and -y was used without --force-yes

after executed “vagrant up”, i will get the errors following:
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.

– what can i do?

Hi, I think this happen to people quite often, just add the suggested flag into the vagrant configuration file. Open it in a text editor and modify that:

function install_mongod(){
echo “Install MongoDB Enterprise”
apt-get install -y –force-yes mongodb-enterprise
sh -c “killall mongod; true”
echo “Set LC_ALL=C to .profile”
echo “export LC_ALL=C” >> /home/vagrant/.profile
}

Note this is from my “random” vagrant from some course here - just adjust that flag, other is just to help you to locate, I do not say that it has to be exactly the same

edit : two “-” before the flag, this page formatting issue…

2 Likes

:hugs: above changed can solve my problem, thank you! but this time is “infrastructure” turn, it appear following:
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:19 7:44:12 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:20 7:44:11 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:21 7:44:10 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:22 7:44:09 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:23 7:44:08 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:24 7:44:07 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:25 7:44:06 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:26 7:44:05 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:27 7:44:04 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:28 7:44:03 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:29 7:44:02 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:30 7:44:01 0
12 1734k 12 213k 0 0 56 0 8:48:31 1:04:31 7:44:00 0


over 3 hours, it’s done? (i guess not) what should i do?

Not sure never experienced that, maybe some issue with downloading/updating? I would destroy (really command) and try it again.

Let me know if provisioning / destroying vagrant solved the issue.

Kanika

i found the content is come from following script line in “provision-infrastructure”:
curl “https://bootstrap.pypa.io/get-pip.py” -o “get-pip.py”

i try to ssh infrastructure, and run the rest of script manual (should be use sudo prefix or have permission problem)

Thank you all!