Closed burntoc closed 4 years ago
Thanks for the report.
This issue seems to be rooted in the fact that at line 491 of pfSense there is a call to phpsession_begin()
which fails because phpsessionmanager.inc
from pfSense has not been loaded.
What's curious here is that pfSense code uses an @
prefix before the phpsession_begin()
call which should silence the error-condition - digging even further shows that pfSense does something unusual with the error_reporting
setting here
My expectation is that this can be resolved by making sure phpsessionmanager.inc
gets loaded before FauxAPI attempts to call the pfSense write_config
function
I'll mark this up as a bug until I have time to investigate and resolve
Thanks for taking a look! I'll be happy to test whenever it's appropriate.
I feel like it's unlikely they'd address it on their end at this time, but I wanted to provide an update. The calls have been mostly failing, rather than mostly succeeding. For some reason they do on occasion work, which I suppose has to do with the execution order happening to fire right as you suspect. But I will say this - it could be luck, but I upgraded to the final RC this morning and 7 or 8 attempts have worked so far. Even for the 1 that failed I didn't get the crash detection notification on my dash as I had before. Maybe even that 1 failure had something else going on.
Just confirming that it's still a problem with the latest RC. I didn't expect it had solved it, but I hoped it had.
Closing this issue two ways
/etc/inc/phpsessionmanager.inc
in the current development version
I'd posted on r/pfSense first because I'm afraid I'll have to have my hand held if I need to troubleshoot this further - but I'm happy to try. They pointed me here. I installed FauxAPI on my box to use a custom component for Home Assistant to toggle pfSense rules . Sometimes toggling the switch in Hassio works, but many times it doesn't and when I visit pfSense I see this:
If I go to that .inc file referenced it looks like 491 is just a bit of code checking to see if the call is made by admin or another user. In any case, I'm wondering if maybe the issue is FauxAPI tripping up on the RC version of pfSense 2.4.5 I'm running or something in the custom components, which haven't been updated in about a year.
I'd appreciate any help getting to the bottom of this so the rule toggles will work all the time.