NOTE
If your issue is for security or deals with sensitive info please mark it as private using the checkbox below.
I was trying to connect to the official Wiki yesterday. I made a request in discourse and I was told better do make a ticket here. Is there a way to check if the system hast troubles or just reporting would be the right thing ?
https://discussion.fedoraproject.org/t/id-fedoraproject-org-throws-a-504-gateway-timeout/99219 You might answer in discourse so we do have an answer there ... thanks.
ASSAP
Is this happening 100% of the time? or sporadic?
Is it:
or
or something else?
Gateway Timeout: The gateway did not receive a timely response from the upstream server or application. 23:15:15 UTC Thursday, December 14, 2023
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation, low-gain, low-trouble, ops
Metadata Update from @abompard: - Issue assigned to abompard
I saw similar issue happening here https://pagure.io/fedora-infrastructure/issue/11671
Experienced the same when trying to login to https://communityblog.fedoraproject.org/
It should be OK now. In the logs I had:
pam_sss(ipsilon:auth): received for user abompard: 4 (System error)
I had to restart sssd on ipsilon01, no idea why it wasn't responding to pam_sss, but now I can login.
Let me try that as well
I'm still getting 504 when trying to login to https://communityblog.fedoraproject.org/
Maybe it just needed some time, I was able to log now.
Closing the ticket
Metadata Update from @zlopez: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Actually I'm unable to reach ipsilon02. It responds to ping but I can't SSH into it. That may by why there are still 502 errors sometimes, when haproxy sends to ipsilon02.
Metadata Update from @abompard: - Issue status updated to: Open (was: Closed)
Load seems to be around 1 since this morning. Could it be power-cycled maybe?
Metadata Update from @abompard: - Assignee reset
I can't SSH to it either, but if it would be offline we should get Nagios alert.
Oh yeah it does respond to ping. Looks like we don't check for SSH access in Nagios though: https://nagios.fedoraproject.org/nagios/cgi-bin//status.cgi?host=ipsilon02.iad2.fedoraproject.org
@darknao restarted the ipsilon02 from vmhost-x86-06 and this should resolve the issue.
Log in to comment on this ticket.