Messages

Hi there

I had that very same errors over and over, and just went and reinstalled Package mongodb40. And the errors were gone... maybe helps with your issue.

BR

Think I got it:

Multiple-non-related: Bios stuff from above and then UPS-Power-Issues this afternoon.

So, there is a UPS, that is connected to a Syno-NAS (USB). This NAS provides Net-UPS-Infos to 2 other NAS - and the Opnsense! And it seems, that it was flapping somewhat around that time (effectively, at the time of reboot, a proper reboot). Found some respective log entries:

Code Select Expand

UPS ups@xxx.xxx.xxx.xxx:3493: forced shutdown in progress

Code Select Expand

Executing automatic power-fail shutdown

So, deactivated NUT for instance and will search on, if there is another cause... (UPS has oodles of runtime, and even if, the device is not exactely business critical)...

I'll keep you posted if...

Had it again, this morning at around 3.45ish am. And first thing i did was a complete reinstall, did not take that long and was up and running shortly after.

So, this afternoon I had to move that device phisicaly in another rack. Did a proper shutdown, moved it, the usual stuff, power on - same thing as in screenshot.
As I had time, I tried to do a debug, as I did not think, that either the hardware nor the software (OPNs) as such are the trigger.

Checked the CL, there was a Bios-Update somewhat recently. So, checked the Bios. WatchDog was active, so I de-activated. Booted and it ran - for almost 1 and a half minutes, got the console pluged and saw, that it was a seemingly somewhat proper shutdown (like no sudden poweroff).

So, back to bios, checked with a TK-Wiki-Article: PCIe AER Support was enabled - as this might lead to a problem, I disabled it.

Am online now for an hour-ish ...

Keeping an eye on this and will go now for the logs.

Hi

Just to let you/someone know: had the strangest issue in update from 22.1.7(_1?) to 22.1.8_1 (current as of this morning).
Saved config (ful), did the update, updater going into reboot;
In boot process, this showed for an extended period of time on the console (see attachment, don't know how to insert image here, darn complicated - UX... whaaa).

Some pings to FW-LAN interface and WAN (googles DNS) went through, without a change on display of attached screenshot.
Then, without any further ado, no warning, no message or whatsoever, the system turns itself completely off.
Turning on the sytem again manualy, same thing (boot, attached screenshot, some pings, off)
Again, over and over. Did the whole thing maybe 10 times, had the IPMI-Function in suspect for the "poweroff". No, i did not connect IPMI to WAN or any such rubbish...

So, did a download of 22.1.2, install, update, config-restore - and am up and running again.
Not had something like that the past times...

Is this a sign of faulty drive or alike? because, SMART says, that the disks seem fine... (SSD)...?

br. D

I'm using pretty much the same board (A1SAi-2750F ), with a stock Supermicro chassis, 2x SSD (ZFS-Raid) and 32GB of RAM (MultiGW-LB, some shaped-VLANs VPN, Proxy, captive, etc.)... since 2015.

Recently - this morning in fact, I had to reinstall after a successful Bios-Update (yes, there is one dating from 2019 with spectre and meltdown - did not see this, as I thought: there won't be any new bios till the end of things). But update worked, booting afterwards did not  (don't know for shure what it was) - reinstall was easy, restore from backup-config simple...

Even got a new IPMI-Firmware with a HTML-KVM... also this morning... and got a serial for the inband-bios-update (if anyone is interested on unlocking the IPMI-BIOS-Update-feature, PM).

It's a sturdy little board with loads of reserve in power, has not let me down since 2015.

Thanks Fabian

Don't know what did not work yesterday, but cron ran this morning and did a backup to nextcloud - so: works as it should. Will keep a lazy eye on it and let it fill up the 30TB store after ;).

BR
Simu

Hi

Got the backup to nextcloud working - but do have a minor question (noobish) concerning the related cron-job:
Is there a parameter needed for cron? If yes: which one(s)? If no: howto debug (as i entered no parameter, enabled and applied, but alas, no regular job is running resp. it only works manually (via Backup => Test/Save))?

BR
Simu

Hi

Traffic reporting is a useful meaning to see first hand, if f.ex. WAN is used and to what grade.
In my case - I'm using 2 WAN-Lines, separate providers on respective interfaces - this reporting feature is semi-useful to me - see the screenshot:

The two WAN lines have similar colors, both colors in the dropdown do not match f.ex. the color in the bps-stat.
The two WAN lines visible in Inbps: do they cover the 3rd graphline (i.eg. in my case must be Swisscomdsl..)?
The out bps only shows lan and overlays all other, correct.

I know, that i can select the desired interface - but somehow i'd wish i'd see lines instaed of areas.

But i might use it wrong - how do you use this? Is it useful to you?

Thanks for some input if you like to respond
kind regards
just a dumb user ;)

During Reporting Traffic, pop-up appears :

An API exeption occured:

Code Select Expand

Error at /usr/local/opnsense/mvc/app/controllers/OPNsense/Diagnostics/Api/TrafficController.php:74 - Invalid argument supplied for foreach() (errno=2)


OPNsense 20.7.7_1-amd64
FreeBSD 12.1-RELEASE-p11-HBSD
LibreSSL 3.1.5

see screenshot.

BR

Upgrade from 18.7 to 19.1.1 on homebrew C2758 supermicro with some ssds was successful. A fortunate nobrainer to me.

Many thanks to all that made this possible

Hi there

Just had the exact same issue, and by the force of noob deleted the pidfile - service came up again and all is well.
Allthough you wrote in 2018, hope, you some luck in the meantime.

br
s