by Luc Saffre · in Developers · assigned to Luc Saffre

Summary

Children

Comments

• 11 months, 4 weeks ago by Luc Saffre about #6442 (lino.laudate.ee says 502 Bad Gateway) : Bad gateway came because i had introduced a typo during a manual patch. But that typo failed to shop up in the logs. Maybe because there were two supervisor conf files specifying stopsignal=KILL.
• 11 months, 4 weeks ago by Luc Saffre about #6442 (lino.laudate.ee says 502 Bad Gateway) : The problem is back. According to the /etc/supervisor/conf.d/*-asgi.conf files, Jane is on 8001, welcht is on 8003, ets on 8004, I see no conflict. After rebooting it is gone again. What's the explanation?
• 1 year ago by Luc Saffre about #6442 (lino.laudate.ee says 502 Bad Gateway) : PS thanks to serverfault.com/questions/808732/supervisor-sock-file-missing
• 1 year ago by Luc Saffre about #6442 (lino.laudate.ee says 502 Bad Gateway) : restart didn't help, neither did stop and start. But the issue was gone after a reboot. I guess that it's because each site creates a socket, and I changed configuration while supervisor was running.
• 1 year ago by Luc Saffre about #6442 (lino.laudate.ee says 502 Bad Gateway) : I said systemctl status supervisor to see: Process: 1530174 ExecStart=/usr/bin/supervisord -n -c /etc/supervisor/supervisord.conf (code=exited, status=1/FAILURE)
  and then ran this process manually. Result:
  2025-10-26 07:56:00,546 INFO Included extra file "/etc/supervisor/conf.d/ets-asgi.conf" d...
• 1 year ago by Luc Saffre about #6442 (lino.laudate.ee says 502 Bad Gateway) : Created new Ticket #6442 (lino.laudate.ee says 502 Bad Gateway).