Q1) How can I troubleshoot/fix this problem?
Q2) How can I prevent the directory listing being shown when something goes wrong with the mongrel cluster?
Mongrel Cluster throws directory listing of /public
- Pirkka
- Posts: 7
- Starts: 5
- Wiki Edits: 0
- Location: Helsinki
My recently configured mongrel cluster stopped working suddenly - I tried to issue mongrel::cluster restart first and then restarted my mongrel cluster manually. It still doesn't work even though everything looks good looking at processes, accessing the same application through fcgi etc.
Q1) How can I troubleshoot/fix this problem?
Q2) How can I prevent the directory listing being shown when something goes wrong with the mongrel cluster?
Q1) How can I troubleshoot/fix this problem?
Q2) How can I prevent the directory listing being shown when something goes wrong with the mongrel cluster?
- Willc
- Posts: 45
- Starts: 1
- Wiki Edits: 15
Pirkka, the command you should be entering is:
mongrel_rails cluster::restart
2007-10-03 01:23 AM
- Pirkka
-
- Posts: 7
- Starts: 5
- Wiki Edits: 0
- Location: Helsinki
Oops. Yep, that's what I meant. mongrel_rails cluster::restart does not give an error, it just gives
stopping port 4***0
stopping port 4***1
starting port 4***0
starting port 4***1
and now I have fresh pair of mongrel processes. Still, the website serves up the directory listing of /public.
stopping port 4***0
stopping port 4***1
starting port 4***0
starting port 4***1
and now I have fresh pair of mongrel processes. Still, the website serves up the directory listing of /public.
2007-10-03 01:36 AM
- Pirkka
-
- Posts: 7
- Starts: 5
- Wiki Edits: 0
- Location: Helsinki
Looks like this was a DNS problem: the application is hosted on a subdomain and the DNS entry was pointing to a wrong IP that was actually serving my app's public folder on a DIFFERENT SERVER altogether. My bad, sorry!