View Issue Details

IDProjectCategoryView StatusLast Update
0005186Kali LinuxKali Websites & Docspublic2025-07-14 09:36
Reporterfyzbyt Assigned Torhertzog  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version2018.4 
Summary0005186: git.kali.org is down
Description

Unable to reach the git archives via git or via http. page renders without any content besides page header and footer.

Steps To Reproduce

Go to website.
Observe outage

Additional Information

We've tried this via multiple different browsers/git clients and different systems to make sure that this is ok.

Git seems to be down, but hephaestus seems up.

Activities

Mister_X

Mister_X

2019-01-03 18:31

reporter   ~0010140

Which website?

Are you talking about http://git.kali.org/gitweb/ ? It works fine (also via https). It takes a little bit to load the long list of repositories.

fyzbyt

fyzbyt

2019-01-03 18:37

reporter   ~0010141

This does seem to load after 1 or 2 minutes?

So maybe there's something causing increased load times?

fyzbyt

fyzbyt

2019-01-03 18:46

reporter   ~0010142

Updating ticket.

we're having issues reaching live-build-config.git

It does appear as if the site is working, we're just experiencing really long load times.

git.exc.GitCommandError: Cmd('git') failed due to: exit code(128)
cmdline: git clone -v git://git.kali.org/live-build-config.git $LOCALFOLDER
stderr: '$LOCALFOLDER'...
Looking up git.kali.org ... done.
Connecting to git.kali.org (port 9418) ... 67.23.72.103 done.
fatal: read error: Connection reset by peer

rhertzog

rhertzog

2019-01-03 20:13

administrator   ~0010144

The daily build of ISO also experienced those "Connection reset by peer". It looks like the machine ran out of memory a couple of times in the last days, probably due to some faulty git/gitweb process.

rhertzog

rhertzog

2019-01-04 13:28

administrator   ~0010153

There were many old git-upload-pack processes left, and due to this I think that some limit was reached and fewer parallel connections were usable. I cleaned up and restarted git-daemon. The situation should be back to normal.

Issue History

Date Modified Username Field Change
2019-01-03 18:21 fyzbyt New Issue
2019-01-03 18:31 Mister_X Note Added: 0010140
2019-01-03 18:37 fyzbyt Note Added: 0010141
2019-01-03 18:46 fyzbyt Note Added: 0010142
2019-01-03 20:13 rhertzog Note Added: 0010144
2019-01-04 13:28 rhertzog Assigned To => rhertzog
2019-01-04 13:28 rhertzog Status new => closed
2019-01-04 13:28 rhertzog Resolution open => fixed
2019-01-04 13:28 rhertzog Note Added: 0010153
2025-07-14 09:36 g0tmi1k Priority high => normal