FYI, pkgs git process cleanup | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
We started getting some failed builds today due to koji not being able to get git checkouts from pkgs01. $ git clone -n git://pkgs.fedoraproject.org/gnome-shell /var/lib/mock/f17-build-1342530-216385/root/tmp/scmroot/gnome-shell fatal: read error: Connection reset by peer Cloning into /var/lib/mock/f17-build-1342530-216385/root/tmp/scmroot/gnome-shell... and $ git clone -n git://pkgs.fedoraproject.org/digikam /var/lib/mock/f17-build-1342529-216385/root/tmp/scmroot/digikam fatal: read error: Connection reset by peer Cloning into /var/lib/mock/f17-build-1342529-216385/root/tmp/scmroot/digikam... There were some IP's hitting pkgs01 pretty hard on checkouts, but that turns out to not be the real issue. There were a number of old stale connections laying around, making it so it hit xinetd limits much faster than normal. I killed 46 old git upload-pack processes and 51 old stale ssh connections that were all from Feb, then restarted xinetd. This seemed to clear things up. We may want to look at a automated script to clean up these processes? kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
[Home] [Fedora Users] [Fedora Legacy List] [Fedora Maintainers] [Fedora Desktop] [Red Hat 9 Bible] [Fedora Bible] [Fedora SELinux] [Big List of Linux Books] [Yosemite News] [Yosemite Photos] [KDE Users] [Fedora Tools]