Using Puppetdb-terminus via rubygems...?

[Matt W]

We have entirely-gem based Puppet masters (no Ubuntu packages installing Puppet)... we're trying to add in the puppetdb-terminus gemfile. We have it configured, and installed:

# gem list | grep -i puppet

hiera-puppet (1.0.0)

puppet (3.7.3)

puppet-catalog-test (0.3.1)

puppet-lint (1.0.1)

puppet-syntax (1.3.0)

puppetdb-terminus (1.0)

puppetlabs_spec_helper (0.8.2)

rspec-hiera-puppet (1.0.0)

We're running into a problem with our Unicorn/Nginx config though... 

puppet-master[17213]: Could not configure routes from /etc/puppet/routes.yaml: Could not find terminus puppetdb for indirection facts 

 

Is there something special we need to do to the config.ru or something so that it can find the puppetdb terminus from the gem thats installed?

[Ken Barber]

> We have entirely-gem based Puppet masters (no Ubuntu packages installing
> Puppet)... we're trying to add in the puppetdb-terminus gemfile. We have it
> configured, and installed:
>
>
> # gem list | grep -i puppet
> hiera-puppet (1.0.0)
> puppet (3.7.3)
> puppet-catalog-test (0.3.1)
> puppet-lint (1.0.1)
> puppet-syntax (1.3.0)
> puppetdb-terminus (1.0)
> puppetlabs_spec_helper (0.8.2)
> rspec-hiera-puppet (1.0.0)

That is not an official gem for puppetdb-terminus :-). Someone
uploaded it in the past, I think its a dud.

We don't really ship a rubygem, we do have a gemfile however:
https://github.com/puppetlabs/puppetdb/tree/master/contrib/gem

That can be used to create your own gem.

> We're running into a problem with our Unicorn/Nginx config though...
>
> puppet-master[17213]: Could not configure routes from
> /etc/puppet/routes.yaml: Could not find terminus puppetdb for indirection
> facts
>
> Is there something special we need to do to the config.ru or something so
> that it can find the puppetdb terminus from the gem thats installed?

That just looks like the necessary ruby library files aren't in place,
probably due to the bad gem.

ken.

[Matt Wise]

Thanks for that Ken... This morning I found a gem 'md-puppetdb-terminus' that someone has published that works perfectly, thankfully.

Matt Wise

Sr. Systems Architect

Nextdoor.com

--
You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/830HwH-1JCY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNTnH4ZQXnsGJpxB-W6SAypsJAsXtU0F%3DFoFXtcoRmTJbTA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Darin Perusich]

On Mon, Dec 8, 2014 at 5:01 AM, Ken Barber <k...@puppetlabs.com> wrote:
>> We have entirely-gem based Puppet masters (no Ubuntu packages installing
>> Puppet)... we're trying to add in the puppetdb-terminus gemfile. We have it
>> configured, and installed:
>>
>>
>> # gem list | grep -i puppet
>> hiera-puppet (1.0.0)
>> puppet (3.7.3)
>> puppet-catalog-test (0.3.1)
>> puppet-lint (1.0.1)
>> puppet-syntax (1.3.0)
>> puppetdb-terminus (1.0)
>> puppetlabs_spec_helper (0.8.2)
>> rspec-hiera-puppet (1.0.0)
>
> That is not an official gem for puppetdb-terminus :-). Someone
> uploaded it in the past, I think its a dud.

If this isn't official, would Puppet Labs be willing to have it
removed or publish the gem?

> We don't really ship a rubygem, we do have a gemfile however:
> https://github.com/puppetlabs/puppetdb/tree/master/contrib/gem
>
> That can be used to create your own gem.
>
>> We're running into a problem with our Unicorn/Nginx config though...
>>
>> puppet-master[17213]: Could not configure routes from
>> /etc/puppet/routes.yaml: Could not find terminus puppetdb for indirection
>> facts
>>
>> Is there something special we need to do to the config.ru or something so
>> that it can find the puppetdb terminus from the gem thats installed?
>
> That just looks like the necessary ruby library files aren't in place,
> probably due to the bad gem.
>
> 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 puppet-users...@googlegroups.com.

[Matt Wise]

+1

Matt Wise

Sr. Systems Architect

Nextdoor.com

You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/830HwH-1JCY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CADaviKuX8s3cUms_d7LP7QHR-dtyT%3DMG%3D%3DPz85WJrohiVPqUJA%40mail.gmail.com.

[Spencer Krum]

The gem owner would be the only one who could remote the gem. That, obviously, is not puppetlabs.

 

--

Spencer Krum

ni...@spencerkrum.com

 

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAOHkZxOi0g3Ey%3Dj2r0SDAHhgF5JBVX4wLRWLRwOPaBYfd9GmCw%40mail.gmail.com.

[Darin Perusich]

I contacted the gem owner requesting that he remove this gem.
--
Later,
Darin

> https://groups.google.com/d/msgid/puppet-users/1418104128.4043275.200558617.75DF529D%40webmail.messagingengine.com.