Issue #13317 has been updated by Andrew Parker. Status changed from Accepted to Closed
---------------------------------------- Bug #13317: Storeconfig error with postgresql https://projects.puppetlabs.com/issues/13317#change-59626 Author: Svein Harald Soleim Status: Closed Priority: Normal Assignee: Andrew Parker Category: Target version: Affected Puppet version: 2.7.12 Keywords: Branch: I'm using CentOS 6.2 with http://yum.puppetlabs.com. When I run puppetmaster from init.d I get pgsql errors in the log: Mar 22 09:58:13 puppet puppet-master[7156]: could not connect to server: Permission denied#012#011Is the server running on host "puppet.example.com" and accepting#012#011TCP/IP connections on port 5432?#012could not connect to server: Permission denied#012#011Is the server running on host "puppet.example.com" and accepting#012#011TCP/IP connections on port 5432? But when I run it from commandline it seems to run fine puppet master --verbose --no-daemonize --masterport 8140 notice: Starting Puppet master version 2.7.12 info: access[^/catalog/([^/]+)$]: allowing 'method' find info: access[^/catalog/([^/]+)$]: allowing $1 access info: access[^/node/([^/]+)$]: allowing 'method' find info: access[^/node/([^/]+)$]: allowing $1 access info: access[/certificate_revocation_list/ca]: allowing 'method' find info: access[/certificate_revocation_list/ca]: allowing * access info: access[/report]: allowing 'method' save info: access[/report]: allowing * access info: access[/file]: allowing * access info: access[/certificate/ca]: adding authentication any info: access[/certificate/ca]: allowing 'method' find info: access[/certificate/ca]: allowing * access info: access[/certificate/]: adding authentication any info: access[/certificate/]: allowing 'method' find info: access[/certificate/]: allowing * access info: access[/certificate_request]: adding authentication any info: access[/certificate_request]: allowing 'method' find info: access[/certificate_request]: allowing 'method' save info: access[/certificate_request]: allowing * access info: access[/status]: adding authentication any info: access[/status]: allowing 'method' find info: access[/status]: allowing 'method' save info: access[/status]: allowing * access info: access[/]: adding authentication any info: access[/]: adding environment production info: access[/]: allowing * access info: Connecting to postgresql database: puppet info: Expiring the node cache of puppetnode2.example.com info: Not using expired node for puppetnode2.example.com from cache; expired at Thu Mar 22 10:06:51 +0100 2012 info: Caching node for puppetnode2.example.com The database also comfirms that the commandline works. I'm using the following gems: * abstract (1.0.0) * actionmailer (3.0.11) * actionpack (3.0.11) * activemodel (3.0.11) * activerecord (3.0.11) * activeresource (3.0.11) * activesupport (3.0.11) * arel (3.0.2, 2.0.10) * builder (3.0.0, 2.1.2) * bundler (1.1.2) * erubis (2.7.0, 2.6.6) * fastthread (1.0.7) * hike (1.2.1) * i18n (0.6.0, 0.5.0) * journey (1.0.3) * json (1.6.5) * mail (2.4.4, 2.2.19) * mime-types (1.18) * multi_json (1.1.0) * pg (0.13.2) * polyglot (0.3.3) * postgres (0.8.1) * rack (1.4.1, 1.2.5, 1.1.0) * rack-cache (1.2) * rack-mount (0.6.14) * rack-ssl (1.3.2) * rack-test (0.6.1, 0.5.7) * rails (3.2.2) * railties (3.2.2) * rake (0.9.2.2) * rdoc (3.12) * sprockets (2.1.2) * stomp (1.1.8) * thor (0.14.6) * tilt (1.3.3) * treetop (1.4.10) * tzinfo (0.3.32) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
