Hi all,
I'm working on an install of Puppet and Foreman however the dashboard
is showing that none of my hosts are in sync (something which I know
to be false!)
I'm running Puppet-server 0.25.4 and the reports are being created (in
YAML Format at least!) in the correct directory.
Reporting is enabled for both logs and foreman and the ruby report is
in the correct directory, however the URL http://foreman:3000/reports/create/?format=yml
does not appear to exist, even though foreman is running on port 3000
(or at least the main web interface is!)
Does any one know if this is a bug that I've found or if this is
expected behaviour for foreman 0.1.3?
Thanks in advance,
PF.
does your host foreman resolve anything?
if its a local install, change it to localhost of fqdn of your real server
name.
btw: there is no need to store the reports locally for Foreman.
cheers,
Ohad
···
On Thu, Mar 4, 2010 at 8:54 PM, Prof Falken wrote:
Hi all,
I’m working on an install of Puppet and Foreman however the dashboard
is showing that none of my hosts are in sync (something which I know
to be false!)
I’m running Puppet-server 0.25.4 and the reports are being created (in
YAML Format at least!) in the correct directory.
Reporting is enabled for both logs and foreman and the ruby report is
in the correct directory, however the URL
http://foreman:3000/reports/create/?format=yml
does not appear to exist, even though foreman is running on port 3000
(or at least the main web interface is!)
Does any one know if this is a bug that I’ve found or if this is
expected behaviour for foreman 0.1.3?
Thanks in advance,
PF.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
Hi Ohad,
I can visit http://foreman.domain.tld:3000/ in a browser and I get
presented with the dashboard and all the other links work.
It's only when I try and access the /reports/create/?format=yml in the
browser that I get a 404.
I have just checked the foreman.rb and noticed that it was pointing to
the foreman server's FQDN, not the actual URL (foreman.domain.tld)
that we're running it under, however as I get the 404 in the browser,
I'm still not convinced that resolution is the issue (although I'm
happy to be proved wrong!)
Cheers,
PF
···
On 4 March 2010 13:07, Ohad Levy wrote:
> does your host foreman resolve anything?
> if its a local install, change it to localhost of fqdn of your real server
> name.
> btw: there is no need to store the reports locally for Foreman.
> cheers,
> Ohad
>
> On Thu, Mar 4, 2010 at 8:54 PM, Prof Falken wrote:
>>
>> Hi all,
>>
>> I'm working on an install of Puppet and Foreman however the dashboard
>> is showing that none of my hosts are in sync (something which I know
>> to be false!)
>>
>> I'm running Puppet-server 0.25.4 and the reports are being created (in
>> YAML Format at least!) in the correct directory.
>>
>> Reporting is enabled for both logs and foreman and the ruby report is
>> in the correct directory, however the URL
>> http://foreman:3000/reports/create/?format=yml
>> does not appear to exist, even though foreman is running on port 3000
>> (or at least the main web interface is!)
>>
>> Does any one know if this is a bug that I've found or if this is
>> expected behaviour for foreman 0.1.3?
>>
>> Thanks in advance,
>>
>> PF.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> foreman-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
Hi,
when you use your browser, you perform an http get operation, the report is
post, therefor you get the error in the browser 
Ohad
···
On Thu, Mar 4, 2010 at 9:12 PM, Matthew Macdonald-Wallace < mattmacwall@gmail.com> wrote:
Hi Ohad,
I can visit http://foreman.domain.tld:3000/ in a browser and I get
presented with the dashboard and all the other links work.
It’s only when I try and access the /reports/create/?format=yml in the
browser that I get a 404.
I have just checked the foreman.rb and noticed that it was pointing to
the foreman server’s FQDN, not the actual URL (foreman.domain.tld)
that we’re running it under, however as I get the 404 in the browser,
I’m still not convinced that resolution is the issue (although I’m
happy to be proved wrong!)
Cheers,
PF
On 4 March 2010 13:07, Ohad Levy ohadlevy@gmail.com wrote:
does your host foreman resolve anything?
if its a local install, change it to localhost of fqdn of your real
server
name.
btw: there is no need to store the reports locally for Foreman.
cheers,
Ohad
On Thu, Mar 4, 2010 at 8:54 PM, Prof Falken mattmacwall@gmail.com > wrote:
Hi all,
I’m working on an install of Puppet and Foreman however the dashboard
is showing that none of my hosts are in sync (something which I know
to be false!)
I’m running Puppet-server 0.25.4 and the reports are being created (in
YAML Format at least!) in the correct directory.
Reporting is enabled for both logs and foreman and the ruby report is
in the correct directory, however the URL
http://foreman:3000/reports/create/?format=yml
does not appear to exist, even though foreman is running on port 3000
(or at least the main web interface is!)
Does any one know if this is a bug that I’ve found or if this is
expected behaviour for foreman 0.1.3?
Thanks in advance,
PF.
–
You received this message because you are subscribed to the Google
Groups
“Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
ah, that makes sense.
I'll have to wait for the next puppet run and see what I get!
M.
···
On 4 March 2010 13:15, Ohad Levy wrote:
> Hi,
> when you use your browser, you perform an http get operation, the report is
> post, therefor you get the error in the browser :)
> Ohad
>
> On Thu, Mar 4, 2010 at 9:12 PM, Matthew Macdonald-Wallace > wrote:
>>
>> Hi Ohad,
>>
>> I can visit http://foreman.domain.tld:3000/ in a browser and I get
>> presented with the dashboard and all the other links work.
>>
>> It's only when I try and access the /reports/create/?format=yml in the
>> browser that I get a 404.
>>
>> I have just checked the foreman.rb and noticed that it was pointing to
>> the foreman server's FQDN, not the actual URL (foreman.domain.tld)
>> that we're running it under, however as I get the 404 in the browser,
>> I'm still not convinced that resolution is the issue (although I'm
>> happy to be proved wrong!)
>>
>> Cheers,
>>
>> PF
>>
>> On 4 March 2010 13:07, Ohad Levy wrote:
>> > does your host foreman resolve anything?
>> > if its a local install, change it to localhost of fqdn of your real
>> > server
>> > name.
>> > btw: there is no need to store the reports locally for Foreman.
>> > cheers,
>> > Ohad
>> >
>> > On Thu, Mar 4, 2010 at 8:54 PM, Prof Falken >> > wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I'm working on an install of Puppet and Foreman however the dashboard
>> >> is showing that none of my hosts are in sync (something which I know
>> >> to be false!)
>> >>
>> >> I'm running Puppet-server 0.25.4 and the reports are being created (in
>> >> YAML Format at least!) in the correct directory.
>> >>
>> >> Reporting is enabled for both logs and foreman and the ruby report is
>> >> in the correct directory, however the URL
>> >> http://foreman:3000/reports/create/?format=yml
>> >> does not appear to exist, even though foreman is running on port 3000
>> >> (or at least the main web interface is!)
>> >>
>> >> Does any one know if this is a bug that I've found or if this is
>> >> expected behaviour for foreman 0.1.3?
>> >>
>> >> Thanks in advance,
>> >>
>> >> PF.
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> >> Groups
>> >> "Foreman users" group.
>> >> To post to this group, send email to foreman-users@googlegroups.com.
>> >> To unsubscribe from this group, send email to
>> >> foreman-users+unsubscribe@googlegroups.com.
>> >> For more options, visit this group at
>> >> http://groups.google.com/group/foreman-users?hl=en.
>> >>
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Foreman users" group.
>> > To post to this group, send email to foreman-users@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > foreman-users+unsubscribe@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/foreman-users?hl=en.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> foreman-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
OK, the run has just completed (according to the logs) and although
there are no errors from Foreman as far as I can see, The dashboard is
still reporting that all hosts are out of sync and the "run
distribution" graph is still showing that no clients have run.
Any ideas?
PF
···
On 4 March 2010 13:19, Matthew Macdonald-Wallace wrote:
> ah, that makes sense.
>
> I'll have to wait for the next puppet run and see what I get!
>
> M.
>
> On 4 March 2010 13:15, Ohad Levy wrote:
>> Hi,
>> when you use your browser, you perform an http get operation, the report is
>> post, therefor you get the error in the browser :)
>> Ohad
>>
>> On Thu, Mar 4, 2010 at 9:12 PM, Matthew Macdonald-Wallace >> wrote:
>>>
>>> Hi Ohad,
>>>
>>> I can visit http://foreman.domain.tld:3000/ in a browser and I get
>>> presented with the dashboard and all the other links work.
>>>
>>> It's only when I try and access the /reports/create/?format=yml in the
>>> browser that I get a 404.
>>>
>>> I have just checked the foreman.rb and noticed that it was pointing to
>>> the foreman server's FQDN, not the actual URL (foreman.domain.tld)
>>> that we're running it under, however as I get the 404 in the browser,
>>> I'm still not convinced that resolution is the issue (although I'm
>>> happy to be proved wrong!)
>>>
>>> Cheers,
>>>
>>> PF
>>>
>>> On 4 March 2010 13:07, Ohad Levy wrote:
>>> > does your host foreman resolve anything?
>>> > if its a local install, change it to localhost of fqdn of your real
>>> > server
>>> > name.
>>> > btw: there is no need to store the reports locally for Foreman.
>>> > cheers,
>>> > Ohad
>>> >
>>> > On Thu, Mar 4, 2010 at 8:54 PM, Prof Falken >>> > wrote:
>>> >>
>>> >> Hi all,
>>> >>
>>> >> I'm working on an install of Puppet and Foreman however the dashboard
>>> >> is showing that none of my hosts are in sync (something which I know
>>> >> to be false!)
>>> >>
>>> >> I'm running Puppet-server 0.25.4 and the reports are being created (in
>>> >> YAML Format at least!) in the correct directory.
>>> >>
>>> >> Reporting is enabled for both logs and foreman and the ruby report is
>>> >> in the correct directory, however the URL
>>> >> http://foreman:3000/reports/create/?format=yml
>>> >> does not appear to exist, even though foreman is running on port 3000
>>> >> (or at least the main web interface is!)
>>> >>
>>> >> Does any one know if this is a bug that I've found or if this is
>>> >> expected behaviour for foreman 0.1.3?
>>> >>
>>> >> Thanks in advance,
>>> >>
>>> >> PF.
>>> >>
>>> >> --
>>> >> You received this message because you are subscribed to the Google
>>> >> Groups
>>> >> "Foreman users" group.
>>> >> To post to this group, send email to foreman-users@googlegroups.com.
>>> >> To unsubscribe from this group, send email to
>>> >> foreman-users+unsubscribe@googlegroups.com.
>>> >> For more options, visit this group at
>>> >> http://groups.google.com/group/foreman-users?hl=en.
>>> >>
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "Foreman users" group.
>>> > To post to this group, send email to foreman-users@googlegroups.com.
>>> > To unsubscribe from this group, send email to
>>> > foreman-users+unsubscribe@googlegroups.com.
>>> > For more options, visit this group at
>>> > http://groups.google.com/group/foreman-users?hl=en.
>>> >
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Foreman users" group.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> foreman-users+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/foreman-users?hl=en.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> foreman-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
please check the puppetmater logs, to be sure that foreman log has been
processed, additionally have a look at foreman logs (logs/production.log) to
see if you can see any errors.
my guess is that the puppet foreman report is not in the right place or that
its not pointing to the right url.
cheers,
Ohad
···
On Thu, Mar 4, 2010 at 9:24 PM, Matthew Macdonald-Wallace < mattmacwall@gmail.com> wrote:
OK, the run has just completed (according to the logs) and although
there are no errors from Foreman as far as I can see, The dashboard is
still reporting that all hosts are out of sync and the “run
distribution” graph is still showing that no clients have run.
Any ideas?
PF
On 4 March 2010 13:19, Matthew Macdonald-Wallace mattmacwall@gmail.com > wrote:
ah, that makes sense.
I’ll have to wait for the next puppet run and see what I get!
M.
On 4 March 2010 13:15, Ohad Levy ohadlevy@gmail.com wrote:
Hi,
when you use your browser, you perform an http get operation, the report
is
post, therefor you get the error in the browser
Ohad
On Thu, Mar 4, 2010 at 9:12 PM, Matthew Macdonald-Wallace > >> mattmacwall@gmail.com wrote:
Hi Ohad,
I can visit http://foreman.domain.tld:3000/ in a browser and I get
presented with the dashboard and all the other links work.
It’s only when I try and access the /reports/create/?format=yml in the
browser that I get a 404.
I have just checked the foreman.rb and noticed that it was pointing to
the foreman server’s FQDN, not the actual URL (foreman.domain.tld)
that we’re running it under, however as I get the 404 in the browser,
I’m still not convinced that resolution is the issue (although I’m
happy to be proved wrong!)
Cheers,
PF
On 4 March 2010 13:07, Ohad Levy ohadlevy@gmail.com wrote:
does your host foreman resolve anything?
if its a local install, change it to localhost of fqdn of your real
server
name.
btw: there is no need to store the reports locally for Foreman.
cheers,
Ohad
On Thu, Mar 4, 2010 at 8:54 PM, Prof Falken mattmacwall@gmail.com > >>> > wrote:
Hi all,
I’m working on an install of Puppet and Foreman however the
dashboard
is showing that none of my hosts are in sync (something which I know
to be false!)
I’m running Puppet-server 0.25.4 and the reports are being created
(in
YAML Format at least!) in the correct directory.
Reporting is enabled for both logs and foreman and the ruby report
is
in the correct directory, however the URL
http://foreman:3000/reports/create/?format=yml
does not appear to exist, even though foreman is running on port
3000
(or at least the main web interface is!)
Does any one know if this is a bug that I’ve found or if this is
expected behaviour for foreman 0.1.3?
Thanks in advance,
PF.
–
You received this message because you are subscribed to the Google
Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com
.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google
Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google
Groups
“Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google
Groups
“Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
ok, I've checked and when the server was running 0.24.x under RACK
foreman reporting was working without issue. Now that it's running
0.25.x it's not running the foreman reports.
I'll ask on the Puppet list.
Thanks for all your help.
PF
···
On 4 March 2010 13:28, Ohad Levy wrote:
> please check the puppetmater logs, to be sure that foreman log has been
> processed, additionally have a look at foreman logs (logs/production.log) to
> see if you can see any errors.
> my guess is that the puppet foreman report is not in the right place or that
> its not pointing to the right url.
> cheers,
> Ohad
>
> On Thu, Mar 4, 2010 at 9:24 PM, Matthew Macdonald-Wallace > wrote:
>>
>> OK, the run has just completed (according to the logs) and although
>> there are no errors from Foreman as far as I can see, The dashboard is
>> still reporting that all hosts are out of sync and the "run
>> distribution" graph is still showing that no clients have run.
>>
>> Any ideas?
>>
>> PF
>>
>> On 4 March 2010 13:19, Matthew Macdonald-Wallace >> wrote:
>> > ah, that makes sense.
>> >
>> > I'll have to wait for the next puppet run and see what I get!
>> >
>> > M.
>> >
>> > On 4 March 2010 13:15, Ohad Levy wrote:
>> >> Hi,
>> >> when you use your browser, you perform an http get operation, the
>> >> report is
>> >> post, therefor you get the error in the browser :)
>> >> Ohad
>> >>
>> >> On Thu, Mar 4, 2010 at 9:12 PM, Matthew Macdonald-Wallace >> >> wrote:
>> >>>
>> >>> Hi Ohad,
>> >>>
>> >>> I can visit http://foreman.domain.tld:3000/ in a browser and I get
>> >>> presented with the dashboard and all the other links work.
>> >>>
>> >>> It's only when I try and access the /reports/create/?format=yml in the
>> >>> browser that I get a 404.
>> >>>
>> >>> I have just checked the foreman.rb and noticed that it was pointing to
>> >>> the foreman server's FQDN, not the actual URL (foreman.domain.tld)
>> >>> that we're running it under, however as I get the 404 in the browser,
>> >>> I'm still not convinced that resolution is the issue (although I'm
>> >>> happy to be proved wrong!)
>> >>>
>> >>> Cheers,
>> >>>
>> >>> PF
>> >>>
>> >>> On 4 March 2010 13:07, Ohad Levy wrote:
>> >>> > does your host foreman resolve anything?
>> >>> > if its a local install, change it to localhost of fqdn of your real
>> >>> > server
>> >>> > name.
>> >>> > btw: there is no need to store the reports locally for Foreman.
>> >>> > cheers,
>> >>> > Ohad
>> >>> >
>> >>> > On Thu, Mar 4, 2010 at 8:54 PM, Prof Falken >> >>> > wrote:
>> >>> >>
>> >>> >> Hi all,
>> >>> >>
>> >>> >> I'm working on an install of Puppet and Foreman however the
>> >>> >> dashboard
>> >>> >> is showing that none of my hosts are in sync (something which I
>> >>> >> know
>> >>> >> to be false!)
>> >>> >>
>> >>> >> I'm running Puppet-server 0.25.4 and the reports are being created
>> >>> >> (in
>> >>> >> YAML Format at least!) in the correct directory.
>> >>> >>
>> >>> >> Reporting is enabled for both logs and foreman and the ruby report
>> >>> >> is
>> >>> >> in the correct directory, however the URL
>> >>> >> http://foreman:3000/reports/create/?format=yml
>> >>> >> does not appear to exist, even though foreman is running on port
>> >>> >> 3000
>> >>> >> (or at least the main web interface is!)
>> >>> >>
>> >>> >> Does any one know if this is a bug that I've found or if this is
>> >>> >> expected behaviour for foreman 0.1.3?
>> >>> >>
>> >>> >> Thanks in advance,
>> >>> >>
>> >>> >> PF.
>> >>> >>
>> >>> >> --
>> >>> >> You received this message because you are subscribed to the Google
>> >>> >> Groups
>> >>> >> "Foreman users" group.
>> >>> >> To post to this group, send email to
>> >>> >> foreman-users@googlegroups.com.
>> >>> >> To unsubscribe from this group, send email to
>> >>> >> foreman-users+unsubscribe@googlegroups.com.
>> >>> >> For more options, visit this group at
>> >>> >> http://groups.google.com/group/foreman-users?hl=en.
>> >>> >>
>> >>> >
>> >>> > --
>> >>> > You received this message because you are subscribed to the Google
>> >>> > Groups
>> >>> > "Foreman users" group.
>> >>> > To post to this group, send email to foreman-users@googlegroups.com.
>> >>> > To unsubscribe from this group, send email to
>> >>> > foreman-users+unsubscribe@googlegroups.com.
>> >>> > For more options, visit this group at
>> >>> > http://groups.google.com/group/foreman-users?hl=en.
>> >>> >
>> >>>
>> >>> --
>> >>> You received this message because you are subscribed to the Google
>> >>> Groups
>> >>> "Foreman users" group.
>> >>> To post to this group, send email to foreman-users@googlegroups.com.
>> >>> To unsubscribe from this group, send email to
>> >>> foreman-users+unsubscribe@googlegroups.com.
>> >>> For more options, visit this group at
>> >>> http://groups.google.com/group/foreman-users?hl=en.
>> >>>
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> >> Groups
>> >> "Foreman users" group.
>> >> To post to this group, send email to foreman-users@googlegroups.com.
>> >> To unsubscribe from this group, send email to
>> >> foreman-users+unsubscribe@googlegroups.com.
>> >> For more options, visit this group at
>> >> http://groups.google.com/group/foreman-users?hl=en.
>> >>
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> foreman-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
i think you should only have /etc/puppet/puppet.conf and not
puppetmasterd.conf
cheers,
Ohad
···
On Thu, Mar 4, 2010 at 10:02 PM, Matthew Macdonald-Wallace < mattmacwall@gmail.com> wrote:
ok, I’ve checked and when the server was running 0.24.x under RACK
foreman reporting was working without issue. Now that it’s running
0.25.x it’s not running the foreman reports.
I’ll ask on the Puppet list.
Thanks for all your help.
PF
On 4 March 2010 13:28, Ohad Levy ohadlevy@gmail.com wrote:
please check the puppetmater logs, to be sure that foreman log has been
processed, additionally have a look at foreman logs (logs/production.log)
to
see if you can see any errors.
my guess is that the puppet foreman report is not in the right place or
that
its not pointing to the right url.
cheers,
Ohad
On Thu, Mar 4, 2010 at 9:24 PM, Matthew Macdonald-Wallace > > mattmacwall@gmail.com wrote:
OK, the run has just completed (according to the logs) and although
there are no errors from Foreman as far as I can see, The dashboard is
still reporting that all hosts are out of sync and the “run
distribution” graph is still showing that no clients have run.
Any ideas?
PF
On 4 March 2010 13:19, Matthew Macdonald-Wallace <mattmacwall@gmail.com > > > >> wrote:
ah, that makes sense.
I’ll have to wait for the next puppet run and see what I get!
M.
On 4 March 2010 13:15, Ohad Levy ohadlevy@gmail.com wrote:
Hi,
when you use your browser, you perform an http get operation, the
report is
post, therefor you get the error in the browser
Ohad
On Thu, Mar 4, 2010 at 9:12 PM, Matthew Macdonald-Wallace > >> >> mattmacwall@gmail.com wrote:
Hi Ohad,
I can visit http://foreman.domain.tld:3000/ in a browser and I get
presented with the dashboard and all the other links work.
It’s only when I try and access the /reports/create/?format=yml in
the
browser that I get a 404.
I have just checked the foreman.rb and noticed that it was pointing
to
the foreman server’s FQDN, not the actual URL (foreman.domain.tld)
that we’re running it under, however as I get the 404 in the
browser,
I’m still not convinced that resolution is the issue (although I’m
happy to be proved wrong!)
Cheers,
PF
On 4 March 2010 13:07, Ohad Levy ohadlevy@gmail.com wrote:
does your host foreman resolve anything?
if its a local install, change it to localhost of fqdn of your
real
server
name.
btw: there is no need to store the reports locally for Foreman.
cheers,
Ohad
On Thu, Mar 4, 2010 at 8:54 PM, Prof Falken < > mattmacwall@gmail.com> > >> >>> > wrote:
Hi all,
I’m working on an install of Puppet and Foreman however the
dashboard
is showing that none of my hosts are in sync (something which I
know
to be false!)
I’m running Puppet-server 0.25.4 and the reports are being
created
(in
YAML Format at least!) in the correct directory.
Reporting is enabled for both logs and foreman and the ruby
report
is
in the correct directory, however the URL
http://foreman:3000/reports/create/?format=yml
does not appear to exist, even though foreman is running on port
3000
(or at least the main web interface is!)
Does any one know if this is a bug that I’ve found or if this is
expected behaviour for foreman 0.1.3?
Thanks in advance,
PF.
–
You received this message because you are subscribed to the
Google
Groups
"Foreman users" group.
To post to this group, send email to
foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google
Groups
"Foreman users" group.
To post to this group, send email to
foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google
Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com
.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google
Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google
Groups
“Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
