using pymongo in Gunicorn

Hey @basilcabrera,

Check your logs, what does Nginx say other than 502 bad gateway? Additionally, check your application’s log, do you see anything there? it’s important to have access to logs. By default, Gunicorn logs errors and warnings. You can configure Gunicorn logging to get more information, including access logs.

Here are a few steps to enable and manage Gunicorn logging:

Update your gunicorn configuration:

In your gunicorn service file /etc/systemd/system/gunicorn.service, update the ExecStart line to include log file paths for access and error logs. Replace the following line:

--access-logfile - \

with

--access-logfile /path/to/your/access.log \
--error-logfile /path/to/your/error.log \
--log-level info \

Make sure to replace /path/to/your/access.log and /path/to/your/error.log with the desired paths for your log files.

The --log-level flag can be set to different values, depending on the level of detail you want in your logs:

• debug: Detailed logs including all messages, useful for debugging.
• info: Default logging level, includes error and informational messages.
• warning: Only logs warning and error messages.
• error: Logs only error messages.
• critical: Logs only critical error messages.

After updating the configuration, restart the gunicorn service for the changes to take effect:

sudo systemctl daemon-reload 
sudo systemctl restart gunicorn