Topics

Hello,

I have freshly installed Nginx plugin.
However, any attempt to configure it (add new "Location", for example) leads to the same strange error:

Unexpected error, check log for details

No information in the logs, but System Firmware Reporter gave me several errors like this:

Code Select Expand

Error: Call to undefined method OPNsense\Base\Constraints\NgxBusyBufferConstraint::isEmpty() in /usr/local/opnsense/mvc/app/models/OPNsense/Base/Constraints/NgxBusyBufferConstraint.php:46
Stack trace:
#0 /usr/local/opnsense/mvc/app/models/OPNsense/Base/Validation.php(83): OPNsense\Base\Constraints\NgxBusyBufferConstraint->validate(Object(OPNsense\Base\Validation), 'location.661a48...')
#1 /usr/local/opnsense/mvc/app/models/OPNsense/Base/BaseModel.php(517): OPNsense\Base\Validation->validate(Array)
#2 /usr/local/opnsense/mvc/app/controllers/OPNsense/Base/ApiMutableModelControllerBase.php(260): OPNsense\Base\BaseModel->performValidation(false)
#3 /usr/local/opnsense/mvc/app/controllers/OPNsense/Base/ApiMutableModelControllerBase.php(466): OPNsense\Base\ApiMutableModelControllerBase->validate(Object(OPNsense\Base\FieldTypes\ContainerField), 'location')
#4 /usr/local/opnsense/mvc/app/controllers/OPNsense/Nginx/Api/SettingsController.php(192): OPNsense\Base\ApiMutableModelControllerBase->addBase('location', 'location')
#5 /usr/local/opnsense/mvc/app/library/OPNsense/Mvc/Dispatcher.php(165): OPNsense\Nginx\Api\SettingsController->addlocationAction()
#6 /usr/local/opnsense/mvc/app/library/OPNsense/Mvc/Router.php(156): OPNsense\Mvc\Dispatcher->dispatch(Object(OPNsense\Mvc\Request), Object(OPNsense\Mvc\Response), Object(OPNsense\Mvc\Session))
#7 /usr/local/opnsense/mvc/app/library/OPNsense/Mvc/Router.php(139): OPNsense\Mvc\Router->performRequest(Object(OPNsense\Mvc\Dispatcher))
#8 /usr/local/opnsense/www/api.php(36): OPNsense\Mvc\Router->routeRequest('/api/nginx/sett...', Array)
#9 {main}

Is anything wrong with my OPNsense installation or it is broken for everybody?

After upgrade to 23.7.1_3 the Unbound daemon failed to stop without any errors in logs.

I'm using combination of Unbound + Dnscrypt-proxy and for this reason I have custom Unfound configuration file. 23.7 introduced changes in ACL handling and has small bug in configuration file.

As a workaround I used duplicated "server:" clause in custom configuration file. See here: https://forum.opnsense.org/index.php?topic=10670.msg172282#msg172282 It solved problem with starting Unbound.

The proper fix is submitted via PR on GitHub: https://github.com/opnsense/core/pull/6756

The initial steps were not obvious because no error is recorded in logs, while command `configctl unbound check` clearly indicated errors in config file. It is possible to record such errors in the log?

I upgraded my router to version 23.7.1_3 and after some migration fixes it has been working fine.
However, after two days uptime, I've found very high CPU load.
My typical load average is in range 0.18-0.35 for five and fifteen minutes averages. Even with full network load CPU load stays in these borders.
However, today the average load was 2.1-2.8 (for both five and fifteen minutes) with very light network load. I'm using passive cooled device and the temperature was unusually high.
I rebooted my router and for one hour the average load is below 0.4.

What should I check if I notice the high load again? Which command should I run to find the problematic daemon or process?

I recently upgraded my router to  23.7.1_3 from 23.1.11.

After upgrade I noticed error message in console during each boot:
Configuring system logging...Error opening plugin module; module='examples', error='/usr/local/lib/syslog-ng/libexamples.so: Undefined symbol "random_choice_generator_parser"'

The same message could be found in system log.

I solved it by renaming libexamples.so to libexamples.so.bak, as this module probably was built by mistake, but I'm not sure whether this is correct fix or not.

[Reconfiguring IPv4 on igb0: error in configd communication %s, see syslog for details]

I have the same problem starting from 20.7 versions.

Each boot stops for about 100 seconds after message Reconfiguring IPv4 on WAN NIC.
After the error message the boot process continues and finished fine.

Related lines from boot screen:

Starting UPnP service...done.
Starting NTP service...deferred.
Starting Unbound DNS...done.
Generating RRD graphs...done.
Configuring system logging...done.
>>> Invoking start script 'newwanip'
Reconfiguring IPv4 on ovpnc2: OK
Reconfiguring IPv4 on igb0: error in configd communication %s, see syslog for details
Reconfiguring routes: OK
>>> Invoking start script 'freebsd'
Starting vnstat.
Starting dnscrypt_proxy.
WARNING: attempt to domain_add(netgraph) after domainfinalize()
setup igb1
setup ovpnc2 [egress only)
ngctl: send msg: No such file or directory error
ovpnc2: cannot create netflow node for ovpnc2
setup ovpnc1 [egress only)
ngctl: send msg: No such file or directory
error ovpnc1: cannot create netflow node for ovpnc1
setup igb0 [egress only)
Updating CPU Microcode...

Related lines from GUI, general log:

2021-06-19T16:49:19   opnsense[74603]   /usr/local/etc/rc.routing_configure: ROUTING: keeping current default gateway '46.88.22.44'   
2021-06-19T16:49:19   opnsense[74603]   /usr/local/etc/rc.routing_configure: ROUTING: setting IPv4 default route to 46.88.22.44   
2021-06-19T16:49:19   opnsense[74603]   /usr/local/etc/rc.routing_configure: ROUTING: IPv4 default gateway set to wan   
2021-06-19T16:49:19   opnsense[74603]   /usr/local/etc/rc.routing_configure: ROUTING: entering configure using defaults   
2021-06-19T16:49:18   configctl[11670]   error in configd communication Traceback (most recent call last): File "/usr/local/opnsense/service/configd_ctl.py", line 68, in exec_config_cmd line = sock.recv(65536).decode() socket.timeout: timed out   
2021-06-19T16:47:19   opnsense[91535]   /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface WAN.   
2021-06-19T16:47:19   opnsense[91535]   plugins_configure vpn (execute task : openvpn_configure_do(,wan))   
2021-06-19T16:47:19   opnsense[91535]   plugins_configure vpn (execute task : ipsec_configure_do(,wan))   
2021-06-19T16:47:19   kernel   pflog0: promiscuous mode enabled   
2021-06-19T16:47:19   kernel   pflog0: promiscuous mode disabled   
2021-06-19T16:47:19   kernel       
2021-06-19T16:47:19   opnsense[91535]   plugins_configure vpn (,wan)

This happens every boot, no exceptions.

Maybe this is related to two OpenVPN clients configured.

How to fix this? What else to check?

Hello,

I have combination of DNSCrypt-Proxy + Unbound configured as described at https://docs.opnsense.org/manual/how-tos/dnscrypt-proxy.html and https://forum.opnsense.org/index.php?topic=10670.0.

The problem is uncoordinated starts of DNSCrypt-Proxy and Unbound.
During the boot process Unbound started usually before DNSCrypt-Proxy and even when DNSCrypt-Proxy is started, Unbound still fails to resolve addresses. This could be solved by manual restart of Unbound service, but it is quite annoying to manually restart Unbound after each reboot.

Could it be solved somehow?

Got error message in the upgrade log in the GUI:

[25/28] Extracting os-tor-1.8_2: .......... done
Stopping configd...done
Starting configd.
Keep version OPNsense\Tor\ACLSocksPolicy (0.0.0)
Keep version OPNsense\Tor\General (1.0.0)

Fatal error: Uncaught Error: Class 'Phalcon\Validation\Message\Group' not found in /usr/local/opnsense/mvc/app/models/OPNsense/Base/BaseModel.php:442
Stack trace:
#0 /usr/local/opnsense/mvc/app/models/OPNsense/Base/BaseModel.php(564): OPNsense\Base\BaseModel->performValidation(false)
#1 /usr/local/opnsense/mvc/app/models/OPNsense/Base/BaseModel.php(686): OPNsense\Base\BaseModel->serializeToConfig()
#2 /usr/local/opnsense/mvc/script/run_migrations.php(55): OPNsense\Base\BaseModel->runMigrations()
#3 {main}
  thrown in /usr/local/opnsense/mvc/app/models/OPNsense/Base/BaseModel.php on line 442
Reloading plugin configuration
Configuring system logging...done.
Reloading template OPNsense/Tor: OK
[26/28] Reinstalling os-theme-rebellion-1.8.7...

The upgrade process finished fine, but I'm not sure whether all settings are successfully migrated.