Puppet Passenger Error 500
Contents |
QueryOpen cron issuesPlatform Report - 2 Week ActivityPuppet Solaris issuesRuby 1.9 IssuesSupport Customer TicketsSupport TicketsTelly DeprecationsTickets - Assigned to MeTickets - Authored by MeTickets - By PriorityTickets - In
Could Not Request Certificate: Error 500 On Server
Topic Branch Pending ReviewTickets - Top by votesTickets - Unassigned to a puppet error 500 target releaseTickets - UnreviewedTickets - unreviewed and outside SLATickets - waiting for actionTickets with simple fixes Watchers (1) Marc Fournier The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA: The Puppet Projects Workflow describes how to file tickets against Puppet projects. Bug #2691 "Could not retrieve catalog: HTTP-Error: 500 Internal Server Error" with tagged exported resources Added by Marc Fournier over 6 years ago. Updated about 6 years ago. Status:ClosedStart date:10/01/2009Priority:NormalDue date:Assignee:James Turnbull% Done:100%Category:RailsTarget version:0.25.1 Affected Puppet version:0.25.1rc2 Branch:tickets/0.25/2691 Keywords:rails, storeconfigs We've Moved! Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com Description The problem happens with this sort of manifest (in fact, this simple example works fine): node a { @@file { "/tmp/foo": content => "fjskfjs\n", tag => "foofile", } } node b { File <<| tag == 'foofile' |>> } In my case, I have a about 20 nodes, each one having: @@nagios_host { $fqdn: tag => "nagiosserver.domain.tld", ... } @@nagios_service { "a": tag => "nagiosserver.domain.tld", ... } @@nagios_service { "b": tag => "nagiosserver.domain.tld", ... } @@nagios_service { "c": tag => "nagiosserver.domain.tld", ... } @@nagios_service { "d": tag => "nagiosserver.domain.tld", ... } @@nagios_service { "e": tag => "nagiosserver.domain.tld", ... } I suspect the problem occurs when many exported resources are involved (if 20x5 can be considered many). The problem happens when running puppet on a node containing: Nagios_host <<| tag == "nagiosserver.domain.tld" |>> Nagios_service <<| tag == nagiosserver.domain.tld" |>> On the puppetmaster, one ruby process consumes 100% CPU during a few minutes, then the client says: err: Could not call puppetmaster.getconfig: # err:
with passenger edit asked 2016-06-23 10:02:49 -0500 Reedler 1 ●1 updated 2016-06-25 10:56:36 -0500 Alex Harvey 2182 ●2 ●9 ●27 http://razorconsulting... Brand new install versions below. ruby 2.0.0p598 (2014-11-13) [x86_64-linux] puppet 4.5.2 Phusion Passenger 5.0.29 CentOS Linux release 7.2.1511 (Core) Followed the latest documentation here. https://docs.puppet.com/puppet/latest... When I stop puppetserver and start httpd I can see the netstat listening tcp6 0 0 :::8140 :::* LISTEN 5908/httpd** When I run puppet https://projects.puppetlabs.com/issues/2691 agent --test on the node Error: Could not request certificate: Error 500 on SERVER: ** In the httpd error log I get Error ID: 59e3b2be Error details saved to: /tmp/passenger-error-VEvXNv.html Message from application: cannot load such file -- puppet/util/command_line (LoadError) There is no passenger log in the /tmp dir to view The paths in https://ask.puppet.com/question/26798/could-not-request-certificate-issue-with-passenger/ the /etc/httpd/conf.d/puppetmaster.conf to my certs and logs are correct. When I stop httpd and start the puppetserver I can check in a node just fine. edit retag flag offensive close merge delete CommentsAny movement on this issue?Reedler( 2016-07-25 08:23:43 -0500 )editadd a comment Be the first one to answer this question! Please start posting anonymously - your entry will be published after you log in or create a new account. Add Answer Question Tools Follow subscribe to rss feed Stats Asked: 2016-06-23 10:02:49 -0500 Seen: 72 times Last updated: Jun 25 Overview Product Solutions Resource Library Company Open Source Projects Security Resources Get Help Find a Partner Training Downloads Site Map Connect Contact Us Events Blog Join our newsletter Join up and get notified about new products, updates, and special offers. Legal Privacy Policy Terms of Use © 2016 Puppet Please note: AskPuppet requires javascript to work properly, please enable javascript in your browser, here is how ( 2016-10-24 17:26:38 -0500 )editnone×
I'm rebuilding - ubuntu 12.04.2 LTS.After fiddling http://grokbase.com/t/gg/puppet-users/133t79hxsy/ruby-rack-application-could-not-be-started / tweaking / reading docs<http://docs.puppetlabs.com/guides/passenger.html>for hours now and I am reduced to hair-pulling frustration.I'm endeavoring to install 3.1.1 (3.0.2 http://serverfault.com/questions/455299/passengermod-rails-fails-to-start-puppet-master-under-nginx on the old server) and I'm getting "Ruby(Rack) application could not be started<http://thinkwelldesigns.com/errors2.html>"errors. I updated my config.ru <http://thinkwelldesigns.com/config.txt>file with the 3.1source<https://github.com/puppetlabs/puppet/blob/master/ext/rack/files/config.ru>.1. I'm not getting errors in the /var/log/apache2/errors.log as the errormessage hints I should.2. I tried my certs from my backup.3. I tried recreating server certs, but no change.I don't manage my puppet master with puppet, so puppet passenger error I came on this discoveryvery late. For whatever it's worth.1. Installed puppet agent on the puppet master.2. Ran puppet agent -t to generate an agent certificate3. Get this error:Error: Could not request certificate: Error 500 on SERVER:
Internal Server Error
The server encountered an internal error ormisconfiguration and was unable to completeyour request.
Please contact the server administrator,[no address given] and inform them of the time the error occurred,and anything you might have done that may havecaused the error.
More information about this error may be availablein the server error log.
Apache/2.2.22 (Ubuntu) Server at puppet Port 8140here is my gem list which shows rack is installed.*** LOCAL GEMS ***activemodel (3.2.13)activerecord (3.2.13)activesupport (3.2.13)arel (3.0.2)builder (3.0.4)daemon_controller (1.1.2)fastthread (1.0.7)i18n (0.6.1)multi_json (1.7.2)passenger (3.0.19)rack (1.5.2)
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top passenger(mod_rails) fails to start puppet master under nginx up vote 3 down vote favorite On the server [root@bangvmpllDA02 logs]# ruby -v ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@bangvmpllDA02 logs]# puppet --version 3.0.1 and [root@bangvmpllDA02 logs]# service nginx configtest nginx: the configuration file /apps/nginx/nginx.conf syntax is ok nginx: configuration file /apps/nginx/nginx.conf test is successful [root@bangvmpllDA02 logs]# service nginx status nginx (pid 25923 25921 25920 25917 25908) is running... [root@bangvmpllDA02 logs]# however none of my agents are able to connect to the master, they all fail with errors like so [amisr1@blramisr195602 ~]$ puppet agent --test --verbose --server bangvmpllda02.XXX.com Info: Creating a new SSL certificate request for blramisr195602.XXX.com Info: Certificate Request fingerprint (SHA256): 26:EB:08:1F:82:32:E4:03:7A:64:8E:30:A3:99:93:26:E6:66:B9:B0:49:B6:08:F9:67:CA:1B:0C:00:B9:1D:41 Error: Could not request certificate: Error 405 on SERVER: