Recent Posts by rob5

Topic: Brightbox Help / App works on ServerAlias not ServerName

The very helpful guys at Brightbox have sorted this for me. Too embarassing to tell you the problem (hint – bit of an .htaccess disaster on my part).

Topic: Brightbox Help / App works on ServerAlias not ServerName

Hi,

I’m moving a Ruby Rails app onto one of our Brightbox accounts (from another external server).

I’ve added an entry to the hosts file on my laptop so it looks for the domain at the Brightbox server so I can test the deployment before I switch the DNS at the regsitrar.

I’m getting a 503 error and in the application log the error message is
[Mon Oct 04 17:33:05 2010] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:xxxxx (*) failed

(have swapped out the port for xxxxx in the above)

I’m using a Passenger deployment (hopefully similar to other apps which are ok).

What I’ve realised is that if I access the app via the server alias

ie app.username.vm.brightbox.net then the app is visible and working fine.

I’ve also got a second alias using my own web domain with a subdomain mapped to the app externally and that’s working fine.

I tried adding an entry to the hosts file on the server (telling it that the domain is coming from this server) and that didn’t help either.

Any ideas on why the ServerName (the real domain) isn’t responding? Is there some reason why changing my laptop hosts file isn’t enough to test with the rails app like this?

I’m stumped by this at the moment.

Any help much appreciated.

Cheers

Rob

Topic: Brightbox Help / Mysql tunnel on Mac

Hi,

In the past I’ve connected to the mysql cluster from a Windows machine without problems.

I’m now trying to get a tunnelled connection working on a Mac.

I’ve followed the notes on the WIKI re tunneling through to MYSQL (from a MAC) but can’t get a connection. I don’t have MySQL running locally (I stopped the service).

I have a SSH shell running with the tunnel commands as per the WIKI.

Error msg is:

“Can’t connect to local MySQL server through socket ‘/tmp/mysql.sock’ (2) (code 2002)”

Can you suggest any pointers to diagnose the problem further?

Cheers

Rob

Topic: Brightbox Help / Rails requires RubyGems >= 1.3.2 (you have 1.3.1). Please `gem update --system` and try again.

Getting some hands on support from Brightbox on this one. Apparently we had RubyGems install from source on the box as well as the packaged version.

Topic: Brightbox Help / Rails requires RubyGems >= 1.3.2 (you have 1.3.1). Please `gem update --system` and try again.

I’m trying to deploy a new Rails app which uses Rails 2.3.4 onto Phusion Passenger.

I’m getting this error: Rails requires RubyGems >= 1.3.2 (you have 1.3.1). Please `gem update —system` and try again. but when I’m logged in as the rails user and run gem -v I see 1.3.6 (I’ve ran gem udpate —system)

Is this a path problem / is Phusion using looking elsehwere for gem to my local path?

Any advice – very appreciated.

Cheers

Rob

Topic: Brightbox Help / why is db:create running?

Solved this one at last. Realised that db:create was leading us on the wrong track. The actual issue was that we had our application.rb controller (rails 2.2.2) called application_controller.rb. Not sure how that happened. I think rails 2.2.3 wants application_controller.rb (haven’t really checked) but we on 2.2.2 at the moment. Anyhow…weird that on windows machine webrrick didn’t complain in testing. Anyhow.. thanks for your help on the above John. Helped us to rule out the problem with the database.yml file.

Topic: Brightbox Help / why is db:create running?

Hi John,

We are using this line from the standard deploy.rb

set :local_shared_files, %w(config/database.yml)

We have copied this file into: /home/ouruserhere/ourappnamehere/shared/config

Here’s the error message..
failed: “sh -c \”sh -c ‘cd /home/ouruserhere/ourappnamehere/releases/20090407180442; rake RAILS_ENV=production db:create’\"" on userhere-001.vm.brightbox.net

Thanks for any help. I keep thinking there must be a typo in the file but I can’t see it.

Rob

Topic: Brightbox Help / why is db:create running?

We’re trying to get our second app running on brightbox (didn’t have this issue on first one) and db:create is getting called and failing even though we’ve already setup the database. Have double and triple checked the database.yml file and can’t see any probs. It gets copied over from a shared area.

Any ideas how to get to root of the issue. Because cap is rolling back each time it’s tricky to test the tasks individually from the box.

Topic: Brightbox Help / deployment problems

Guess you’ve sorted by now.. but in case others read it.. I found that if you are using Windows you don’t want Cap to deploy from your local copy (it gets the directory slashes wrong and falls over). Instead check in the code to svn and run the deployment via checkout. This is done in the deploy.rb.