Another upgrade to 2.2 issue

genic

i am too having the same issues. i did the direct auto update to 2.2.1 and i am receiving the same error messages that others have stated. NOTHING changed on the hardware side, and everything worked just fine prior to the firmware auto-update.

so i would say its not just TWO or THREE people having problems.

error at the top of the gui –

"Warning: date(): It is not safe to rely on the system's timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /etc/inc/globals.inc on line 63 Warning: date(): It is not safe to rely on the system's timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /etc/inc/globals.inc on line 63 "

i tried to change the time zone to CST (which is where i am, and also looked at NTP which is working) ... and still the same problems as others have stated.

also when trying to change the time zone in the general setup (btw, the drop downs in chrome no longer work past the first selection) i receive the following error.

03-25-15 13:51:58 [ Unable to open /cf/conf/config.xml for writing in write_config()]

…..i know what my problem is. for some reason the filesystem went into readonly due to corruption. i cant write anything to the CF card, but the actual system works (a watchguard XTM 1050...lucky this only happened on ONE of my routers...or i would be f-ed!)
so, i am going to grab another card i have...put the release 2.2 on it, and then just go back and recreate the rules from a fresh system.

what/why do you have to update a file before the firmware upgrade...shouldnt that be automatic?

Thilroy

Same thing for me :

HW: quite basic Dell GX260 SFF with two Nics
Initially pfSense2.2
Packages Squid, LightSquid and OpenVpn Client Export Utility
Tried an upgrade to 2.2.2.

symptoms :

message on top of gui : "Warning: date(): It is not safe to rely on the system's timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /etc/inc/globals.inc on line 63 Warning: date(): It is not safe to rely on the system's timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this "
during the upgrade nothing abnormal. After restart gui message (see before) and furthermore it's like there wasn't any upgrade at all since under "system/firmware/auto update" I'm still reading :

_A new version is now available
Current version: 2.2-RELEASE
Built On: Thu Jan 22 14:04:25 CST 2015
New version: 2.2.2-RELEASE
Update source: https://updates.pfsense.org/updaters

under "system/general setup", the time zone dropdown list is totally empty, and doesn't display any possible choice.

I tried 2 times a manual upgrade, no change.
I also went looking in /usr/local/etc/php.ini : the date.timezone parameter was "". Changed it to "europe/brussels", still no luck, symptoms still there.

Any help ?

Supermule

I get a crash report warning in the GUI.

Crash report begins. Anonymous machine information:

amd64
10.1-RELEASE-p9
FreeBSD 10.1-RELEASE-p9 #0 57b23e7(releng/10.1)-dirty: Mon Apr 13 20:30:25 CDT 2015 root@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10

Crash report details:

PHP Errors:
[21-Apr-2015 13:40:35 Europe/Copenhagen] PHP Parse error: syntax error, unexpected end of file in /usr/local/www/exec.php(250) : eval()'d code on line 1
[21-Apr-2015 13:40:40 Europe/Copenhagen] PHP Parse error: syntax error, unexpected end of file in /usr/local/www/exec.php(250) : eval()'d code on line 1

Filename: /var/crash/minfree
2048

cmb

@Supermule:

I get a crash report warning in the GUI.

PHP Errors:
[21-Apr-2015 13:40:35 Europe/Copenhagen] PHP Parse error: syntax error, unexpected end of file in /usr/local/www/exec.php(250) : eval()'d code on line 1
[21-Apr-2015 13:40:40 Europe/Copenhagen] PHP Parse error: syntax error, unexpected end of file in /usr/local/www/exec.php(250) : eval()'d code on line 1

which is from wrong code you put yourself into PHP Execute box in exec.php.

Supermule

Thx Chris

Can you elaborate some more since I dont recall executing anything other than running kldstat in the execute prompt…

@cmb:

@Supermule:

I get a crash report warning in the GUI.

PHP Errors:
[21-Apr-2015 13:40:35 Europe/Copenhagen] PHP Parse error: syntax error, unexpected end of file in /usr/local/www/exec.php(250) : eval()'d code on line 1
[21-Apr-2015 13:40:40 Europe/Copenhagen] PHP Parse error: syntax error, unexpected end of file in /usr/local/www/exec.php(250) : eval()'d code on line 1

which is from wrong code you put yourself into PHP Execute box in exec.php.

cmb

@Supermule:

Thx Chris

Can you elaborate some more since I dont recall executing anything other than running kldstat in the execute prompt…

any stray character in that box (other than just whitespace) will result in that message. An inadvertent single character typed in there would do that.

NOYB

@cmb:

@Dustin:

Side note: I find it very un-helpful and almost insulting that nearly every issue that this very buggy release of pfSense has, you guys are trying to blow off as a one-off issue.

Only where they are one-off issues! Two people on earth now, out of into 5 digits of upgraded systems, have seen that.

Two people on earth now, out of into 5 digits of upgraded systems, have ~~seen~~ reported that.

As Dustin mentioned not everyone sits here working as unpaid QA staff. Thus "seen" = "reported" + n

cmb

@genic:

(btw, the drop downs in chrome no longer work past the first selection)

A Chrome update broke that and similar functionality on a variety of other sites within the past month or so on Windows. Non-issue in Chrome on OS X and Linux. On affected Windows systems, right click, hit "inspect element", and it'll work around it.

@genic:

i receive the following error.

03-25-15 13:51:58 [ Unable to open /cf/conf/config.xml for writing in write_config()]

…..i know what my problem is. for some reason the filesystem went into readonly due to corruption. i cant write anything to the CF card, but the actual system works (a watchguard XTM 1050...lucky this only happened on ONE of my routers...or i would be f-ed!)
so, i am going to grab another card i have...put the release 2.2 on it, and then just go back and recreate the rules from a fresh system.

Likely a bad CF.

@genic:

what/why do you have to update a file before the firmware upgrade…shouldnt that be automatic?

Normally no need to touch anything before upgrade. The Watchguard boxes tend to have broken DMA so disabling it before upgrade may be necessary since it used to be off by default for nano.

lowprofile

@Supermule:

Thx Chris

Can you elaborate some more since I dont recall executing anything other than running kldstat in the execute prompt…

@cmb:

@Supermule:

I get a crash report warning in the GUI.

PHP Errors:
[21-Apr-2015 13:40:35 Europe/Copenhagen] PHP Parse error: syntax error, unexpected end of file in /usr/local/www/exec.php(250) : eval()'d code on line 1
[21-Apr-2015 13:40:40 Europe/Copenhagen] PHP Parse error: syntax error, unexpected end of file in /usr/local/www/exec.php(250) : eval()'d code on line 1

which is from wrong code you put yourself into PHP Execute box in exec.php.

I am having exact same issue, i also submitted the report for some minutes ago. please check.

cmb

@lowprofile:

I am having exact same issue, i also submitted the report for some minutes ago. please check.

Same thing, looks like you submitted something in the PHP execute box. Do you have a form filler or something that might be putting something in there? Is it replicable for you?

lowprofile

@cmb:

@lowprofile:

I am having exact same issue, i also submitted the report for some minutes ago. please check.

Same thing, looks like you submitted something in the PHP execute box. Do you have a form filler or something that might be putting something in there? Is it replicable for you?

I am 100% sure that i don't. I've though used the php execute box days before, but no auto fill or anything related.
I cannot replicate it, it just happened on a fresh browser, chrome - dashboard.

if it's not critical then i wont go deeper into it since it only happened once. There is other critical issues to looking at :)

David Handelman

Downgraded to 2.2.1 and no sync as well,

Will downgrade to 2.2 and test