I received errors on upgrade ,and All “Status” section except (mdstat,inet traffic, connections) n web interface are not working.
"Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log."
[root@morgul httpd]# tail -f error_log
Compilation failed in require at /var/ipfire/graphs.pl line 26.
BEGIN failed–compilation aborted at /var/ipfire/graphs.pl line 26.
Compilation failed in require at /srv/web/ipfire/cgi-bin/memory.cgi line 31.
[Wed Feb 14 01:12:58.056150 2024] [cgid:error] [pid 4811:tid 129750676788928] [client 192.168.0.30:45754] End of script output before headers: memory.cgi, referer: https://192.168.0.1:444/
Can’t load ‘/usr/lib/perl5/site_perl/5.36.0/x86_64-linux-thread-multi/auto/RRDs/RRDs.so’ for module RRDs: libxml2.so.2: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.36.0/x86_64-linux-thread-multi/DynaLoader.pm line 206.
at /var/ipfire/graphs.pl line 26.
Compilation failed in require at /var/ipfire/graphs.pl line 26.
BEGIN failed–compilation aborted at /var/ipfire/graphs.pl line 26.
Compilation failed in require at /srv/web/ipfire/cgi-bin/memory.cgi line 31.
[Wed Feb 14 01:12:59.588912 2024] [cgid:error] [pid 4811:tid 129750785828544] [client 192.168.0.30:47816] End of script output before headers: memory.cgi, referer: https://192.168.0.1:444/
core183 ships /usr/lib/libxml2.so.2 and usr/lib/libxml2.so.2.12.3 so this file should not missing.
( /usr/lib64 should a symlink to /usr/lib )
i assume there was an error at unpack the archive or a write error to your disk. (is there enough space free ?)
There are missing, but i try to restore with backup from core 181 and reatore all configurations. After new try to upgrade, there is no problem. Yesterday’s night upgrade process return some errors from some download servers. Maybe not all files are downloaded correctly.
I had on 2 instances issues so far. One was a proxmox virtual ipfire and another one running on intel hardware industrial grade PC. On both the WebUI stopped working and I had to issue a reboot after that they seem to work normally.
I also had such an issue when going to 182 on one of the firewalls and the annoying thing is it is a remote one. The Firewall and Internet capabilities are still working but no access to WebUI is possible and it is holiday time so no one on site so I have to drive there and issue a reboot manually
I really had this “WebUI gone bad” issue now on multiple updates in the last year. Such things of course makes you hesitating and not want to update if it triggers such issues.
Would it not be possible to just restart the WebUI after an update as a preventive measure?
I really now have to remind myself all the time to turn on SSH access in case the WebUI is not coming back. That way I can at least reboot it. But I really think this should not be necessary
This indicates that radius is linked to openssl and therefore radius needs to be incremented and shipped every time there is an openssl update.
The problem has obviously been there since Core Update 180 because Openssl was updated to 3.1.4 in Core Update 181 and then to 3.2.1 in Core Update 183.
Unfortunately no one using the radius addon tested out the Core Updates 181, 182 or 183.
I will run a build to increment radius so it gets shipped with Core Update 184.
In the meantime the only option I think is to run a backup, save it and then do a fresh install of Core Update 180 and restore.