are right about my typo with manifests instead of manifest.
Sometimes I guess you just need a second set of eyes! It didn't error out,
but changing that and it looks like my module with storeconfigs is now
working. Thank you!!!
-Larry
On Wednesday, July 24, 2013 11:57:17 PM UTC-4, Larry Long
after making the changes to puppet.conf right?
I don't mean to insult, but you'll be amazed how often people forget
that :-).
On Thu, Jul 25, 2013 at 3:58 PM, Larry Long djsly...@gmail.comjavascript:
wrote:
I really don't want to go back to ActiveRecord... any ideas anyone
I have my foreman running over Passenger, but if you are using the default
webrick, you need to specify the port. The default is 3000.
On Thursday, July 25, 2013 8:04:47 AM UTC-4, Andreas Dvorak wrote:
Dear all
I am trying to set up reports in foreman, but foreman tells me to
Maybe an issue with puppetdb? I see some weirdness, although no apparent
errors on it.
On Wednesday, July 24, 2013 11:57:17 PM UTC-4, Larry Long wrote:
# cat /etc/redhat-release
CentOS release 6.4 (Final)
# puppet --version
3.2.3
# rpm -q puppetdb
puppetdb-1.3.2-1.el6.noarch
I am now
, Larry Long wrote:
# cat /etc/redhat-release
CentOS release 6.4 (Final)
# puppet --version
3.2.3
# rpm -q puppetdb
puppetdb-1.3.2-1.el6.noarch
I am now receiving Not collecting exported resources without
storeconfigs for my opsview module. It was working fine on puppet 2.7 with
Activerecord
Well, it seems puppet config print is useless as it is incorrect with most
values it shows. I know storeconfigs are up and running and I think its
going to puppetdb. I am still having issues with my mod.
On Wednesday, July 24, 2013 11:57:17 PM UTC-4, Larry Long wrote:
# cat /etc/redhat
# cat /etc/redhat-release
CentOS release 6.4 (Final)
# puppet --version
3.2.3
# rpm -q puppetdb
puppetdb-1.3.2-1.el6.noarch
I am now receiving Not collecting exported resources without storeconfigs
for my opsview module. It was working fine on puppet 2.7 with
Activerecord/MySQL. I am still new