Beginner issues: This webpage is not available

ohadlevy · February 2, 2013, 5:57am

> I've been in IT for over 25 years, and a *nix system admin for over 20 of
> them. I've done a lot of C programming before switching over. I've been a
> Linux user since Soft Landing Software (SLS) linux and the 0.90 kernel. I
> learned ruby several years ago, and it's been my favorite system admin
> scripting language since I learned it, so puppet was a natural for me. I
> started using Puppet in a standard puppetmaster → ~150 developer
> workstations configuration about 18 months ago, using the free version of
> puppet (not the commercial distro from puppetlabs), and maintain my modules
> using git. I've decided that I'm ready to start using TheForeman to take
> it to the next level.
>
> I've started playing with foreman, and am using a virtual machine to work
> out my misunderstandings in the process before I try to do it for real, but
> I'm having problems.
>
> I've installed Ubuntu 12.04 LTS server on the virtual machine, and run the
> updates, and installed puppet (and took a snapshot of the VM so I could
> restart at this spot) My VM is configured with Bridged networking so I can
> hit it from other machines with a web browser. Now I'm trying to work
> through the installation. It seems simple, but it doesn't appear to be
> working.
>
> I've read Foreman :: Manual, and some of
> the manual pages, then run the code on the quickstart guide page on my
> Ubuntu 12.04 server VM, including the “echo include puppet, puppet::server,
> foreman, foreman_proxy | puppet apply --modulepath
> /etc/puppet/modules/common” line, Everything seems to install fine (one
> error which says it couldn't delete /etc/puppet/files because it didn't
> exist, but that didn't seem to be a problem) But when I browse to the base
> URL of the site (port 80), it properly redirects me to the https site, then
> errors out with the following error in Chrome:
>
> This webpage is not available
> The webpage at https://foremansvr1/ might be temporarily down or it may
> have moved permanently to a new web address.
> Error 2 (net::ERR_FAILED): Unknown error.
>
>
> Foremansvr1 is in my local hosts file (correctly) on the workstation
> running my VM, which is where I'm running the browser. The logs show that
> it's properly redirecting to the https site, then nothing.
>
> The foreman installer configured both ports (80 & 443) into apache in the
> /etc/apache2/conf.d/foreman.conf file, both should be working fine.
>
What does apache and foreman logs show?

Ohad

···

On Fri, Feb 1, 2013 at 9:54 PM, Ronald Wolf wrote:

Both Apache, and the foreman_proxy are running. No errors in the foreman
logs or the apache logs. Just that one error on the web page. Beyond
that, I’m lost. Anybody got any guidance? Where do I go next?

Thanks in advance for your help.

Ron

–
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-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Ronald_Wolf · February 4, 2013, 4:28pm

Thanks for helping me out, Ohad. The apache "access.log" is empty. The
apache "error.log" contains:

[Fri Feb 01 12:28:36 2013] [notice] Apache/2.2.22 (Ubuntu)
Phusion_Passenger/2.2.11 mod_ssl/2.2.22 OpenSSL/1.0.1 configured –
resuming normal operations
Libvirt binding are missing - hypervisor management is disabled

Both lines came from startup, neither from my attempt to access a page.
The "otherhost_vhosts_access.log" contained:

···

* * foremansvr1:80 172.24.143.137 - - [01/Feb/2013:13:17:39 -0600] "GET / HTTP/1.1" 302 559 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.95 Safari/537.11"

The foreman production.log shows:

Started GET “/” for foremansvr1 at Fri Feb 01 12:16:41 -0600 2013
Processing by DashboardController#index as HTML
Redirected to https://foremansvr1/
Completed 302 Found in 5ms
Fog is not installed - unable to manage compute resources

The foreman-proxy log directory is empty.

Beyond this, where should I be looking for foreman related errors?

Thanks,

Ron

On Friday, February 1, 2013 11:57:44 PM UTC-6, ohad wrote:

What does apache and foreman logs show?

Ohad

Both Apache, and the foreman_proxy are running. No errors in the foreman
logs or the apache logs. Just that one error on the web page. Beyond
that, I’m lost. Anybody got any guidance? Where do I go next?

Thanks in advance for your help.

Ron

–
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 <javascript:>.
To post to this group, send email to forema...@googlegroups.com<javascript:>
.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Gwmngilfen · February 4, 2013, 5:37pm

The first thing that leaps to mind is the apache config - we don't do
<VirtualHost *:443> but rather specifically bind to the IP of eth0 - if
you're hitting it from another interface, or perhaps using a different DNS
name, that can cause problems.

Can you try going to https://ip_of_foremans_eth0_interface/ and see if it
works? The logs show it trying to redirect you to https://foremansvr1/ so
if the DNS for that doesn't match eth0 you may well be hitting this problem.

Greg

Ronald_Wolf · February 4, 2013, 5:51pm

Thanks, Greg, but no joy. My vm has only one network interface up at this
time (although the plan is to bring up a hostonly network to put my
"client" vms on, and this "server" vm will be dual-homed in the final
version) and the machine I'm running the browser on has a local hosts file
entry for this vm.

I ran your test, but it's exactly like the other tries. Same error
message, same log file output (except using ip address instead of name).

···

On Monday, February 4, 2013 11:37:01 AM UTC-6, Greg Sutcliffe wrote: > > The first thing that leaps to mind is the apache config - we don't do > but rather specifically bind to the IP of eth0 - if > you're hitting it from another interface, or perhaps using a different DNS > name, that can cause problems. > > Can you try going to https://ip_of_foremans_eth0_interface/ and see if it > works? The logs show it trying to redirect you to https://foremansvr1/ so > if the DNS for that doesn't match eth0 you may well be hitting this problem. > > Greg >

Gwmngilfen · February 4, 2013, 5:55pm

Intriguing. Lets remove the redirect from the equation - if you set ":ssl:
false" in Foreman's settings.yaml file, and restart apache, you stop seeing
the redirect in foreman's logs. Do you get access at that point? If not,
apache/foreman logs of what you do get without the ssl redirect might be
handy.

Greg

···

On 4 February 2013 17:51, Ronald Wolf wrote:

Thanks, Greg, but no joy. My vm has only one network interface up at this
time (although the plan is to bring up a hostonly network to put my
“client” vms on, and this “server” vm will be dual-homed in the final
version) and the machine I’m running the browser on has a local hosts file
entry for this vm.

Ronald_Wolf · February 4, 2013, 6:15pm

Finally, some progress: I changed ':require_ssl: true' to
':require_ssl: false' in /etc/foreman/settings.yaml, restarted apache and
the login screen came right up. I checked the apache config file generated
for foreman (/etc/apache2/conf.d/foreman.conf) and looked at the
certificates this apache config requires, all certs appear to be right
where apache expects them, and appear to be correctly generated. Certs
appear to be the only real difference between the two virtual hosts. ??

···

On Monday, February 4, 2013 11:55:02 AM UTC-6, Greg Sutcliffe wrote: > > > > > On 4 February 2013 17:51, Ronald Wolf <iba...@gmail.com >wrote: > >> Thanks, Greg, but no joy. My vm has only one network interface up at >> this time (although the plan is to bring up a hostonly network to put my >> "client" vms on, and this "server" vm will be dual-homed in the final >> version) and the machine I'm running the browser on has a local hosts file >> entry for this vm. > > > Intriguing. Lets remove the redirect from the equation - if you set ":ssl: > false" in Foreman's settings.yaml file, and restart apache, you stop seeing > the redirect in foreman's logs. Do you get access at that point? If not, > apache/foreman logs of what you do get without the ssl redirect might be > handy. > > Greg >

Dominic_Cleal1 · April 16, 2013, 3:10pm

> Hi,
>
> I am also running into issues on a Ubuntu 12.04 fresh install.

What issues exactly? You've got diagnostics below, but it's not clear
to me what problem you're seeing.

> Foreman is running and ports are bing listened to:
>
> root@foreman:~# netstat -tan
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address
> State
> tcp 0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN
> tcp 0 0 0.0.0.0:3000 0.0.0.0:*
> LISTEN
> tcp 0 0 0.0.0.0:25 0.0.0.0:*
> LISTEN
> tcp 0 0 0.0.0.0:443 0.0.0.0:*
> LISTEN
> tcp 0 0 0.0.0.0:8443 0.0.0.0:*
> LISTEN
> tcp 0 0 0.0.0.0:8140 0.0.0.0:*
> LISTEN
> tcp 0 0 0.0.0.0:80 0.0.0.0:*
> LISTEN
> Looking for processes containing foreman …
> 998 8467 0.0 2.9 104788 29604 ? S 14:15 0:00
> ruby /usr/share/foreman-proxy/bin/smart-proxy
> foreman 8933 0.0 13.1 218564 133968 ? S 14:21 0:00
> /usr/bin/ruby1.8 script/rails server -b 0.0.0.0 -p 3000 -e production -d

You normally see a "Rack" process too, though maybe that's only when the
first client connects.

> /var/log/foreman/production.log is empty
> Apache error.log
> Apache/2.2.22 (Ubuntu) Phusion_Passenger/2.2.11 mod_ssl/2.2.22
> OpenSSL/1.0.1 configured
> /var/log/apache2/access.log /var/log/apache2/other_vhosts_access.log empty.
>
> Tried setting ssl:false in /etc/foreman/settings.yaml
>
> Installation was done as follows:
>
> # some dependancies additonally needed
>
> apt-get install sqlite3
> mkdir -p /usr/share/puppet/modules /etc/puppet/files
>
>
>
> echo "deb http://deb.theforeman.org/ squeeze stable" >
> /etc/apt/sources.list.d/foreman.list
> wget -q http://deb.theforeman.org/foreman.asc -O- | apt-key add -
> apt-get update && apt-get install foreman-installer
>
> ruby /usr/share/foreman-installer/generate_answers.rb
> su - foreman -s /bin/bash -c /usr/share/foreman/extras/dbmigrate
> vi /etc/default/foreman
> /etc/init.d/foreman start
> Libvirt binding are missing - hypervisor management is disabled

This should be unnecessary, it runs a separate service on port 3000
while it should be running under Apache and Passenger.

···

On 16/04/13 13:33, Sean Boran wrote:

–
Dominic Cleal
Red Hat Engineering

Sean_Boran · April 16, 2013, 3:38pm

I cannot see anything in the webgui (https or http:////myhost.mysite.com),
as described in the first post in the thread.
Although the daemons seem to running, not much is happening.

Sean

···

On Tuesday, April 16, 2013 5:10:13 PM UTC+2, Dominic Cleal wrote: > > On 16/04/13 13:33, Sean Boran wrote: > > Hi, > > > > I am also running into issues on a Ubuntu 12.04 fresh install. > > What issues exactly? You've got diagnostics below, but it's not clear > to me what problem you're seeing. > > > Foreman is running and ports are bing listened to: > > > > root@foreman:~# netstat -tan > > Active Internet connections (servers and established) > > Proto Recv-Q Send-Q Local Address Foreign Address > > State > > tcp 0 0 0.0.0.0:22 0.0.0.0:* > > LISTEN > > tcp 0 0 0.0.0.0:3000 0.0.0.0:* > > LISTEN > > tcp 0 0 0.0.0.0:25 0.0.0.0:* > > LISTEN > > tcp 0 0 0.0.0.0:443 0.0.0.0:* > > LISTEN > > tcp 0 0 0.0.0.0:8443 0.0.0.0:* > > LISTEN > > tcp 0 0 0.0.0.0:8140 0.0.0.0:* > > LISTEN > > tcp 0 0 0.0.0.0:80 0.0.0.0:* > > LISTEN > > Looking for processes containing foreman ... > > 998 8467 0.0 2.9 104788 29604 ? S 14:15 0:00 > > ruby /usr/share/foreman-proxy/bin/smart-proxy > > foreman 8933 0.0 13.1 218564 133968 ? S 14:21 0:00 > > /usr/bin/ruby1.8 script/rails server -b 0.0.0.0 -p 3000 -e > production -d > > You normally see a "Rack" process too, though maybe that's only when the > first client connects. > > > /var/log/foreman/production.log is empty > > Apache error.log > > Apache/2.2.22 (Ubuntu) Phusion_Passenger/2.2.11 mod_ssl/2.2.22 > > OpenSSL/1.0.1 configured > > /var/log/apache2/access.log /var/log/apache2/other_vhosts_access.log > empty. > > > > Tried setting ssl:false in /etc/foreman/settings.yaml > > > > Installation was done as follows: > > > > # some dependancies additonally needed > > > > apt-get install sqlite3 > > mkdir -p /usr/share/puppet/modules /etc/puppet/files > > > > > > > > echo "deb http://deb.theforeman.org/ squeeze stable" > > > /etc/apt/sources.list.d/foreman.list > > wget -q http://deb.theforeman.org/foreman.asc -O- | apt-key add - > > apt-get update && apt-get install foreman-installer > > > > ruby /usr/share/foreman-installer/generate_answers.rb > > su - foreman -s /bin/bash -c /usr/share/foreman/extras/dbmigrate > > vi /etc/default/foreman > > /etc/init.d/foreman start > > Libvirt binding are missing - hypervisor management is disabled > > This should be unnecessary, it runs a separate service on port 3000 > while it should be running under Apache and Passenger. > > -- > Dominic Cleal > Red Hat Engineering >

Sean_Boran · April 16, 2013, 4:10pm

How does puppet fit into the installer picture? Below the installed was
downloaded and run, but when/where is the puppet master started, and
the puppet client run. Is the install only finished when puppet client and
master have run?

Puppet master I've not enabled via:
vi /etc/default/puppetmaster
/etc/init.d/puppetmaster start

then ran puppet agent --test but get some warnings:

Apr 16 18:04:37 foreman puppet-agent[10344]: (/File[/var/lib/puppet/lib])
Could not evaluate: Could not retrieve information
from environment production source(s) puppet://foreman.mysite.ch/plugins
err: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve
information from environmen t production source(s)
puppet://foreman.mysite.ch/plugins
Apr 16 18:04:37 foreman puppet-agent[10344]:
(/File[/var/lib/puppet/lib/puppet]) Dependency File[/v
ar/lib/puppet/lib] has failures: true
notice: /File[/var/lib/puppet/lib/puppet]: Dependency
File[/var/lib/puppet/lib] has failures: true
Apr 16 18:04:37 foreman puppet-agent[10344]:
(/File[/var/lib/puppet/lib/puppet]) Skipping because o
f failed dependencies
warning: /File[/var/lib/puppet/lib/puppet]: Skipping because of failed
dependencies

Questions;

Are the puppet master + client to be started as part of the install?
Could this be stopping the webgui from working?

Also set:login: false in /etc/foreman/settings.yaml and restarted apache to
see if that would allow some access, but not luck.

Sean

···

On Tuesday, April 16, 2013 5:38:59 PM UTC+2, Sean Boran wrote: > > > I cannot see anything in the webgui (https or http:////myhost.mysite.com), > as described in the first post in the thread. > Although the daemons seem to running, not much is happening. > > Sean > > > On Tuesday, April 16, 2013 5:10:13 PM UTC+2, Dominic Cleal wrote: >> >> On 16/04/13 13:33, Sean Boran wrote: >> > Hi, >> > >> > I am also running into issues on a Ubuntu 12.04 fresh install. >> >> What issues exactly? You've got diagnostics below, but it's not clear >> to me what problem you're seeing. >> >> > Foreman is running and ports are bing listened to: >> > >> > root@foreman:~# netstat -tan >> > Active Internet connections (servers and established) >> > Proto Recv-Q Send-Q Local Address Foreign Address >> > State >> > tcp 0 0 0.0.0.0:22 0.0.0.0:* >> >> > LISTEN >> > tcp 0 0 0.0.0.0:3000 0.0.0.0:* >> >> > LISTEN >> > tcp 0 0 0.0.0.0:25 0.0.0.0:* >> >> > LISTEN >> > tcp 0 0 0.0.0.0:443 0.0.0.0:* >> >> > LISTEN >> > tcp 0 0 0.0.0.0:8443 0.0.0.0:* >> >> > LISTEN >> > tcp 0 0 0.0.0.0:8140 0.0.0.0:* >> >> > LISTEN >> > tcp 0 0 0.0.0.0:80 0.0.0.0:* >> >> > LISTEN >> > Looking for processes containing foreman ... >> > 998 8467 0.0 2.9 104788 29604 ? S 14:15 0:00 >> > ruby /usr/share/foreman-proxy/bin/smart-proxy >> > foreman 8933 0.0 13.1 218564 133968 ? S 14:21 0:00 >> > /usr/bin/ruby1.8 script/rails server -b 0.0.0.0 -p 3000 -e >> production -d >> >> You normally see a "Rack" process too, though maybe that's only when the >> first client connects. >> >> > /var/log/foreman/production.log is empty >> > Apache error.log >> > Apache/2.2.22 (Ubuntu) Phusion_Passenger/2.2.11 mod_ssl/2.2.22 >> > OpenSSL/1.0.1 configured >> > /var/log/apache2/access.log /var/log/apache2/other_vhosts_access.log >> empty. >> > >> > Tried setting ssl:false in /etc/foreman/settings.yaml >> > >> > Installation was done as follows: >> > >> > # some dependancies additonally needed >> > >> > apt-get install sqlite3 >> > mkdir -p /usr/share/puppet/modules /etc/puppet/files >> > >> > >> > >> > echo "deb http://deb.theforeman.org/ squeeze stable" > >> > /etc/apt/sources.list.d/foreman.list >> > wget -q http://deb.theforeman.org/foreman.asc -O- | apt-key add - >> > apt-get update && apt-get install foreman-installer >> > >> > ruby /usr/share/foreman-installer/generate_answers.rb >> > su - foreman -s /bin/bash -c /usr/share/foreman/extras/dbmigrate >> > vi /etc/default/foreman >> > /etc/init.d/foreman start >> > Libvirt binding are missing - hypervisor management is disabled >> >> This should be unnecessary, it runs a separate service on port 3000 >> while it should be running under Apache and Passenger. >> >> -- >> Dominic Cleal >> Red Hat Engineering >> >

Dominic_Cleal1 · April 17, 2013, 7:27am

So you get the Foreman interface and there's no data in it (just the
welcome page)?

Or you don't get the Foreman interface and you get some sort of error or
another page?

···

-- Dominic Cleal Red Hat Engineering

On 16/04/13 16:38, Sean Boran wrote:

I cannot see anything in the webgui (https or
http:////myhost.mysite.com), as described in the first post in the thread.
Although the daemons seem to running, not much is happening.

Sean

On Tuesday, April 16, 2013 5:10:13 PM UTC+2, Dominic Cleal wrote:

On 16/04/13 13:33, Sean Boran wrote:
> Hi,
>
> I am also running into issues on a Ubuntu 12.04 fresh install.

What issues exactly?  You've got diagnostics below, but it's not clear
to me what problem you're seeing.

> Foreman is running and ports are bing listened to:
>
>     root@foreman:~# netstat -tan
>     Active Internet connections (servers and established)
>     Proto Recv-Q Send-Q Local Address           Foreign Address  
     
>     State
>     tcp        0      0 0.0.0.0:22 <http://0.0.0.0:22>            
 0.0.0.0:*              
>     LISTEN
>     tcp        0      0 0.0.0.0:3000 <http://0.0.0.0:3000>        
   0.0.0.0:*              
>     LISTEN
>     tcp        0      0 0.0.0.0:25 <http://0.0.0.0:25>            
 0.0.0.0:*              
>     LISTEN
>     tcp        0      0 0.0.0.0:443 <http://0.0.0.0:443>          
  0.0.0.0:*              
>     LISTEN
>     tcp        0      0 0.0.0.0:8443 <http://0.0.0.0:8443>        
   0.0.0.0:*              
>     LISTEN
>     tcp        0      0 0.0.0.0:8140 <http://0.0.0.0:8140>        
   0.0.0.0:*              
>     LISTEN
>     tcp        0      0 0.0.0.0:80 <http://0.0.0.0:80>            
 0.0.0.0:*              
>     LISTEN
>     Looking for processes containing foreman ...
>     998       8467  0.0  2.9 104788 29604 ?        S    14:15   0:00
>     ruby /usr/share/foreman-proxy/bin/smart-proxy
>     foreman   8933  0.0 13.1 218564 133968 ?       S    14:21   0:00
>     /usr/bin/ruby1.8 script/rails server -b 0.0.0.0 -p 3000 -e
production -d

You normally see a "Rack" process too, though maybe that's only when
the
first client connects.

> /var/log/foreman/production.log is empty
> Apache error.log
>  Apache/2.2.22 (Ubuntu) Phusion_Passenger/2.2.11 mod_ssl/2.2.22
> OpenSSL/1.0.1 configured
> /var/log/apache2/access.log
/var/log/apache2/other_vhosts_access.log empty.
>
> Tried setting ssl:false in /etc/foreman/settings.yaml
>
> Installation was done as follows:
>
>     # some dependancies additonally needed
>
>     apt-get install sqlite3          
>     mkdir -p /usr/share/puppet/modules /etc/puppet/files
>
>  
>
>     echo "deb http://deb.theforeman.org/ squeeze stable" >
>     /etc/apt/sources.list.d/foreman.list
>     wget -q http://deb.theforeman.org/foreman.asc
<http://deb.theforeman.org/foreman.asc> -O- | apt-key add -
>     apt-get update && apt-get install foreman-installer
>        
>     ruby /usr/share/foreman-installer/generate_answers.rb
>     su - foreman -s /bin/bash -c /usr/share/foreman/extras/dbmigrate
>     vi /etc/default/foreman
>     /etc/init.d/foreman start
>       Libvirt binding are missing - hypervisor management is disabled

This should be unnecessary, it runs a separate service on port 3000
while it should be running under Apache and Passenger.

-- 
Dominic Cleal
Red Hat Engineering

–
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-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Sean_Boran · April 17, 2013, 8:30am

Er, I was getting nothing at all, but this morning I can login and see the
GUI, its working fine.
Strange indeed, perhaps its the puppet master/agent changes made (see
higher is this thread):

vi /etc/default/puppetmaster
/etc/init.d/puppetmaster start

 export MODULE_PATH=&quot;/etc/puppet/modules/common&quot;
mkdir -p $MODULE_PATH
for mod in apache foreman foreman_proxy passenger puppet tftp xinetd; do
  mkdir -p $MODULE_PATH/$mod
  wget http://github.com/theforeman/puppet-$mod/tarball/master -O - |

tar xzvf - -C $MODULE_PATH/$mod --strip-components=1
done;
sudo puppet agent --test

I dont quite understand how puppet fits into the installation procedure.

Sean

···

On Wednesday, April 17, 2013 9:27:14 AM UTC+2, Dominic Cleal wrote: > > So you get the Foreman interface and there's no data in it (just the > welcome page)? > > Or you don't get the Foreman interface and you get some sort of error or > another page? > > -- > Dominic Cleal > Red Hat Engineering > > On 16/04/13 16:38, Sean Boran wrote: > > > > I cannot see anything in the webgui (https or > > http:////myhost.mysite.com), as described in the first post in the > thread. > > Although the daemons seem to running, not much is happening. > > > > Sean > > > > > > On Tuesday, April 16, 2013 5:10:13 PM UTC+2, Dominic Cleal wrote: > > > > On 16/04/13 13:33, Sean Boran wrote: > > > Hi, > > > > > > I am also running into issues on a Ubuntu 12.04 fresh install. > > > > What issues exactly? You've got diagnostics below, but it's not > clear > > to me what problem you're seeing. > > > > > Foreman is running and ports are bing listened to: > > > > > > root@foreman:~# netstat -tan > > > Active Internet connections (servers and established) > > > Proto Recv-Q Send-Q Local Address Foreign Address > > > > > State > > > tcp 0 0 0.0.0.0:22 > > > 0.0.0.0:* > > > LISTEN > > > tcp 0 0 0.0.0.0:3000 > > > 0.0.0.0:* > > > LISTEN > > > tcp 0 0 0.0.0.0:25 > > > 0.0.0.0:* > > > LISTEN > > > tcp 0 0 0.0.0.0:443 > > > 0.0.0.0:* > > > LISTEN > > > tcp 0 0 0.0.0.0:8443 > > > 0.0.0.0:* > > > LISTEN > > > tcp 0 0 0.0.0.0:8140 > > > 0.0.0.0:* > > > LISTEN > > > tcp 0 0 0.0.0.0:80 > > > 0.0.0.0:* > > > LISTEN > > > Looking for processes containing foreman ... > > > 998 8467 0.0 2.9 104788 29604 ? S 14:15 > 0:00 > > > ruby /usr/share/foreman-proxy/bin/smart-proxy > > > foreman 8933 0.0 13.1 218564 133968 ? S 14:21 > 0:00 > > > /usr/bin/ruby1.8 script/rails server -b 0.0.0.0 -p 3000 -e > > production -d > > > > You normally see a "Rack" process too, though maybe that's only when > > the > > first client connects. > > > > > /var/log/foreman/production.log is empty > > > Apache error.log > > > Apache/2.2.22 (Ubuntu) Phusion_Passenger/2.2.11 mod_ssl/2.2.22 > > > OpenSSL/1.0.1 configured > > > /var/log/apache2/access.log > > /var/log/apache2/other_vhosts_access.log empty. > > > > > > Tried setting ssl:false in /etc/foreman/settings.yaml > > > > > > Installation was done as follows: > > > > > > # some dependancies additonally needed > > > > > > apt-get install sqlite3 > > > mkdir -p /usr/share/puppet/modules /etc/puppet/files > > > > > > > > > > > > echo "deb http://deb.theforeman.org/ squeeze stable" > > > > /etc/apt/sources.list.d/foreman.list > > > wget -q http://deb.theforeman.org/foreman.asc > > -O- | apt-key add - > > > apt-get update && apt-get install foreman-installer > > > > > > ruby /usr/share/foreman-installer/generate_answers.rb > > > su - foreman -s /bin/bash -c > /usr/share/foreman/extras/dbmigrate > > > vi /etc/default/foreman > > > /etc/init.d/foreman start > > > Libvirt binding are missing - hypervisor management is > disabled > > > > This should be unnecessary, it runs a separate service on port 3000 > > while it should be running under Apache and Passenger. > > > > -- > > Dominic Cleal > > Red Hat Engineering > > > > -- > > 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?hl=en. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > >

Dominic_Cleal1 · April 17, 2013, 9:10am

The puppetmaster should have nothing to do with it, and on a default
install you shouldn't need to do any of those steps. The puppetmaster
runs under Apache and you already have those modules in
/usr/share/foreman-installer.

Puppet is used locally only with no agent/master setup for the
installation. It runs "puppet apply" against
/usr/share/foreman-installer to configure Foreman and also sets up a
puppetmaster on the host which is then able to serve itself and other
agents.

···

-- Dominic Cleal Red Hat Engineering

On 17/04/13 09:30, Sean Boran wrote:

Er, I was getting nothing at all, but this morning I can login and see
the GUI, its working fine.
Strange indeed, perhaps its the puppet master/agent changes made (see
higher is this thread):

vi /etc/default/puppetmaster
/etc/init.d/puppetmaster start

     export MODULE_PATH="/etc/puppet/modules/common"
    mkdir -p $MODULE_PATH
    for mod in apache foreman foreman_proxy passenger puppet tftp
xinetd; do
      mkdir -p $MODULE_PATH/$mod
      wget http://github.com/theforeman/puppet-$mod/tarball/master
-O - | tar xzvf - -C $MODULE_PATH/$mod --strip-components=1
    done;
     sudo puppet agent --test

I dont quite understand how puppet fits into the installation procedure.

Sean

On Wednesday, April 17, 2013 9:27:14 AM UTC+2, Dominic Cleal wrote:

So you get the Foreman interface and there's no data in it (just the
welcome page)?

Or you don't get the Foreman interface and you get some sort of
error or
another page?

-- 
Dominic Cleal
Red Hat Engineering

On 16/04/13 16:38, Sean Boran wrote:
>
> I cannot see anything in the webgui (https or
> http:////myhost.mysite.com <http://myhost.mysite.com>), as
described in the first post in the thread.
> Although the daemons seem to running, not much is happening.
>
> Sean
>
>
> On Tuesday, April 16, 2013 5:10:13 PM UTC+2, Dominic Cleal wrote:
>
>     On 16/04/13 13:33, Sean Boran wrote:
>     > Hi,
>     >
>     > I am also running into issues on a Ubuntu 12.04 fresh install.
>
>     What issues exactly?  You've got diagnostics below, but it's
not clear
>     to me what problem you're seeing.
>
>     > Foreman is running and ports are bing listened to:
>     >
>     >     root@foreman:~# netstat -tan
>     >     Active Internet connections (servers and established)
>     >     Proto Recv-Q Send-Q Local Address           Foreign
Address  
>          
>     >     State
>     >     tcp        0      0 0.0.0.0:22 <http://0.0.0.0:22>
<http://0.0.0.0:22>            
>      0.0.0.0:*              
>     >     LISTEN
>     >     tcp        0      0 0.0.0.0:3000 <http://0.0.0.0:3000>
<http://0.0.0.0:3000>        
>        0.0.0.0:*              
>     >     LISTEN
>     >     tcp        0      0 0.0.0.0:25 <http://0.0.0.0:25>
<http://0.0.0.0:25>            
>      0.0.0.0:*              
>     >     LISTEN
>     >     tcp        0      0 0.0.0.0:443 <http://0.0.0.0:443>
<http://0.0.0.0:443>          
>       0.0.0.0:*              
>     >     LISTEN
>     >     tcp        0      0 0.0.0.0:8443 <http://0.0.0.0:8443>
<http://0.0.0.0:8443>        
>        0.0.0.0:*              
>     >     LISTEN
>     >     tcp        0      0 0.0.0.0:8140 <http://0.0.0.0:8140>
<http://0.0.0.0:8140>        
>        0.0.0.0:*              
>     >     LISTEN
>     >     tcp        0      0 0.0.0.0:80 <http://0.0.0.0:80>
<http://0.0.0.0:80>            
>      0.0.0.0:*              
>     >     LISTEN
>     >     Looking for processes containing foreman ...
>     >     998       8467  0.0  2.9 104788 29604 ?        S  
 14:15   0:00
>     >     ruby /usr/share/foreman-proxy/bin/smart-proxy
>     >     foreman   8933  0.0 13.1 218564 133968 ?       S  
 14:21   0:00
>     >     /usr/bin/ruby1.8 script/rails server -b 0.0.0.0 -p 3000 -e
>     production -d
>
>     You normally see a "Rack" process too, though maybe that's
only when
>     the
>     first client connects.
>
>     > /var/log/foreman/production.log is empty
>     > Apache error.log
>     >  Apache/2.2.22 (Ubuntu) Phusion_Passenger/2.2.11 mod_ssl/2.2.22
>     > OpenSSL/1.0.1 configured
>     > /var/log/apache2/access.log
>     /var/log/apache2/other_vhosts_access.log empty.
>     >
>     > Tried setting ssl:false in /etc/foreman/settings.yaml
>     >
>     > Installation was done as follows:
>     >
>     >     # some dependancies additonally needed
>     >
>     >     apt-get install sqlite3          
>     >     mkdir -p /usr/share/puppet/modules /etc/puppet/files
>     >
>     >  
>     >
>     >     echo "deb http://deb.theforeman.org/ squeeze stable" >
>     >     /etc/apt/sources.list.d/foreman.list
>     >     wget -q http://deb.theforeman.org/foreman.asc
<http://deb.theforeman.org/foreman.asc>
>     <http://deb.theforeman.org/foreman.asc
<http://deb.theforeman.org/foreman.asc>> -O- | apt-key add -
>     >     apt-get update && apt-get install foreman-installer
>     >        
>     >     ruby /usr/share/foreman-installer/generate_answers.rb
>     >     su - foreman -s /bin/bash -c
/usr/share/foreman/extras/dbmigrate
>     >     vi /etc/default/foreman
>     >     /etc/init.d/foreman start
>     >       Libvirt binding are missing - hypervisor management is
disabled
>
>     This should be unnecessary, it runs a separate service on port
3000
>     while it should be running under Apache and Passenger.
>
>     --
>     Dominic Cleal
>     Red Hat Engineering
>
> --
> 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 <javascript:>.
> To post to this group, send email to forema...@googlegroups.com
<javascript:>.
> Visit this group at
http://groups.google.com/group/foreman-users?hl=en
<http://groups.google.com/group/foreman-users?hl=en>.
> For more options, visit https://groups.google.com/groups/opt_out
<https://groups.google.com/groups/opt_out>.
>  
>

–
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-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.