Project

General

Profile

Actions
Copy link

Bug #12135

closed

firewall_nat.php, Line: 40, Message: require_once(): Failed opening required 'firewall_nat.inc'

Added by Stefan Bauer almost 3 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Web Interface
Target version:
-
Start date:
07/16/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

Hi,

we see on several pfsense systems following error message after clicking Firewall -> NAT.

PHP ERROR: Type: 64, File: /usr/local/www/firewall_nat.php, Line: 40, Message: require_once(): Failed opening required 'firewall_nat.inc' (include_path='.:/etc/inc:/etc/inc/web:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear:/usr/local/share/openssl_x509_crl/')

2.5.2-RELEASE (amd64)
built on Fri Jul 02 15:33:00 EDT 2021
FreeBSD 12.2-STABLE

Is this a known problem?

Actions
Copy link
 #1

Updated by Renato Botelho almost 3 years ago

  • Status changed from New to Rejected
  • Priority changed from High to Normal

It seems include_path is missing needed directories. I've checked a 2.5.2 installation and include_path content is:

include_path = ".:/etc/inc:/usr/local/pfSense/include/www:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear:/usr/local/share/openssl_x509_crl/"

I also checked and the commit that added needed directory is there since April:

commit b73947ee74
Author: Steve Beaver <sbeaver@netgate.com>
Date:   Fri Apr 16 09:36:54 2021

    Moved web include files from /etc/inc/web to /usr/local/pfSense/include/www

Considering the fact that there are thousands of 2.5.2 instances running out there and issue is not reproducible It's better to discuss on forum and try to collect more data about it.

Actions
Copy link
 #2

Updated by Stefan Bauer almost 3 years ago

It seems to happen if you update from 2.5.1 to 2.5.2.
I maintain several pfsense systems and some of them have the same problem after update.

How does one fix this manually?

Actions
Copy link
 #3

Updated by Jim Pingle almost 3 years ago

It isn't a general issue with upgrading as tens of thousands of users have upgraded and nobody else is hitting this that we know of except for you. It must be something specific to your setup.

This site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .

See Reporting Issues with pfSense Software for more information.

Actions
Copy link

Also available in: Atom PDF