PHP Error in pfsense 2.4.5
-
It's just a PHP core function, that handles Sockets (basic Ethetnet transfer thing) that times out.
That's a 99,9 % "no Internet/Ethernet" chance.It could be as simple as (example, purely hypothetical) : unbound was started, pfSense is resolving locally because it is still downloading packages which can take time because the upgrade servers are saturated - unbound was being restarted in the back ground during a package install, the process that wanted to build the socket isn't aware of this .... and times out on a PHP max-execution-time (== 900 secs)
Most probably some rare race condition. Won't happen again. -
Ok, so basically no need to be worried :) Thanks for the confirmation.
-
Oh and by the way, I had the same exact error with a second pfsense box that I upgraded just now.
-
Similar config on both? Same packages? Something slightly obscure
I've upgraded countless boxes and never seen that.Steve
-
@stephenw10 said in PHP Error in pfsense 2.4.5:
Similar config on both? Same packages? Something slightly obscure
I've upgraded countless boxes and never seen that.Steve
Yes, very similar config on both, just more VLAN's on one of them. And yes, same packages for both. So not sure what's causing it.
-
What packages do you have installed?
-
-
Hmm, NUT maybe.... Can you disable that just as a test?
Steve
-
@stephenw10 said in PHP Error in pfsense 2.4.5:
Hmm, NUT maybe.... Can you disable that just as a test?
Steve
I can but how do I know if it solves the problem? I already marked the error messages as read as I thought I can ignore them altogether (in both boxes).
-
Oh, it only appeared during the upgrade? I thought you were saying it keeps re-appearing.
Then if it doesn't appear again it's unlikely to be a problem. Just watch for futher alerts for a while.
Steve
-
@stephenw10 said in PHP Error in pfsense 2.4.5:
Oh, it only appeared during the upgrade? I thought you were saying it keeps re-appearing.
Then if it doesn't appear again it's unlikely to be a problem. Just watch for futher alerts for a while.
Steve
Nope, it was a one-time occurrence. So yeah, I guess I can ignore for now. Thanks.
