Hi there
Get an error when installing 18.1.9. Installation screen hangs with extracting opnsense-18.1.9 and the following error message appears:
[31-May-2018 20:58:01 Europe/Berlin] PHP Fatal error: Uncaught Error: Class 'OPNsense\Core\Routing' not found in /usr/local/opnsense/mvc/app/config/services_api.php:87
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('router', NULL)
#3 [internal function]: Phalcon\Di->getShared('router')
#4 /usr/local/opnsense/www/api.php(26): Phalcon\Mvc\Application->handle()
#5 {main}
thrown in /usr/local/opnsense/mvc/app/config/services_api.php on line 87
Any idea how to fix that?
Br br
Hi bringha,
Looks like a race condition during install: a file was not yet accessible on the file system.
You should have 18.1.9 installed now? To be safe, a reboot will take care of the missing configuration (if any).
But to be safe you should run a health audit from the firmware GUI prior to reboot.
Cheers,
Franco
Thanks Franco,
Will reboot when back home. As I found all files and also the Router Class thought something like that. Interesting enough, 18.1.9 runs normal and also the Router Configis there ...
Dashboard says that 18.1.9. is installed, but I can't likely get away the error message without reboot ?!
BR br
It looks like a glitch during upgrade: files being rewritten and something being loaded before that file is accessible by the system to do what it should. If it were a hard error you'd never see the GUI again, because a vital file would be missing.
The reboot is to ensure that whatever migration or setup script ran post-update can be properly restarted. But in fact, just going to System: Firmware: Packages and reinstalling "opnsense" package should do the trick as well.
Cheers,
Franco
Hmmm,
this only shows 'führe aus, bitte warten', and nothing happens ....
Br br
I would assume this was prior to reboot? Restart "configd" from System: Diagnostics: Services.
Cheers,
Franco
Yes, it was - tried the proposal without reboot first, also restart of configd did not change the situation - I simply rebooted and now all is fine ...
Br br