Displaying 2 results from an estimated 2 matches for "nodequery".
2019 May 23
1
Second VPN network fails to start
...at step CHDIR spawning /usr/sbin/tincd: No such file or directory
May 23 14:35:14 db2 systemd[1]: tinc at VPN1.service: Main process exited, code=exited, status=200/CHDIR
May 23 14:35:14 db2 systemd[1]: tinc at VPN1.service: Failed with result 'exit-code'.
May 23 14:36:01 db2 CRON[31389]: (nodequery) CMD (bash /etc/nodequery/nq-agent.sh > /etc/nodequery/nq-cron.log 2>&1)
May 23 14:36:14 db2 systemd[1]: tinc at VPN1.service: Service hold-off time over, scheduling restart.
May 23 14:36:14 db2 systemd[1]: tinc at VPN1.service: Scheduled restart job, restart counter is at 1166.
May 23 14...
2013 May 27
2
Puppetdbquery 1.1.0, now featuring hiera backendception
...ckend `puppetdb`to the backends list in `hiera.yaml`.
So instead of writing something like this in for example your
`hiera-data/common.yaml`:
ntp::servers:
- ''ntp1.example.com''
- ''ntp2.example.com''
You can now instead write:
ntp::servers::_nodequery: ''Class[Ntp::Server]''
It will then find all nodes with the class ntp::server and return an array
containing their certname. If you instead want to return the value of a
fact, for example the `ipaddress`, the nodequery can be a query and fact
tuple, like:
ntp::servers::_nodeq...