similar to: Nodes not showing up under 'Live Management' on fresh install of PE 2.7

Hello all, To experiment with Puppet Enterprise (we already use open source) and to create a case for our management to buy it, I''m trying to set up a Puppet Enterprise environment on some virtuals. While the puppet part works fine, and the client I''ve set up is doing fine as well, it seems the Live Management part is not. When I click on the Live Management tab it only

Hello All, Unable to install Puppet Enterprise v2.0.0 for RHEL 5-x86_64. [root@1801 puppet-enterprise-2.0.0-el-5-x86_64]# ./puppet-enterprise- installer -a answers/full_suite.answer.sample ============================================================================================================================ Puppet Enterprise v2.0.0 installer for el-5-x86_64

Im new to puppet and installed it in my home lab to mess with, when i installed it i used the hostname rather than FQDN so went back and changed puppet and reran the certificate tool to regenerate the certificates etc, the agent works fine now but i am getting an mccollective error i think, is there anything in the config i need to change for mccollective after altering the name to the FQDN?

I have a Ubuntu 12.04 server running PE 2.8.2. I have a Fedora 18 node that I would like to manage. I installed the F18 node using a kickstart installation. During this install I enabled the puppetlabs repo and installed puppet from the puppetlabs repo. One of the post installation tasks executed the following command: puppet agent -t --server <server name>. Everything seemed to

Puppet 2.7.19 (Puppet Enterprise 2.7.0) When I try to uninstall/purge the product using command below, /var/lib/peadmin/.* remains ./puppet-enterprise-uninstaller -pd [root@puppettarget peadmin]# ls -la total 44 drwx------ 5 502 502 4096 Feb 13 13:13 . drwxr-xr-x. 24 root root 4096 Feb 13 15:13 .. -rw------- 1 500 500 1952 Feb 12 16:18 .bash_history -rw-r--r-- 1 502 502 192 Feb 11

Hi guys, I''m a three days new Puppet user. I''ve installed Puppet Enterpise 3 in a Debian box with Console enabled. I''ve setup a Windows 7 with puppet enterprise 3 and it have been discovered and signed by Puppet Master. I see my Windows node in Nodes tab. I can''t figure out what mistake I did, but the Windows node never appears on Live Management tab. I

I had installed puppet master and client on two different machines. machine A has puppet master and machine B has client. both are centos6 64 bit machines. Machine B (client) is successfully connected to master (machine A). My aim is to install New Relic agent (server monitorinig tool) on different clients. I had installed new relic agent on machine A and trying to build a module so that I

Hi List, I would like to discuss with whoever is interested one topic that I suppose has general interest. I want to implement some kind of automatic testing on the status of a node after a Puppet Run. These tests involve trivial and less trivial things things like: - A local service is running - A local port is open - A remote server on a remote port is reachable by the node - An URL replies

Hi, I deployed MCollective to our Puppet clients. approx. ~ 200. Our platform requires the most secure setup possible, so PSK as securityprovider is not an option. Therefor I changed the security provider to aes_security reusing puppets certificates in the server.cfg as found in the docs (1) Our goal is to use mcollective to offload event-driven actions to agents running on designated nodes from

I''ve almost gotten PE running -- Based on tips from a recent Webinar, I''ve started on a minimal RHEL 6 system, and have installed the PE 2.03 packages. Once I set up /etc/ hosts (DNS will come later), I started the PE services. Given past problems (possibly just me), I was pleasantly surprised that the puppet-enterprise-updater script was so accommodating as I remembered which

This patch series is the lastest version that fix the PE headers generated for syslinux for UEFI. Compared to the previous versions of this patch series, the relocation fixing has been made less brutal. Namely, patch 3/5 remove the useless relocation that is rejected by OVMF and the whole .reloc section removal has been made a separate patch 5/5. This last patch is optional. Of course they are

Moshe, Nir wrote: [...] > I have a question about the LLVM ARM backend: > > I try to build *.c files for Windows Phone (Windows 8) - so, basically > I need to generate an "arm-pe" file (I *think* it has the same file > structure like x86-pe file, but i am not sure). > unfortunately, LLVM has no support with ARM PE\COFF. We recently ran into this. Unfortunately

So, we have plans to be smarter about cross-machine dependencies, and about managing the network rather than just the nodes. Part of that comes from the MCollective system, which is all over "network". What I don''t have is a timeline for you: today we don''t have that around, other than the MCollective puppet agent, and we don''t have a concrete plan (that I am

Hi guys, I have a question about the LLVM ARM backend: I try to build *.c files for Windows Phone (Windows 8) - so, basically I need to generate an "arm-pe" file (I *think* it has the same file structure like x86-pe file, but i am not sure). unfortunately, LLVM has no support with ARM PE\COFF. Any ideas? How difficult is to add the support in this file format? (LLC can generate ARM

I am having the darnedest of times trying to get my WinPE to work off the syslinux loader. I used to use isolinux, and my isolinux config would just invoke the etfsboot.com file which i had renamed to loader.bin, and everything would work just fine off a cd. But now I'm trying to transfer all of my cd functionality to thumbdrives. With Syslinux, i have my syslinux.cfg file calling loader.bin

Hi everyone, I run MCollective 1.2.1 together with ActiveMQ 5.5 under Scientific Linux 6.1 on Amazon EC2. Overall it works like a charm, but sometimes (eg. 1/30) discovery fails. Still the exit-code of mco will be 0, which is a problem for me as I use MCollective e.g. to trigger deployments from Jenkins. I would like to ask for some feedback on the following ideas, that could fix this problem.

Here are the fix as suggested. For patch 2/4 I chosed to hardcore the value 512 instead of computing the fittest needed value. There are 3 reasons for that. - The header size may not need to be bigger than this in a near future. - There is an test in case increasing the header size would be needed. - It would make the code quite more complex to keep a consistent value for all the fields when the

> -----Original Message----- > From: Luke Ledgerd > Sent: Monday, November 24, 2014 1:10 PM > To: 'syslinux at zytor.com' > Subject: Windows PE booting without chainloading ipxe > > I have an interest in booting Windows PE from PXELinux, and it seems that wimboot from ipxe project is the solution. > http://ipxe.org/wimboot > > MENU LABEL Windows 8.1

I am working toward pitching a move from Open Source Puppet to Puppet Enterprise. One of the driving points is that Where-I-Work has just made a huge investment in hardware/software in the form of a VMWare "local cloud". In trying to figure out how to plug my current Puppet setup into it, I keep hitting references to middleware tools like "vSphere CLI for Linux" and

Hi , I want to use PE 2.0 compliance feature , however i am not seeing any data on puppet-dashboard on compliance tab , it says no baseline set , reviewed NA etc..... I have written audit manifests class foo { file {''/etc/resolv.conf'': audit => all, } file {''/etc/services'': audit => all, } } and