Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi, firewalls would not normally block localhost connections as it is the node connecting to itself.
Are you sure the service is running and listening on port 8500? To find out, try this command on the console / SSH terminal:
netstat -tnlp
That should list all active TCP listeners as well as the process id (pid) and process name.
If you do not see 8500 in that output then your problem probably lies elsewhere.
Hope this helps and let us know how it is going.
Yes, in order to connect to port 8500 something has to be listening. This happens after install AND starting the service (maybe ansible doesn’t start it?)
You could try checking syslog or other logs for errors. Maybe try starting the service manually, as it might display the problem right there on the screen.
If ansible experiences an issue it should report an error too as well so double-check that - might be something straightforward.
Thanks @baraboom for your help.
I think your original suggestion was correct to start the service and see the errors.I was able to figure out the issue. It was failing because of the invalid config key log_file. I ended up removing “log_file”: “{{ consul_logfile }}”, from consul.json.j2 and it all reinstalled perfectly.
Not sure if it is because I am using 1.2.1.