Puppet Community

image.png

Can you run  `systemctl cat puppet` and `puppet agent -t` ? (as root or with sudo like <@U112RM52S> :arrow_down: )

thanks for your replies .....it was expired certificate issue and generated again and its working now

Can you run  `systemctl cat puppet` and `puppet agent -t` ?

:businessparrot: _:teacher: Bolt_ is about to start up in <#CFD8Z9A4T|>

Offering another alternative: <https://github.com/skx/puppet-summary>
which has an "orphaned" screen.

Can you run  `systemctl cat puppet` and `puppet agent -t` ? (as root or with sudo lie <@U112RM52S> :arrow_down: )

Do you use PuppetDB? If so, use one of:
• <https://puppet.com/docs/puppetdb/7/api/query/examples-pql.html#querying-for-inactive-nodes>
• <https://puppet.com/docs/puppetdb/7/api/query/examples-pql.html#timestamp-filtering>
If you don’t use PuppetDB or aren’t collecting reports somewhere, there’s not really a good, central way to do that.

Do you use PuppetDB? If so, <https://puppet.com/docs/puppetdb/7/api/query/examples-pql.html#querying-for-inactive-nodes>

If you don’t use PuppetDB or aren’t collecting reports somewhere, there’s not really a good, central way to do that.

I'd log back or refresh your terminal. Puppet adds logic to /etc/profile.d/ IIRC that adds /opt/puppetlabs/bin to your path. Though `no such file` makes me wonder if something else happened like a failed install.

Hello, I am getting this error after upgrading server.....xargs: /opt/puppetlabs/bin/puppet: No such file or directory

<https://simp-project.atlassian.net/jira/projects>

I feel foolish now:   <https://simp-project.atlassian.net/browse/SIMP-10733>

I guess that's what happens when one gets old.

<@U016X9SDPK6> I just opened up the issues on the project if that's easier for you

Yes, thank you.  I have very little experience on submitting PRs and Issues so please be patient.

Ugh, I smell whitespace differences :cry:

That's my guess but I have absolutely no Ruby experience to be able to submit any kind of rational PR.

No worries. Not sure when we can get to it, but it might be an easy fix

The module just [blindly?] deletes the original files and recreates them.

<@U11L48K6J> I submitted a very hackish PR:  <https://github.com/simp/pupmod-simp-incron/pull/56>

puppet-lint complain about :    top-scope variable being used without an explicit namespacePuppet(variable_scope)    lol
euh? what’s wrong here?
```$test = 123

file { tmp/test:
  ensure  =&gt; file,
  content =&gt; testfile$test,
}```
same result if I use:
```content =&gt; "testfile${test}",```

must be not the whole story. which line exactly ?

nope infact..  my class inherits test::params

for some reason that syntax seems working. now !
```content =&gt; 'testfile$test',```

this will be a literal string, variable not interpolated

uising that syntax i get the top-scope variable being used without an explicit namespacePuppet(variable_scope)

Hi <@U2S1MUUQ7> ,
if now my `testfile` in that example below is a *Function*.
How should I formulate.
I tried several ays and puppet-lint still complains about
“Could not parse for environment *root*: Syntax error at ‘test’


It should be something like this ?
```content =&gt; testfile${test},```

because is a function I can’t put the ” double quote,  right?

if I interpret it that way ,   it should be :
```content   =&gt; "func(testfile)${test}",```

```content =&gt; "${func('testfile')}${test}",```

```Error 500 on SERVER: Server Error: Evaluation Error: Unknown function: 'func'.```


that suppose to be the name of your function