I need help AWS Elastic Beanstalk webapp deployment

2023/07/07 21:02:42.142045 [WARN] Failed to read file /var/pids/web.pid, retry attempt: 1
2023/07/07 21:02:43.144366 [WARN] Failed to read file /var/pids/web.pid, retry attempt: 2
2023/07/07 21:02:45.144554 [WARN] Failed to read file /var/pids/web.pid, retry attempt: 3
2023/07/07 21:02:48.144706 [WARN] Failed to read file /var/pids/web.pid, retry attempt: 4
2023/07/07 21:02:52.147801 [WARN] Failed to read file /var/pids/web.pid, retry attempt: 5
2023/07/07 21:02:57.148022 [ERROR] update processes [web healthd nginx cfn-hup] pid symlinks failed with error read pid source file /var/pids/web.pid failed with error:open /var/pids/web.pid: no such file or directory
2023/07/07 21:02:57.148068 [ERROR] An error occurred during execution of command [app-deploy] - [Track pids in healthd]. Stop running the command. Error: update processes [web healthd nginx cfn-hup] pid symlinks failed with error read pid source file /var/pids/web.pid failed with error:open /var/pids/web.pid: no such file or directory
2023/07/07 21:02:57.148071 [INFO] Executing cleanup logic
2023/07/07 21:02:57.148271 [INFO] CommandService Response: {"status":"FAILURE","api_version":"1.0","results":[{"status":"FAILURE","msg":"Engine execution has encountered an error.","returncode":1,"events":[{"msg":"Instance deployment successfully generated a 'Procfile'.","timestamp":1688763757767,"severity":"INFO"},{"msg":"Instance deployment failed. For details, see 'eb-engine.log'.","timestamp":1688763777148,"severity":"ERROR"}]}]}

Based on this I'm guessing that the user executing the service doesn't have access to store the web.pid. You should contact the service provider.

yeah, it may be permession, or the folder doesn't exist at all.

can you get the full logs, something like:

1. Navigate to the management page for your environment.
2. Choose 'Logs' in the sidebar.
3. Click 'Request Logs'.
4. Choose 'Last 100 lines' or 'Full Logs'. Note that 'Full Logs' will take longer to prepare and download.
5. Download the logs and look for 'eb-engine.log' in the downloaded files.

@admin Hello Hasan, thanks so much for your comment. Please, note that the log presented here is the eb-engine.log. I tried attaching the file here but the site rejected it so I had to copy and paste everything here.

@ssadvisor Hello, thanks so much for your comment. I'm actually the one doing all of these. Frankly, I don't have a strong background in coding. Initially, I thought it'll be easy to deploy the zipped file but the AWS environment as a whole appears to be complicated, maybe it's because I'm a total newbie in this.

@Hasan actually used Streamlit to demonstrate in the video I watched but I needed something that I could exercise more control, and then I discovered AWS EB (was actually searching for free webapp hosting). So, I had to rewrite the Python code using Flask framework. However, this whole AWS EB error thing has so frustrated me. I couldn't even find any good help on YouTube because the 502 Bad Gateway error from Nginx probably means a different thing to different situations.

I just feel bad. I wanted to see this working.

@samuelson00 As I mentioned already the issue is that the process cannot write to the expected PID control file. This is related to a service trying to start your python code. I've not use AWS and haven't had experience with NGINX which is the service requiring PID control. There are most likely environment variables that you could set to start the service differently. Do you have root access to the server? Maybe consider using https://www.pythonanywhere.com/pricing/  instead.

@ssadvisor Thank you for your comment once again. It appears I've been able to resolve the PID control issues. Sadly, the error has transitioned to 504 Gateway Time-out.

Any ideas what I can do?

Here's the error log: https://drive.google.com/file/d/1sL3QLhobwFDcx5KFkFmr2mch7Q1HMxdP/view?usp=sharing

@samuelson00 I don't see anything in the file you provided. However, take a look at https://repost.aws/knowledge-center/504-error-alb