error 503: Can't deploy rails 3 app with apache + thin (bitnamy ruby stack)
Posted
by
Pacu
on Server Fault
See other posts from Server Fault
or by Pacu
Published on 2012-11-22T04:26:03Z
Indexed on
2012/11/22
5:02 UTC
Read the original article
Hit count: 215
As you'll notice, I'm a bit of a noob on Rails. Here's the thing
I have a EC2 Bitnami RubyStack AMI running. I'm trying to deploy the sample project to be sure I'm doing the right thing, but I'm not getting anywhere at all. I just get a 503 error
I'm following bitnami's docs on thin + apache
Here are my files:
the httpd.conf I include in the main httpd.conf
Alias /sample "/home/bitnami/stack/projects/sample/public"
<Directory "/home/bitnami/stack/projects/sample/public">
AllowOverride None
Order allow,deny
Allow from all
</Directory>
ProxyPass /sample balancer://appcluster
ProxyPassReverse /sample balancer://appcluster
<Proxy balancer://appcluster>
BalancerMember http://127.0.0.1:3001/sample
BalancerMember http://127.0.0.1:3002/sample
BalancerMember http://127.0.0.1:3003/sample
BalancerMember http://127.0.0.1:3004/sample
</Proxy>
the thin.yml file
chdir: /opt/bitnami/projects/sample
environment: production
address: 127.0.0.1
port: 3000
timeout: 30
log: log/thin.log
pid: tmp/pids/thin.pid
max_conns: 1024
max_persistent_conns: 512
require: []
wait: 30
servers: 5
prefix: /sample
daemonize: true
I'm able to start and stop apache, but thin does not stop correctly though. When I try to stop thin, I get this output
/opt/bitnami/projects/sample$ sudo thin -C config/thin.yml stop
Stopping server on 127.0.0.1:3000 ...
Can't stop process, no PID found in tmp/pids/thin.3000.pid
Stopping server on 127.0.0.1:3001 ...
Can't stop process, no PID found in tmp/pids/thin.3001.pid
Stopping server on 127.0.0.1:3002 ...
Can't stop process, no PID found in tmp/pids/thin.3002.pid
Stopping server on 127.0.0.1:3003 ...
Can't stop process, no PID found in tmp/pids/thin.3003.pid
Stopping server on 127.0.0.1:3004 ...
Can't stop process, no PID found in tmp/pids/thin.3004.pid
I've tried to use nginx as well, without any luck unfortunately.
Thank you for your time and help!
© Server Fault or respective owner