similar to: file retrieval problems

Hi, I''m not sure what I''ve did wrong, I now get an error message denying authenticated client ... access to puppetreports.repot anyone has an idea where should i look ? Thanks, Ohad _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

I''m trying to wrap my head around these files... do both of them need to reside on the client and master? are there any docs that describe these files and what all the option/ sections are and what they do? Thanks all.... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

What''s this mean? root@gravity:/etc/puppet/manifests# puppetd -v --listen info: Starting handler for Runner info: Starting server for Puppet version 0.22.1 info: Listening on port 8139 notice: Starting Puppet client version 0.22.1 err: Could not run Puppet::Client::MasterClient: Host gravity.example.org not authorized to call puppetmaster.freshness Thanks, Kent -- "It may be true

Hi, I''ve setup my systems to do reporting as explained in https:// reductivelabs.com/cgi-bin/puppet.cgi/wiki/ReportsAndReporting, with tagmail defined as one of the report types - but I do not recieve any mail at all. I''ve configured a tagmail.conf file like this: all: root@localhost But the documentation mentions three options, namely sendmail, reportfrom,

Hi, We''re trying to follow the instructions at http://reductivelabs.com/trac/puppet/wiki/UsingMongrel (Just using a single puppetmaster/mongrel instance and plain mod_proxy for now, instead of balancer one) We got past the "Server is not a class" error by modifying mongrel.rb We also kind-of got past the: /opt/bin/puppetmasterd:293: undefined method `daemonize'' for

We''re still intermittantly getting these messages in syslog on various different systems: Feb 14 17:32:10 server-dev puppetd[20363]: Could not call puppetreports.report: #<EOFError: end of file reached> Feb 14 17:32:10 server-dev puppetd[20363]: Reporting failed: end of file reached Anyone else ever see stuff like this?

I have very strange problem. I set up puppet client on serveral servers but have problem with one of them. When I invoke: root@www ~ # puppet agent --server puppetmaster.domain.ltd --test notice: Ignoring --listen on onetime run info: Caching catalog for puppetclient.domain.ltd info: Applying configuration version ''1326444431'' notice: Finished catalog run in

On 02/22/2018 11:41 AM, Riccardo Ravaioli wrote: > Hi, > > I'm having trouble starting a VM with vhostuser interfaces. > > I have a simple configuration where a VM running Debian has 1 vhostuser > interface plugged into an OVS switch where a DPDK interface is already > plugged in. > $ ovs-vsctl show: > Bridge "switch1" >     Port "switch1"

Hi, I'm having trouble starting a VM with vhostuser interfaces. I have a simple configuration where a VM running Debian has 1 vhostuser interface plugged into an OVS switch where a DPDK interface is already plugged in. $ ovs-vsctl show: Bridge "switch1" Port "switch1" Interface "switch1" type: internal Port "1.switch1"

Hi all, Today we have had a strange problem that has taken down our website, we understand what happened but not why so I am hoping someone has seen this before. We have our web servers (web1 web2 web3 ..... web10) mounting an NFS share (/export/data) from server nfs1. On the web server side we use autofs in the format nfs-dedicated:/export/data where nfs-dedicated is an alias in our

TB --- 2008-06-03 09:06:24 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-03 09:06:24 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2008-06-03 09:06:24 - cleaning the object tree TB --- 2008-06-03 09:06:55 - cvsupping the source tree TB --- 2008-06-03 09:06:55 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/sparc64/sparc64/supfile TB ---

Hello, On our ''dev'' puppetmaster, we are experiencing a weird error, or bug. If I manually call puppet (or let the schedule kick it off) this is returned.. err: Could not retrieve catalog from remote server: Error 400 on SERVER: private method `gsub'' called for :"puppetreports.report":Symbol warning: Not using cache on failed catalog err: Could not retrieve

TB --- 2012-04-08 08:26:29 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-04-08 08:26:29 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-04-08 08:26:29 - starting RELENG_9 tinderbox run for sparc64/sparc64 TB --- 2012-04-08 08:26:29 - cleaning the

TB --- 2008-06-03 08:42:30 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-03 08:42:30 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2008-06-03 08:42:30 - cleaning the object tree TB --- 2008-06-03 08:43:09 - cvsupping the source tree TB --- 2008-06-03 08:43:09 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/i386/supfile TB --- 2008-06-03 08:43:22

On 2 September 2016 at 14:51, Rowland Penny via samba <samba at lists.samba.org > wrote: > > > As I said, I know very little about freebsd, but you should be aware > that Samba only supports the last three major versions i.e. at the > moment 4.2.X, 4.3.x and 4.4.x > They are supported in three ways, the oldest version (now 4.2.x) only > gets security fixes, the middle

so I would check with him.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o= :p></span></font></p> <div> <p class=3DMsoNormal =

Hi, I have a Gentoo server running puppetmasterd from Puppet 0.24.1 and a Ubuntu server running puppetd from Puppet 0.23.2. I have added listen=true to the [puppetd] section on the client and run puppetd --debug. I then run puppetrun --debug --host hostname on the puppetmaster server. This is the output I get: Puppetmaster: # puppetrun --debug --host hostname Failed to load ruby LDAP library.

My BIND9.6.0 on FreeBSD 6.2 works fine when I manually start with: root@ns2# named -4 -S 1024 -c /etc/namedb/named.conf But it won't start on boot and no error messages or log. And it won't start using rndc, it cause error message. Why does the error shows port 953 when I specified for port 53 in the config? rndc: connect failed: 127.0.0.1#953: connection refused Below are

I have a system running rsync in daemon mode, the version information: > rsync --version rsync version 2.6.8 protocol version 29 On another system I have: > authoritative# rsync --version rsync version 3.0.7 protocol version 30 I have the following problem when trying to fetch files from the system running the old daemon: # /usr/local/bin/rsync --protocol=29 -vvvvvvvv

Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/core/core/handle.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/core/core/handle.c b/drivers/gpu/drm/nouveau/core/core/handle.c index b8d2cbf..264c2b3 100644 --- a/drivers/gpu/drm/nouveau/core/core/handle.c +++