I made an error when I configured the last kernel.  While 6.1.7 does appear to be stable AND it appears to have fixed the long standing NFS bug for which I enabled the extra debugging, I accidentally compiled it with premption which I do not want on a server as it adds additional context switching overhead and decreases overall efficiency.  Thus I am going to be making a new kernel at least for the web server tonight (which is most affected) and will be doing a kernel upgrade just to fix this on the rest of the servers next Friday.  In the meantime, things may at times get a little slow.

Fedora is messed beyond repair, going to have to re-install.  It will work kind of for non-graphical sessions, but I can’t get any display manager to work properly.

     We have changed the default PHP from version 7.4 to version 8.0 now.

     Everything from 5.6 to 8.2 is available, anything older than 8.0 is no longer receiving security updates so should be avoided IF POSSIBLE but some older applications may not work with 8.0.

     It is best to update those applications if possible, but if not you can use an .htaccess file to override the default PHP version.  See:

     https://www.eskimo.com/support/override-php-version/

     The Yacy search engine “https://yacy.eskimo.com/” is down at present.  Something is causing it to eat up all available memory and then die.  I have opened a trouble ticket after doing some preliminary troubleshooting and am waiting upon a response.

     I am going to have to reboot virtual private servers later this evening because iptables on the physical host is messed up, ufw reset isn’t working, and now I’ve locked myself out of the machine altogether.

     We will be upgrading to the 6.1.7 kernel this evening at 11pm.  Because KASAN caused issues with some of our servers, some would not boot with it, some were slower, we will only be putting it on two NFS servers that have been problematic.  I believe however that 6.1.7 has already addressed the bug because I found a patch in the changelog that addresses exactly the issue we’ve been experiencing, a use after free in nfsd.

     We will be rebooting centos7 and scientific7 earlier in the afternoon because of difficulties in upgrading those kernels that requires some extra processes.

     Tonight will affect all services, if all goes well we should be done by 11:30 and no service should be out more than 10 minutes EXCEPT for Yacy.  Yacy rebuilds it’s database upon reboot and this takes 30-45 minutes.

     This will also affect all of our fediverse servers, https://friendica.eskimo.com/, https://hubzilla.eskimo.com/, https://nextcloud.eskimo.com/ (currently unfederated owing to a plugin problem), and https://yacy.eskimo.com/.

Comcast has completed their work and I’m back online and phones are operational.

CentOS Stream has not been used since last March and MxLinux since last July, so I am going to ask if anyone wants to continue these or should I discontinue them and save the resources?

     Comcast will be doing work on the 18th that will take my telephone system, fax, and Internet connection away from my home office during part of that day.  I do not know what time or how long.  I hope to have some internet access via my tablet but it is very limited.  If you have an issue and the website is working, please generate a ticket, else please try to contact me periodically,

     The machine which hosts vps1-6 and 8 failed to reboot properly.  I am headed down to the co-location facility now to troubleshoot.  I should arrive there about 12:10AM.