URGENT: pfsense eats his /etc/inc/system.inc

[rudivd]

Hi all,

I'm running 2.1.3 on a soekris 6501 (boot from usb) where I had no problems for a month or so.
Right now, I see pfsense corrupting the /etc/inc/system.inc on a regular basis. it seems to be
connected to the restarting packages, where either it tries to stop postfix:

Jun 24 19:12:22 pfsense postfix/postfix-script[79176]: fatal: the Postfix mail system is not running
Jun 24 19:12:22 pfsense php: rc.start_packages: The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '1', the output was ''
Jun 24 19:12:22 pfsense php: rc.start_packages: sync_package_postfix called with via_rpc=no
Jun 24 19:12:22 pfsense php: rc.start_packages: The command '/sbin/mount -u -w -o sync,noatime /cf' returned exit code '1', the output was 'mount: /dev/ufs/cf : Device busy'
Jun 24 19:12:23 pfsense php: rc.start_packages: sync_package_postfix called with via_rpc=no

or someway it tries to restart unbound:

Jun 24 19:12:53 pfsense php: rc.start_packages: Stopping postfix
Jun 24 19:12:53 pfsense postfix/postfix-script[45581]: fatal: the Postfix mail system is not running
Jun 24 19:12:53 pfsense php: rc.start_packages: The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '1', the output was ''
Jun 24 19:13:00 pfsense php: servicewatchdog_cron.php: Service Watchdog detected service unbound stopped. Restarting unbound (Unbound is a validating, recursive, and caching DN…)
Jun 24 19:13:06 pfsense php: servicewatchdog_cron.php: Message sent to xxx@xxx OK
Jun 24 19:13:09 pfsense php: config.inc: The command '/usr/pbi/unbound-i386/sbin/unbound-control start' returned exit code '1', the output was '[1403629989] unbound-control[91750:0] fatal error: could not exec unbound: No such file or directory'
Jun 24 19:13:14 pfsense Unbound_Alarm[96496]: Unbound has exited.
Jun 24 19:13:14 pfsense Unbound_Alarm[96897]: Attempting restart…
Jun 24 19:13:18 pfsense Unbound_Alarm[1080]: Unbound has resumed.

which then results in a next time :

Jun 24 20:17:15 pfsense postfix/postfix-script[31549]: fatal: the Postfix mail system is not running
Jun 24 20:17:16 pfsense php: rc.start_packages: The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '1', the output was ''
Jun 24 20:17:18 pfsense php: rc.start_packages: The command '/sbin/mount -u -w -o sync,noatime /cf' returned exit code '1', the output was 'mount: /dev/ufs/cf : Device busy'
Jun 24 20:17:19 pfsense php: rc.start_packages: The command '/usr/local/etc/rc.d/unbound.sh stop' returned exit code '255', the output was ' Parse error: syntax error, unexpected $end, expecting T_VARIABLE or T_END_HEREDOC or T_DOLLAR_OPEN_CURLY_BRACES or T_CURLY_OPEN in /etc/inc/system.inc on line 948'
Jun 24 20:17:19 pfsense php: rc.start_packages: The command '/usr/local/etc/rc.d/unbound.sh stop' returned exit code '255', the output was ' Parse error: syntax error, unexpected $end, expecting T_VARIABLE or T_END_HEREDOC or T_DOLLAR_OPEN_CURLY_BRACES or T_CURLY_OPEN in /etc/inc/system.inc on line 948'

and if you look in the filesystem the first (19:13) action has corrupted /etc/inc/system.inc.
Needless to say the GUI does not work anymore after this.
When I manually copy the system.inc things seem to be ok again.

I have installed the following packages:

mailreport      Network Management    2.0.12
Postfix Forwarder        Services      2.10.2 pkg v.2.3.7
Service Watchdog        Services      1.6 
Unbound  Services      1.4.22_2

Have any of you encountered such a problem ??
This is really weird, as it started occurring seemingly "out of the blue"

Rudi

[jimp]

Unless one of those packages is severely broken, that looks more like a failing/corrupted filesystem. Replace the USB media.

[rudivd]

@jimp,

Thanks for your reply. A broken USB media was also the thing I was expecting, but a brand-new
(brand, kingston) USB key did the same thing with the same config, after restart_packages was
called. Now I removed postfix and things look promising (fingers crossed) for 2 days now.

Rudi

[jimp]

Probably is that old option in postfix that I mentioned in the other linked thread. It tries to change system.inc in a very dangerous way. The package maintainer will need to fix it, so you'll want to make a post in the Packages board to get their attention.