cgit.freebsd.org not reachable?

PMc

PMc

doesnt work from two of my providers... since last night...

# host cgit.freebsd.org
cgit.freebsd.org is an alias for cgit.nyi.freebsd.org.
cgit.nyi.freebsd.org has address 96.47.72.110
cgit.nyi.freebsd.org has IPv6 address 2610:1c1:1:606c::16:6e

Are there alternates?
 
getopt said:
Interesting downtime for a production server. Obviously there was no redundancy.
Click to expand...
A web frontend for browsing git isn't exactly a mission-critical system, so, this doesn't surprise me. After all, all the infrastructure operated by the FreeBSD project must be paid for...

There wasn't another update from clusteradm yet, so obviously they didn't succeed moving cgit to a new box yet. Well, most of the people operating that infrastructure do that mostly in their spare time. ?‍♂️
 
zirias@ said:
A web frontend for browsing git isn't exactly a mission-critical system
Click to expand...
So it's only the cgit? So if I would run a pull, I would get current data?

Then there is no problem, only the information could be a real bit better.
 
PMc said:
So if I would run a pull, I would get current data?
Click to expand...
As far as I know the git server itself (git.freebsd.org) is still up and running. It's only the web frontend (cgit.freebsd.org) that's down.

Code: 
root@fbsd-test:/usr/ports # git remote -v
origin  https://git.freebsd.org/ports.git (fetch)
origin  https://git.freebsd.org/ports.git (push)
root@fbsd-test:/usr/ports # git pull -p
remote: Enumerating objects: 102, done.
remote: Counting objects: 100% (73/73), done.
remote: Compressing objects: 100% (62/62), done.
remote: Total 102 (delta 12), reused 16 (delta 11), pack-reused 29
Receiving objects: 100% (102/102), 210.31 KiB | 1.56 MiB/s, done.
Resolving deltas: 100% (18/18), completed with 9 local objects.
From https://git.freebsd.org/ports
   3fb6e860eddf..28cfe20550b8  main       -> origin/main
   1719e290f6d2..056d16ee00b0  2024Q1     -> origin/2024Q1
Updating 3fb6e860eddf..28cfe20550b8
Fast-forward
{snip}
 41 files changed, 715 insertions(+), 698 deletions(-)
 create mode 100644 comms/klog/files/patch-src_main.cpp
 
PMc said:
only the information could be a real bit better.
Click to expand...
Indeed, it was only announced internally. It's not something really important, so posting to freebsd-announce@ or putting something on the website front page would probably be over the top. But there's the freebsd-ops-announce mailing list, which looks like it's the perfect place for something like that. Looking at its archives, it seems people forgot it exists ?‍♂️.

Maybe our ops also erroneously assumed only developers would browse the git repos ?
 
PMc said:
Then where is the problem?
Click to expand...
On the server that runs the cgit frontend? The git repository itself and the web frontend don't need to be on same server?

If meant differently, yes, it's not a problem. Everyone's git push/pull/fetch/clone/whatever still works. Just browsing it is a bit cumbersome. Especially because freshports only links to cgit, and I use that a LOT.
 
Code: 
GIT_CURL_VERBOSE=1 GIT_TRACE=1 GIT_TRACE_PACKET=1 git  clone https://git.freebsd.org/src .
trace: run_command: git remote-https origin https://git.freebsd.org/src

Recv header: HTTP/1.1 302 Moved Temporarily
Recv header: Location: https://cgit.freebsd.org/src

Info: Issue another request to this URL: 'https://cgit.freebsd.org/src'
Info: Failed to connect to cgit.freebsd.org port 443 after 75203 ms: Couldn't connect to server

GitLab, however, gets access:
This project is mirrored from https://git.freebsd.org/ports.git. Pull mirroring updated 9 minutes ago.
Click to expand...

Ha. My mistake. Disregard.
 
diizzy said:
Freshports links to all "mirrors" including GitHub, Codeberg etc
Click to expand...

Yep, in alphabetical order (example pictured below):
  • cgit
  • Codeberg
  • GitHub
  • GitLab
  • SVNWeb.
 

Attachments

  • 1704762502203.png
    1704762502203.png
    79.5 KB · Views: 92

VuXML​

From <https://lists.freebsd.org/archives/dev-commits-ports-all/2024-January/094579.html>:

It looks like there was something up with the vuxml build because the two commits after 06b20337d have yet to be incorporated into the site.

make -C /usr/ports/security/vuxml validate looks fine, so it's probably related to the recent hardware issues. A few jails, including the one for vuxml, were moved to a different system. Clusteradm is aware, so there should be an update soon.

Joe
Click to expand...

(<https://www.vuxml.org/freebsd/4c8c2218-b120-11ee-90ec-001b217b3468.html> is currently 404, not found.)
 
You must log in or register to reply here.
Back
Top