I'm after doing a clean install of foreman on CentOS 6.4 using the
foreman-installer but am having trouble getting to the web UI.
I added the puppetlabs repo for redhat and installed puppet 3 then ran the
foreman installer as per Foreman :: Manual and chose
to have foreman install everything as its gong onto a clean vm with just
the OS and latest updates installed (no apache, db etc installed previously)
I've tried http:localhost:3000, https://localhost:3000 as well as 127.0.0.1
and the servers own IP address as well trying port 80 and 443 but can't
access any webpage
I've also tried with the firewall off
I can ping the foreman server's IP address from another host
There is no entries in the cron log and the production.log has db migration
and connection entries and ends with connecting to database specified by
database.yml
The service status of foreman is reported as "Foreman is running under
passenger"
The service status of http is reported as stopped but when I go to start it
I get the following error
Syntax error in line 10 of /etc/httpd/conf.d/foreman.conf
Invalid command 'PassengerAppRoot' perhaps mispelled or defined by a module
not included in the server configuration
The output of foreman-dedug is #foreman-debug
hostname: Unknown Host
hostname: Unknown Host
I know there is something very simple I'm missing but can't place my finger
on it and know that editting the foreman.conf would probably only last
until the next puppet run
> Hi Foreman Users,
>
> I'm after doing a clean install of foreman on CentOS 6.4 using the
> foreman-installer but am having trouble getting to the web UI.
>
> I added the puppetlabs repo for redhat and installed puppet 3 then ran the
> foreman installer as per http://theforeman.org/manuals/**1.2/index.html#3.
> **InstallingForeman<Foreman :: Manual>and chose to have foreman install everything as its gong onto a clean vm
> with just the OS and latest updates installed (no apache, db etc installed
> previously)
>
> I've tried http:localhost:3000, https://localhost:3000 as well as
> 127.0.0.1 and the servers own IP address as well trying port 80 and 443 but
> can't access any webpage
> I've also tried with the firewall off
> I can ping the foreman server's IP address from another host
> There is no entries in the cron log and the production.log has db
> migration and connection entries and ends with connecting to database
> specified by database.yml
>
> The service status of foreman is reported as "Foreman is running under
> passenger"
> The service status of http is reported as stopped but when I go to start
> it I get the following error
>
> Syntax error in line 10 of /etc/httpd/conf.d/foreman.conf
> Invalid command 'PassengerAppRoot' perhaps mispelled or defined by a
> module not included in the server configuration
>
> The output of foreman-dedug is
> #foreman-debug
> hostname: Unknown Host
> hostname: Unknown Host
>
>
> HOSTNAME:
> OS; redhat
> RELEASE: 6.4
> FOREMAN: 1.2.0
> RUBY: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
> PUPPET: 3.2.3
>
> I know there is something very simple I'm missing but can't place my
> finger on it and know that editting the foreman.conf would probably only
> last until the next puppet run
>
> Anyone able to point me to a solution?
The host most likely doesn't have its FQDN set. What's the output of facter -p fqdn on it?
···
On 24/07/13 13:26, michael.obrien@ul.ie wrote:
> The service status of foreman is reported as "Foreman is running under
> passenger"
> The service status of http is reported as stopped but when I go to start
> it I get the following error
>
> Syntax error in line 10 of /etc/httpd/conf.d/foreman.conf
> Invalid command 'PassengerAppRoot' perhaps mispelled or defined by a
> module not included in the server configuration
It gives the fqdn of the server but I cant ping fqdn
My etc/hosts file just lists the 127.0.0.1 and localhost values, nothing
in there for the servers IP or fqdn
···
On Wednesday, July 24, 2013 1:30:46 PM UTC+1, Sam Kottler wrote:
>
>
>
> On Wed, Jul 24, 2013 at 8:26 AM, <michael...@ul.ie > wrote:
>
>> Hi Foreman Users,
>>
>> I'm after doing a clean install of foreman on CentOS 6.4 using the
>> foreman-installer but am having trouble getting to the web UI.
>>
>> I added the puppetlabs repo for redhat and installed puppet 3 then ran
>> the foreman installer as per http://theforeman.org/manuals/**
>> 1.2/index.html#3.**InstallingForemanand chose to have foreman install everything as its gong onto a clean vm
>> with just the OS and latest updates installed (no apache, db etc installed
>> previously)
>>
>> I've tried http:localhost:3000, https://localhost:3000 as well as
>> 127.0.0.1 and the servers own IP address as well trying port 80 and 443 but
>> can't access any webpage
>> I've also tried with the firewall off
>> I can ping the foreman server's IP address from another host
>> There is no entries in the cron log and the production.log has db
>> migration and connection entries and ends with connecting to database
>> specified by database.yml
>>
>> The service status of foreman is reported as "Foreman is running under
>> passenger"
>> The service status of http is reported as stopped but when I go to start
>> it I get the following error
>>
>> Syntax error in line 10 of /etc/httpd/conf.d/foreman.conf
>> Invalid command 'PassengerAppRoot' perhaps mispelled or defined by a
>> module not included in the server configuration
>>
>> The output of foreman-dedug is
>> #foreman-debug
>> hostname: Unknown Host
>> hostname: Unknown Host
>>
>>
>> HOSTNAME:
>> OS; redhat
>> RELEASE: 6.4
>> FOREMAN: 1.2.0
>> RUBY: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
>> PUPPET: 3.2.3
>>
>> I know there is something very simple I'm missing but can't place my
>> finger on it and know that editting the foreman.conf would probably only
>> last until the next puppet run
>>
>> Anyone able to point me to a solution?
>
>
> The host most likely doesn't have its FQDN set. What's the output of
> `facter -p fqdn` on it?
>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
Would the install log be saved in a particular location?
I didn't notice any error messages after running the ruby command
ruby /usr/share/foreman-installer/generate_answers.rb and answering the questions
When i run the commands
rpm -qa | grep passenger
The command prompt just returns and
cat /etc/httpd/conf.d/passenger.conf
No such file or directory
···
On Wednesday, July 24, 2013 1:42:35 PM UTC+1, Dominic Cleal wrote:
>
> On 24/07/13 13:26, michael...@ul.ie wrote:
> > The service status of foreman is reported as "Foreman is running under
> > passenger"
> > The service status of http is reported as stopped but when I go to start
> > it I get the following error
> >
> > Syntax error in line 10 of /etc/httpd/conf.d/foreman.conf
> > Invalid command 'PassengerAppRoot' perhaps mispelled or defined by a
> > module not included in the server configuration
>
> This suggests Passenger hasn't loaded. Do you have the log from the
> installer run, possibly there were errors and it didn't complete?
>
> Also get the output from:
>
> rpm -qa | grep passenger
> cat /etc/httpd/conf.d/passenger.conf
>
> --
> Dominic Cleal
> Red Hat Engineering
>
I don't think the log's kept anywhere at the moment, something that's
being fixed for 1.3. Try re-running the installer, either with
generate_answers.rb or by running:
echo include foreman_installer | puppet apply -v --modulepath
/usr/share/foreman-installer
···
On 24/07/13 13:47, michael.obrien@ul.ie wrote:
> Would the install log be saved in a particular location?
> I didn't notice any error messages after running the ruby command
>
> >ruby /usr/share/foreman-installer/generate_answers.rb and answering the questions
>
> When i run the commands
> >rpm -qa | grep passenger
>
> The command prompt just returns and
>
> cat /etc/httpd/conf.d/passenger.conf
>
>
> No such file or directory
echo include foreman_installer | puppet apply -v --modulepath
/usr/share/foreman-installer
Info: Loading facts in
/usr/share/foreman-installer/stdlib/lib/facter/root_home.rb
Info: Loading facts in
/usr/share/foreman-installer/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in
/usr/share/foreman-installer/stdlib/lib/facter/pe_version.rb
Info: Loading facts in
/usr/share/foreman-installer/postgresql/lib/facter/postgres_default_version.rb
Info: Loading facts in
/usr/share/foreman-installer/concat/lib/facter/concat_basedir.rb
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Info: Loading facts in
/usr/share/foreman-installer/stdlib/lib/facter/root_home.rb
Info: Loading facts in
/usr/share/foreman-installer/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in
/usr/share/foreman-installer/stdlib/lib/facter/pe_version.rb
Info: Loading facts in
/usr/share/foreman-installer/postgresql/lib/facter/postgres_default_version.rb
Info: Loading facts in
/usr/share/foreman-installer/concat/lib/facter/concat_basedir.rb
Info: Applying configuration version '1374670472'
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install foreman-proxy'
returned 1: Error: Package: foreman-proxy-1.2.0-1.el6.noarch (foreman)
Requires: rubygem(sinatra)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Error: /Stage[main]/Foreman_proxy::Install/Package[foreman-proxy]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y install foreman-proxy' returned 1: Error: Package:
foreman-proxy-1.2.0-1.el6.noarch (foreman)
Requires: rubygem(sinatra)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Info: FileBucket adding {md5}ec750430705af88c03915208d9f56d2e
Info: /File[/etc/xinetd.d/tftp]: Filebucketed /etc/xinetd.d/tftp to puppet
with sum ec750430705af88c03915208d9f56d2e
Notice: /File[/etc/xinetd.d/tftp]/content: content changed
'{md5}ec750430705af88c03915208d9f56d2e' to
'{md5}d0826233b3460441ca5132d7609f522f'
Notice: /File[/etc/xinetd.d/tftp]/seltype: seltype changed 'etc_runtime_t'
to 'etc_t'
Info: /File[/etc/xinetd.d/tftp]: Scheduling refresh of Service[xinetd]
Info: /File[/etc/xinetd.d/tftp]: Scheduling refresh of Service[xinetd]
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install
ruby193-rubygem-passenger-native' returned 1: Error: Package:
ruby193-rubygem-passenger-native-4.0.5-3.el6.x86_64 (foreman)
Requires: libev.so.4()(64bit)
Error: Package: ruby193-rubygem-passenger-native-4.0.5-3.el6.x86_64
(foreman)
Requires: libev
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Error:
/Stage[main]/Passenger::Install::Scl/Package[ruby193-rubygem-passenger-native]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y install ruby193-rubygem-passenger-native' returned 1: Error: Package:
ruby193-rubygem-passenger-native-4.0.5-3.el6.x86_64 (foreman)
Requires: libev.so.4()(64bit)
Error: Package: ruby193-rubygem-passenger-native-4.0.5-3.el6.x86_64
(foreman)
Requires: libev
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Notice: /Stage[main]/Xinetd/Service[xinetd]: Triggered 'refresh' from 2
events
Info: Class[Tftp::Config]: Scheduling refresh of Class[Tftp::Service]
Notice: /Stage[main]/Foreman::Service/Service[foreman]/enable: enable
changed 'true' to 'false'
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install mod_passenger'
returned 1: Error: Package: rubygem-passenger-native-4.0.5-3.el6.x86_64
(foreman)
Requires: libev
Error: Package: rubygem-passenger-native-4.0.5-3.el6.x86_64 (foreman)
Requires: libev.so.4()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Error: /Stage[main]/Passenger::Install::Redhat/Package[passenger]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y install mod_passenger' returned 1: Error: Package:
rubygem-passenger-native-4.0.5-3.el6.x86_64 (foreman)
Requires: libev
Error: Package: rubygem-passenger-native-4.0.5-3.el6.x86_64 (foreman)
Requires: libev.so.4()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency
Package[passenger] has failures: true
Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency
Package[ruby193-rubygem-passenger-native] has failures: true
Warning: /Stage[main]/Apache::Service/Service[httpd]: Skipping because of
failed dependencies
Notice: /Stage[main]/Apache::Service/Exec[reload-apache]: Dependency
Package[passenger] has failures: true
Notice: /Stage[main]/Apache::Service/Exec[reload-apache]: Dependency
Package[ruby193-rubygem-passenger-native] has failures: true
Warning: /Stage[main]/Apache::Service/Exec[reload-apache]: Skipping because
of failed dependencies
Notice: /User[foreman-proxy]: Dependency Package[foreman-proxy] has
failures: true
Warning: /User[foreman-proxy]: Skipping because of failed dependencies
Notice: /File[/etc/sudoers.d]: Dependency Package[foreman-proxy] has
failures: true
Warning: /File[/etc/sudoers.d]: Skipping because of failed dependencies
Notice: /File[/etc/sudoers.d/foreman-proxy]: Dependency
Package[foreman-proxy] has failures: true
Warning: /File[/etc/sudoers.d/foreman-proxy]: Skipping because of failed
dependencies
Notice: /File[/var/lib/tftpboot//boot]: Dependency Package[foreman-proxy]
has failures: true
Warning: /File[/var/lib/tftpboot//boot]: Skipping because of failed
dependencies
Notice: /File[/var/lib/tftpboot//pxelinux.cfg]: Dependency
Package[foreman-proxy] has failures: true
Warning: /File[/var/lib/tftpboot//pxelinux.cfg]: Skipping because of failed
dependencies
Notice: /File[/etc/puppet/autosign.conf]: Dependency Package[foreman-proxy]
has failures: true
Warning: /File[/etc/puppet/autosign.conf]: Skipping because of failed
dependencies
Notice: /File[/etc/foreman-proxy/settings.yml]: Dependency
Package[foreman-proxy] has failures: true
Warning: /File[/etc/foreman-proxy/settings.yml]: Skipping because of failed
dependencies
Notice: /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]:
Dependency Package[foreman-proxy] has failures: true
Warning: /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]:
Skipping because of failed dependencies
Notice: Finished catalog run in 12.79 seconds
[root@cdi-pup ~]# vim foreman_installer
[1]+ Stopped vim foreman_installer
···
On Wednesday, 24 July 2013 13:52:36 UTC+1, Dominic Cleal wrote:
>
> On 24/07/13 13:47, michael...@ul.ie wrote:
> > Would the install log be saved in a particular location?
> > I didn't notice any error messages after running the ruby command
> >
> > >ruby /usr/share/foreman-installer/generate_answers.rb and answering the
> questions
> >
> > When i run the commands
> > >rpm -qa | grep passenger
> >
> > The command prompt just returns and
> >
> > cat /etc/httpd/conf.d/passenger.conf
> >
> >
> > No such file or directory
>
> I don't think the log's kept anywhere at the moment, something that's
> being fixed for 1.3. Try re-running the installer, either with
> generate_answers.rb or by running:
>
> echo include foreman_installer | puppet apply -v --modulepath
> /usr/share/foreman-installer
>
> --
> Dominic Cleal
> Red Hat Engineering
>
···
On Wednesday, July 24, 2013 1:56:08 PM UTC+1, Lukas Zapletal wrote:
>
> Hey,
>
> on a very generic note:
>
> > It gives the fqdn of the server but I cant ping fqdn
>
> If you can't ping FQDN, there is something wrong with our network setup.
>
>
> http://lukas.zapletalovi.com/2011/12/setting-hostname-properly-in-fedora-and.html
>
> --
> Later,
>
> Lukas "lzap" Zapletal
> irc: lzap #theforeman
>
> The output from the puppet apply is
>
> echo include foreman_installer | puppet apply -v --modulepath
> /usr/share/foreman-installer
…
> Info: Applying configuration version '1374670472'
> Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install foreman-proxy'
> returned 1: Error: Package: foreman-proxy-1.2.0-1.el6.noarch (foreman)
> Requires: rubygem(sinatra)
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
>
> Error:
> /Stage[main]/Foreman_proxy::Install/Package[foreman-proxy]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e
> 0 -y install foreman-proxy' returned 1: Error: Package:
> foreman-proxy-1.2.0-1.el6.noarch (foreman)
> Requires: rubygem(sinatra)
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
Alot less red after I added the epel repo and reran the installer. I also
have a lovely foreman web page greeting me on http://localhost now andl https://IPaddress/ and able to login with the default admin and password.
Not sure how I missed the epel repo as I had noticed it in various documents
Thanks everyone for the help.
···
On Wednesday, July 24, 2013 2:03:38 PM UTC+1, Dominic Cleal wrote:
>
> On 24/07/13 14:00, michael...@ul.ie wrote:
> > The output from the puppet apply is
> >
> > echo include foreman_installer | puppet apply -v --modulepath
> > /usr/share/foreman-installer
> ..
> > Info: Applying configuration version '1374670472'
> > Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install foreman-proxy'
> > returned 1: Error: Package: foreman-proxy-1.2.0-1.el6.noarch (foreman)
> > Requires: rubygem(sinatra)
> > You could try using --skip-broken to work around the problem
> > You could try running: rpm -Va --nofiles --nodigest
> >
> > Error:
> > /Stage[main]/Foreman_proxy::Install/Package[foreman-proxy]/ensure:
> > change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e
> > 0 -y install foreman-proxy' returned 1: Error: Package:
> > foreman-proxy-1.2.0-1.el6.noarch (foreman)
> > Requires: rubygem(sinatra)
> > You could try using --skip-broken to work around the problem
> > You could try running: rpm -Va --nofiles --nodigest
>
> You're missing the EPEL repo:
> http://fedoraproject.org/wiki/EPEL
>
> --
> Dominic Cleal
> Red Hat Engineering
>
