Reset States from GUI fails with error
Running pfsense version
2.4.4-RELEASE-p2 (amd64) built on Wed Dec 12 07:40:18 EST 2018 FreeBSD 11.2-RELEASE-p6
When I go via the GUI to Diagnostics/ States/ Reset States and select and run the command "Reset the firewall state table" I am seeing the following in the Status/ System Logs
nginx: 2019/04/05 08:39:45 [alert] 95187#100120: *223 writev() failed (13: Permission denied) while sending to client, client: 192.168.123.250, server: , request: "POST /diag_resetstate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.123.254", referrer: "http://192.168.123.254/diag_resetstate.php"
which suggests that it is a permissions issue. Rather than blindly meddle with permissions (I am not a geek) I wonder if anyone has come across this issue and whether there is a solution.
Firewall has been rebooted.
Grimson last edited by
Still to lazy to search the forums? This is the last time: https://forum.netgate.com/topic/136083/reset-states-in-2-4-4/4
I am sorry to have offended you - I appreciate that (apparently) repetitive questions from those who are relatively new to both pfsense (and Linux) must be a great irritation to the learned members of such a busy forum.
All “gurus” were beginners once ….
Grimson last edited by
pfSense offers great resources, there is the manual:
I suggest you read at least the book thoroughly.
Then there are the hangouts:
and if you can't find an answer in all of these use this before you post:
Thank you for such a constructive response.
I am aware, from my membership of various internet message boards/forums, that tolerance towards "newbies" and what may be considered basic or repetitive questions varies. Some boards (although apparently not this one) offer sections specifically devoted to the newcomer, thereby insulating the erudite from such irritations.
Fear not I hear you loud and clear and hope that others viewing this thread and considering posting to the firewall section (unless they have completed the requisite prior reading/viewing) will learn from my mistake and leave the gurus in peace.
Thanks again ...
Yes, that error is expected when you reset the states because it closes the state the GUI was using to talk to your browser.
Thanks for confirming that this is expected behaviour.
The background to my query was that I was configuring various rules/aliases and hit a problem whereby the firewall was still blocking traffic, notwithstanding what I considered to be the relevant rule had been deleted.
As part of my troubleshooting I had already reset the state with apparent no effect, although strangely a reboot did clear the issue. I then spotted the log error and in rushing to put 2+2 together came up with 5