Two Error Messages
-
I think its safe to ignore.. I've seen it sometimes, but never seemed to affect any functionality..
As far as I can tell you're correct it doesn't seem to impact any systems. Having said that, I never had this issue with the last 2.3.4 final release nor any of these other problems found here: https://forum.pfsense.org/index.php?topic=138019.0 I would really like someone from the pfSense team to review those issues and perhaps offer some insight as to how to resolve them.
As of this writing there a lot of Lookly Lues but no feedback about next steps . . .
Given how many threads have already been created for the 2.4.0 branch there's something wrong.
-
I've been running 2.4 since it's first inception, through all the beta stages and RCs, so have a lot of other people.
I can count on one hand the number of problems my system has had that were 'notable', only one was a showstopper and that was resolved within hours.
99% of the issues are not down to pfSense per say, but the jump to FreeBSD 11.* Even Microsoft and Apple have issues you know.
The particular issue you are noticing there I have only seen when I force a pfBlocker update when the system is busy doing something else, it settles and sorts itself out and carries on, nothing to worry about.
Perhaps they need to set the log levels to a lower level so a lot of these junk warnings are not shown, and there are several.
-
@marjohn56:
I've been running 2.4 since it's first inception, through all the beta stages and RCs, so have a lot of other people.
I can count on one hand the number of problems my system has had that were 'notable', only one was a showstopper and that was resolved within hours.
99% of the issues are not down to pfSense per say, but the jump to FreeBSD 11.* Even Microsoft and Apple have issues you know.
The particular issue you are noticing there I have only seen when I force a pfBlocker update when the system is busy doing something else, it settles and sorts itself out and carries on, nothing to worry about.
Perhaps they need to set the log levels to a lower level so a lot of these junk warnings are not shown, and there are several.
At the moment it's not a show stopper for me. Just not used to seeing alert messages from the system that don't seem to correlate to how the system is running. As noted this was never seen in the 2.3.4 final build - but your thoughts this could be related to FreeBSD 1.1 may be spot on.
Hopefully more people start to see this and the pfsense team can resolve it in the next RC builds.
-
just fyi, the times i have seen it was on 2.3.x , i don't think i have seen this particular message yet in 2.4 myself.. but maybe it happens more often than before.. time will tell..
-
Same problem here.
-
im getting the same problem, except my pfsense box will basically lock up, where i cant access HTTP sites, the web UI, SSH into it, and if i plug a keyboard and mouse into it there's no way for me to log into it, i just get a blank screen i can type into
-
Not the same problem then. Yours sounds like the 502 error.
-
I have updated ntopng, suricata and pfblocker (twice) and the error still exists.
I have noticed this error occurs after system comes online and for some reason the modem disconnects for a few seconds and then reconnects.
Did not have this error when I was testing the RC builds. Only difference is that I have installed ntopng
-
Made a little fix to retry the command when pf is apparently 'busy' processing commands from another program: https://github.com/pfsense/pfsense/pull/3857
It seems to be related to this issue reported on FreeBSD 10.4 where also a 'retry' is advised as the proper thing to do.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223093Still probably ignoring the 'messages' doesn't hurt, but the actions taken by code will now hopefully be a bit more 'clean' once the PR is pulled.
-
Made a little fix to retry the command when pf is apparently 'busy' processing commands from another program: https://github.com/pfsense/pfsense/pull/3857
It seems to be related to this issue reported on FreeBSD 10.4 where also a 'retry' is advised as the proper thing to do.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223093Still probably ignoring the 'messages' doesn't hurt, but the actions taken by code will now hopefully be a bit more 'clean' once the PR is pulled.
Great detective work there. I hope to see the fix soon.
-
This is the same problem I have. It basically bricks my firewall and the internet. When I wake up in the morning I will have like 140 notifications, the same ones listed above.
-
Since updating to 2.4.2 and updating the various applications this problem appears to be solved. Much thanks to all the developers who had a hand in this.
Now, lets get to the bottom of why my WiFi connection keeps getting dropped along with the 502 error!
-
Now, lets get to the bottom of […] the 502 error!
Do you run pfBlockerng? There appears to be an issue with it that causes the 502 error.
https://forum.pfsense.org/index.php?topic=137103.msg767259#msg767259
-
just fyi: pfBlockerNG 2.1.2_2 includes that patch.
-
@virgiliomi:
Now, lets get to the bottom of […] the 502 error!
Do you run pfBlockerng? There appears to be an issue with it that causes the 502 error.
https://forum.pfsense.org/index.php?topic=137103.msg767259#msg767259
Yes, I've been tracking that ongoing thread since it was created. Looking forward to root cause being identified and a fix issued.
-
