I've received nearly 20k emails over the week-end from pagure about the error:
_pygit2.GitError: Repository not found at /srv/git/repositories/releng/fedora-scm-requests.git
if I try to access it in the UI, I get a 500 error not a 404, so I'm thinking the repo hasn't been moved.
I'm going to check the on server what things look like
Somehow the permissions were changed to:
drwx------+ 6 root git 165 May 4 2020 fedora-scm-requests.git
I brought them back to:
drwxr-xr-x+ 6 git git 165 May 4 2020 fedora-scm-requests.git
The subfolders look fine, so I didn't touch them.
Leaving this open so someone from CLE can ack and close the ticket :) (or follow-up to understand why the permissions were changed)
I'm not sure what could change the permission like that, but thanks for changing it back.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation
It was me. ;)
On friday, many many IPs started doing git blames in that repo. This caused postgres and pagure to become 100% unresponsive cpu bound. ;( Load was ~100 or so.
So, I blocked access to that repo and everything went back to normal.
I didn't think that repo was used by anything anymore... it's not the ticket repo, it's the main git repo that we don't use? I didn't realize it would email you about it. ;(
Anyhow, just a bit ago they were back, but I managed to block a bunch of /24's and get things down to mostly normal.
So, sorry about that. ;(
Should we do something so you don't get these emails?
Pesky DDOS :(
The error log doesn't send the IP of the request that triggered the error so I couldn't see if they were all coming from a certain IP range or not.
Isn't that repo still used to request new package/branch? Automated with toddlers?
Otherwise I think the easiest would be a 302 in apache that sends them to another page, this way no error email while also reducing the load on our side
That base git repo is not used since 2022... back when we had people commit to files directly.
The tickets repo for this project is used for people to request things and toddlers to process.
Yeah, good idea on the 302. If it starts happening again (or on another place) we could 302 it.
Metadata Update from @kevin: - Issue assigned to kevin
Anyhow, I am going to close this now. :)
let me know if you see anything still happening.
Metadata Update from @kevin: - Issue untagged with: Needs investigation - Issue tagged with: medium-gain, medium-trouble
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.