similar to: Puppet doesnt run

Hi, I have a lot of systems where the puppetd doesn''t do anything .. When I test with puppetd -tv, it s running well, but when it is started as deamon th process do nothing :( How can I debug this ? Vincent May 29 10:07:56 puppetd[6160]: Reopening log files May 29 10:07:56 puppetd[6160]: Starting Puppet client version 0.24.8 May 29 10:07:56 puppet: puppetd startup succeeded May 29

What''s the correct yum repo to use for installing Puppet & Facter on RHEL5 and Centos5? I used to get them from the dlutter-rhel5 repo but this seems to be massively out of date now - latest version of puppet-server in there is 0.24.5-1.el5 and facter 1.5.4-1.el5. In Epel I see puppet-server 0.24.8-1.el5.1 and facter 1.5.4-1.el5 which is better but isn''t 1.5.4 the version

I just started getting this error on some machines after a yum update from centos 5.2 to centos 5.3. Does anyone know what it means? Since I''m not a ruby person, I''m not sure how to debug this, but it looks to me like facter is having trouble parsing information about my interfaces. # facter /usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:19: uninitialized constant

I have a new user question. Sorry I know most of you are Linux experts I am not! I am just getting my feet wet with this. And I am sorry to ask this stupid question. I was following an installation post from Wiki that said when using RH 9 you need to make sure that you have the following installed first and you should check them with the following command. Are there any other items I need to

Dear Manager: Thanks in advance for your interest, We mainly produces are Indole series (indole, 3,3'-Methylenebisindole , 5-methoxy indole) Indole >99% POWDER loss on drying: 1% white slight yellow crystalline powder CRYSTAL melting point: 51-53 loss on drying: 0.5% white sheetform crystal

This message appeared in my inbox over the weekend. A useful idea although I have not reviewed the code. Might someone on the list (or the original author) be interested in running with it? Monty > Hello - > I hacked up an ogg winamp output plugin based on the vorbis > example_encoder and the out_raw winamp sdk sample. It requires the same > deal as the winamp input plugin

Hello there I''m having this error: Could not call fileserver.describe: #<Errno:: ECONNRESET: Connection reset by peer> From what i can tell, eventually the master decides it has had enough and freezes. I''ve got about 25 hosts checking in to it, but restarting the master daemon appears to be only a partial solution with the clients occasionally not being able to then

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.24.8 is now available! This is a maintenance release for the 0.24.x branch but contains a small number of new features including some significant performance enhancements for large installations and stored configurations. The tarball is available at: http://reductivelabs.com/downloads/puppet/puppet-0.24.8.tgz MD5 hash:

Hello, Since i use facter 1.5.5 i got error running it by hand. It still work in puppet but i loosed the hability to run it from the command line: (aqadmin)> /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50:in `require'': no such file to load -- facter (LoadError) from /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50

Hi Heidi, Now We tried to install the puppet and puppet-server packages from puppetlabs, but we faced below discrepancy. Please look into this and let us know your suggestions because issue was not found in Puppet community as well. There was 1 issue related to this but it dint help us (http://projects.puppetlabs.com/issues/16634 ) We went through

Hi All Background: I am running Puppet to configure ESX 3.5 servers by NFS mounting the Puppet binaries and configuration from a shared server. This is to ensure VMware don''t come back refusing support for installing non standard software on the server. # ruby -v ruby 1.8.7 (2009-04-08 patchlevel 160) [i686-linux] # facter -v 1.5.5

I have 2 RHEL 5.4 systems where all facter lsb* items are missing. Any ideas? Sanitized facter output: architecture => i386 domain => missyou.edu facterversion => 1.5.7 fqdn => broken.missyou.edu hardwareisa => i686 hardwaremodel => i686 hostname => broken id => root interfaces => eth0,sit0 ipaddress => 1.2.1.5 ipaddress_eth0 => 1.2.1.5 is_virtual => true

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I read that there is several problems about custom facts on this list. However, none is serving my task exactly so I start another. (Topic »custom facts in legacy puppet 0.24.[89]« is the might be the same issue but that gets no answer.) My problem is that I have to serve clients with different versions of puppet. The systems running ubuntu

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have an Debian system running samba 3.0.14a from sarge. It is exporting a file system, /data. This file system has the perms 2770. I have set the following in the smb.conf: inherit permissions = yes inherit acls = yes I mount the filesystem from a linux, ubuntu, client and create a directory. The directory comes out with perms 0770. I can

Hai Victor, Sorry for these, i did not know there was still one going on in the ubuntu package. These are known since 26 july.. What i need/want to know here from which version to which version did you upgrade. I'll fix that in the next update. There where 2 things going on here. - one file moved from package. (apt --fix-broken install) - The othere was due to the changes in ldb with

On 22.09.2019 15:30, Rowland penny via samba wrote: > On 22/09/2019 14:10, Viktor Trojanovic via samba wrote: >> On 22.09.2019 15:07, Rowland penny via samba wrote: >>> On 22/09/2019 13:53, Viktor Trojanovic via samba wrote: >>>> I just ran "apt upgrade" on my DC (Ubuntu 18.04, Samba 4.10 from Louis >>>> Repo) and it ended with error messages

I tried to use a Puppet variable named "$memory" and access it from a template, like this: $memory = 4711 file { "/tmp/test.txt": content => inline_template("memory = <%= memory %>\n"); } One would think that my file would contain "memory = 4711" after that, but instead the memory variable seems to hold a

I''m using puppet-0.24.8-4.el5 on CentOS 5.4. My problem is yumrepo isn''t writing the "name=" field to the repository files which causes yum to complain with the error: Repository ''local-CentOS-5.4-x86_64'' is missing name in configuration, using id I get this behavior on all of my yumrepo definitions. One of them looks like this: yumrepo {

Recently a production "stable" samba server started producing this: samba-log.cpr8r: oplock_break failed for file Share1/Files/Financial/Comms.xls (dev = b, inode = 151073815, file_id = 31). samba-log.cpr8r: oplock_break failed for file Share1/Files/Financial/Futures.xls (dev = b, inode = 411546895, file_id = 31). samba-log.cpr8r: oplock_break failed for file

On 22.09.2019 15:07, Rowland penny via samba wrote: > On 22/09/2019 13:53, Viktor Trojanovic via samba wrote: >> I just ran "apt upgrade" on my DC (Ubuntu 18.04, Samba 4.10 from Louis >> Repo) and it ended with error messages about unmet dependencies in >> regards >> to libldb1. >> > Yes, but did you run 'apt-get update' first ? > >