[Puppet Users] Couldn't worked reports in last foreman snapshot's (09.28.10)

2010-09-29 Thread koliama
Hello all,
I upgrade my foreman from last snapshot's in testing env. When I click
on "Reports" or "host name" url I see error message in foreman
error_log:

=> Booting WEBrick
=> Rails 2.3.5 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
[2010-09-29 16:35:46] INFO  WEBrick 1.3.1
[2010-09-29 16:35:46] INFO  ruby 1.8.7 (2009-06-08) [i386-linux]
[2010-09-29 16:35:46] INFO  WEBrick::HTTPServer#start: pid=13573
port=3000


Processing HostsController#index (for 172.30.64.135 at 2010-09-29
16:35:49) [GET]
  Parameters: {"action"=>"index", "controller"=>"hosts"}
Rendering template within layouts/standard
Rendering hosts/index
Completed in 233ms (View: 101, DB: 11) | 200 OK [http://srv2-puppet/]


Processing HostsController#show (for 172.30.64.135 at 2010-09-29
16:35:51) [GET]
  Parameters: {"action"=>"show", "id"=>"srv-redhat.net.billing.ru",
"controller"=>"hosts"}

NoMethodError (undefined method `round_with_precision' for 0:Fixnum):
  app/models/report.rb:68:in `config_retrieval'
  app/models/host.rb:394:in `graph'
  app/models/host.rb:393:in `graph'
  app/controllers/hosts_controller.rb:28:in `show'
  app/controllers/hosts_controller.rb:22:in `show'
  /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
  /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
  /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
  /usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
  /usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
  /usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:82:in `start'

Rendering /var/rails/foreman/public/500.html (500 Internal Server
Error)


Processing ReportsController#index (for 172.30.64.135 at 2010-09-29
16:36:15) [GET]
  Parameters: {"action"=>"index", "controller"=>"reports"}
Rendering template within layouts/standard
Rendering reports/index

ActionView::TemplateError (undefined method `round_with_precision' for
0:Fixnum) on line #27 of app/views/reports/_list.html.erb:
24:   <%= h report.failed %>
25:   <%= h report.failed_restarts %>
26:   <%= h report.skipped %>
27:   <%= h report.config_retrieval %>
28:   <%= h report.runtime %>
29:   
30: <%= link_to "Details", report %>

app/models/report.rb:68:in `config_retrieval'
app/views/reports/_list.html.erb:27
app/views/reports/_list.html.erb:16:in `each'
app/views/reports/_list.html.erb:16
app/views/reports/index.html.erb:3
/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:82:in `start'

Rendering /var/rails/foreman/public/500.html (500 Internal Server
Error)

What's wrong?

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



[Puppet Users] Puppet+Foreman: class into module couldn't apply on nodes

2009-11-26 Thread koliama
Hello,
I try config puppet with foreman frontend. Into puppetmasterd I create
modules "test" and create init.pp:
# Create "/tmp/testfile" if it doesn't exist.
class test_class {
file { "/tmp/testfile":
   ensure => present,
   mode   => 644,
   owner  => root,
   group  => root
}
}
Configure nodes in site.pp and import module:
import "test"

node "srv2-svc8.net.billing.ru" {
include test_class
}

Run puppetmasterd and restart puppetd on node. File /tmp/testfile is
created.
Next time I configure foreman:
1. Untar in /var/rails/foreman
2. Run RAILS_ENV=production rake db:migrate
3. Run RAILS_ENV=production rake puppet:import:hosts_and_facts
(in /var/rails/foreman)
Importing from /var/puppet/yaml/facts
Importing srv2-svc8.net.billing.ru
4. Run rake puppet:import:puppet_classes --trace RAILS_ENV=production
(in /var/rails/foreman)
Environment   old:0current:1
PuppetClasses old:0 current:1
5. Start foreman: ./script/server -e production - OK
Into web-interface I see srv2-svc8 node with all facts, environment
"prodaction" and class "test_calss"
6. After this I create new host in Foreman web page. I include class
"test_calss" to new host. And I do not add new host in site.pp
manifest in puppet.
7. After restart puppetd on new node file /tmp/testfile is not
created :(

I don't understand - if I create host within foreman interface I all
the same should create node in site.pp and adhere class "test_class"
to it?

--

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




[Puppet Users] Re: Puppet+Foreman: class into module couldn't apply on nodes

2009-11-27 Thread koliama
Thanks, Ohad!
I will read documentation more attentively. After configure
puppetmasterd with use external node - all has worked fine.

On 27 ноя, 04:11, Ohad Levy  wrote:
> did you configure puppet to actually query foreman for node information?
> e.g.http://theforeman.org/wiki/foreman/External_Nodes#Example-puppet-exte...
>
> you can also have a look at this puppet module (which configures foreman 
> )http://theforeman.org/repositories/entry/foreman/extras/puppet/foreman
>
> the idea is that you don't need to define each of your nodes in the manifest
> anymore
>
> Ohad
>
> On Thu, Nov 26, 2009 at 11:18 PM, koliama  wrote:
> > Hello,
> > I try config puppet with foreman frontend. Into puppetmasterd I create
> > modules "test" and create init.pp:
> > # Create "/tmp/testfile" if it doesn't exist.
> > class test_class {
> >    file { "/tmp/testfile":
> >       ensure => present,
> >       mode   => 644,
> >       owner  => root,
> >       group  => root
> >    }
> > }
> > Configure nodes in site.pp and import module:
> > import "test"
>
> > node "srv2-svc8.net.billing.ru" {
> >    include test_class
> > }
>
> > Run puppetmasterd and restart puppetd on node. File /tmp/testfile is
> > created.
> > Next time I configure foreman:
> > 1. Untar in /var/rails/foreman
> > 2. Run RAILS_ENV=production rake db:migrate
> > 3. Run RAILS_ENV=production rake puppet:import:hosts_and_facts
> > (in /var/rails/foreman)
> > Importing from /var/puppet/yaml/facts
> > Importing srv2-svc8.net.billing.ru
> > 4. Run rake puppet:import:puppet_classes --trace RAILS_ENV=production
> > (in /var/rails/foreman)
> > Environment   old:0    current:1
> > PuppetClasses old:0     current:1
> > 5. Start foreman: ./script/server -e production - OK
> > Into web-interface I see srv2-svc8 node with all facts, environment
> > "prodaction" and class "test_calss"
> > 6. After this I create new host in Foreman web page. I include class
> > "test_calss" to new host. And I do not add new host in site.pp
> > manifest in puppet.
> > 7. After restart puppetd on new node file /tmp/testfile is not
> > created :(
>
> > I don't understand - if I create host within foreman interface I all
> > the same should create node in site.pp and adhere class "test_class"
> > to it?
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-us...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@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-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.




[Puppet Users] Couldn't see RRDReport in foreman

2009-12-19 Thread koliama
Hello,
I have configured puppet 0.25.1+passenger+foreman 0.1-3+ruby-rrdtools
(into fedora EPEL repository).
When I try to look RRDRoport link by host I see "Close Sorry, no
graphs for this host"
When I try to look Reports link I couldn't see anything. But when I
enter in adress bar "http:// mypuppethost/reports/host_fqdn/" - I see
rrd reports graph (Daily, Weekly, e.t.c)
How to configure puppet+foreman+apache for correct display puppet rrd
reports in foreman web interface?

My conf:
puppet.conf
[main]
external_nodes = /etc/puppet/node.rb
node_terminus  = exec
vardir = /var/puppet
logdir = $vardir/log
rundir = $vardir/run
ssldir = $vardir/ssl

[puppetmasterd]

reportdir = /var/puppet/reports
reports = log,store,tagmail,rrdgraph
tagmap = $confdir/tagmail.conf
rrddir = $vardir/rrd
rrdinternval = $runinterval
rrdgraph = true
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
autosign = /etc/puppet/autosign.conf
modulepath = /etc/puppet/modules

apache.conf
Listen 3000

ServerName puppet
DocumentRoot /var/rails/foreman/public/
ErrorLog /var/rails/foreman/log/error_log
LogLevel error

# Grant access to puppet reports
  Alias /reports/ /var/puppet/rrd/
  
PassengerEnabled off
Options Indexes
Order deny,allow
Allow from all
  


foreman settingc.yaml
---
:modulepath: /etc/puppet/modules/
:rrd_report_url: reports/
:puppet_server: srv2-puppet

--

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




[Puppet Users] Re: Couldn't see RRDReport in foreman

2009-12-20 Thread koliama
Yes, I configured reporting in Foreman:

puppet.conf
report = log,store,tagmail,rrdgraph,foreman

Copy file foreman-report.rb into dir /usr/lib/ruby/site_ruby/1.8/
puppet/reports/foreman.rb and as edited
$foreman_url = "http://mypuppethost";
After this restart Apache - is the same result. RRDReports are not
displayed in Foreman web page :(

On 20 дек, 03:56, Ohad Levy  wrote:
> Did you enable reporting in Foreman? - 
> e.g.http://theforeman.org/wiki/foreman/Puppet_Reports
>
> I'm planning to generate all of the graphs within Foreman (no need to use
> RRD anymore) soon (that is when I'll come back from Xmas vacation ), so
> hopefully this wont be required and will look much nicer.
>
> Cheers,
> Ohad
>
> On Sun, Dec 20, 2009 at 6:15 AM, koliama  wrote:
> > Hello,
> > I have configured puppet 0.25.1+passenger+foreman 0.1-3+ruby-rrdtools
> > (into fedora EPEL repository).
> > When I try to look RRDRoport link by host I see "Close Sorry, no
> > graphs for this host"
> > When I try to look Reports link I couldn't see anything. But when I
> > enter in adress bar "http:// mypuppethost/reports/host_fqdn/" - I see
> > rrd reports graph (Daily, Weekly, e.t.c)
> > How to configure puppet+foreman+apache for correct display puppet rrd
> > reports in foreman web interface?
>
> > My conf:
> > puppet.conf
> > [main]
> >    external_nodes = /etc/puppet/node.rb
> >    node_terminus  = exec
> >    vardir = /var/puppet
> >    logdir = $vardir/log
> >    rundir = $vardir/run
> >    ssldir = $vardir/ssl
>
> > [puppetmasterd]
>
> >    reportdir = /var/puppet/reports
> >    reports = log,store,tagmail,rrdgraph
> >    tagmap = $confdir/tagmail.conf
> >    rrddir = $vardir/rrd
> >    rrdinternval = $runinterval
> >    rrdgraph = true
> >    ssl_client_header = SSL_CLIENT_S_DN
> >    ssl_client_verify_header = SSL_CLIENT_VERIFY
> >    autosign = /etc/puppet/autosign.conf
> >    modulepath = /etc/puppet/modules
>
> > apache.conf
> > Listen 3000
> > 
> >    ServerName puppet
> >    DocumentRoot /var/rails/foreman/public/
> >    ErrorLog /var/rails/foreman/log/error_log
> >    LogLevel error
>
> > # Grant access to puppet reports
> >  Alias /reports/ /var/puppet/rrd/
> >  
> >    PassengerEnabled off
> >    Options Indexes
> >    Order deny,allow
> >    Allow from all
> >  
> > 
>
> > foreman settingc.yaml
> > ---
> > :modulepath: /etc/puppet/modules/
> > :rrd_report_url: reports/
> > :puppet_server: srv2-puppet
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-us...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@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-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.




[Puppet Users] Re: Couldn't see RRDReport in foreman

2009-12-21 Thread koliama
Q1: Ohad, I has not understood your assumption. You consider that in
my options there is an error?

Just in case I have edited options ServerName:
ServerName puppet -> ServerName puppet:3000
And I see that Foreman listen only 3000 port.
[u...@puppet foreman]$ netstat -an | grep 80
udp0  0 *:123 *:*
unix  3  [ ] STREAM CONNECTED 3017806
unix  3  [ ] STREAM CONNECTED 3017805
unix  2  [ ] DGRAM10806
[r...@srv2-puppet foreman]# netstat -an | grep 3000
tcp0  0 :::
3000 :::*LISTEN
tcp0  0 :::192.168.1.68:3000 :::
192.168.1.106:1724TIME_WAIT

Socket on port 80 is not opened.
P.S. In error_log I have seen the message:

[Mon Dec 21 17:19:20 2009] [error] [client 192.168.1.106] File does
not exist: /var/puppet/rrd/update_table, referer: 
http://srv2-puppet:3000/reports

What can it mean?

On 20 дек, 18:09, Ohad Levy  wrote:
> reading your apache configs, i guess that foreman links to port 80 (and you
> are using 3000).
>
> you may switch to 80 or reformat the url statement yourself in
> app/views/hosts/_rrdreport.rhtml.
>
> cheers,
> Ohad
>
> On Sun, Dec 20, 2009 at 8:38 PM, koliama  wrote:
> > Yes, I configured reporting in Foreman:
>
> > puppet.conf
> > report = log,store,tagmail,rrdgraph,foreman
>
> > Copy file foreman-report.rb into dir /usr/lib/ruby/site_ruby/1.8/
> > puppet/reports/foreman.rb and as edited
> > $foreman_url = "http://mypuppethost";
> > After this restart Apache - is the same result. RRDReports are not
> > displayed in Foreman web page :(
>
> > On 20 дек, 03:56, Ohad Levy  wrote:
> > > Did you enable reporting in Foreman? - e.g.
> >http://theforeman.org/wiki/foreman/Puppet_Reports
>
> > > I'm planning to generate all of the graphs within Foreman (no need to use
> > > RRD anymore) soon (that is when I'll come back from Xmas vacation ), so
> > > hopefully this wont be required and will look much nicer.
>
> > > Cheers,
> > > Ohad
>
> > > On Sun, Dec 20, 2009 at 6:15 AM, koliama  wrote:
> > > > Hello,
> > > > I have configured puppet 0.25.1+passenger+foreman 0.1-3+ruby-rrdtools
> > > > (into fedora EPEL repository).
> > > > When I try to look RRDRoport link by host I see "Close Sorry, no
> > > > graphs for this host"
> > > > When I try to look Reports link I couldn't see anything. But when I
> > > > enter in adress bar "http:// mypuppethost/reports/host_fqdn/" - I see
> > > > rrd reports graph (Daily, Weekly, e.t.c)
> > > > How to configure puppet+foreman+apache for correct display puppet rrd
> > > > reports in foreman web interface?
>
> > > > My conf:
> > > > puppet.conf
> > > > [main]
> > > >    external_nodes = /etc/puppet/node.rb
> > > >    node_terminus  = exec
> > > >    vardir = /var/puppet
> > > >    logdir = $vardir/log
> > > >    rundir = $vardir/run
> > > >    ssldir = $vardir/ssl
>
> > > > [puppetmasterd]
>
> > > >    reportdir = /var/puppet/reports
> > > >    reports = log,store,tagmail,rrdgraph
> > > >    tagmap = $confdir/tagmail.conf
> > > >    rrddir = $vardir/rrd
> > > >    rrdinternval = $runinterval
> > > >    rrdgraph = true
> > > >    ssl_client_header = SSL_CLIENT_S_DN
> > > >    ssl_client_verify_header = SSL_CLIENT_VERIFY
> > > >    autosign = /etc/puppet/autosign.conf
> > > >    modulepath = /etc/puppet/modules
>
> > > > apache.conf
> > > > Listen 3000
> > > > 
> > > >    ServerName puppet
> > > >    DocumentRoot /var/rails/foreman/public/
> > > >    ErrorLog /var/rails/foreman/log/error_log
> > > >    LogLevel error
>
> > > > # Grant access to puppet reports
> > > >  Alias /reports/ /var/puppet/rrd/
> > > >  
> > > >    PassengerEnabled off
> > > >    Options Indexes
> > > >    Order deny,allow
> > > >    Allow from all
> > > >  
> > > > 
>
> > > > foreman settingc.yaml
> > > > ---
> > > > :modulepath: /etc/puppet/modules/
> > > > :rrd_report_url: reports/
> > > > :puppet_server: srv2-puppet
>
> > > > --
>
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "Puppet Users&qu

[Puppet Users] Re: Couldn't see RRDReport in foreman

2009-12-24 Thread koliama
I try to edit file app/views/hosts/_rrdreport.rhtml

<%= host.name %> Last puppet report on <%=
host.last_report.getlocal %>, which is <%= time_ago_in_words
(host.last_report) %> ago

  <% url = "http://srv2-puppet:3000/#{SETTINGS
[:rrd_report_url]}/#{host.name}" -%>
  Daily
  >
  >
  weekly
  >
  >


Restart apache. It has not helped :(

On 21 дек, 22:37, koliama  wrote:
> Q1: Ohad, I has not understood your assumption. You consider that in
> my options there is an error?
>
> Just in case I have edited options ServerName:
> ServerName puppet -> ServerName puppet:3000
> And I see that Foreman listen only 3000 port.
> [u...@puppet foreman]$ netstat -an | grep 80
> udp        0      0 *:123     *:*
> unix  3      [ ]         STREAM     CONNECTED     3017806
> unix  3      [ ]         STREAM     CONNECTED     3017805
> unix  2      [ ]         DGRAM                    10806
> [r...@srv2-puppet foreman]# netstat -an | grep 3000
> tcp        0      0 :::
> 3000                     :::*                        LISTEN
> tcp        0      0 :::192.168.1.68:3000     :::
> 192.168.1.106:1724    TIME_WAIT
>
> Socket on port 80 is not opened.
> P.S. In error_log I have seen the message:
>
> [Mon Dec 21 17:19:20 2009] [error] [client 192.168.1.106] File does
> not exist: /var/puppet/rrd/update_table, 
> referer:http://srv2-puppet:3000/reports
>
> What can it mean?
>
> On 20 дек, 18:09, Ohad Levy  wrote:
>
> > reading your apache configs, i guess that foreman links to port 80 (and you
> > are using 3000).
>
> > you may switch to 80 or reformat the url statement yourself in
> > app/views/hosts/_rrdreport.rhtml.
>
> > cheers,
> > Ohad
>
> > On Sun, Dec 20, 2009 at 8:38 PM, koliama  wrote:
> > > Yes, I configured reporting in Foreman:
>
> > > puppet.conf
> > > report = log,store,tagmail,rrdgraph,foreman
>
> > > Copy file foreman-report.rb into dir /usr/lib/ruby/site_ruby/1.8/
> > > puppet/reports/foreman.rb and as edited
> > > $foreman_url = "http://mypuppethost";
> > > After this restart Apache - is the same result. RRDReports are not
> > > displayed in Foreman web page :(
>
> > > On 20 дек, 03:56, Ohad Levy  wrote:
> > > > Did you enable reporting in Foreman? - e.g.
> > >http://theforeman.org/wiki/foreman/Puppet_Reports
>
> > > > I'm planning to generate all of the graphs within Foreman (no need to 
> > > > use
> > > > RRD anymore) soon (that is when I'll come back from Xmas vacation ), so
> > > > hopefully this wont be required and will look much nicer.
>
> > > > Cheers,
> > > > Ohad
>
> > > > On Sun, Dec 20, 2009 at 6:15 AM, koliama  wrote:
> > > > > Hello,
> > > > > I have configured puppet 0.25.1+passenger+foreman 0.1-3+ruby-rrdtools
> > > > > (into fedora EPEL repository).
> > > > > When I try to look RRDRoport link by host I see "Close Sorry, no
> > > > > graphs for this host"
> > > > > When I try to look Reports link I couldn't see anything. But when I
> > > > > enter in adress bar "http:// mypuppethost/reports/host_fqdn/" - I see
> > > > > rrd reports graph (Daily, Weekly, e.t.c)
> > > > > How to configure puppet+foreman+apache for correct display puppet rrd
> > > > > reports in foreman web interface?
>
> > > > > My conf:
> > > > > puppet.conf
> > > > > [main]
> > > > >    external_nodes = /etc/puppet/node.rb
> > > > >    node_terminus  = exec
> > > > >    vardir = /var/puppet
> > > > >    logdir = $vardir/log
> > > > >    rundir = $vardir/run
> > > > >    ssldir = $vardir/ssl
>
> > > > > [puppetmasterd]
>
> > > > >    reportdir = /var/puppet/reports
> > > > >    reports = log,store,tagmail,rrdgraph
> > > > >    tagmap = $confdir/tagmail.conf
> > > > >    rrddir = $vardir/rrd
> > > > >    rrdinternval = $runinterval
> > > > >    rrdgraph = true
> > > > >    ssl_client_header = SSL_CLIENT_S_DN
> > > > >    ssl_client_verify_header = SSL_CLIENT_VERIFY
> > > > >    autosign = /etc/puppet/autosign.conf
> > > > >    modulepath = /etc/puppet/modules
>
> > > > > apache.conf
> > > > > Listen 3000
> > > > > 
> > > > >    ServerName puppet
> > > > >    DocumentRo

[Puppet Users] Re: Couldn't see RRDReport in foreman

2009-12-25 Thread koliama
I wished to allocate with tag  change in URL. Probably it does not
work in google groups.
In a reality I certainly do not use this tag in URL.

On 24 дек, 15:11, Frank Sweetser  wrote:
> On 12/24/2009 5:16 AM, koliama wrote:
>
> > I try to edit file app/views/hosts/_rrdreport.rhtml
>
> > <%= host.name %>  Last puppet report on<%=
> > host.last_report.getlocal %>, which is<%= time_ago_in_words
> > (host.last_report) %>  ago
> > 
> >    <% url = "http://srv2-puppet:3000/#{SETTINGS
> > [:rrd_report_url]}/#{host.name}" -%>
>
> That's not a valid url - you're attempting to point it at a hostname of
> 'srv2-puppet' on a port of '3000'.  Try taking the bold tags out.
>
> --
> Frank Sweetser fs at wpi.edu  |  For every problem, there is a solution that
> WPI Senior Network Engineer   |  is simple, elegant, and wrong. - HL Mencken
>      GPG fingerprint = 6174 1257 129E 0D21 D8D4  E8A3 8E39 29E3 E2E8 8CEC

--

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




[Puppet Users] Re: Couldn't see RRDReport in foreman

2009-12-25 Thread koliama
I wished to allocate with tag  change in URL. Probably it does not
work in google groups.
In a reality I certainly do not use this tag in URL.

On 24 дек, 15:11, Frank Sweetser  wrote:
> On 12/24/2009 5:16 AM, koliama wrote:
>
> > I try to edit file app/views/hosts/_rrdreport.rhtml
>
> > <%= host.name %>  Last puppet report on<%=
> > host.last_report.getlocal %>, which is<%= time_ago_in_words
> > (host.last_report) %>  ago
> > 
> >    <% url = "http://srv2-puppet:3000/#{SETTINGS
> > [:rrd_report_url]}/#{host.name}" -%>
>
> That's not a valid url - you're attempting to point it at a hostname of
> 'srv2-puppet' on a port of '3000'.  Try taking the bold tags out.
>
> --
> Frank Sweetser fs at wpi.edu  |  For every problem, there is a solution that
> WPI Senior Network Engineer   |  is simple, elegant, and wrong. - HL Mencken
>      GPG fingerprint = 6174 1257 129E 0D21 D8D4  E8A3 8E39 29E3 E2E8 8CEC

--

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




[Puppet Users] Re: Couldn't see RRDReport in foreman

2009-12-25 Thread koliama
I wished to allocate with tag  change in URL. Probably it does not
work in google groups.
In a reality I certainly do not use this tag in URL.

On 24 дек, 15:11, Frank Sweetser  wrote:
> On 12/24/2009 5:16 AM, koliama wrote:
>
> > I try to edit file app/views/hosts/_rrdreport.rhtml
>
> > <%= host.name %>  Last puppet report on<%=
> > host.last_report.getlocal %>, which is<%= time_ago_in_words
> > (host.last_report) %>  ago
> > 
> >    <% url = "http://srv2-puppet:3000/#{SETTINGS
> > [:rrd_report_url]}/#{host.name}" -%>
>
> That's not a valid url - you're attempting to point it at a hostname of
> 'srv2-puppet' on a port of '3000'.  Try taking the bold tags out.
>
> --
> Frank Sweetser fs at wpi.edu  |  For every problem, there is a solution that
> WPI Senior Network Engineer   |  is simple, elegant, and wrong. - HL Mencken
>      GPG fingerprint = 6174 1257 129E 0D21 D8D4  E8A3 8E39 29E3 E2E8 8CEC

--

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




[Puppet Users] Re: Couldn't see RRDReport in foreman

2010-01-17 Thread koliama
http://srv2-puppet:3000/hosts/rrdreport/2?_method=get - it's link on
which I try to go to RRDReport.

In firebug I see next:


   Close
   Sorry, no graphs for this host

 wrote:
> On 25.12.2009 13:11, koliama wrote:> I wished to allocate with tag  change 
> in URL. Probably it does not
> > work in google groups.
> > In a reality I certainly do not use this tag in URL.
>
> Use firefox + firebug, inspect element there and check the output, it
> will probably point you in the right direction :)
>
> Silviu
-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.