Messages

what other reasons would samplicate be running besides netflow using it?

Stop being dramatic about it and start being pragmatic:

System: Configuration: Defaults: Components: select "NetFlow configuration" -> Reset.

There was also this a few weeks ago already:

https://github.com/opnsense/changelog/blob/ba90671071f1a0528774b9de4fd0e233b7a444dc/community/26.7/26.7.2#L25


Cheers,
Franco

i'm not being dramatic, i'm being factual. your solution results in the same boot loop. thanks for trying to help but it didn't help. for whatever reason the machine will not boot without having at least 1 interface chosen for netflow and the destination ports being localhost 2055 and 2056. maybe one day i'll just start over from scratch but right now i just don't have the time.

it's shocking to me that i'm the only one experiencing this samplicate issue. it's still pegging my cpu. my box literally runs 1 core at 99 to 100% 24/7. at times the temp hits 85C. this cpu is known for running hot so I haven't been too worried. i just find it interesting the bug that I am experiencing. the minute I try to stop the samplicate service I get a kernel panic and reboot loop. when I remove the WAN interface from netflow reporting and remove the 2 localhost destinations it goes into a boot loop and I can't figure out why. so, what I have is a machine that's constantly sending data to 127.0.0.1:2055 and :2056 with nothing capturing it. I just can't remove them or my machine goes into a boot loop and I can't figure out why because by the time I ssh into the box to troubleshoot it, it'll just reboot again.

the problem is that when I try to remove all interfaces opnsense gets stuck in a boot loop. it'll boot up and then just keep restarting itself. I don't know how to fix this. i don't want to do a fresh install because of the many firewall rules and all the other stuff I have configured would be a pain to have to redo. i wouldn't want to restore a backup in fear of it importing this wrong netflow logging issue.

do I need to re-enable it

No. You should not have any third party repos enabled unless you know exactly what you are doing. And expect major upgrades to fail and manual intervention to be necessary if you do use them.

E.g. Zenarmor or AdGuard Home need extra repos. The best advice then is to postpone the OPNsense upgrade until the third party repos are updated, too.

The FreeBSD repo should never be active.

i wonder why it was active to begin with. I never enabled it. It must have enabled itself after installing some addons i'm guessing? My only question is now that i'm upgraded, will whatever package that enabled that repo become stagnant without a repo to keep it updated. below are the only plugings i have installed.

Code Select Expand

os-acme-client (installed)    4.16_1    821KiB    3    OPNsense    ACME Client   
os-cpu-microcode-amd (installed)    1.1_1    872B    3    OPNsense    AMD CPU microcode updates   
os-git-backup (installed)    1.1_3    14.8KiB    2    OPNsense    Track config changes using git   
os-isc-dhcp (installed)    1.0_6    284KiB    2    OPNsense    ISC DHCPv4/v6 server   
os-nut (installed)    1.9_1    55.4KiB    3    OPNsense    Network UPS Tools   
os-realtek-re (installed)    1.0    409B    3    OPNsense    Realtek re(4) vendor driver   
os-theme-rebellion (installed)    1.9.5    5.23MiB    3    OPNsense    A suitably dark theme   
os-upnp (installed)

all is working after I disabled the FreeBSD repo but my question would be why was it enabled in the first place and do I need to re-enable it now that 26.7.1 is installed and working?

i edited /etc/pkg/FreeBSD.conf, that was the only file in /etc/pkg/, i disabled the repository. Went to the webgui and did another update. I was staring at this screen
https://pastebin.com/41hUyBL3
and the Updates tab in System:Firmware had a spinning circle progress bar. I let it do that for about 10 minutes. then I hit refresh in my browser. Now when i go to System Firmware Status, its completely blank.. I don't know what to do. Can someone help please?
so

Disable the FreeBSD repository/repositories. For this do the opposite of what you did to enable them. OPNsense never does this on its own.

Check /etc/pkg and /usr/local/etc/pkg/repos directories.

i never enabled them. i've only ever done what I could right through the web gui. it appears they were added when I choose to install some plugins maybe? I just asked google and it said I have to disable them through the command line.

can you explain what i need to do in order to upgrade please?

Trying to upgrade opnsense to 26.7 but it fails. Here's the pastebin link
Can someone help me finish the update?

this is crazy to me that not a single person responded to this. I am still dealing with samplicate pegging my cpu. I don't know what else to do

Code Select Expand

opnsense-revert -r 26.1.7 nut
pkg lock nut


this fixed my issue as well. THANKS!!! Interesting when trying to figure out why my NUT status was no longer working, Claude informed me that a UI bug has been around since 2021. Not sure if that's related or what but thanks for this temp fix anyway.

I am very new to opnsense.
Environment
OPNsense 26.1.4 (amd64)
Hardware: HP Pavilion tower, AMD A12-9800 CPU
NICs: igc0 (WAN), igc1 (LAN), re0 (DMZ)

Problem
samplicate is running at 100% CPU continuously. It was configured with two NetFlow destinations (127.0.0.1:2055 and 127.0.0.1:2056) but nothing is actually consuming data on those ports — sockstat confirms nothing is listening on 2056 and only samplicate itself is on 2055.

Reproduction steps
Any attempt to stop samplicate causes an instant silent reboot loop that requires restoring a config backup to recover. Attempts made:
— GUI: Clearing NetFlow destinations and hitting Apply
— CLI: service netflow stop
— CLI: kill <pid>
— CLI: ngctl shutdown ksocket_netflow_igc0: then ngctl shutdown netflow_igc0: then kill <pid>
All result in an immediate reboot loop. System log captures nothing before the reboot — the kernel appears to die before it can write to disk.

Diagnostics
— /var/crash/ is empty — no crash dumps generated
— dmesg shows no panic or fatal entries
— monit is not watching samplicate (monit summary shows only System and RootFs)
— samplicate is launched via daemon wrapper by /usr/local/etc/rc.d/netflow
— netflow stop uses kill -9 on samplicate then ngctl shutdown on netflow nodes
— UPS is healthy (CyberPower 1350VA, 100% charge, OL status)
— No os-netflow, os-insight, or os-ntopng plugins installed — NetFlow is OPNsense core

Current netflow.conf

netflow_interfaces="igc0"
netflow_egress_only="igc0"
netflow_version="9"
netflow_int_destination="127.0.0.1:2055"
netflow_destinations=" 127.0.0.1/2055  127.0.0.1/2056 "
netflow_active_timeout=1800
netflow_inactive_timeout=15
Question
Is this a known issue with netgraph + samplicate on this kernel version? Is there a safe way to disable NetFlow/samplicate without triggering a kernel panic? Is there a way to enable crash dumps to capture the panic for a proper bug report?

Any help appreciated. Happy to run additional diagnostics.