AH00094: Command line: 'apache2 (mod_wsgi-express) -f /tmp/mod_wsgi-localhost:8080:0/httpd.conf

[YooYongGil]

I am a Korean web developer. I will speak in advance. I am Korean. I would appreciate your understanding if you can not speak English.

root@TOTOBOT:/var/www/html/mysite# mod_wsgi-express start-server --user=www-data --group=www-data --port=8080 /var/www/html/mysite/mysite/wsgi.py Server URL : http://localhost:8080/ Server Root : /tmp/mod_wsgi-localhost:8080:0 Server Conf : /tmp/mod_wsgi-localhost:8080:0/httpd.conf Error Log File : /tmp/mod_wsgi-localhost:8080:0/error_log (warn) Request Capacity : 5 (1 process * 5 threads) Request Timeout : 60 (seconds) Startup Timeout : 15 (seconds) Queue Backlog : 100 (connections) Queue Timeout : 45 (seconds) Server Capacity : 20 (event/worker), 20 (prefork) Server Backlog : 500 (connections) Locale Setting : en_US.UTF-8

---

On the Web, the connection is good. However, there is no API connection to the kakao platform. I have analyzed the error.log in / tmp / mod_wsgi-localhost: 8080: 0. Again, the connection is good on the web. The TELNET and PING commands also work well.

[Mon Jan 21 17:21:41.319836 2019] [core:warn] [pid 10751:tid 139778681853824] AH00098: pid file /tmp/mod_wsgi-localhost:8080:0/httpd.pid overwritten -- Unclean shutdown of previous Apache run? [Mon Jan 21 17:21:41.320393 2019] [mpm_event:notice] [pid 10751:tid 139778681853824] AH00489: Apache/2.4.7 (Ubuntu) mod_wsgi/4.6.5 Python/3.4 configured -- resuming normal operations [Mon Jan 21 17:21:41.320432 2019] [core:notice] [pid 10751:tid 139778681853824] AH00094: Command line: 'apache2 (mod_wsgi-express) -f /tmp/mod_wsgi-localhost:8080:0/httpd.conf -D MOD_WSGI_MPM_ENABLE_EVENT_MODULE -D MOD_WSGI_MPM_EXISTS_EVENT_MODULE -D MOD_WSGI_MPM_EXISTS_WORKER_MODULE -D MOD_WSGI_MPM_EXISTS_PREFORK_MODULE -D FOREGROUND'

---

I think there is a problem with /tmp/mod_wsgi-localhost:8080:0/httpd.conf

error_log.txt httpd.conf.txt wsgi.py.txt

[GrahamDumpleton]

What happens when from the same host, you run:

curl http://localhost:8080/

or use a web browser on the same host to access:

http://localhost:8080/

Have you verified the Django application is responding and working.

Also suggest you add --access-log command so you can see when requests received.

And for debugging, you can use --log-to-terminal so log messages come to your terminal and can be seen immediately.

Also suggest for Django you read:

• http://blog.dscpl.com.au/2015/04/using-modwsgi-express-with-django.html
• http://blog.dscpl.com.au/2015/04/integrating-modwsgi-express-as-django.html

So first up verify locally that you have your Django application is working correctly. If that is okay, then next can look at how you are trying to access this from outside of the host and whether you are using correct URL and whether request can be routed to the application or not.

[YooYongGil]

Printed normally! Korean is broken. and w3m http: // localhost: 8080 command will connect.

and, In django, do you want to test it locally with the python mange.py runserver command?

[GrahamDumpleton]

I would not expect curl to necessarily display things correctly depending on what is returned. You would need to use a web browser. What it shows though is that it is responding.

Now what I understand is that you are saying that when access from another computer it doesn't connect at all. Is that what you mean. What is the URL you are using from another machine? Are you using a hostname in the URL which maps to the IP for the host where mod_wsgi-express is being run? Are you connecting explicitly on port 8080 in the URL?

[YooYongGil]

This is my current server address. When you connect from the outside, you have entered your own IP: 8080. Connection from outside will be successful. My server IP is open to the public, but I am very curious about the error_log in /tmp/mod_wsgi-localhost:8080:0/httpd.conf.

[GrahamDumpleton]

If you are talking about the error:

[Mon Jan 21 17:21:41.319836 2019] [core:warn] [pid 10751:tid 139778681853824] AH00098: pid file /tmp/mod_wsgi-localhost:8080:0/httpd.pid overwritten -- Unclean shutdown of previous Apache run?

it isn't something that is usually a problem. It usually indicates that Apache was killed using SIGKILL signal instead of SIGTERM and as a result Apache was denied the opportunity to shutdown properly and clean things up.

[YooYongGil]

I ended it by pressing Ctrl + c and ran it again as shown.

I initialized the error_log file and reopened it.

[GrahamDumpleton]

Which looks fine and normal, so I am not sure I understand what problem it is that you are asking about.

Also, can you avoid closing and re-opening the issue each time. If using the GitHub web interface, just click on the Green Comment button and it should add the comment but not close it.