Jineu

To be clear - that line /service-worker.js : File not found is appearing in BOTH miniserv.error and miniserv.log. The difference is that in miniserv.log it's showing 401 errors. [17/Jan/2023:07:47:26 +0100] "GET /session_login.cgi?logout=1 HTTP/1.1" 401 5087 [17/Jan/2023:07:47:27 +0100] "GET /service-worker.js HTTP/1.1" 401 4918 [17/Jan/2023:20:15:19 +0100] "GET / HTTP/1.1" 401 4918 It does not appear to be a Webmin issue as the Webmin upgrade works as deisred with other browsers. So we will look...

Thanks very much for the quick reply. Definitely odd - as Webmin upgrades typically go smoothly and without any drama at all. Was very surprised to see 100% CPU spikes. Answers and details: 1. Upgrade was from the last official Webmin version - we keep current with all updates. 2. Only thing of interest in miniser.error is: /service-worker.js : File not found 3. Same upgrade of Webmin/Usermin is working without any problems on another server with same config. So that points to something with this...

Added info: Only seen in Authentic Theme. Change of theme results in immediate CPU utilization drop to normal.

Background: Webmin/Usermin upgrades have gone without inciden for years. Current situation: Last upgrade to Webmin 2.011 on Debian 11/Php 8.1/Apache2.4/MariaDB server suddenly causing 100% long CPU spikes. Only seen/caused in Mozilla Browser. Other browsers do not cause the spike. Compleltely strange. Looping on: /usr/share/webmin/authentic-theme/session_login.cgi

2014 .isoinfo and .iso files - cannot open - any ideas