similar to: Setup 2.6 + apache, passenger

Hi, My organization is going to set up puppet soon. We have thousands servers and desktops. Would WEBrick work well for this? Or should we use Passenger? Thanks, Haiyan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to

Hi all, I have experience using puppet, however I am new to setting puppet up as it was already done for me in past environments. I am running into an issue while trying to set puppet up for the first time on RHEL 6.4. I was hoping y''all might be able to help me! I get the following error from the puppet client''s /var/log/messages log: May 30 07:06:30 pclient

I have a freshly installed and updated CentOS 5.4 system running puppet 0.25.5. I followed the passenger docs here: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Passenger Upon starting the client, the following appears in the apache error log. [Thu Jun 24 10:48:40 2010] [error] [client 10.10.4.45] Premature end of script headers: production [ pid=6785 file=ext/apache2/Hooks.cpp:706

Has anyone seen this come up, I am using 0.24.8 version of puppet. I followed the directions on the wiki and installed passenger correctly from what I can tell. [Wed Mar 17 09:07:56 2010] [notice] Apache/2.2.14 (Unix) DAV/2 Phusion_Passenger/2.2.5 mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.14 OpenSSL/0.9.8g mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal operations

Dear experts, Since I''ve moved my *puppetmaster* form SL5 (Scientific Linux) to SL6 with SELinux on, I''m facing loads of trouble. I also move away from WEBrick to apache/passenger, following the instruction here: http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger > and I can''t start httpd any more. It fails with this: Starting httpd: (98)Address

OK. What did I booger up this time ? agent.myexample.org and puppetmaster.myexample.org are the same server. ---------------------------------------------------------------------------- # puppetd --no-daemonize --onetime --debug --noop debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not

Hello, I randomly errors like this: Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (err): Could not retrieve catalog from remote server: end of file reached Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (notice): Using cached catalog Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (err): Could not retrieve catalog; skipping run Here are the versions: puppetmaster

Hi, I''m currently trying to debug a performance issue I''m having. Therefore I would need "DEBUG" output. When using one puppetmaster process, this is fairly easy by starting it like this: > puppet master --no-daemonize --debug Now I need to see this debug output when running puppetmaster the way I ususally do - using Apache/Rack/Passenger. After looking

The particular issue is with puppetmaster (which admittedly takes 4 minutes to actually start, setting TimeoutStartSec=300 in it's unit file stopped the false timeout report) but I have seen it one other time (don't remember the details). systemctl status puppetmaster ? puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor

I downloaded the puppet-dashboard.git from http://github.com/puppetlabs/puppet-dashboard and did the installation in my ubuntu lucid puppet server following the steps in "Installation". Now I can run it fine using the WEBrick like this root@sys-ubuntu { ~/git/puppet-dashboard }$ ./script/server -e production => Booting WEBrick => Rails 2.3.5 application starting on

Hi all, I''m currently getting a lot of update failures showing up with no logs in the dashboard. This happens for about half of our 28 nodes, about once an hour. When re-run half an hour later, everything seems fine. Through a combination of server restarts and our Puppet master locking up entirely yesterday, almost all of our nodes are now trying to do their half hourly update at

I am getting all these messages when run `passenger-status''. Do I need to worry about this? I am using passenger 2.2.2 with puppet 0.24.8 and apache2 on ubuntu 9.04. I installed it using the wiki http://reductivelabs.com/trac/puppet/wiki/UsingPassenger Thread ''Main thread'': in ''int Server::start()'' (ApplicationPoolServerExecutable.cpp:553)

Hi @all, after upgrading my puppet server to Puppet 3.0 I got the following error every time a client connect to the server: [ pid=1532 thr=70147393710520 file=utils.rb:176 time=2012-10-08 11:17:56.504 ]: *** Exception NoMethodError in PhusionPassenger::Rack::ApplicationSpawner (undefined method `settings'' for Puppet:Module) (process 1532, thread #<Thread:0x7f98ecf7d370>):

----- Original Message ----- From: "James Hogarth" <james.hogarth at gmail.com> To: "centos" <centos at centos.org> Sent: Tuesday, August 29, 2017 2:03:44 PM Subject: Re: [CentOS] Syncronize systemctl status with reality? On 29 Aug 2017 17:58, "Leroy Tennison" <leroy at datavoiceint.com> wrote: The particular issue is with puppetmaster (which

Hi, I''m currently trying to get my puppetmaster work in passenger, but have not succeeded so far. Passenger itself seems to work (a small "hello world" app runs fine), but when I point a puppet client (0.24.8) to it, I get: info: Retrieving plugins err: Could not call fileserver.list: #<RuntimeError: HTTP-Error: 500 Internal Server Error> err:

I am working on setting up a Puppet configuration where some of the data is stored on a DRBD volume. The modules and vardir are stored on the drbd volume. The puppet.conf files point to the drbd volume for vardir. I created a cert for a VIP puppet-master using the puppetca -- create command I had everything working on the primary drbd node, but when I fail over, everything starts up fine, but I

Hi, I have a couple of FreeBSD-servers that I try to manage using puppet. I''m just trying it out at the moment and have just deployed 5 new boxes (from PXE and scripted installation so supposedly they are all identical except for the name and ip-addresses). On two of the servers I get the error-messages at the bottom of the post. The first error- message I get every time I run puppet on

Hello, I really didn''t expect this to be difficult, but I''ve been struggling with this all day :( I''m running CentOS 5.3, with rubygems, rack and fastthread, from EPEL. I''m running puppet-0.25.0-1 built from the spec file in the latest stable tarball. I''m using mod_passenger-2.2.5-2.el5 from Jeroen van Meeuwen (kanarip), which is effectively EPEL

Hi, I install puppet 2.6.18, test it and it was working okay. Then I install Apache and Passenger on the Puppet server. I run on a puppet agent: puppet agent —test And I got the error: "warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run" In the puppet server access_log I have: "GET

I updated some of my gems, and I think it may be the reason I am getting the following error when the agents try to retrieve a catalog. err: Could not retrieve catalog from remote server: Error 400 on SERVER: The single-table inheritance mechanism failed to locate the subclass: ''Host::Managed''. This error is raised because the column ''type'' is reserved for