Project

General

Profile

Actions

Bug #4835

closed

Configuration changes are slow to save after upgrade

Added by Sean Pappalardo almost 9 years ago. Updated over 8 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
07/14/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.3
Affected Architecture:
amd64

Description

I have a HA setup (two physical machines with direct crossover connection for the SYNC interface) previously running the 4GB AMD64 nanoBSD variant of 2.1.5 from USB flash successfully. After upgrading to 2.2.3 using the auto-upgrade feature (doing the slave first, then the master,) saving any configuration changes (aliases, rules, etc.) takes a very long time (over a minute.) But applying them happens quickly though. This is the case even if I shut down the slave node. It also takes about 45 seconds to bring up the config history page on either unit.

Actions #1

Updated by Kill Bill almost 9 years ago

Duplicate of #4814

Actions #2

Updated by Chris Buechler almost 9 years ago

  • Status changed from New to Duplicate
Actions #3

Updated by Chris Buechler almost 9 years ago

this is probably much better with latest 2.2.4 @ https://snapshots.pfsense.org, would appreciate your feedback if you can upgrade one of the two.

Actions #4

Updated by Sean Pappalardo over 8 years ago

I finally got the chance to upgrade both boxes and the problem is not any better. It's so bad that XMLRPC sync fails from time to time (I presume due to timeout because of the slow Flash write.) Since I had to make a number of config changes, I set both boxes to permanent R/W, made the changes, then set them back to RO.

Actions #5

Updated by Sean Pappalardo over 8 years ago

No improvement in 2.2.5 either.

Actions #6

Updated by Sean Pappalardo over 8 years ago

In reading the linked dupe bug above and its references, am I correct in understanding that I will need to re-flash my media with 2.2.4 or later in order to get the fix?

Actions #7

Updated by Jim Pingle over 8 years ago

More likely you need a better/different CF card. See https://forum.pfsense.org/index.php?topic=96383.msg546892#msg546892

Actions #8

Updated by Kill Bill over 8 years ago

Nope. The correct understanding is that there will be no fix whatsoever for this. Run permanent RW, or get a full install.

Actions

Also available in: Atom PDF