This post is a proof-of-concept for creating a new jail instead of upgrading one in-place. I think the process is easier, given there are no packages installed in the jail. Re https://github.com/FreshPorts/freshports/issues/622 Each ingress node in a FreshPorts instance contains a FreeBSD jail. It has some shell scripts, but no installed packages. I think it […]
Updating a jail by replacing it Read More »
It’s time to clear old distfiles. Based on Moving distfiles to a new filesystem & deleting unused distfiles, I did the following on the aws-1-ingress01 jail. In short: fetch index list DISTFILES used by index remove DISTFILES not used by index The commands: root@freshports:/usr/ports # make fetchindex /usr/bin/env fetch -am -o /usr/ports/INDEX-14.xz https://download.FreeBSD.org/ports/index/INDEX-14.xz /usr/ports/INDEX-14.xz 1864
Time to clear out the distfiles Read More »
This morning I was created with 6 emails, all announcing FAILED: MASTER_PORT, one for each FreshPorts node. Each was sent at 5AM (1000 UTC). Something happened which upset every one of them. I have no idea why. However, I’m writing this down for future reference. This announcement came from one of the many system checks
FAILED: MASTER_PORT Read More »
FreshPorts pulls down a lot of distfiles (the file distributed by the software author which contains the software). Much more than your average user. Every distfile for every commit is fetched. Let’s look at my private FreshPorts development instance: [13:18 dvl-ingress01 dvl /jails/freshports/usr/ports] % du -ch -d 0 distfiles 125G distfiles 125G total That’s 125GB.
Moving distfiles to a new filesystem & deleting unused distfiles Read More »
The original problem was explained and fixed however it seems to have resurfaced. Either that, or it was not fixed at all. In short: FreshPorts sees the first commit for a port on a branch the commit is deleting that port FreshPorts detects that the port has been deleted It forgets, somehow, that the port
When a port on a branch is deleted, FreshPorts tried, and fails, to refresh it Read More »
On November 19 2024, these errors appeared on every FreshPorts node: That’s my clue to go look closer as to why the processing failed. This processing is related to the security/vuxml port which documents known vulnerabilities within the FreeBSD ports tree and operating system. This tool helps system administrators identify and patch known problems. The
vuxml processing broken – files have grown too much Read More »
This is mostly for my own future reference. I was looking at /categories.php and didn’t see the new filesystems category. I also note it does not sort by what it says it will sort. I eventually found it was loading data from this table: That’s all from 2017… 7 years ago. Grepping for the table
CategoryStatsUpdate and the category_stats table Read More »
I’ve updated the code (look for pseduo code in Welcome to the new category: filesystems) and now I’m ready to test that code. I have a copy of the database from before the commit. I’ve configured my test environment I can rollback the filesystem and get to a known good point. Am I doing this
Rerunning the filesystems commit to create the new category Read More »
Following on from yesterday’s blog post about the new filesystems category, today I hope to fix the code and get the website up to date again. At present, the code is spinning, trying to fetch category information using outdate code which assumes subversion is still in use. [16:46 dvl-ingress01 dvl ~freshports/message-queues/spooling] % ps auwwx |
Fixing the category creation code Read More »
A recent commit to the FreeBSD ports tree brought in a new category: filesystems See also the followup to this blog post: Fixing the category creation code This commit has been processed by FreshPorts, the results are only partially good. For example, this screenshot shows the deleted ports (moved from their old categories to the
Welcome to the new category: filesystems Read More »