[master] reports = log, store, http reporturl = https://puppet-test.uis.example.com/reports/upload am running dashboar in the same host as puppetmaster, which is puppet-test, both behind apache/phusion. reports fail and master logs: Report http failed: wrong status line: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">" How can I furthe rdebug this? am using dashboard for a github checkout and puppet 2.6.3 Thanks a lot. Mohamed. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Mohamed Lrhazi
2011-Mar-22 04:28 UTC
[Puppet Users] Re: Error sending reports to dashboard
If I run the dash-board directly, with built-in web-server, on default port, and remove the reporturl , reports are posted successfully! Any idea what I am missing for a behind apache/Phusion setup? Thanks a lot. Mohamed. On Mon, Mar 21, 2011 at 7:12 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote:> [master] > reports = log, store, http > reporturl = https://puppet-test.uis.example.com/reports/upload > > am running dashboar in the same host as puppetmaster, which is > puppet-test, both behind apache/phusion. > > reports fail and master logs: > > Report http failed: wrong status line: "<!DOCTYPE HTML PUBLIC > \"-//IETF//DTD HTML 2.0//EN\">" > > How can I furthe rdebug this? am using dashboard for a github checkout > and puppet 2.6.3 > > > Thanks a lot. > Mohamed. >-- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Mohamed Lrhazi
2011-Mar-22 04:41 UTC
[Puppet Users] Re: Error sending reports to dashboard
I enabled debug log level in apache virtual and it seems like puppetmaster is trying to speak http, instead of https. Is https not supported for posting reports? [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1819): OpenSSL: read 11/11 bytes from BIO#2b225d284100 [mem: 2b225d2f9650] (BIO dump follows) [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1766): +-------------------------------------------------------------------------+ [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1791): | 0000: 50 4f 53 54 20 2f 72 65-70 6f 72 POST /repor | [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1797): +-------------------------------------------------------------------------+ [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_kernel.c(1838): OpenSSL: Exit: error in SSLv2/v3 read client hello A [Tue Mar 22 00:39:43 2011] [info] [client 141.161.245.113] SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page [Tue Mar 22 00:39:43 2011] [info] SSL Library Error: 336027804 error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request speaking HTTP to HTTPS port!? On Tue, Mar 22, 2011 at 12:28 AM, Mohamed Lrhazi <lrhazi@gmail.com> wrote:> If I run the dash-board directly, with built-in web-server, on default > port, and remove the reporturl , reports are posted successfully! > > Any idea what I am missing for a behind apache/Phusion setup? > > Thanks a lot. > Mohamed. > > On Mon, Mar 21, 2011 at 7:12 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote: >> [master] >> reports = log, store, http >> reporturl = https://puppet-test.uis.example.com/reports/upload >> >> am running dashboar in the same host as puppetmaster, which is >> puppet-test, both behind apache/phusion. >> >> reports fail and master logs: >> >> Report http failed: wrong status line: "<!DOCTYPE HTML PUBLIC >> \"-//IETF//DTD HTML 2.0//EN\">" >> >> How can I furthe rdebug this? am using dashboard for a github checkout >> and puppet 2.6.3 >> >> >> Thanks a lot. >> Mohamed. >> >-- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Bump. Anyone know the answer? Can puppet use https to post reports? I''m having trouble sending reports using https too, although I haven''t yet found anything useful in the logs. On Mar 21, 2011, at 9:41 PM, Mohamed Lrhazi wrote:> I enabled debug log level in apache virtual and it seems like > puppetmaster is trying to speak http, instead of https. > Is https not supported for posting reports? > > [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1819): OpenSSL: > read 11/11 bytes from BIO#2b225d284100 [mem: 2b225d2f9650] (BIO dump > follows) > [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1766): > +-------------------------------------------------------------------------+ > [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1791): | 0000: 50 > 4f 53 54 20 2f 72 65-70 6f 72 POST /repor | > [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1797): > +-------------------------------------------------------------------------+ > [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_kernel.c(1838): OpenSSL: > Exit: error in SSLv2/v3 read client hello A > [Tue Mar 22 00:39:43 2011] [info] [client 141.161.245.113] SSL > handshake failed: HTTP spoken on HTTPS port; trying to send HTML error > page > [Tue Mar 22 00:39:43 2011] [info] SSL Library Error: 336027804 > error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request > speaking HTTP to HTTPS port!? > > > > On Tue, Mar 22, 2011 at 12:28 AM, Mohamed Lrhazi <lrhazi@gmail.com> wrote: >> If I run the dash-board directly, with built-in web-server, on default >> port, and remove the reporturl , reports are posted successfully! >> >> Any idea what I am missing for a behind apache/Phusion setup? >> >> Thanks a lot. >> Mohamed. >> >> On Mon, Mar 21, 2011 at 7:12 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote: >>> [master] >>> reports = log, store, http >>> reporturl = https://puppet-test.uis.example.com/reports/upload >>> >>> am running dashboar in the same host as puppetmaster, which is >>> puppet-test, both behind apache/phusion. >>> >>> reports fail and master logs: >>> >>> Report http failed: wrong status line: "<!DOCTYPE HTML PUBLIC >>> \"-//IETF//DTD HTML 2.0//EN\">" >>> >>> How can I furthe rdebug this? am using dashboard for a github checkout >>> and puppet 2.6.3 >>> >>> >>> Thanks a lot. >>> Mohamed. >>> >> > > -- > 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 puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Mohamed Lrhazi
2011-Apr-11 16:55 UTC
Re: [Puppet Users] Re: Error sending reports to dashboard
I did not find any reference.... I just added a second apache virtual server to do http on port 80. On Mon, Apr 11, 2011 at 12:14 PM, Patrick <kc7zzv@gmail.com> wrote:> Bump. Anyone know the answer? Can puppet use https to post reports? I''m having trouble sending reports using https too, although I haven''t yet found anything useful in the logs. > > On Mar 21, 2011, at 9:41 PM, Mohamed Lrhazi wrote: > >> I enabled debug log level in apache virtual and it seems like >> puppetmaster is trying to speak http, instead of https. >> Is https not supported for posting reports? >> >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1819): OpenSSL: >> read 11/11 bytes from BIO#2b225d284100 [mem: 2b225d2f9650] (BIO dump >> follows) >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1766): >> +-------------------------------------------------------------------------+ >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1791): | 0000: 50 >> 4f 53 54 20 2f 72 65-70 6f 72 POST /repor | >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1797): >> +-------------------------------------------------------------------------+ >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_kernel.c(1838): OpenSSL: >> Exit: error in SSLv2/v3 read client hello A >> [Tue Mar 22 00:39:43 2011] [info] [client 141.161.245.113] SSL >> handshake failed: HTTP spoken on HTTPS port; trying to send HTML error >> page >> [Tue Mar 22 00:39:43 2011] [info] SSL Library Error: 336027804 >> error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request >> speaking HTTP to HTTPS port!? >> >> >> >> On Tue, Mar 22, 2011 at 12:28 AM, Mohamed Lrhazi <lrhazi@gmail.com> wrote: >>> If I run the dash-board directly, with built-in web-server, on default >>> port, and remove the reporturl , reports are posted successfully! >>> >>> Any idea what I am missing for a behind apache/Phusion setup? >>> >>> Thanks a lot. >>> Mohamed. >>> >>> On Mon, Mar 21, 2011 at 7:12 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote: >>>> [master] >>>> reports = log, store, http >>>> reporturl = https://puppet-test.uis.example.com/reports/upload >>>> >>>> am running dashboar in the same host as puppetmaster, which is >>>> puppet-test, both behind apache/phusion. >>>> >>>> reports fail and master logs: >>>> >>>> Report http failed: wrong status line: "<!DOCTYPE HTML PUBLIC >>>> \"-//IETF//DTD HTML 2.0//EN\">" >>>> >>>> How can I furthe rdebug this? am using dashboard for a github checkout >>>> and puppet 2.6.3 >>>> >>>> >>>> Thanks a lot. >>>> Mohamed. >>>> >>> >> >> -- >> 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 puppet-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >> > > -- > 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 puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Felix Frank
2011-Apr-12 07:12 UTC
Re: [Puppet Users] Re: Error sending reports to dashboard
On 04/11/2011 06:55 PM, Mohamed Lrhazi wrote:> I did not find any reference.... I just added a second apache virtual > server to do http on port 80. > > On Mon, Apr 11, 2011 at 12:14 PM, Patrick <kc7zzv@gmail.com> wrote: >> Bump. Anyone know the answer? Can puppet use https to post reports? I''m having trouble sending reports using https too, although I haven''t yet found anything useful in the logs.Hi, I''m clueless, but from a technical angle, you can use another workaround if you need your reports to be encrypted en route. Use a local HTTP reporturl, have stunnel listen to the local HTTP port and connect to the remote HTTPS. The agent can speak HTTP while the dashboard should dutifully receive HTTPS. HTH, Felix -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Cody Robertson
2011-Apr-14 22:54 UTC
[Puppet Users] Re: Error sending reports to dashboard
Although I don''t know the answer I''m curious as to why you''re worried about using HTTPS when you''re sending the reports locally? There is no need to encrypt the ports if you''re just sending them to the same machine / localhost. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Mohamed Lrhazi
2011-Apr-15 02:19 UTC
Re: [Puppet Users] Re: Error sending reports to dashboard
Sure. but if you already configured access to puppetmaster on HTTPS, it would be nice to use it, instead of adding and maintaining another setup for HTTP access. On Thu, Apr 14, 2011 at 6:54 PM, Cody Robertson <cody@hawkhost.com> wrote:> Although I don''t know the answer I''m curious as to why you''re worried about > using HTTPS when you''re sending the reports locally? There is no need to > encrypt the ports if you''re just sending them to the same machine / > localhost. > > -- > 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 > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Apr 14, 2011, at 3:54 PM, Cody Robertson wrote:> Although I don''t know the answer I''m curious as to why you''re worried about using HTTPS when you''re sending the reports locally? There is no need to encrypt the ports if you''re just sending them to the same machine / localhost.In my case, I wanted to run dashboard using SSL (for when I connect remotely, so the passwords aren''t in cleartext). It would have been easier for me if I was able to set the only instance of dashboard (set of instances?) running under passenger to be SSL. I understand this would have been a waste of CPU, but I believe the difference in CPU usage would have been negligible. A real case that might eventually happen is this is if I use authentication on sending reports, and the puppetmaster sending the report isn''t on the same lan. I''ll admit it doesn''t help if send to "localhost" but I consider that beside the point. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
My point exactly for now, though there are reasons to send reports over HTTPS that I mentioned in my response. On Apr 14, 2011, at 7:19 PM, Mohamed Lrhazi wrote:> Sure. but if you already configured access to puppetmaster on HTTPS, > it would be nice to use it, instead of adding and maintaining another > setup for HTTP access. > > On Thu, Apr 14, 2011 at 6:54 PM, Cody Robertson <cody@hawkhost.com> wrote: >> Although I don''t know the answer I''m curious as to why you''re worried about >> using HTTPS when you''re sending the reports locally? There is no need to >> encrypt the ports if you''re just sending them to the same machine / >> localhost.-- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Michael Altfield
2012-Jun-15 16:28 UTC
Re: [Puppet Users] Re: Error sending reports to dashboard
Hi, I''m also having this issue running puppet-2.7.16 & puppet-dashboard-1.2.9 on CentOS 6.2. Has there been any solution to this yet besides running redundant vhosts? In either case, can you please post your apache vhost configuration files? On Monday, April 11, 2011 12:55:10 PM UTC-4, Mohamed wrote:> > I did not find any reference.... I just added a second apache virtual > server to do http on port 80. > > On Mon, Apr 11, 2011 at 12:14 PM, Patrick <k@gmail.com> wrote: > > Bump. Anyone know the answer? Can puppet use https to post reports? > I''m having trouble sending reports using https too, although I haven''t yet > found anything useful in the logs. > > > > On Mar 21, 2011, at 9:41 PM, Mohamed Lrhazi wrote: > > > >> I enabled debug log level in apache virtual and it seems like > >> puppetmaster is trying to speak http, instead of https. > >> Is https not supported for posting reports? > >> > >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1819): OpenSSL: > >> read 11/11 bytes from BIO#2b225d284100 [mem: 2b225d2f9650] (BIO dump > >> follows) > >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1766): > >> > +-------------------------------------------------------------------------+ > >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1791): | 0000: 50 > >> 4f 53 54 20 2f 72 65-70 6f 72 POST /repor | > >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1797): > >> > +-------------------------------------------------------------------------+ > >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_kernel.c(1838): OpenSSL: > >> Exit: error in SSLv2/v3 read client hello A > >> [Tue Mar 22 00:39:43 2011] [info] [client 141.161.245.113] SSL > >> handshake failed: HTTP spoken on HTTPS port; trying to send HTML error > >> page > >> [Tue Mar 22 00:39:43 2011] [info] SSL Library Error: 336027804 > >> error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request > >> speaking HTTP to HTTPS port!? > >> > >> > >> > >> On Tue, Mar 22, 2011 at 12:28 AM, Mohamed Lrhazi <l@gmail.com> wrote: > >>> If I run the dash-board directly, with built-in web-server, on default > >>> port, and remove the reporturl , reports are posted successfully! > >>> > >>> Any idea what I am missing for a behind apache/Phusion setup? > >>> > >>> Thanks a lot. > >>> Mohamed. > >>> > >>> On Mon, Mar 21, 2011 at 7:12 PM, Mohamed Lrhazi <l@gmail.com> wrote: > >>>> [master] > >>>> reports = log, store, http > >>>> reporturl = https://puppet-test.uis.example.com/reports/upload > >>>> > >>>> am running dashboar in the same host as puppetmaster, which is > >>>> puppet-test, both behind apache/phusion. > >>>> > >>>> reports fail and master logs: > >>>> > >>>> Report http failed: wrong status line: "<!DOCTYPE HTML PUBLIC > >>>> \"-//IETF//DTD HTML 2.0//EN\">" > >>>> > >>>> How can I furthe rdebug this? am using dashboard for a github checkout > >>>> and puppet 2.6.3 > >>>> > >>>> > >>>> Thanks a lot. > >>>> Mohamed. > >>>> > >>> > >> > >> -- > >> 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 > puppet-users+unsubscribe@googlegroups.com. > >> For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >> > > > > -- > > 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 > puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > > > >-- 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/-/wwnktt7LihAJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Michael, I would configure report delivery via http and user access via https. Simple "Allow" rules for your host netblocks plus a rewrite to https based on the browser-agent would meet your needs. It WFM ;-) On Jun 15, 2012, at 9:28 AM, Michael Altfield wrote:> I''m also having this issue running puppet-2.7.16 & puppet-dashboard-1.2.9 on CentOS 6.2. Has there been any solution to this yet besides running redundant vhosts? > > In either case, can you please post your apache vhost configuration files? > > On Monday, April 11, 2011 12:55:10 PM UTC-4, Mohamed wrote: > I did not find any reference.... I just added a second apache virtual > server to do http on port 80. > On Mon, Apr 11, 2011 at 12:14 PM, Patrick <k@gmail.com> wrote: > > Bump. Anyone know the answer? Can puppet use https to post reports? I''m having trouble sending reports using https too, although I haven''t yet found anything useful in the logs. > > > > On Mar 21, 2011, at 9:41 PM, Mohamed Lrhazi wrote: > > > >> I enabled debug log level in apache virtual and it seems like > >> puppetmaster is trying to speak http, instead of https. > >> Is https not supported for posting reports? > >> > >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1819): OpenSSL: > >> read 11/11 bytes from BIO#2b225d284100 [mem: 2b225d2f9650] (BIO dump > >> follows) > >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1766): > >> +-------------------------------------------------------------------------+ > >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1791): | 0000: 50 > >> 4f 53 54 20 2f 72 65-70 6f 72 POST /repor | > >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1797): > >> +-------------------------------------------------------------------------+ > >> [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_kernel.c(1838): OpenSSL: > >> Exit: error in SSLv2/v3 read client hello A > >> [Tue Mar 22 00:39:43 2011] [info] [client 141.161.245.113] SSL > >> handshake failed: HTTP spoken on HTTPS port; trying to send HTML error > >> page > >> [Tue Mar 22 00:39:43 2011] [info] SSL Library Error: 336027804 > >> error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request > >> speaking HTTP to HTTPS port!? > >> > >> > >> > >> On Tue, Mar 22, 2011 at 12:28 AM, Mohamed Lrhazi <l@gmail.com> wrote: > >>> If I run the dash-board directly, with built-in web-server, on default > >>> port, and remove the reporturl , reports are posted successfully! > >>> > >>> Any idea what I am missing for a behind apache/Phusion setup? > >>> > >>> Thanks a lot. > >>> Mohamed. > >>> > >>> On Mon, Mar 21, 2011 at 7:12 PM, Mohamed Lrhazi <l@gmail.com> wrote: > >>>> [master] > >>>> reports = log, store, http > >>>> reporturl = https://puppet-test.uis.example.com/reports/upload > >>>> > >>>> am running dashboar in the same host as puppetmaster, which is > >>>> puppet-test, both behind apache/phusion. > >>>> > >>>> reports fail and master logs: > >>>> > >>>> Report http failed: wrong status line: "<!DOCTYPE HTML PUBLIC > >>>> \"-//IETF//DTD HTML 2.0//EN\">" > >>>> > >>>> How can I furthe rdebug this? am using dashboard for a github checkout > >>>> and puppet 2.6.3 > >>>> > >>>> > >>>> Thanks a lot. > >>>> Mohamed. > >>>> > >>> > >> > >> -- > >> 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 puppet-users+unsubscribe@googlegroups.com. > >> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >> > > > > -- > > 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 puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > > > > > > > -- > 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/-/wwnktt7LihAJ. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.-- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi,
In your puppet.conf, change :
[master]
reports = log, store, http*s*
reporturl =
https://puppet-test.uis.example.com:443/reports/upload<https://puppet-test.uis.example.com/reports/upload>
Then add in your reports folder (under debian with puppetlabs packets) ;
/usr/lib/ruby/1.8/puppet/reports/https.rb :
require ''puppet''
require ''net/http''
require ''net/https''
require ''uri''
Puppet::Reports.register_report(:https) do
desc <<-DESC
Send report information via HTTPS to the `reporturl`. Each host sends
its report as a YAML dump and this sends this YAML to a client via HTTPS
POST.
The YAML is the `report` parameter of the request."
DESC
def process
url = URI.parse(Puppet[:reporturl].to_s)
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
http.verify_mode = OpenSSL::SSL::VERIFY_NONE
req = Net::HTTP::Post.new(url.path)
req.body = self.to_yaml
req.content_type = "application/x-yaml"
http.start do |http|
response = http.request(req)
unless response.code == "200"
Puppet.err "Unable to submit report to #{Puppet[:reporturl].to_s}
[#{response.code}] #{response.msg}"
end
end
end
end
Found in the VM Labs shipped by puppetlabs.
Julien
>
--
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/-/W-0uWK3waMoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Cosmo Valentine
2012-Sep-10 10:02 UTC
[Puppet Users] Re: Error sending reports to dashboard
Julien, Thanks, this solved the issue for me. We had the puppet dashboard running on a separate host to the Puppet masters. The puppet masters were trying to send the reports to the Dashboard using HTTP when the dashboard comes configured for HTTPS. So I copied the /opt/puppet/lib/ruby/site_ruby/1.8/puppet/reports/https.rb file (path may different for other people) from the dashboard host to the puppet masters and changed puppet.conf report settings to HTTPS and then it worked perfectly. Cheers, Cosmo On Wednesday, July 4, 2012 2:13:49 PM UTC+1, Julien wrote:> > Hi, > > In your puppet.conf, change : > > [master] > reports = log, store, http*s* > reporturl = https://puppet-test.uis.example.com:443/reports/upload<https://puppet-test.uis.example.com/reports/upload> > > Then add in your reports folder (under debian with puppetlabs packets) ; > > /usr/lib/ruby/1.8/puppet/reports/https.rb : > > require ''puppet'' > require ''net/http'' > require ''net/https'' > require ''uri'' > > Puppet::Reports.register_report(:https) do > > desc <<-DESC > Send report information via HTTPS to the `reporturl`. Each host sends > its report as a YAML dump and this sends this YAML to a client via HTTPS > POST. > The YAML is the `report` parameter of the request." > DESC > > def process > url = URI.parse(Puppet[:reporturl].to_s) > http = Net::HTTP.new(url.host, url.port) > http.use_ssl = true > http.verify_mode = OpenSSL::SSL::VERIFY_NONE > > req = Net::HTTP::Post.new(url.path) > req.body = self.to_yaml > req.content_type = "application/x-yaml" > > http.start do |http| > response = http.request(req) > unless response.code == "200" > Puppet.err "Unable to submit report to #{Puppet[:reporturl].to_s} > [#{response.code}] #{response.msg}" > end > end > > end > end > > Found in the VM Labs shipped by puppetlabs. > > Julien > >>-- 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/-/YyTdCP-eJFgJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I wanted to configure the puppet dashboard to require authentication of
client certs and had to modify the previous script to get it to send the
client certificate. I also adjusted it to use the puppet CA cert to verify
the remote server as well. Simple changes, but providing it in case anyone
else wants to lock down their dashboard (or other report collector).
It uses the cert settings as configured in puppet.conf.
require ''puppet''
require ''net/http''
require ''net/https''
require ''uri''
Puppet::Reports.register_report(:https) do
desc <<-DESC
Send report information via HTTPS to the `reporturl`. Each host sends
its report as a YAML dump and this sends this YAML to a client via HTTPS
POST.
The YAML is the `report` parameter of the request."
DESC
def process
url = URI.parse(Puppet[:reporturl].to_s)
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
http.cert =
OpenSSL::X509::Certificate.new(File.read(Puppet[:hostcert].to_s))
http.key = OpenSSL::PKey::RSA.new(File.read(Puppet[:hostprivkey].to_s))
http.ca_file = Puppet[:localcacert].to_s
http.verify_mode = OpenSSL::SSL::VERIFY_PEER
req = Net::HTTP::Post.new(url.path)
req.body = self.to_yaml
req.content_type = "application/x-yaml"
http.start do |http|
response = http.request(req)
unless response.code == "200"
Puppet.err "Unable to submit report to #{Puppet[:reporturl].to_s}
[#{response.code}] #{response.msg}"
end
end
end
end
On Wednesday, July 4, 2012 9:13:49 AM UTC-4, Julien
wrote:>
> Hi,
>
> In your puppet.conf, change :
>
> [master]
> reports = log, store, http*s*
> reporturl =
https://puppet-test.uis.example.com:443/reports/upload<https://puppet-test.uis.example.com/reports/upload>
>
> Then add in your reports folder (under debian with puppetlabs packets) ;
>
> /usr/lib/ruby/1.8/puppet/reports/https.rb :
>
> require ''puppet''
> require ''net/http''
> require ''net/https''
> require ''uri''
>
> Puppet::Reports.register_report(:https) do
>
> desc <<-DESC
> Send report information via HTTPS to the `reporturl`. Each host sends
> its report as a YAML dump and this sends this YAML to a client via HTTPS
> POST.
> The YAML is the `report` parameter of the request."
> DESC
>
> def process
> url = URI.parse(Puppet[:reporturl].to_s)
> http = Net::HTTP.new(url.host, url.port)
> http.use_ssl = true
> http.verify_mode = OpenSSL::SSL::VERIFY_NONE
>
> req = Net::HTTP::Post.new(url.path)
> req.body = self.to_yaml
> req.content_type = "application/x-yaml"
>
> http.start do |http|
> response = http.request(req)
> unless response.code == "200"
> Puppet.err "Unable to submit report to
#{Puppet[:reporturl].to_s}
> [#{response.code}] #{response.msg}"
> end
> end
>
> end
> end
>
> Found in the VM Labs shipped by puppetlabs.
>
> Julien
>
>>
--
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/-/QRlDKyvE3VUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.