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

unable to up the machine #4

Open
maaixprt opened this issue Dec 10, 2019 · 5 comments
Open

unable to up the machine #4

maaixprt opened this issue Dec 10, 2019 · 5 comments

Comments

@maaixprt
Copy link

Here are log detail any idea. What should I do now ?

==> default: Notice: /Stage[main]/Redis/Exec[unpack-redis]/returns: executed successfully
==> default: Notice: /Stage[main]/Redis/Exec[install-redis]/returns: executed successfully
==> default: Notice: /Stage[main]/Redis/Redis::Instance[redis-default]/File[redis-lib-port-6379]/ensure: created
==> default: Notice: /Stage[main]/Redis/Redis::Instance[redis-default]/File[redis-init-6379]/ensure: created
==> default: Info: /Stage[main]/Redis/Redis::Instance[redis-default]/File[redis-init-6379]: Scheduling refresh of Service[redis-6379]
==> default: Notice: /Stage[main]/Redis/Redis::Instance[redis-default]/File[redis_port_6379.conf]/ensure: created
==> default: Info: /Stage[main]/Redis/Redis::Instance[redis-default]/File[redis_port_6379.conf]: Scheduling refresh of Service[redis-6379]
==> default: Error: Could not start Service[redis-6379]: Execution of '/etc/init.d/redis_6379 start' returned 1:
==> default: Error: /Stage[main]/Redis/Redis::Instance[redis-default]/Service[redis-6379]/ensure: change from stopped to running failed: Could not start Service[redis-6379]: Execution of '/etc/init.d/redis_6379 start' returned 1:
==> default: Notice: /Stage[main]/Redis/Redis::Instance[redis-default]/Service[redis-6379]: Triggered 'refresh' from 2 events
==> default: Info: Creating state file /var/lib/puppet/state/state.yaml
==> default: Notice: Finished catalog run in 172.63 seconds
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.

@maaixprt
Copy link
Author

$ vagrant ssh
Welcome to Ubuntu 14.04.6 LTS (GNU/Linux 3.13.0-170-generic x86_64)

System information as of Tue Dec 10 09:31:57 UTC 2019

System load: 0.87 Processes: 84
Usage of /: 3.6% of 39.34GB Users logged in: 0
Memory usage: 25% IP address for eth0: 10.0.2.15
Swap usage: 0%

Graph this data and manage this system at:
https://landscape.canonical.com/

UA Infrastructure Extended Security Maintenance (ESM) is not enabled.

0 updates can be installed immediately.
0 of these updates are security updates.

Enable UA Infrastructure ESM to receive 64 additional security updates.
See https://ubuntu.com/advantage or run: sudo ua status

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

vagrant@vagrant-ubuntu-trusty-64:~$ redis.cli h localhost -p 6379
No command 'redis.cli' found, did you mean:
 Command 'redis-cli' from package 'redis-tools' (universe)
redis.cli: command not found
vagrant@vagrant-ubuntu-trusty-64:~$ mongo localhost 27017
The program 'mongo' is currently not installed. To run 'mongo' please ask your administrator to install the package 'mongodb-clients'
vagrant@vagrant-ubuntu-trusty-64:~$

@flik
Copy link

flik commented Dec 10, 2019

same issue with me too...

@gravelander
Copy link

Do you have puppet installed?

@flik
Copy link

flik commented Dec 10, 2019

no. Just virtual box and vagrant is installed and I am using windows 10

@gravelander
Copy link

@flik Try installing puppet on the local machine

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

3 participants