Pro Puppet wouldn't mention puppetdb, as it was written before puppetdb came out. As to your original question, if the puppetmaster service is running, that would probably inhibit you from starting a second one, as the PID file would already be in use. For the client not being able to connect, you need to make sure that the master is listening on the correct port and that your firewall isn't blocking on that port.
On Tuesday, March 19, 2013 7:30:34 PM UTC-7, mike wrote: > > I don't have idea of mysql and backed becoming obsolete. My guide is the > book: Pro Puppet, but within the section "stored configuration" speak > about: mysql, postgres, sqlite and oracle and never puppetdb. (Thanks for > this tips). > Respect whether puppet master is running, yes is ok and the ports is 8140 > is available . > > [………………...] > [root@puppet ~]# netstat -tlpn > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address > State PID/Program name > tcp 0 0 0.0.0.0:3306 0.0.0.0:* > LISTEN 8288/mysqld > tcp 0 0 0.0.0.0:8140 0.0.0.0:* > LISTEN 15436/ruby > tcp 0 0 0.0.0.0:22 0.0.0.0:* > LISTEN 1120/sshd > tcp 0 0 :::22 :::* > LISTEN 1120/sshd > [root@puppet ~]# > [root@puppet ~]# service puppetmaster status > puppet (pid 15436) is running… > [………………...] > > > Thanks!! > > El 19-03-2013, a las 22:13, 尹川 <yinchu...@gmail.com <javascript:>> > escribió: > > backend > > > -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
