These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Using Redmine on the new forum.
Web Hosting and Cloud Computing Control Panels
As a followup, I know that redmine defaults (at least on their home page install instructions) to port 3000, and when I use this port I get page that just says "NOT FOUND".
Thanks,
Nick
Hi Nick,
While I haven't used it, it's possible the error logs will point us in the right direction for fixing it.
Anytime you get a 500 error, that means you can poke in the Apache error log for that Virtual Server to get a more detailed description of the problem.
So when you attempt to access that again, what goodies show up in $HOME/logs/error_log?
-Eric
I couldn't find anything in the logs for this, but I think that's because it's running under mongrel, not apache - would that be right?
When I looked in $HOME/logs there were 3 extra files :
rails.3000.log
redmine.3000.log
redmine.3001.log
I took a stab in the dark and tried to open :
domain.com:3001/redmine
and it worked. So, given how the install script works, is it correct to start on port 3000 (or 3001 in my case, probably from an old install), or should it run under apache?
So does the install script need updating, or does it just need to amend the url it presents once the install is done? Or is my old install attempt just breaking everything? :)
Cheers,
Nick
Rails is started by default under a cluster of Mongrels. I never liked this, but for a couple of years it was the agreed upon industry standard best practice for running Rails apps. mod_rails is now solid and provides all the capabilities we need (I think) to switch off to it, so it's very likely that Mongrel will be dying a well-deserved death in the near future in Virtualmin.
However, Virtualmin sets up proxy rules to talk to the mongrels. You should never need (or want) to connect on port 3000 (or 3001...Virtualmin sets up mongrels on IPs drawn from a pool of available high ports).
Your old install attempt might be breaking things. I don't know.
Redmine is very new, which means two things:
1. It was very recently tested to work, by Jamie.
2. Very few other people have tested it on the widely varying platforms and environments out their in the wild.
1 is good. It means it's not a forgotten installer, or isn't known to be workable. 2 is bad. It means that there are probably still some situations where installation will go wrong.
Rails apps, in general, are pretty fragile because of their complexity. So many moving parts is just asking for trouble. Hopefully mod_rails will decrease that complexity by a lot.
Here's what I'd recommend:
Create a fresh virtual server, for testing. This way, you'll know nothing weird is hanging around in the virtual host configuration or home directory.
Install redmine. Look for errors during install. Make a note of any. We'll need these, if you make it to the final step.
Test it on the URL Virtualmin gives you. Does it work?
If so, then you know your other virtual host has something weird going on, possibly from the older install attempt. If not, proceed to the final step.
File a bug in the bug tracker. Jamie knows the install scripts better than anybody, and will be able to guide you through getting the information he needs to correct the problem. (Don't forget to include the really important details...your OS and version is absolutely vital, any error messages you saw, and whether you can actually connect to redmine on the mongrel port directly. The latter indicates a problem with the proxy rules, rather than the installer itself, so that's very useful to know.)
--
Check out the forum guidelines!