Foreman 0.2 Release Candidate

Hello All,

I'm happy to announce a new release candidate of Foreman, top highlights
for this release includes:

  • New look and feel
  • Extended restful API
  • Support for New Puppet Reports format
  • Full VM/physical host Provisioning
  • Powerful template generator ( pxelinux, gpxe, kickstart, preseed, grub
    etc…)
  • introduce a new service called smart proxy (which can run on remote
    machines) to manage the following services:
    ** DNS Management
    ** DHCP Management
    ** TFTP Management
    ** Puppet/PuppetCA Management

This release is a major release packed with goodies, around 130 tickets
were closed

Release notes can be found here:
http://theforeman.org/projects/foreman/wiki/ReleaseNotes

Full change log can be found here: http://theforeman.org/versions/show/9

As usually many many thanks to all contributors and users

RPMS for both smart proxy and foreman can be found at
http://yum.theforeman.org/test

Have fun,
Ohad

>
>
>
>> Super cool, Ohad.
>> Is there a RPM for this RC?
>>
> http://yum.theforeman.org/test/RPMS/foreman-0.2-rc1.1.noarch.rpm
>
>
> The version of rubygem-rest-client in EPEL is 1.3.1 however the the new
> version requires 1.4.0. Maybe update the spec file / RPM to reflect this?
>
> Thanks for the reminder :slight_smile:

I guess I was not sure what would be better, a failure to install foreman on
RHEL5 (as the package is missing) or a failure when starting foreman.

I know (and its in the release notes), I've asked the upstream maintainer in
EPEL to update the package, but if that won't be provided, I guess we could
try to provide a newer version in foreman's repo.

··· On Tue, Mar 22, 2011 at 10:28 PM, Cody Robertson wrote: > On 03/22/2011 04:23 PM, Ohad Levy wrote: > On Tue, Mar 22, 2011 at 10:04 PM, Eduardo S. Scarpellini < > scarpellini@gmail.com> wrote:


Cody Robertson 1-800-859-8803 ext. 5


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

Note that the latest RPM for the smart proxy is actually in the stable repo

··· On Tue, Mar 22, 2011 at 10:23 PM, Ohad Levy wrote:

On Tue, Mar 22, 2011 at 10:04 PM, Eduardo S. Scarpellini < > scarpellini@gmail.com> wrote:

Super cool, Ohad.
Is there a RPM for this RC?

http://yum.theforeman.org/test/RPMS/foreman-0.2-rc1.1.noarch.rpm

Ohad

http://yum.theforeman.org/stable/RPMS/foreman-proxy-0.1-1.noarch.rpm

Ohad

On Mar 22, 2011 4:52 PM, “Martin Willemsma” mwillemsma@gmail.com wrote:

Thanks guys. Really cool new features to try out tomorrow!

I would love to see the unattended installation part replace our
deployer
solution which is currently installing hosts 1 by 1.


Kind regards,

Martin Willemsma

2011/3/22 Ohad Levy ohadlevy@gmail.com

Hello All,

I’m happy to announce a new release candidate of Foreman, top
highlights

for this release includes:

  • New look and feel
  • Extended restful API
  • Support for New Puppet Reports format
  • Full VM/physical host Provisioning
  • Powerful template generator ( pxelinux, gpxe, kickstart, preseed,
    grub

etc…)

  • introduce a new service called smart proxy (which can run on remote
    machines) to manage the following services:
    ** DNS Management
    ** DHCP Management
    ** TFTP Management
    ** Puppet/PuppetCA Management

This release is a major release packed with goodies, around 130 tickets
were closed

Release notes can be found here:
ReleaseNotes - Foreman

Full change log can be found here:
http://theforeman.org/versions/show/9

As usually many many thanks to all contributors and users

RPMS for both smart proxy and foreman can be found at
http://yum.theforeman.org/test

Have fun,
Ohad


You received this message because you are subscribed to the Google
Groups

“Puppet Users” group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@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-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@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-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi,

there are also new packages for Foreman 0.2 RC1 and Smart-Proxy 0.1 (package
called foreman-proxy) in the testing repository for Debian and Ubuntu Linux.

You can find installation instructions in the Foreman wiki under 1.

I'd like to encourage everybody with some spare time to give these packages a
test run so that they can move to the stable repository in a timely manner
after the coming Foreman 0.2 release. If you encounter any errors, please file
a bug for the packages in our issue tracker[2].

Ubuntu-Packages
[2]: Issues - Foreman

Regards
Jochen

··· Am Dienstag, 22. März 2011, 16:21:34 schrieb Ohad Levy: > Hello All, > > I'm happy to announce a new release candidate of Foreman, top highlights > for this release includes: > > * New look and feel > * Extended restful API > * Support for New Puppet Reports format > * Full VM/physical host Provisioning > * Powerful template generator ( pxelinux, gpxe, kickstart, preseed, grub > etc..) > * introduce a new service called smart proxy (which can run on remote > machines) to manage the following services: > ** DNS Management > ** DHCP Management > ** TFTP Management > ** Puppet/PuppetCA Management > > This release is a major release packed with goodies, around 130 tickets > were closed > > Release notes can be found here: > http://theforeman.org/projects/foreman/wiki/ReleaseNotes > > Full change log can be found here: http://theforeman.org/versions/show/9 > > As usually many many thanks to all contributors and users > > RPMS for both smart proxy and foreman can be found at > http://yum.theforeman.org/test > > Have fun, > Ohad

Hello All,

I'm happy to announce a new release of Foreman, top highlights
for this release includes:

  • New look and feel
  • Extended restful API
  • Support for New Puppet Reports format
  • Full VM/physical host Provisioning
  • Powerful template generator ( pxelinux, gpxe, kickstart, preseed, grub
    etc…)
  • introduce a new service called smart proxy (which can run on remote
    machines) to manage the following services:
    ** DNS Management
    ** DHCP Management
    ** TFTP Management
    ** Puppet/PuppetCA Management

This release is a major release packed with goodies, more than 130
tickets were closed.

Release notes can be found here:
http://theforeman.org/projects/foreman/wiki/ReleaseNotes

Full change log can be found here: http://theforeman.org/versions/show/9

As usually many many thanks to all contributors and users

RPMS for both smart proxy and foreman can be found at
http://yum.theforeman.org/stable

Have fun,
Ohad

> Hi,
>
> there are also new packages for Foreman 0.2 RC1 and Smart-Proxy 0.1
> (package
> called foreman-proxy) in the testing repository for Debian and Ubuntu
> Linux.
>
> You can find installation instructions in the Foreman wiki under [1].
>
> I'd like to encourage everybody with some spare time to give these packages
> a
> test run so that they can move to the stable repository in a timely manner
> after the coming Foreman 0.2 release. If you encounter any errors, please
> file
> a bug for the packages in our issue tracker[2].
>
>
> [1]:
>
> Installation instructions - Foreman
> Ubuntu-Packages
> [2]: Issues - Foreman
>
>
> Regards
> Jochen
>
> Thanks Jochen, I' ve installed foreman 0.2 on Debian Squeeze 6.0.1, found
one issue though.

When starting foreman from the init script it does not start:
root@squeeze:~# /etc/init.d/foreman start
root@squeeze:~# ps aux|grep foreman|grep -v grep
foreman 6857 0.0 0.5 73056 11160 ? S 21:27 0:00 ruby
/usr/share/foreman-proxy/bin/smart-proxy

Doing some debugging I got:

  • PATH=/sbin:/usr/sbin:/bin:/usr/bin
  • DESC='Foreman systems management web application'
  • NAME=foreman
  • SCRIPTNAME=/etc/init.d/foreman
  • '[' -r /etc/default/foreman ']'
  • . /etc/default/foreman
    ++ START=yes
    ++ FOREMAN_HOME=/usr/share/foreman
    ++ FOREMAN_IFACE=192.168.0.102
    ++ FOREMAN_PORT=3000
    ++ FOREMAN_USER=foreman
    ++ FOREMAN_ENV=production
  • FOREMAN_IFACE=192.168.0.102
  • FOREMAN_PORT=3000
  • FOREMAN_USER=foreman
  • FOREMAN_HOME=/usr/share/foreman
  • FOREMAN_ENV=production
  • FOREMAN_PID=/usr/share/foreman/tmp/pids/server.pid
  • DAEMON=/usr/share/foreman/script/server
  • DAEMON_OPTS='-b 192.168.0.102 -p 3000 -e production -d'
  • . /lib/init/vars.sh
    ++ '[' -f /etc/default/rcS ']'
    ++ . /etc/default/rcS
    +++ TMPTIME=0
    +++ SULOGIN=no
    +++ DELAYLOGIN=no
    +++ UTC=yes
    +++ VERBOSE=no
    +++ FSCKFIX=no
    +++ RAMRUN=no
    +++ RAMLOCK=no
    ++ '[' -r /proc/cmdline ']'
    +++ cat /proc/cmdline
    ++ for ARG in '$(cat /proc/cmdline)'
    ++ case $ARG in
    ++ for ARG in '$(cat /proc/cmdline)'
    ++ case $ARG in
    ++ for ARG in '$(cat /proc/cmdline)'
    ++ case $ARG in
    ++ for ARG in '$(cat /proc/cmdline)'
    ++ case $ARG in
    ++ '[' '' ']'
    ++ break
    ++ '[' '' ']'
  • . /lib/lsb/init-functions
    ++ FANCYTTY=
    ++ '[' -e /etc/lsb-base-logging.sh ']'
    ++ true
  • case "$1" in
  • '[' no '!=' no ']'
  • do_start
  • is_true yes
  • '[' xyes = xtrue -o xyes = xyes -o xyes = x0 ']'
  • return 0
  • start-stop-daemon --start --quiet --chuid foreman --pidfile
    /usr/share/foreman/tmp/pids/server.pid --chdir /usr/share/foreman --exec
    /usr/share/foreman/script/server – -b 192.168.0.102 -p 3000 -e production
    -d
  • case "$?" in
  • RETVAL=0
  • '[' no '!=' no ']'
  • exit 0

Trying the start-stop-daemon manually works:

root@squeeze:~# start-stop-daemon --start --quiet --chuid foreman --pidfile
/usr/share/foreman/tmp/pids/server.pid --chdir /usr/share/foreman --exec
/usr/share/foreman/script/server – -b 192.168.0.102 -p 3000 -e production
-d
=> Booting WEBrick
=> Rails 2.3.11 application starting on http://192.168.0.102:3000
root@squeeze:/usr/share/foreman/script# ps aux|grep foreman|grep -v grep
foreman 6857 0.0 0.5 73056 11160 ? S 21:27 0:00 ruby
/usr/share/foreman-proxy/bin/smart-proxy
foreman 7756 68.8 5.6 229444 116596 ? S 22:02 0:04 ruby
/usr/share/foreman/script/server -b 192.168.0.102 -p 3000 -e production -d

any thoughts?

Thanks.

··· On Wed, Mar 23, 2011 at 5:18 PM, Jochen Schalanda wrote:

Am Dienstag, 22. März 2011, 16:21:34 schrieb Ohad Levy:

Hello All,

I’m happy to announce a new release candidate of Foreman, top highlights
for this release includes:

  • New look and feel
  • Extended restful API
  • Support for New Puppet Reports format
  • Full VM/physical host Provisioning
  • Powerful template generator ( pxelinux, gpxe, kickstart, preseed, grub
    etc…)
  • introduce a new service called smart proxy (which can run on remote
    machines) to manage the following services:
    ** DNS Management
    ** DHCP Management
    ** TFTP Management
    ** Puppet/PuppetCA Management

This release is a major release packed with goodies, around 130 tickets
were closed

Release notes can be found here:
ReleaseNotes - Foreman

Full change log can be found here: http://theforeman.org/versions/show/9

As usually many many thanks to all contributors and users

RPMS for both smart proxy and foreman can be found at
http://yum.theforeman.org/test

Have fun,
Ohad


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.


Tony
http://blog.tonyskapunk.net

Hi Tony,

the output of the Foreman init script doesn't print any error in the output
you've provided. Maybe you could change the start-stop-daemon call in the init
script's do_start() function to include the --verbose (-v) parameter and
remove the output redirection (>/dev/null) from the same line.

I hope that this will give an indication where to look for the error.

Regards
Jochen

··· Am Donnerstag, 24. März 2011, 04:58:58 schrieb Tony G.: > On Wed, Mar 23, 2011 at 5:18 PM, Jochen Schalanda wrote: > > Hi, > > > > there are also new packages for Foreman 0.2 RC1 and Smart-Proxy 0.1 > > (package > > called foreman-proxy) in the testing repository for Debian and Ubuntu > > Linux. > > > > You can find installation instructions in the Foreman wiki under [1]. > > > > I'd like to encourage everybody with some spare time to give these > > packages a > > test run so that they can move to the stable repository in a timely > > manner after the coming Foreman 0.2 release. If you encounter any > > errors, please file > > a bug for the packages in our issue tracker[2]. > > > > > > [1]: > > > > http://theforeman.org/projects/foreman/wiki/Installation_instructions#Deb > > ian- Ubuntu-Packages > > [2]: http://theforeman.org/projects/foreman/issues > > > > > > Regards > > Jochen > > > > Thanks Jochen, I' ve installed foreman 0.2 on Debian Squeeze 6.0.1, > > found > > one issue though. > > When starting foreman from the init script it does not start: > root@squeeze:~# /etc/init.d/foreman start > root@squeeze:~# ps aux|grep foreman|grep -v grep > foreman 6857 0.0 0.5 73056 11160 ? S 21:27 0:00 ruby > /usr/share/foreman-proxy/bin/smart-proxy > > Doing some debugging I got: > > + PATH=/sbin:/usr/sbin:/bin:/usr/bin > + DESC='Foreman systems management web application' > + NAME=foreman > + SCRIPTNAME=/etc/init.d/foreman > + '[' -r /etc/default/foreman ']' > + . /etc/default/foreman > ++ START=yes > ++ FOREMAN_HOME=/usr/share/foreman > ++ FOREMAN_IFACE=192.168.0.102 > ++ FOREMAN_PORT=3000 > ++ FOREMAN_USER=foreman > ++ FOREMAN_ENV=production > + FOREMAN_IFACE=192.168.0.102 > + FOREMAN_PORT=3000 > + FOREMAN_USER=foreman > + FOREMAN_HOME=/usr/share/foreman > + FOREMAN_ENV=production > + FOREMAN_PID=/usr/share/foreman/tmp/pids/server.pid > + DAEMON=/usr/share/foreman/script/server > + DAEMON_OPTS='-b 192.168.0.102 -p 3000 -e production -d' > + . /lib/init/vars.sh > ++ '[' -f /etc/default/rcS ']' > ++ . /etc/default/rcS > +++ TMPTIME=0 > +++ SULOGIN=no > +++ DELAYLOGIN=no > +++ UTC=yes > +++ VERBOSE=no > +++ FSCKFIX=no > +++ RAMRUN=no > +++ RAMLOCK=no > ++ '[' -r /proc/cmdline ']' > +++ cat /proc/cmdline > ++ for ARG in '$(cat /proc/cmdline)' > ++ case $ARG in > ++ for ARG in '$(cat /proc/cmdline)' > ++ case $ARG in > ++ for ARG in '$(cat /proc/cmdline)' > ++ case $ARG in > ++ for ARG in '$(cat /proc/cmdline)' > ++ case $ARG in > ++ '[' '' ']' > ++ break > ++ '[' '' ']' > + . /lib/lsb/init-functions > ++ FANCYTTY= > ++ '[' -e /etc/lsb-base-logging.sh ']' > ++ true > + case "$1" in > + '[' no '!=' no ']' > + do_start > + is_true yes > + '[' xyes = xtrue -o xyes = xyes -o xyes = x0 ']' > + return 0 > + start-stop-daemon --start --quiet --chuid foreman --pidfile > /usr/share/foreman/tmp/pids/server.pid --chdir /usr/share/foreman --exec > /usr/share/foreman/script/server -- -b 192.168.0.102 -p 3000 -e production > -d > + case "$?" in > + RETVAL=0 > + '[' no '!=' no ']' > + exit 0 > > Trying the start-stop-daemon manually works: > > root@squeeze:~# start-stop-daemon --start --quiet --chuid foreman --pidfile > /usr/share/foreman/tmp/pids/server.pid --chdir /usr/share/foreman --exec > /usr/share/foreman/script/server -- -b 192.168.0.102 -p 3000 -e production > -d > => Booting WEBrick > => Rails 2.3.11 application starting on http://192.168.0.102:3000 > root@squeeze:/usr/share/foreman/script# ps aux|grep foreman|grep -v grep > foreman 6857 0.0 0.5 73056 11160 ? S 21:27 0:00 ruby > /usr/share/foreman-proxy/bin/smart-proxy > foreman 7756 68.8 5.6 229444 116596 ? S 22:02 0:04 ruby > /usr/share/foreman/script/server -b 192.168.0.102 -p 3000 -e production -d > > any thoughts? > > Thanks.

Hi,

there are also new packages for Foreman 0.2 and Smart-Proxy 0.1 (package
called foreman-proxy) in the testing and stable repository for Debian and
Ubuntu Linux.

The packages should work with

  • Debian Linux 5.0 (Lenny)
  • Debian Linux 6.0 (Squeeze)
  • Ubuntu Linux 10.04 LTS (Lucid Lynx)
  • Ubuntu Linux 10.10 (Maverick Meerkat)
  • Ubuntu Linux 11.04 (Natty Narwhal)

You can find installation instructions in the Foreman wiki under 1.

If you encounter any errors, please file a bug report for the packages in our
issue tracker[2].

Ubuntu-Packages
[2]: Issues - Foreman

Regards
Jochen

··· Am Dienstag, 29. März 2011, 18:57:36 schrieb Ohad Levy: > Hello All, > > I'm happy to announce a new release of Foreman, top highlights > for this release includes: > > * New look and feel > * Extended restful API > * Support for New Puppet Reports format > * Full VM/physical host Provisioning > * Powerful template generator ( pxelinux, gpxe, kickstart, preseed, grub > etc..) > * introduce a new service called smart proxy (which can run on remote > machines) to manage the following services: > ** DNS Management > ** DHCP Management > ** TFTP Management > ** Puppet/PuppetCA Management > > This release is a major release packed with goodies, more than 130 > tickets were closed. > > Release notes can be found here: > http://theforeman.org/projects/foreman/wiki/ReleaseNotes > > Full change log can be found here: http://theforeman.org/versions/show/9 > > As usually many many thanks to all contributors and users > > RPMS for both smart proxy and foreman can be found at > http://yum.theforeman.org/stable > > Have fun, > Ohad

Hi Jochen, thanks for looking into it, next day I did a try and everything
looked good, not really sure what happened, I just couldn't see foreman
running after initializing, I've tried to replicate but haven't had luck so
far, and I think that is good, I'll let you all know if there is anything
odd on it.

Thanks.

··· On Sun, Mar 27, 2011 at 12:23 PM, Jochen Schalanda wrote:

Hi Tony,

the output of the Foreman init script doesn’t print any error in the output
you’ve provided. Maybe you could change the start-stop-daemon call in the
init
script’s do_start() function to include the --verbose (-v) parameter and
remove the output redirection (>/dev/null) from the same line.

I hope that this will give an indication where to look for the error.

Regards
Jochen

Am Donnerstag, 24. März 2011, 04:58:58 schrieb Tony G.:

On Wed, Mar 23, 2011 at 5:18 PM, Jochen Schalanda > jochen@schalanda.namewrote:

Hi,

there are also new packages for Foreman 0.2 RC1 and Smart-Proxy 0.1
(package
called foreman-proxy) in the testing repository for Debian and Ubuntu
Linux.

You can find installation instructions in the Foreman wiki under [1].

I’d like to encourage everybody with some spare time to give these
packages a
test run so that they can move to the stable repository in a timely
manner after the coming Foreman 0.2 release. If you encounter any
errors, please file
a bug for the packages in our issue tracker[2].

[1]:

Installation instructions - Foreman

ian- Ubuntu-Packages
[2]: Issues - Foreman

Regards
Jochen

Thanks Jochen, I’ ve installed foreman 0.2 on Debian Squeeze 6.0.1,
found

one issue though.

When starting foreman from the init script it does not start:
root@squeeze:~# /etc/init.d/foreman start
root@squeeze:~# ps aux|grep foreman|grep -v grep
foreman 6857 0.0 0.5 73056 11160 ? S 21:27 0:00 ruby
/usr/share/foreman-proxy/bin/smart-proxy

Doing some debugging I got:

  • PATH=/sbin:/usr/sbin:/bin:/usr/bin
  • DESC=‘Foreman systems management web application’
  • NAME=foreman
  • SCRIPTNAME=/etc/init.d/foreman
  • ‘[’ -r /etc/default/foreman ‘]’
  • . /etc/default/foreman
    ++ START=yes
    ++ FOREMAN_HOME=/usr/share/foreman
    ++ FOREMAN_IFACE=192.168.0.102
    ++ FOREMAN_PORT=3000
    ++ FOREMAN_USER=foreman
    ++ FOREMAN_ENV=production
  • FOREMAN_IFACE=192.168.0.102
  • FOREMAN_PORT=3000
  • FOREMAN_USER=foreman
  • FOREMAN_HOME=/usr/share/foreman
  • FOREMAN_ENV=production
  • FOREMAN_PID=/usr/share/foreman/tmp/pids/server.pid
  • DAEMON=/usr/share/foreman/script/server
  • DAEMON_OPTS=’-b 192.168.0.102 -p 3000 -e production -d’
  • . /lib/init/vars.sh
    ++ ‘[’ -f /etc/default/rcS ‘]’
    ++ . /etc/default/rcS
    +++ TMPTIME=0
    +++ SULOGIN=no
    +++ DELAYLOGIN=no
    +++ UTC=yes
    +++ VERBOSE=no
    +++ FSCKFIX=no
    +++ RAMRUN=no
    +++ RAMLOCK=no
    ++ ‘[’ -r /proc/cmdline ‘]’
    +++ cat /proc/cmdline
    ++ for ARG in ‘$(cat /proc/cmdline)’
    ++ case $ARG in
    ++ for ARG in ‘$(cat /proc/cmdline)’
    ++ case $ARG in
    ++ for ARG in ‘$(cat /proc/cmdline)’
    ++ case $ARG in
    ++ for ARG in ‘$(cat /proc/cmdline)’
    ++ case $ARG in
    ++ ‘[’ ‘’ ‘]’
    ++ break
    ++ ‘[’ ‘’ ‘]’
  • . /lib/lsb/init-functions
    ++ FANCYTTY=
    ++ ‘[’ -e /etc/lsb-base-logging.sh ‘]’
    ++ true
  • case “$1” in
  • ‘[’ no ‘!=’ no ‘]’
  • do_start
  • is_true yes
  • ‘[’ xyes = xtrue -o xyes = xyes -o xyes = x0 ‘]’
  • return 0
  • start-stop-daemon --start --quiet --chuid foreman --pidfile
    /usr/share/foreman/tmp/pids/server.pid --chdir /usr/share/foreman --exec
    /usr/share/foreman/script/server – -b 192.168.0.102 -p 3000 -e
    production
    -d
  • case “$?” in
  • RETVAL=0
  • ‘[’ no ‘!=’ no ‘]’
  • exit 0

Trying the start-stop-daemon manually works:

root@squeeze:~# start-stop-daemon --start --quiet --chuid foreman
–pidfile
/usr/share/foreman/tmp/pids/server.pid --chdir /usr/share/foreman --exec
/usr/share/foreman/script/server – -b 192.168.0.102 -p 3000 -e
production
-d
=> Booting WEBrick
=> Rails 2.3.11 application starting on http://192.168.0.102:3000
root@squeeze:/usr/share/foreman/script# ps aux|grep foreman|grep -v grep
foreman 6857 0.0 0.5 73056 11160 ? S 21:27 0:00 ruby
/usr/share/foreman-proxy/bin/smart-proxy
foreman 7756 68.8 5.6 229444 116596 ? S 22:02 0:04 ruby
/usr/share/foreman/script/server -b 192.168.0.102 -p 3000 -e production
-d

any thoughts?

Thanks.


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.


Tony
http://blog.tonyskapunk.net