Talk:Portal:Toolforge/Admin/Infrastructure tools
Appearance
Rendered with Parsoid
Latest comment: 4 months ago by BryanDavis in topic k8s-status tool's status is 502 Bad Gateway and unreachable
This talk page is not a Cloud VPS or Toolforge support forum. Contact information for Cloud VPS and Toolforge can be found at Help:Cloud Services communication.
Move projects list to Cloud VPS namespace
Related to the FIXME tag about relocating the Projects section. Yes, my initial impulse would be to search that information in the CloudVPS admin namespace.
k8s-status tool's status is 502 Bad Gateway and unreachable
Hi, the maintainers of k8s-status.toolforge.org, @Majavah and @Majavah. I don't think if this is the right place for this and I don't know if you are aware about the tool's status or not, but I just wanted to let you both know about its status which is 502 Bad Gateway and unreachable. Thanks! Aram (talk) 18:30, 2 June 2024 (UTC)
- and @BryanDavis. Aram (talk) 18:32, 2 June 2024 (UTC)
- Logs looked like the webservice was getting killed by the uwsgi container for taking too long to respond. I set a new 5 minute max time in uwsgi.ini and also increased the initial ram and cpu for the container. Things seem to be working now. -- BryanDavis (talk) 21:48, 2 June 2024 (UTC)
- and @BryanDavis. Aram (talk) 18:32, 2 June 2024 (UTC)