Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: JDK not getting installed ? #4

Open
Tusharsb opened this issue Mar 10, 2016 · 1 comment
Open

Bug: JDK not getting installed ? #4

Tusharsb opened this issue Mar 10, 2016 · 1 comment

Comments

@Tusharsb
Copy link

When I do vagrant up i get the following error

Running Puppet with init.pp...
Notice: /Stage[main]/Elasticsearch/Package[elasticsearch]/ensure: created
Notice: /Stage[main]/Elasticsearch/File[/etc/yum.repos.d/elasticsearch.repo]/ensure: defined content as '{md5}da2fef5be7c8b7eef741e3a7652620ef'
Notice: /Stage[main]/Epel/Package[epel-release]/ensure: created
Error: Could not start Service[elasticsearch]: Execution of '/sbin/service elasticsearch start' returned 1: 
Error: /Stage[main]/Elasticsearch/Service[elasticsearch]/ensure: change from stopped to running failed: Could not start Service[elasticsearch]: Execution of '/sbin/service elasticsearch start' returned 1: 
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install java-1.7.0-openjdk-devel.x86_64' returned 1: Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again

Error: /Stage[main]/Base/Package[java-1.7.0-openjdk-devel.x86_64]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install java-1.7.0-openjdk-devel.x86_64' returned 1: Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again

Notice: /Stage[main]/Base/Service[iptables]/ensure: ensure changed 'running' to 'stopped'

Would a mix of http://stackoverflow.com/a/27667111/3143538 and http://stackoverflow.com/a/10855977/3143538 work? I dont know - but still i tried to stich these solutions together - but they didnt worked either. Any clues on what am I doing wrong ?

@Tusharsb
Copy link
Author

@duffj are you sure your vagrant instance is also running centos-64-x64-vbox4210 as defined in Vagrantfile? Because I am running into a few more bugs than just this one I am suspecting your Vagrant VM might be using a more up to date CentOS version than this one. if it is, let me know and I will try the same vagrant file on a more up to date centos version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant