Re: Running a django website on AWS EC2 on ubuntu

[Jason]

show your systemd file .  looks like an issue there

On Monday, July 2, 2018 at 7:13:44 PM UTC-4, Anirudh Jain wrote:

I am getting the following error on running the command :-

"sudo journalctl -u gunicorn"

Error is :-

Jul 02 20:05:35 ip-172-31-40-226 systemd[1]: Started gunicorn daemon.

Jul 02 20:05:35 ip-172-31-40-226 systemd[1]: gunicorn.service: Main process exited, code=exited, status=200/CHDIR

Jul 02 20:05:35 ip-172-31-40-226 systemd[1]: gunicorn.service: Unit entered failed state.

Jul 02 20:05:35 ip-172-31-40-226 systemd[1]: gunicorn.service: Failed with result 'exit-code'.

Jul 02 20:44:45 ip-172-31-40-226 systemd[1]: Started gunicorn daemon.

Jul 02 20:44:45 ip-172-31-40-226 systemd[1]: gunicorn.service: Main process exited, code=exited, status=203/EXEC

Jul 02 20:44:45 ip-172-31-40-226 systemd[1]: gunicorn.service: Unit entered failed state.

Jul 02 20:44:45 ip-172-31-40-226 systemd[1]: gunicorn.service: Failed with result 'exit-code'.

before running this command, I had saved the file gunicorn.service and run the following commands :-

sudo systemctl daemon-reload sudo systemctl start gunicorn sudo systemctl enable gunicorn

Command "sudo systemctl status gunicorn" also gave the eror as :-

gunicorn.service - gunicorn daemon

   Loaded: loaded (/etc/systemd/system/gunicorn.service; enabled; vendor preset: enabled)

   Active: failed (Result: exit-code) since Mon 2018-07-02 23:09:49 UTC; 16s ago

 Main PID: 3671 (code=exited, status=203/EXEC)

Jul 02 23:09:49 ip-172-31-40-226 systemd[1]: Started gunicorn daemon.

Jul 02 23:09:49 ip-172-31-40-226 systemd[1]: gunicorn.service: Main process exited, code=exited, status=203/EXEC

Jul 02 23:09:49 ip-172-31-40-226 systemd[1]: gunicorn.service: Unit entered failed state.

Jul 02 23:09:49 ip-172-31-40-226 systemd[1]: gunicorn.service: Failed with result 'exit-code'.

Can anyone please tell me what is exactly the error and how to resolve it?

Thank you.