oops ... I was wrong about that. It does define a resource. my bad
On Wed, Jun 7, 2017 at 3:28 PM, Red Cricket
wrote:
> I took a look at https://github.com/xaque208/puppet-ssh/blob/
> master/manifests/server/subsystem.pp
> There is no subsystem resource defined ... just this:
>
> # Define: ssh::
I took a look at
https://github.com/xaque208/puppet-ssh/blob/master/manifests/server/subsystem.pp
There is no subsystem resource defined ... just this:
# Define: ssh::server::subsystem
#
# Add an ssh subsystem to sshd_config(5)
#
# Examples:
#
# ssh::server::subsystem { 'sftp':
# system => '
Thank you, guys.
Unfortunately it still doesn't produce anything.
I guess I'll have to figure out the author's code.
@Peter Kristolaitis, thank you for bringing to my attention that the "sftp"
title will probably not be a key, or class name.
@amateo, I'm not yet familiar with roles/profiles but t
Hello,
I have my own custom type but I'm having a problem.
In my custom type I have a parameter called "target", that is the path
where the content of the type should be created. This parameter is
optional, and when it is not directly provided, it is initialized in the
next way:
*
On Tuesday, June 6, 2017 at 10:04:51 AM UTC-7, bhan...@gmail.com wrote:
>
> Hi,
>
> Any one saw this error before?
>
> there are a lot of messages like this in
> /var/log/puppetlabs/puppetserver/puppetserver.log
>
> Puppet 'store_report' command for $HOST failed during submission to
> PuppetDB:
I think you wanted /pdb/meta/v1/version? This and the other puppetdb
documentation may help:
https://docs.puppet.com/puppetdb/4.4/api/query/v4/query.html
https://docs.puppet.com/puppetdb/4.4/api/meta/v1/version.html
(Obviously pick your puppetdb version in the drop-down at the top of the page.)
Hi, I am facing the same problem. WIth PuppetDb version 4.10.
Did you find a solution ?
On Saturday, 18 October 2014 21:16:38 UTC+5:30, Stella wrote:
>
> Hi guys,
>
> I am us puppet 3.6.2 and dashboard. When I run "puppet agent --test", got
> this error:
>
> Error: Could not retrieve catalog from
I am facing same issue as above.
I got the following response :-
Error 404
HTTP ERROR: 404
Problem accessing /v4/version. Reason:
Not Found
Powered by Jetty://
On Saturday, 30 August 2014 04:23:35 UTC+5:30, Wyatt Alt wrote:
>
> Hi Spriya,
>
> Can you try accessing your database server
