I have recently tried installing Foreman on my CentOs box after a fresh
install. I installed the pre-requisites and used the directions on the
Foreman quick start page.
However, after installing the foreman installer, when I ran the command:
foreman-installer, it started to prepare the install and then said that
something went wrong and that I should check the log for error-level
output. However upon examining the log, I found no error level output.
I later tried foreman-installer -i to run the installer interactively.
After configuring the settings, I pressed #19 on the Menu to show me the
settings I had chosen. Then I typed #20 – save and run. This exact process
worked to install Foreman and then I could open up the web GUI with no
problem.
However, any different sequence, for example, if I didn't go through #19
before #20, wouldn't work.
Has anyone experienced similar problems? Could anyone explain why
foreman-installer -i worked for me but the other without options doesn't?
Did I miss something internally during the pre-install?
After I finally got the install to work and complete I logged into Foreman
and viewed my host. It appeared to be configured right and was checking in
regularly. However, when I tried to view the web GUI on a machine separate
the error had to do with DNS Lookup Failure. I've tried messing with some
settings in the Foreman Proxy settings file and the Foreman settings and
also checking my etc/hosts and ect/resolv.conf files but I am at a loss now
on how to resolve the problem. Any suggestions or thoughts would be much
appreciated!
Thank you so much!
-Katy
···
from my host, it gave me the error Unknown Host. More information told me
There seems to be a problem with newer puppet versions. The workaround I
use is to edit /usr/bin/puppet before I run foreman-installer. Notice
the GC.disable. It looks like you can remove that line as soon as
foreman is done and make sure you have enough memory in your foreman
server, 2G worked for me but where I got this from said 4G. (redmine of
foreman)
#!/usr/bin/ruby
For security reasons, ensure that '.' is not on the load path
This is primarily for 1.8.7 since 1.9.2+ doesn't put '.' on the load path
···
On 2-7-2014 21:48, Katy McClintic wrote:
> Hi all,
>
> I am new to the Foreman community.
>
> I have recently tried installing Foreman on my CentOs box after a
> fresh install. I installed the pre-requisites and used the directions
> on the Foreman quick start page.
> However, after installing the foreman installer, when I ran the
> command: foreman-installer, it started to prepare the install and then
> said that something went wrong and that I should check the log for
> error-level output. However upon examining the log, I found no error
> level output.
>
> I later tried foreman-installer -i to run the installer interactively.
> After configuring the settings, I pressed #19 on the Menu to show me
> the settings I had chosen. Then I typed #20 -- save and run. This
> exact process worked to install Foreman and then I could open up the
> web GUI with no problem.
> However, any different sequence, for example, if I didn't go through
> #19 before #20, wouldn't work.
>
> Has anyone experienced similar problems? Could anyone explain why
> foreman-installer -i worked for me but the other without options
> doesn't? Did I miss something internally during the pre-install?
>
Thank you so much! After I fixed the puppet file, everything ran smoothly.
I had some weird stuff in there from some gems I installed earlier so I bet
those were not helping either.
Thanks again,
Katy
···
On Wednesday, July 2, 2014 11:31:56 PM UTC-7, jvandewege wrote:
>
> On 2-7-2014 21:48, Katy McClintic wrote:
> > Hi all,
> >
> > I am new to the Foreman community.
> >
> > I have recently tried installing Foreman on my CentOs box after a
> > fresh install. I installed the pre-requisites and used the directions
> > on the Foreman quick start page.
> > However, after installing the foreman installer, when I ran the
> > command: foreman-installer, it started to prepare the install and then
> > said that something went wrong and that I should check the log for
> > error-level output. However upon examining the log, I found no error
> > level output.
> >
> > I later tried foreman-installer -i to run the installer interactively.
> > After configuring the settings, I pressed #19 on the Menu to show me
> > the settings I had chosen. Then I typed #20 -- save and run. This
> > exact process worked to install Foreman and then I could open up the
> > web GUI with no problem.
> > However, any different sequence, for example, if I didn't go through
> > #19 before #20, wouldn't work.
> >
> > Has anyone experienced similar problems? Could anyone explain why
> > foreman-installer -i worked for me but the other without options
> > doesn't? Did I miss something internally during the pre-install?
> >
> There seems to be a problem with newer puppet versions. The workaround I
> use is to edit /usr/bin/puppet before I run foreman-installer. Notice
> the GC.disable. It looks like you can remove that line as soon as
> foreman is done and make sure you have enough memory in your foreman
> server, 2G worked for me but where I got this from said 4G. (redmine of
> foreman)
>
> #!/usr/bin/ruby
>
> # For security reasons, ensure that '.' is not on the load path
> # This is primarily for 1.8.7 since 1.9.2+ doesn't put '.' on the load
> path
> $LOAD_PATH.delete '.'
> GC.disable
> require 'puppet/util/command_line'
> Puppet::Util::CommandLine.new.execute
>
> Joop
>
>
