Messages

Starting from 20.1.4 I have a problem with eastpect that crashes and destroy my LAN NIC. After some minutes it restarts and work for sometime. The problem happens every now and then and I cannot see any relation with other components.

This is the log file:

May  7 11:48:57 OPNsense kernel: pid 33892 (eastpect), uid 0: exited on signal 11
May  7 11:48:57 OPNsense kernel: 937.846498 [ 293] generic_netmap_unregister Emulated adapter for re0 deactivated
May  7 11:48:57 OPNsense kernel: 937.847457 [1033] generic_netmap_dtor       Emulated netmap adapter for re0 destroyed
May  7 11:49:12 OPNsense eastpect[23514]: nm0::re0: permanently promiscuous mode enabled
May  7 11:49:12 OPNsense kernel: 952.519254 [1127] generic_netmap_attach     Emulated adapter for re0 created (prev was 0)
May  7 11:49:12 OPNsense kernel: 952.519307 [1033] generic_netmap_dtor       Emulated netmap adapter for re0 destroyed
May  7 11:49:12 OPNsense kernel: 952.544306 [1127] generic_netmap_attach     Emulated adapter for re0 created (prev was 0)
May  7 11:49:12 OPNsense kernel: 952.544634 [ 318] generic_netmap_register   Emulated adapter for re0 activated
May  7 11:49:12 OPNsense eastpect[23514]: nm1::re0^: permanently promiscuous mode enabled
May  7 11:51:12 OPNsense kernel: pid 23514 (eastpect), uid 0: exited on signal 11
May  7 11:51:12 OPNsense kernel: [HBSD SEGVGUARD] [eastpect (23514)] Suspension expired.
May  7 11:51:12 OPNsense kernel: -> pid: 23514 ppid: 60854 p_pax: 0xa50<SEGVGUARD,ASLR,NOSHLIBRANDOM,NODISALLOWMAP32BIT>
May  7 11:51:12 OPNsense kernel: 072.172948 [ 293] generic_netmap_unregister Emulated adapter for re0 deactivated
May  7 11:51:12 OPNsense kernel: 072.174418 [1033] generic_netmap_dtor       Emulated netmap adapter for re0 destroyed
May  7 11:51:26 OPNsense eastpect[15502]: nm0::re0: permanently promiscuous mode enabled
May  7 11:51:26 OPNsense kernel: 086.361862 [1127] generic_netmap_attach     Emulated adapter for re0 created (prev was 0)
May  7 11:51:26 OPNsense kernel: 086.361912 [1033] generic_netmap_dtor       Emulated netmap adapter for re0 destroyed
May  7 11:51:26 OPNsense kernel: 086.379070 [1127] generic_netmap_attach     Emulated adapter for re0 created (prev was 0)
May  7 11:51:26 OPNsense kernel: 086.379521 [ 318] generic_netmap_register   Emulated adapter for re0 activated
May  7 11:51:26 OPNsense eastpect[15502]: nm1::re0^: permanently promiscuous mode enabled

I have the same problem after a reboot this morning. Everything seems to work well and the log files are correctly written but I cannot see anything in the GUI.

I have a complete image with swap space. From what I can see from console before the reboot I can say it's a kernel error.

I have this problem since updated to 20.1. Everytime I restart the provider's router or disconnect the ethernet cable from the wan port of the opnsense box the system crashes and reboots. I tried to set 'prevent interface removal' without any success. Any suggestion?

Riccardo

I recently upgraded my system to 20.1 and everything went well for a while. But after a reboot my USB 4G dongle didn't come up correctly and I had to remove and recreate it. After this I noticed that Inside datas are switched between WAN1 (my nic with PPPoE) and WAN2 (the USB dongle). Under traffic everything goes as it should with connections showed correctly on WAN1 but under Insight datas are wrong. I tried to restart the box with WAN1 only and datas are displayed correctly but after I add WAN2 interface everything goes back to the wrong situation.

Riccardo

Thanks Franco,

I just updated to 19.7.4 and everything is working well. Will I have problems if I use the command you suggested?

EDIT:
Sorry, I didn't notice that it was related only to pkg package. Just did it without problems.

Riccardo

May be this is the problem...

pkg query %R pkg output:
FreeBSD

pkg query %v pkg output:
1.11.1

I had to to change package source to install a slightly different version of collectd (I need the mqtt part). May be i modified something else...
Is there a way to correct this?

Riccardo

I tried the command:
pkg install -yf opnsense
and this is the output:

Code Select Expand


Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        opnsense: 19.7.3 -> 19.7.4

Number of packages to be upgraded: 1

4 MiB to be downloaded.
[1/1] Fetching opnsense-19.7.4.txz: 100%    4 MiB   4.4MB/s    00:01
Checking integrity... done (0 conflicting)
[1/1] Upgrading opnsense from 19.7.3 to 19.7.4...
[1/1] Extracting opnsense-19.7.4: 100%
Stopping configd...done
Resetting root shell
Updating /etc/shells
Unhooking from /etc/rc
Unhooking from /etc/rc.shutdown
Updating /etc/shells
Registering root shell
Hooking into /etc/rc
Hooking into /etc/rc.shutdown
Starting configd.
Keep version OPNsense\Monit\Monit (1.0.8)
Keep version OPNsense\Firewall\Alias (1.0.0)
Keep version OPNsense\OpenVPN\Export (0.0.1)
Keep version OPNsense\CaptivePortal\CaptivePortal (1.0.0)
Keep version OPNsense\Cron\Cron (1.0.1)
Keep version OPNsense\Backup\NextcloudSettings (1.0.0)
Keep version OPNsense\TrafficShaper\TrafficShaper (1.0.3)
Keep version OPNsense\Syslog\Syslog (1.0.0)
Keep version OPNsense\IDS\IDS (1.0.3)
Keep version OPNsense\Proxy\Proxy (1.0.3)
Migrated OPNsense\Diagnostics\Netflow from 1.0.0 to 1.0.1
Keep version OPNsense\Routes\Route (1.0.0)
Keep version OPNsense\Netdata\General (0.0.1)
Keep version OPNsense\Bind\Dnsbl (1.0.5)
Keep version OPNsense\Bind\General (1.0.5)
Keep version OPNsense\Bind\Domain (1.0.0)
Keep version OPNsense\Bind\Record (1.0.0)
Keep version OPNsense\Bind\Acl (1.0.0)
Keep version OPNsense\Ntopng\General (0.0.1)
Keep version OPNsense\Redis\Redis (0.0.0)
Writing firmware setting...done.
Writing trust files...done.
Configuring login behaviour...done.
Configuring system logging...done.
Message from opnsense-19.7.4:

Roar!


I checked and configd is stopped.

Riccardo

It's not a problem to update to 19.7.4 but the last time I updated I had to force switch off because after I started the update I lost access to ssh and web GUI and I didn't have a way to check the update status. This happened only when I updated from 19.7.2 to .3, not before.

I'll try the first command and I'll let you know the output.

Riccardo

What will be installed with this command? I'm already on 19.7.3 and I prefer not to mess my installation that is working good...

Riccardo

After the upgrade to 19.7 I have the following problem: when i start an update or install or remove a plugin everything goes well until configd is stopped. Then it never restarts. I cannot see the logs and, in case of updates, I don't konw if everything is installed correctly or not. Any suggestion?