Submitted by CedenTi on Wed, 06/08/2016 - 20:16
virtualmin pro
When I install django using python3.4 and any error occurs, the proxy does not generate any log, I have only one error 503 Service temporarily unavailable.
using proxy balancer
Status:
Active
Comments
Submitted by andreychek on Wed, 06/08/2016 - 20:57 Comment #1
Howdy -- you may need to review the Apache error log for both the Virtual Server that is the proxy, and the Virtual Server that it's proxying to.
That would be in $HOME/logs/error_log.
However, I'd be curious what happens if you install that into a domain that isn't using a proxy, do things work differently in that case?
Submitted by CedenTi on Wed, 06/08/2016 - 23:45 Comment #2
Hi, my apache error log:
[Thu Jun 09 01:31:18 2016] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3002 (localhost) failed [Thu Jun 09 01:31:18 2016] [error] ap_proxy_connect_backend disabling worker for (localhost) [Thu Jun 09 01:33:01 2016] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3002 (localhost) failed [Thu Jun 09 01:33:01 2016] [error] ap_proxy_connect_backend disabling worker for (localhost) [Thu Jun 09 01:33:19 2016] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3002 (localhost) failed [Thu Jun 09 01:33:19 2016] [error] ap_proxy_connect_backend disabling worker for (localhost) [Thu Jun 09 04:34:17 2016] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3002 (localhost) failed [Thu Jun 09 04:34:17 2016] [error] ap_proxy_connect_backend disabling worker for (localhost) [Thu Jun 09 01:34:28 2016] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3002 (localhost) failed [Thu Jun 09 01:34:28 2016] [error] ap_proxy_connect_backend disabling worker for (localhost) [Thu Jun 09 01:34:29 2016] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3002 (localhost) failed [Thu Jun 09 01:34:29 2016] [error] ap_proxy_connect_backend disabling worker for (localhost) [Thu Jun 09 01:34:29 2016] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3002 (localhost) failed [Thu Jun 09 01:34:29 2016] [error] ap_proxy_connect_backend disabling worker for (localhost) [Thu Jun 09 01:34:30 2016] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3002 (localhost) failed [Thu Jun 09 01:34:30 2016] [error] ap_proxy_connect_backend disabling worker for (localhost) [Thu Jun 09 01:34:43 2016] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?) [Thu Jun 09 01:34:43 2016] [warn] RSA server certificate wildcard CommonName (CN) `*.cedenti.com' does NOT match server name!? [Thu Jun 09 01:34:50 2016] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3002 (localhost) failed [Thu Jun 09 01:34:50 2016] [error] ap_proxy_connect_backend disabling worker for (localhost)
using python2.7 works but with python3.4 not give this error up
Submitted by JamieCameron on Thu, 06/09/2016 - 00:01 Comment #3
Also, which Linux distribution and version is this, and how did you install Python 3.4?
Submitted by CedenTi on Thu, 06/09/2016 - 00:06 Comment #4
Ubuntu Linux 12.04.3 Webmin 1.801 Virtualmin 5.03 Pro
I installed python using apt-get
Submitted by andreychek on Fri, 06/10/2016 - 08:17 Comment #5
Ah, I didn't realize Virtualmin was installing that on a separate port now.
It sounds like the Django server process isn't running. You may want to try restarting it. Or if that generates an error, let us know what error occurs when attempting that.
There should be a startup script for that located in /etc/init.d, if you aren't sure which it is, let us know what files you see in that directory and we'll point out the right one. Thanks!
Submitted by JamieCameron on Fri, 06/10/2016 - 10:51 Comment #6
Also, you can see the status of the server and re-start it by clicking on the installed Django script on the Script Installers page.