> Right now I'm creating only one VM, co-locating PuppetMaster and PuppetDB to > make it simple - destroying and rebuilding. But it always fails - during the > provisioning/building and also even after if I login to the machine and run > puppet apply. Telnet works fine: > >> root@puppet:~# telnet puppet.internal 8081 >> Trying 127.0.1.1... >> Connected to puppet.internal. >> Escape character is '^]'. >> Connection closed by foreign host. > > > and iptables is not configured at all but here is the output:
Okay, let me zoom out a bit and rethink this. Going back to a point you made originally: > Can anyone explain to me what actually going on/wrong please? Why it was "Not > Found" before and now "Unable to connect"? Any help/pointer would be much > appreciated. Best! I think the 404 is common while the application is loading within Jetty. It might be that the timeout we have for waiting for PuppetDB to be fully available needs to be adjusted? It could also be a legit problem also. So lets try a different tactic. Lets adjust the setting puppetdb_startup_timeout for the puppetdb::master::config class, and change it to something high, like 60 seconds or so. If that still fails, I think we should grab the /var/log/puppetdb/puppetdb.log output, can you put that in a gist or something? The log immediately after the attempted provision is best - so don't try to rerun puppet or anything, we want to see if purely after the provisioning process fails. ken. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNT%3Dx5dQEXKt2frzQr6VK0KLYngzWPZr7HRFZU%3DvT%2BSiACQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
