Another upgrade to 2.2 issue
-
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
Is now shown across the top of the whole web UI all the time. How can I fix it?
-
Have you cleared your browser cache?
Try pressing "F5" and see if that fixes it.
-
yeah i've tried that. no change. :(
that same stuff appears in different frames throughout the web UI too.
-
What is your timezone configured as?
That means your timezone is configured with something PHP doesn't recognize, which seems odd, haven't seen any other reports of that.
-
Before the upgrade it was set to "EST". Since then I've tried setting it to "America/New York" and "US/Eastern". No dice.
-
Anyone have any other ideas? I'll probably just download the new 2.2 iso image and re-install from scratch if not.
-
What does the line containing "date.timezone" in /usr/local/etc/php.ini contain?
Try EST5EDT. The others you mentioned don't seem to be an issue either though.
-
-
That's correct. Given it's configured correctly, and no one else is seeing it, it makes me wonder if you modified something on your system that's somehow causing it. Anything unusual about your system?
-
I am having this issue too.
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. Not everyone has time to sit here and be your unpaid QA staff. When something is put on your site with 'release' after it, people rightfully assume that it is release quality. This build is not. What is odd is that the last RCs were much better then this build. They would use my configs, they would boot without having to know a random line to add to the loader.conf, didn't get these weird error messages, they just worked.
-
I am having this issue too.
Providing some useful info would help. Obviously this is something very unusual given 2 people have seen it, what's atypical about your setup?
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.
What is odd is that the last RCs were much better then this build. They would use my configs, they would boot without having to know a random line to add to the loader.conf, didn't get these weird error messages, they just worked.
Nothing in this regard would have changed since RC. Most definitely nothing would have changed about some "random line to add to loader.conf" since the alpha snapshot days. Post details - what exactly did you have to change in loader.conf?
-
Can a dead battery in a bios clock cause problems with time or time zone?
-
Can a dead battery in a bios clock cause problems with time or time zone?
Until it boots up far enough to NTP sync, yes, the time will be way off (possibly decades behind). That's not an issue for what is being referenced here though. Somehow PHP is running something without using the values in php.ini. Which would be universal if it were actually broken in our code, and what was shown here earlier shows it is being configured correctly on the affected systems.
I'd like to know what these two systems have on them that's unusual, like maybe some package is messing with things, or maybe these are two systems where people got in and starting installing things with pkg manually and something conflicted there.
-
@cmb:
what exactly did you have to change in loader.conf?
I assume, since he previously linked to the modified Marvel drivers, that he is referring to disabling DMA to boot CF.
Steve
-
@cmb:
what exactly did you have to change in loader.conf?
I assume, since he previously linked to the modified Marvel drivers, that he is referring to disabling DMA to boot CF.
Ah, yeah probably. So again, didn't read the upgrade guide. That change was made for a reason, most all circumstances are better off now. But, in some limited cases with certain hardware (mostly the recycled Watchguards it seems), disabling DMA is still required to boot. From time to time, we have to change defaults like these because a different setting is best for nearly all installs. But some like this will leave 1 in several thousand systems unbootable unless you first take the appropriate action prior to upgrading (editing /boot/loader.conf.local before the upgrade, in that case).
This is the biggest reason to use our appliances, as we ensure you're getting optimal settings for that hardware now and in future releases. Otherwise, keep a close eye on any hardware-related things in the upgrade guide. And if you're using something like a recycled Watchguard, check the forum to find others' experiences with the same hardware.
-
I'm afraid I have this exact same issue since I recently upgraded to pfSense 2.2.
I have checked /usr/local/etc/php.ini and my timezone is set to 'Europe/Amsterdam' (Just like I had configured through the web interface). I've also not added anything else to the loader.conf file. My configuration worked flawlessly in 2.1.
Packages installed : 'Service Watchdog' and 'OpenVPN Client Export Utility'
Is there anything I can test or try to isolate the problem?
To clarify a bit see attached screenclip
-
As an update to my earlier post; somehow the issue has resolved itself.
I haven't performed a reboot of the pfSense firewall, it is still online as it was when I took the screen clip. It's not clear to me what made the issue go away but I will keep an eye on it.
-
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?
-
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 ?
-
-
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.10Crash 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 1Filename: /var/crash/minfree
2048
