puppet client could not request certificate: Error 500 on SERVER

5,063 views
Skip to first unread message

hyzhang

unread,
Mar 30, 2011, 2:00:56 PM3/30/11
to Puppet Users
Hi, I am new to puppet.

I have puppet server set up with passenger. But when I start puppetd
from client, I see following error in the syslog file:
Mar 30 13:52:03 puppetclient1 puppet-agent[29732]: Could not request
certificate: Error 500 on SERVER: <!DOCTYPE HTML PUBLIC "-//W3C//DTD
HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html>
<head> <meta http-equiv="Content-Type" content="text/html;
charset=UTF-8"> <meta name="generator" content="Phusion
Passenger"> <title>Ruby (Rack) application could not be started</
title> ....

I see puppetd process from the client
#ps -ef|grep puppet
root 28571 1 0 Mar29 ? 00:00:07 /usr/bin/ruby /usr/
sbin/puppetd --server=puppet-dev.jcvi.org --logdest=syslog

Can anyone tell me what the problem is here?

Thanks,
-Haiyan

Hugo Cisneiros (Eitch)

unread,
Mar 30, 2011, 2:38:40 PM3/30/11
to puppet...@googlegroups.com
On Wed, Mar 30, 2011 at 3:00 PM, hyzhang <hyz...@jcvi.org> wrote:
Hi, I am new to puppet.

I have puppet server set up with passenger. But when I start puppetd
from client, I see following error in the syslog file:
Mar 30 13:52:03 puppetclient1 puppet-agent[29732]: Could not request
certificate: Error 500 on SERVER: <!DOCTYPE HTML PUBLIC "-//W3C//DTD
HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html>
<head>         <meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">     <meta name="generator" content="Phusion
Passenger">     <title>Ruby (Rack) application could not be started</
title> ....


You didn't paste the most important part of the error. Thie page ruby/rack generates usually have some pretty useful information in an error field. Like a module missing on an import/require, permission problems, and so on. Please identify and post the error so we can be helpful :)
 
--
[]'s
Hugo
www.devin.com.br

hyzhang

unread,
Mar 30, 2011, 3:02:43 PM3/30/11
to Puppet Users
Thank. I am pasting the entire message here:

Mar 30 14:01:04 puppetclient1 puppet-agent[28571]: Could not request
certificate: Error 500 on SERVER: <!DOCTYPE HTML PUBLIC "-//W3C//DTD
HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html>
<head> <meta http-equiv="Content-Type" content="text/html;
charset=UTF-8"> <meta name="generator" content="Phusion
Passenger"> <title>Ruby (Rack) application could not be started</
title> <style type="text/css"> body { font-
family: Verdana, 'Bitstream Vera Sans', Arial, Sans-Serif;
font-size: 10pt; background: white; color:
#222222; margin: 0; padding-top: 3em; padding-
bottom: 3em; padding-left: 4.5em; padding-right: 4.5em; } h1
{ font-size: 17pt; font-weight: medium; color:
#533e72; border-bottom: 1px solid #533e72; } h1.title
{ margin-top: 0; } h1.error_title { color: red;
border-bottom: 1px solid red; } a { text-decoration: none; }
a:hover { text-decoration: underline; } dt { font-weight:
bold; color: #280050; } dd { margin-top: 0.5em;
margin-bottom: 1em; } .commands { border: 1px

Somehow I am able to get the certificate for the client. Since above
error message says "Ruby (Rack) application could not be started", I
did
#rackup /usr/share/puppet/rack/puppetmasterd/config.ru
Then I see the rack process on puppet server
#ps -ef|grep rack
puppet 27140 1 0 14:21 ? 00:00:00 Rack: /usr/share/
puppet/rack/puppetmasterd

From then on the server is able to receive the client certificate
request and sign it.

Do I have to start the rack manually in a manner like that? I thought
if I start httpd service, it would start rack automatically.

I am still not sure if I did everything right.

Thanks,
-Haiyan






On Mar 30, 2:38 pm, "Hugo Cisneiros (Eitch)"
<hugo.cisnei...@gmail.com> wrote:

Cody Robertson

unread,
Apr 2, 2011, 2:44:37 PM4/2/11
to puppet...@googlegroups.com
No that's not normal - you shouldn't have to manually start the start the master like that.. it sounds like your setup is goofy - can you provide logs from the actual server? The portion you provided us is simple the result of the web server saying there is no backend / the backend crashed / the backend isn't responding.

There should be more useful logs in the web servers error logs or the masters error logs.

If everything works when you startup the master manually via rack it seems like the issue lies in your passenger / apache setup.

Stuart Cracraft

unread,
Aug 19, 2012, 1:56:51 PM8/19/12
to puppet...@googlegroups.com
I am seriously thinking of putting those recursive chown's in root crontab on puppet masters and puppet agents for /etc/puppet* and 
/var/lib/puppet*

I shouldn't have to do this but have 
seen cases of ownership reversion. 


--Stuart

Via Apple iPhone 4S on the AT&T Wireless Network


On Aug 13, 2012, at 3:04 AM, Frederik Vos <inkt...@gmail.com> wrote:

For the people still looking for an answer:
chown -R puppet:puppet /var/lib/puppet/reports

Op woensdag 30 maart 2011 21:02:43 UTC+2 schreef hyzhang het volgende:

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ltKL6JvCWQEJ.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Jo Rhett

unread,
Aug 20, 2012, 4:03:02 PM8/20/12
to puppet...@googlegroups.com
You should spend some time and determine how and why that is happening. I can assure you that it's not normal, so this is something specific to some custom code on your site.
-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.



Mark Christian

unread,
Aug 20, 2012, 4:11:36 PM8/20/12
to puppet...@googlegroups.com
Have you confirmed that puppet master is running as user = puppet?

On the master check: puppet --genconfig|grep user

Mark
Confidentiality Notice.
This message may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, or copying of this message, or any attachments, is strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail, and delete the message and any attachments. Thank you.

Reply all
Reply to author
Forward
0 new messages