flock() error after upgrading
-
When you reset the config to factory defaults it's exactly that; the config file is replaced by the default config. So, yes, potentially there could be many things left behind.
If you run at the command line:
top -HaSPcan you see what's being run once a minute to trigger this? -
just for testing i have concluded nothing i have configured or installed is causing this
just gone through a fresh hard drive in my hardware, pfsense 2.6ce installed, upgraded to 22.01, upgrade to 22.05 upgrade to 23.01rc and error is there
another fresh hard drive, 2.6ce installed, upgrade to 22.01 then straight to 23.01rc and the error is there
Only things configured was wan connection and basic default lan
-
Am also kinda a novice when it comes to Linux etc, alway trying to learn, I am not sure what I am looking for in the output of that command
Was a lot of things flashing up constantly but didn’t see any refresh to anything in the error output
-
Ah, interesting. So this appears to be something hardware or network related.
What are you running this on? How is the network setup that it's connected to?
-
Running on a Lenovo m720q with a intel 9500t cpu, 16 gig of ram, network card is intel x710-t2l
Port one is dhcp setup to cable modem in modem mode 2.5gbs link
Port 2 is the basic lan setup you go through when installing pfsense 10gb link
Not noticed any issue with this hardware on 22.05
Maybe some form of sensor not working right in the new kernel?
-
@maff said in flock() error after upgrading:
Linux
FreeBSD in this case
top shows running processes.Question: does it happen if you're NOT displaying the dashboard? Logged out of the web GUI?
Is the config file on disk growing in size or changing time stamps? (/conf/config.xml)
-
Mmm, that's a good question. Something that could be configured to update once a minute like that might be a dashboard widget.
-
Does anyone seeing this have some kind of off-firewall monitoring system that probes the firewall once per minute? Maybe some kind of third party integration / tacked on "API" that is leveraging xmlrpc.php?
Nothing in the base system queries that file except for HA sync, and HA sync would not be triggered that often.
-
@jimp I use the home assistant integration and uptime kuma. Is that causing it?
-
How is that querying? SNMP? Some plugin code?
-
Yeah, it almost certainly is that. See: https://forum.netgate.com/post/1081590
-
@stephenw10 https://github.com/travisghansen/hass-pfsense
-
Drop to a shell and run
tail -F /var/log/nginx.logand watch a bit and see what is hittingxmlrpc.phpand trace back from there. You could also grep through the older log entries to see.You can also look at / search the log from the GUI (Status > System Logs, System tab, GUI Service sub-tab), but doing so can be tricky since accessing the GUI will add more entries to the log potentially pushing the older entries off.
-
@blathierry said in flock() error after upgrading:
@jimp I use the home assistant integration and uptime kuma. Is that causing it?
Interesting! I use the HA Integration also!
But from my understanding the integration polls the status every 30 seconds. The error seems to occur more often than every 30 seconds. -
I note that code saw updates as recently as today. Are you running the current version?
-
Anyone hitting this, try installing the System Patches package and then create an entry for
053f60e56d09ba711af245c7f0ce6a06673ccc89to apply the fix.Or apply this diff/change by hand:
diff --git a/src/etc/inc/util.inc b/src/etc/inc/util.inc index f838f6b540..2636fb4aec 100644 --- a/src/etc/inc/util.inc +++ b/src/etc/inc/util.inc @@ -169,12 +169,13 @@ function try_lock($lock, $timeout = 5) { } /* unlock configuration file */ -function unlock($cfglckkey = 0) { - if (!is_null($cfglckkey)) { - @flock($cfglckkey, LOCK_UN); - @fclose($cfglckkey); - } - return; +function unlock($cfglckkey = 0) +{ + if (!is_resource($cfglckkey)) + return; + + flock($cfglckkey, LOCK_UN); + fclose($cfglckkey); } /* unlock forcefully configuration file */ -
Thanks for looking further into this, needed a break from messing around, will test this later and I completely forgot about the home assistant project I was looking into, will test this soon as I can
-
@stephenw10 Yeah, newest version still does it sadly. I updated both of them. I disabled the home assistant integration for now.. I hope the maintainer will fix it soon, it's very unexpected.
-
Try the diff above. What the HA integration is doing should work with that. They are just hitting a code path that pfSense never normally does. It isn't necessarily wrong, something that needs updating.
-
I spun up a Home Assistant VM, setup HACS and added the pfSense integration. Pointed it at a 23.01 install and immediately saw the errors in question. Applied the lock patch above and haven't seen a single error since.
Looks good to me. It should be in the next build.
