[RESOLVED] 14th april nanobsd issues

[xbipin]

upgraded to 14th april nanobsd snapshot and on reboot, i get the below in console and system is unuseable

Creating symlinks......done.
Launching the init system... done.
Initializing............................
Fatal error: Class 'PEAR' not found in /usr/local/captiveportal/radius_accountin
g.inc on line 50
Starting CRON... done.

Fatal error: Class 'PEAR' not found in /usr/local/captiveportal/radius_accountin
g.inc on line 50
Executing rc.d items...
 Starting /usr/local/etc/rc.d/*.sh...done.
Bootup complete

Warning: shmop_open(): unable to attach or create shared memory segment in /etc/
inc/util.inc on line 167

Warning: shmop_read(): no shared memory segment with an id of [0] in /etc/inc/ut
il.inc on line 168

Warning: shmop_close(): no shared memory segment with an id of [0] in /etc/inc/u
til.inc on line 175

[TuxTiger]

Confirmed the same problem….with pfSense-2.0-BETA1-1g-20100414-1518-nanobsd-upgrade.img.gz

I got the box running again by reverting to default settings using serial port, upload snapshot 20100413, retore settings...

[eri--]

Should be ok on latest snaps.

[Clouseau]

@TuxTiger:

Confirmed the same problem….with pfSense-2.0-BETA1-1g-20100414-1518-nanobsd-upgrade.img.gz

I got the box running again by reverting to default settings using serial port, upload snapshot 20100413, retore settings...

Confirm this error- I got it back "alive" just giving manually LAN ip address via console and after that a reboot.

[xbipin]

solved on the 18th april snapshot but i still see these in the system log

Apr 18 13:33:18 	php: : The command 'route add -host 195.229.252.33' returned exit code '1', the output was 'route: writing to routing socket: Invalid argument add host 195.229.252.33: Invalid argument'
Apr 18 13:33:18 	php: : The command 'route add -host 195.229.252.33' returned exit code '1', the output was 'route: writing to routing socket: Invalid argument add host 195.229.252.33: Invalid argument'
Apr 18 13:34:06 	php: : The command '/sbin/sysctl net.inet.flowtable.enable=0' returned exit code '1', the output was 'sysctl: unknown oid 'net.inet.flowtable.enable''