21.1.7: Updates tab is hanging

[tong2x]

upgraded to 21.1.7_1

firefox no issues after upgrade

chrome, same issue as above(upgrade web UI hang), but clearing cache also solved the issue

[thogru]

Hi,

I use Firefox 89.0

I did my OPNsense upgrade 21.1.6 to 21.1.7 without any issue. The upgrade 21.1.7 to 21.1.7_1 hung until cleared the cache.

Regards
Thomas

[XeroX]

Everything was working fine, except these log entries during the update:

Code: [Select]

Checking integrity... done (1 conflicting)
  - php73-phalcon4-4.1.2 conflicts with php73-phalcon-3.4.5 on /usr/local/etc/php/ext-30-phalcon.ini

Code: [Select]

Starting configd.

Fatal error: Uncaught Error: Class 'Phalcon\Validation\Validator' not found in /usr/local/opnsense/mvc/app/models/OPNsense/Base/Constraints/BaseConstraint.php:37
Stack trace:
#0 [internal function]: unknown()
#1 [internal function]: Phalcon\Loader->autoLoad('OPNsense\\Base\\C...')
#2 [internal function]: spl_autoload_call('OPNsense\\Base\\C...')
#3 /usr/local/opnsense/mvc/script/run_migrations.php(50): ReflectionClass->__construct('OPNsense\\Base\\C...')
#4 {main}
  thrown in /usr/local/opnsense/mvc/app/models/OPNsense/Base/Constraints/BaseConstraint.php on line 37

[rmayr]

Another confirmation that clearing cache in Firefox solved this issue.

[Julien]

this the browser related issue. depend on the php
so clear the cache fix it,
i think of a old saved password what causes the browser to hang there.

[jimjohn]

Can confirm that clearing the cache fixes the hanging update page on the newest macOS with Safari.

[Dysprosium11]

Yeah i had the same issue, closing and opening the browser fixed it

[bill.gertz]

That was the trick but on Safari all that was required was to clear history for the last hour.

Perhaps this could be added to the notes *before* or rather at the top of the upgrade text stream?

Sure that was seen during integration and test before this rolled out.

[bucky2780]

had the same issue.
However haproxy now refuses to start, so deeper problems abound. Will revert to previous release...

[0perat0r]

I had this issue but this thread took a long time to find. Adding my specific error in hopes it helps others find it more easily.

Code: [Select]

Fatal error: Uncaught Error: Class 'Phalcon\Session\Manager' not found in /usr/local/opnsense/mvc/app/config/services.php:79 Stack trace: #0 [internal function]: Closure->{closure}() #1 [internal function]: Phalcon\Di\Service->resolve(NULL, Object(Phalcon\Di\FactoryDefault)) #2 [internal function]: Phalcon\Di->get('session', NULL) #3 [internal function]: Phalcon\Di->getShared('session') #4 /usr/local/opnsense/mvc/app/controllers/OPNsense/Base/ControllerRoot.php(148): Phalcon\Di\Injectable->__get('session') #5 /usr/local/opnsense/mvc/app/controllers/OPNsense/Base/ControllerBase.php(138): OPNsense\Base\ControllerRoot->doAuth() #6 [internal function]: OPNsense\Base\ControllerBase->beforeExecuteRoute(Object(Phalcon\Mvc\Dispatcher)) #7 [internal function]: Phalcon\Dispatcher->dispatch() #8 /usr/local/opnsense/www/index.php(72): Phalcon\Mvc\Application->handle('/ui/core/firmwa...') #9 {main} thrown in /usr/local/opnsense/mvc/app/config/services.php on line 79

[franco]

The 21.1.9 update fixes the silent API errors (you can get a lot of popup errors now during the transition to Phalcon 4) and that should improve the handling of browsers as well not trying to cache 500 errors, because previously errors were delivered as 200 and the browser decided to cache them even though it wasn't allowed to in the first place.

During testing we use stock browsers no ad blockers or plugins and we have never seen the browser cache being stuck during the Phalcon 4 transition so the conditions under which this appears are way harder to fix in remote server software than it seems.


Cheers,
Franco

[chrisgch]

After the update to 21.1.9_1, I had another strange error where the update tab was hanging. The error message was:
pkg: http://mirror.ams1.nl.leaseweb.net/opnsense/FreeBSD:12:amd64/21.1/latest/meta.txz: No address record
repository OPNsense has no meta file, using default settings

When I checked on the Dashboard, the "Unbound DNS" service was stopped. After starting it manually, the updates tab is working again. I'm just reporting this here just in case that someone has the same error.