Thank you Deepak You are right There was another process using the same port that was assigned to puppetdb. Is there anything else to modify the port besides modifying it at the file below? puppetdb/conf.d/jetty.ini
On Thursday, July 31, 2014 10:18:33 AM UTC-4, Deepak Giridharagopal wrote: > > On Thu, Jul 31, 2014 at 7:34 AM, Denis Labkovich <denis.l...@gmail.com > <javascript:>> wrote: > >> Hello, >> >> We have >> 3.4.3 (Puppet Enterprise 3.2.3) >> that is running on HyperV VM >> After hard reset, it came back with the issue of failing pe-puppetdb >> service >> >> It starts and then in a minute fails. >> >> Here is the /var/log/pe-puppetdb/puppetdb-daemon.log >> java.net.BindException: Address already in use >> > > This would indicate that something else is using the ports PuppetDB wants > to use, and thus it can't complete its startup. By default, we choose ports > 8080 and 8081...those can be changed through config in > /etc/puppetlabs/puppetdb to something that isn't already taken. > > deepak > -- 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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3e153f00-edc6-4e41-b314-34699aabb7a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
