Random hangs when pushing to pkgs.fedoraproject.org #12442
Labels
No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As/Will Not
Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#12442
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've been seeing this randomly for some time, and I was finally able to capture some logs about what's going on:
Metadata Update from @zlopez:
I was unable to reproduce(but you did say it was something randomly occurring), was there any specific date/time that this occurred?
FWIW I tried looking at the logs for pkgs01.iad2.fedoraproject.org/2025/03/08 and nothing looks different, there were four sessions around that time:
15:39:37
15:39:59
15:40:24
15:40:41
...they all look like the same things happened.
Okay, I used lnav and that helped me find these SELinux errors from the first session:
Mar 8 15:39:43 pkgs01 tag_audit_log: type=USER_ERR msg=audit(1741448375.478:6440543): pid=2063495 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=PAM:bad_ident grantors=? acct="?" exe="/usr/sbin/sshd" hostname=218.92.0.243 addr=218.92.0.243 terminal=ssh res=failed'^]UID="root" AUID="unset"
Mar 8 15:39:43 pkgs01 tag_audit_log: type=USER_LOGIN msg=audit(1741448375.479:6440545): pid=2063495 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login acct="root" exe="/usr/sbin/sshd" hostname=? addr=218.92.0.243 terminal=ssh res=failed'^]UID="root" AUID="unset"
Blah, that's probably a false hit ... it doesn't always happen, but it happens a bunch for a lot of different sessions.
It seems like it never even connects to the pkgs side... just tries and times out.
I wonder if there could something going on at the router/NAT level here? Like it's shutting down due to too many connections or something. ;(
@ngompa when this happens... is it after you have connected a bunch? Or that doesn't seem to matter? and how long do the timeouts last? Or hard to say?
This is happening right now. And I've been stuck for several minutes now.
I've only done a couple of sequential pushes and then I'm locked out via SSH.
I'm also now seeing it with HTTPS too: