Messages

it would've been nice to resolve this but alas I'm going another direction. I'm going to try an Omada Fusion 2.5G Gateway & Controller in One. I got a really good deal on a whole 2.5G kit. Includes the gateway, switch and an AP all for $250 plus I get (5) coupons for the same kit for $50 off so if I can sell them to my customers my kit will be free. It helps me cut down on power usage. Maybe I'll install opnsense in the future on different hardware and give it another shot.

UPDATE: turned out to be a hardware issue with the CPU. i finally was able to see a kernel panic crash dump and that's what the errors are pointing to. uncorrectable errors on cpu3. I guess it was always just coincidental about netflow.

isn't there any log files that are written to even during a kernel panic?

So that means it's set to capture. Not sure how else I can help you.

This will definitely kill the configuration if you confirm deletion... you can recheck with -g

# pluginctl -f OPNsense.Netflow


Cheers,
Franco

running that command and then killing samplicate results in the same reboot loop. is there any log files I can provide that would show why it goes into a reboot loop once that command is run?

Code Select Expand

{
    "@attributes": {
        "version": "1.0.1",
        "persisted_at": "1773874029.39",
        "description": "NetFlow configuration"
    },
    "capture": {
        "interfaces": "wan",
        "egress_only": "wan",
        "version": "v9",
        "targets": "127.0.0.1:2055,127.0.0.1:2056"
    },
    "collect": {
        "enable": "0"
    },
    "activeTimeout": "1800",
    "inactiveTimeout": "15"
}

A stuck template perhaps, but clearing the settings would disable it in that case.  There's no reason it wouldn't.  The stack trace at hand is also unknown, which could confirm the issue or point elsewhere.

What's in /etc/rc.conf.d/netflow ? Removing the file would also cause it not to start although in practice the reboot rebuilds the file so whatever the config mandates is going to steer the YES/No decision.


Cheers,
Franco

Code Select Expand

root@OPNsense:~ # cat /etc/rc.conf.d/netflow
#
# Automatic generated configuration for netflow.
# Do not edit this file manually.
#
netflow_enable="YES

"you have not reset it properly in the settings", I did exactly what you had informed me to do. Is there a way to improperly do what you instructed? I did exactly this, "System: Configuration: Defaults: Components: select "NetFlow configuration" -> Reset."

Should I this time perform the above set of instructions and also edit that file and change it to "No"?

A stuck template perhaps, but clearing the settings would disable it in that case.  There's no reason it wouldn't.  The stack trace at hand is also unknown, which could confirm the issue or point elsewhere.

What's in /etc/rc.conf.d/netflow ? Removing the file would also cause it not to start although in practice the reboot rebuilds the file so whatever the config mandates is going to steer the YES/No decision.


Cheers,
Franco

Code Select Expand

root@OPNsense:~ # cat /etc/rc.conf.d/netflow
#
# Automatic generated configuration for netflow.
# Do not edit this file manually.
#
netflow_enable="YES

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?