Forum: Ruby on Rails Booting WEBrick ... server:invalid option: --trace ???

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
4c0a7395fe7206ec35bae335fea46c0c?d=identicon&s=25 Rusty Rustybucket (rustybucket)
on 2009-06-06 21:58
(Received via mailing list)
I'm migrating an old Rails App to a new server, I think I've got most
of my issues worked out so far.  But....

When I run script/server --trace in the app I get the following
output...  and I have no clue what to do or even where to look...  Any
guidance or assistance would be greatly appreciated.

script/server --trace
=> Booting WEBrick...
server: invalid option: --trace

Thanks in advance for any guidance/assistance.

Af2ce6689213fdb78913a9662b18da6b?d=identicon&s=25 Rick Lloyd (ricklloyd)
on 2009-06-07 00:50
(Received via mailing list)
script/server --help
Usage: server [options]
    -p, --port=port                  Runs Rails on the specified port.
                                     Default: 3000
    -b, --binding=ip                 Binds Rails to the specified ip.
    -c, --config=file                Use custom rackup configuration
    -d, --daemon                     Make server run as a Daemon.
    -u, --debugger                   Enable ruby-debugging for the
    -e, --environment=name           Specifies the environment to run
this server under (test/development/production).
                                     Default: development
    -P, --path=/path                 Runs Rails app mounted at a
specific path.
                                     Default: /

    -h, --help                       Show this help message.

I don't see --trace in there anywhere.
4c0a7395fe7206ec35bae335fea46c0c?d=identicon&s=25 Rusty Rustybucket (rustybucket)
on 2009-06-07 01:37
(Received via mailing list)
yup, definitely not there.. doh.

ok, so I ran script/server without the trace and I get this

=> Booting WEBrick...

and then it comes back to the command prompt.  It doesn't start the
app....?  I was trying to use trace to see why.

Is there any way to troubleshoot this?
This topic is locked and can not be replied to.