2.2 final to 2.2.1 devlopment php error
-
i get one error when i upgrade from 2.2 to 2.2.1 in serial console on nanobsd alix
Welcome to pfSense 2.2.1-DEVELOPMENT ... Creating symlinks......ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/loc al/lib a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout done. >>> Under 512 megabytes of ram detected. Not enabling APC. External config loader 1.0 is now starting... Launching the init system... Warning: PHP Startup: Suhosin was compiled without session support, which is pro bably not what you want. All session related features will not be available, e.g . session encryption. If session support is really not needed, recompile Suhosin with -DSUHOSIN_NO_SESSION_WARNING=1 to suppress this warning. in Unknown on lin e 0 done. Initializing...................... done. Starting device manager (devd)...done. Loading configuration......done.Removing package... Removing Cron components... Configuration... done. done. Beginning package installation for Cron . 100% Installing Cron and its dependencies.cron: /var/cron: No such file or directory cron: /var/cron: created cron: tabs: No such file or directory cron: tabs: created Starting syslog...done. Starting CRON... done. Starting package Cron...done. pfSense (nanobsd) 2.2.1-DEVELOPMENT i386 Tue Feb 17 22:32:24 CST 2015 Bootup complete FreeBSD/i386 (firewall) (ttyu0) Warning: PHP Startup: Suhosin was compiled without session support, which is pro bably not what you want. All session related features will not be available, e.g . session encryption. If session support is really not needed, recompile Suhosin with -DSUHOSIN_NO_SESSION_WARNING=1 to suppress this warning. in Unknown on lin e 0 *** Welcome to pfSense 2.2.1-DEVELOPMENT-nanobsd (i386) on firewall *** -
The cron messages about "No such file or directory"are "normal". The startup is too dumb and those messages get emitted just before the relevant dirs are created. I guess someone should fix that to suppress that output some day.
Someone else also reported the suhosin thing - I think the devs have it on their radar.
-
well the suhosin thing was the error i was reporting and not the cron thing :)
one other thing i noticed was i had sent a pull request for UPNP and it was merged but seems it didnt end up in the snapshot i downlaoded which was dated 18th feb so i guess something wrong there too
-
Already reported. Also, PHP is compiled against some obscure severely outdated libpcre for whatever reason.
-
one other thing i noticed was i had sent a pull request for UPNP and it was merged but seems it didnt end up in the snapshot i downlaoded which was dated 18th feb so i guess something wrong there too
That was commit: https://github.com/pfsense/pfsense/commit/8f637a0c4e323fe48f910aabf8e1662c307ac564
It was committed to master but then never to RELENG_2_2 branch.
Maybe PM to Renato to see if he intended that change to wait for a later release or if it was just an error forgetting to merge to RELENG_2_2.