No response in local (development) mode

[rebala]

Running with test data on fresh installation. Running the server shows:

Loading data (80.00% complete)
Done loading data! That took 140 seconds
Invalidating the usage data cache
Waiting 900000 ms before next refresh

however, I cannot connect using browser from another machine and on the local machine I do not get any response from the server.

What should I look at to troubleshoot this problem?
Is there a way to configure development server (trinidad?) to be accessed from remote machine?

Complete console log:

Initializing ProtocolHandler ["http-bio-8080"]
Starting Servlet Engine: Apache Tomcat/7.0.30
jruby 1.7.3 (1.9.3p385) 2013-02-21 dac429b on OpenJDK 64-Bit Server VM 1.6.0_24-b24 [linux-amd64]
using a shared (threadsafe!) runtime
Running in development mode
Running DB in memory mode
Creating tables
Creating functions
Creating local loader
Starting loader
Running usage loader
Refresh every 900000 ms
Loading avro data
Listing local files in data/usage/*/.avro
Found 10 files to process
Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [1,015] milliseconds.
Starting ProtocolHandler ["http-bio-8080"]
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (0.00% complete)
Loading data (10.00% complete)
Loading data (10.00% complete)
Loading data (10.00% complete)
Loading data (10.00% complete)
Loading data (20.00% complete)
Loading data (20.00% complete)
Loading data (20.00% complete)
Loading data (30.00% complete)
Loading data (30.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (40.00% complete)
Loading data (50.00% complete)
Loading data (50.00% complete)
Loading data (50.00% complete)
Loading data (60.00% complete)
Loading data (60.00% complete)
Loading data (60.00% complete)
Loading data (60.00% complete)
Loading data (80.00% complete)
Loading data (80.00% complete)
Loading data (80.00% complete)
Loading data (80.00% complete)
Loading data (80.00% complete)
Done loading data! That took 141 seconds
Invalidating the usage data cache
Waiting 900000 ms before next refresh

[matthayes]

Are you saying you don't get a response when you try to access the server from the local machine either?

One odd thing from the logs you shared is that the port is 8080, but I think I have the default configured as 3000. Have you made any config changes?

I just tried this myself from the latest commit and it worked for me from the same local machine and from a remote machine.

To troubleshoot I would start by entering "ant reset" and then run "./setup.sh". Copy the output here. This will confirm that the environment is getting set up correctly and the right versions of the gems are installed. I know that there was a version of Sinatra before where it would bind to localhost instead of 0.0.0.0, which had the effect of making the server not accessible from remote machines, at least in development mode. But I'm pretty sure the version I have configured doesn't have this issue.