Added by Andreas N. about 9 years ago
Hi,
i just tried to install the packaged openproject installation.
If I go to http://myhost/openproject i get a 503 error. It does not even work from the server itself.
apache error logs say
proxy:error connection refused, attempt to connect to 127.0.0.1:6000 failed
and:
proxy_http:error failed to make connection to backend 127.0.0.1
selinux and iptables are off.
openproject run check says everthing is fine except for MySQL (“MySQL connection is NOT working”)
I left the openproject.conf as it was, it just does some proxypass to 127.0.0.1
If i do netstat -tlpn nothing is listening on 6000, but it should, right?
I tried the installation on two different machines (Centos 7 and Ubuntu 14.04).
Thanks for your help
Replies (7)
fixed the MySQL Issue with installing libmagickcore5 - the 503 error is still here
The problem is that nothing is listening on Port 6000.
I did the packaged install on fresh installs (tried ubuntu, fedora, centos, debian so far….) and everywhere the same issue.
What do I have to start/install that it works?
Does the output of
openproject configure
produce any errors? If that step succeeds, then the unicorn web worker should be started properly, so I expect some error output there.Best,
Oliver
Hi,
i have almost the same Problem, the same error messages, the same 503.
But running
openproject configure
results in an Argument Error: bad argument (expected URI object or URI string).The complete ouput is in the attachment. It seems like that loading the openproject_github_integration seed data fails (as far as i understand the traceback points to code related to scm, but i can barely read ruby) and after that, the unicorn workers are not spawned. At least everything else seems to work normal, and as stated above, nothing is listening on port 127.0.0.1:6000.
Additionally, this is not a fresh installation, this is upgraded OpenProject to 5.0.18, and after a server restart, everything stopped working.
Some ideas?
Thanks in advance,
Christoph
Hello, could you make sure you’re using a 64bit distribution? (
uname -i
should returnx86_64
)An easy way to debug what happens when you launch the web process is to run it in the foreground, with:
openproject run web
, and see what are the logs there.Confirmed that i am running a 64bit distribution.
That (almost) solved the problem: Running
openproject run web
starts the web component without any errors. The site gets reachable again and everything is back to normal. Run with the-D
option, everyone can resume work as normal. So as a fix, everything perfect. It doesn’t solve the underlying problem of the component not starting by default.Thank you a lot,
Christoph
Which distribution are you using? If you stop
openproject run web
that you just launched, and doopenproject scale web=0 ; openproject scale web=1
(to force a reset of the init scripts), is the process correctly started? Also, from which version did you upgrade?