Rule Web-Gui broken since 151

Hi,

updated IpFire to 151. Since Update it is not possible to edit the Rules. Missing things the NAT- and Destination-Settings in the Rule-Page:

How can i fix this? Help would be fine. Thanks.
Nick

1 Like

Hi Nick,

Did you reset your browser cache? - If so, you should give the installation a new chance I guess. :wink:

Remember to save your settings.

Wayne

Hi Nick,

first, welcome to the IPFire community. :slight_smile:

I unfortunately cannot reproduce your issue on several systems updated to Core Update 151.
Could you please provide more details (such as a Fireinfo profile) and post error log messages in EDIT: /var/log/httpd/error_logs here, if any?

Thanks, and best regards,
Peter Müller

Hi Peter,

thanks for your welcome message. I’m sorry but what is the “Fireinfo Profile” and should this Infirmation posted here?

Best Regards,
Nick

Hi,

please refer to the documentation for those information. :slight_smile:

Thanks, and best regards,
Peter Müller

Hi,

thanks. My Fireinfo Profile.

IpFire was running 143 before updating/upgrading to 151. On the mainpage was the information for an update to 150 (not 151!). Updated with pakfire updater. After reboot ipfire shows 151.

/var/httpd/error_logs There is no httpd-Folder under var-Folder. :confused:.

Best Regards,
Nick

Hi Wayne,

yes, reseted browser cache but this didin’t solved it. the same issue as before.

Thanks. Best Regards,
Nick

Nick, the dir is /var/log/httpd/

1 Like

Should i look for something special in the log? This from today is more than 200 lines. there are e.g.

[Wed Oct 28 10:18:33.426957 2020] [mpm_event:notice] [pid 1237:tid 3083232256] AH00489: Apache/2.4.46 (Unix) OpenSSL/1.1.1h configured -- resuming normal operations
[Wed Oct 28 10:18:33.426971 2020] [core:notice] [pid 1237:tid 3083232256] AH00094: Command line: '/usr/sbin/httpd'
libloc: loc_database_free: Could not unmap network nodes section: Invalid argument
Could not read database: /var/lib/location//database.db

Could not read database: /var/lib/location//database.db
libloc: loc_database_free: Could not unmap network nodes section: Invalid argument

Or should i post the whole log here?

That remembers me to the memory leak error, I’m researching at the moment.
The perl interface to libloc does calls the init() function for every operation ( find country code, … ).
In case of errors the loc_database_free function is called, which throws this error.

I’ll try to write a topic in bugzilla this evening.

2 Likes

Hrmpf, missed the /log/ snippet. :expressionless: Thanks for catching this.

Hi all,

meanwhile, @bbitsch filed a bug report regarding this issue (thanks):

Looks like it affects i686 systems only (I have not noticed it on x86_64 machines, yet), but this needs to be fixed anyway.

Thanks, and best regards,
Peter Müller

1 Like

hi,

i have the same problem on a raspberry pi 3b

1 Like

Good Morning,

effects this Problem only the Gui of the RuleEditor or also the Function of the Firewall itself too?

Have nice Day,
Nick

Hi Nick,

to my understanding, this affects the GUI only, the firewall engine itself works flawlessly.

Thanks, and best regards,
Peter Müller

A broken WUI affects the editing of the internal settings.
The system itself is configured by reading these settings ( which can not altered because of the broken web page ) and writing the configuration of the system modules.
In case of the firewall this means setting the iptables rules. Most of them are independant from the WUI. The internal settings of IPFire usually can be altered by selecting ‘save’ only, what isn’t possible when the web page is broken.

Do you have an ETA on when it will be repaired?

Bug found few hours ago on only one platform, but not on the main one (x86_64).
I think that “good solution” will be preferred to “fast solution”, then… evaluating an ETA is still less important than make a good assessment of the issue and the options for solving.

1 Like

Is there a way to configure the rules without the web GUI?

We should know, why the web user interface is broken for some(!) installations.
All workarounds aren’t really effective.