Slow Save
-
Hello!
I recently installed a fresh version of 2.5.2 CE. Everything seems to be working, the only issue that I am having is that saves take a really long time.No, I do not have auto backup enabled.
I also just tried enabling ram disks for /tmp and /var but that did not improve speeds either.
Any ideas?
-
What are you running on?
Could just be something very slow like maybe a HD that is spinning down/going to standby.
Steve
-
It’s a VM running on RAID0 with 8 drives. Before installing 2.5.2, I had 2.4.5 installed on the same host and never had slow saves like this. The other guests on the same host aren’t slow when saving things.
-
Mmm, not that then.
Check the logs.
Open
top -aSH
in the CLI and check what's waiting when you hit save.Steve
-
@stephenw10 Im not sure what I am looking for here. When I run:
top -aSH
a large list of processes are shown and are shifting about, whether or not I click the save button...
-
Ok, and there is not one process that jumps to the top using a lot of CPU until the save completes?
Is it any save that triggers it?
Does it stall on save and on apply if you add a firewall rule for example?
Does Status > Filter Reload complete in the expected time?
Steve
-
Ok, and there is not one process that jumps to the top using a lot of CPU until the save completes?
I might be able to associate the following process to a save. It seems to jump to the top when I click save, and fall off after the save is complete
php-fpm: pool nginx (php-fpm)
Is it any save that triggers it?
Yes, any save takes an extended period of time.
Does it stall on save and on apply if you add a firewall rule for example?
It only stalls on save, applys work in the expected time frame
Does Status > Filter Reload complete in the expected time?
Filter reload seems to complete in a reasonable time frame (a second or two).
-
Test this :
Backup your config.
Then "Reset to factory defaults".
Assign interfaces, log in and make WAN work.
Do not change anything else - do not import your backup.
Now, edit something that took time to save ; do you see the same delay ?To get back to where you were before : import your config.
-
Test this :
Backup your config.
Then "Reset to factory defaults".
Assign interfaces, log in and make WAN work.
Do not change anything else - do not import your backup.
Now, edit something that took time to save ; do you see the same delay ?To get back to where you were before : import your config.
This did the trick. Thank you!
-
Hmm, so, fixed but no real idea of what was causing it?
-
@stephenw10
No idea whatsoever. Honestly, ever since switching to 2.5.2, pfSense has been anything but reliable. I’ve debated multiple times going back to 2.4.5 -
No idea whatsoever
The difference between your and my pfSense is : the settings.
The code is the same ;)2.5.2, pfSense has been anything but reliable.
Strange. 2.5.2 is rock solid for me.
Another test :
Use another VM host.
Example : I've one running under HyperV, the one Windows 10 offers you for free : its perfect.
Or, even better (better as "one issue less to resolve" : don't use a VM. -
Mmm, what hypervisor are you using?
2.5.0 and 2.5.1 certainly had issues but 2.5.2 has been pretty good. Whatever you were hitting here though seems likely to be something local to you. I've not seen any other reports of it.
Steve
-
I am running esxi 6.7.0 Update 3 (Build 15160138). At first I had run an update, at that time no firewall rule that I would create or update would ever take effect. Applying my changes and rebooting didn’t seem to help anything. I took a backup of my settings, ran a fresh install of 2.5.2 and immediately restored my backup. That’s when I was stuck with the slow saves.
-
-
Mmm, this has been resolved by reinstalling as understand it.
Loads of people running in ESXi so nothing unsual there.... hmm.
-
@stephenw10
Yes resolved.