Re: [pfSense] Strange timezone behavior and then full stop

2015-08-26 Thread Wade Blackwell
Thanks Steve.
On Aug 26, 2015 9:04 AM, "Steve Yates"  wrote:

> Wade Blackwell wrote on Wed, Aug 26 2015 at 10:27 am:
>
> > 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 64
>
> This is a PHP warning that would show on each page load.  Recent
> PHP versions (5.3+?) require the time zone to be set in php.ini or other
> PHP-read .ini files.  It's just a warning so isn't an indicator of a
> problem in and of itself.
>
> --
>
> Steve Yates
> ITS, Inc.
>
>
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] Strange timezone behavior and then full stop

2015-08-26 Thread Steve Yates
Wade Blackwell wrote on Wed, Aug 26 2015 at 10:27 am:

> 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 64

This is a PHP warning that would show on each page load.  Recent PHP 
versions (5.3+?) require the time zone to be set in php.ini or other PHP-read 
.ini files.  It's just a warning so isn't an indicator of a problem in and of 
itself.

--

Steve Yates
ITS, Inc.


___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


[pfSense] Strange timezone behavior and then full stop

2015-08-26 Thread Wade Blackwell
Good morning PF group,
I have *2.2.4-RELEASE * (amd64)running virtually in a VSPhere 5.5
environment. I just recently upgraded from 2.2.3. So I woke up to the
network down, console complaining about timezones and no IP addresses on
any of the interfaces. I rolled back configs from the console,
sequentially, hoping that would at least restore the interface IPs. Not so.
I ended up manually configuring the address local to my workstation and
only then was I able to restore the latest full backup and bring the pf
back up. Curiously I am missing a day worth of logs (8/25 is just not
there). The error messages I got are below, some of these were displayed at
the top of the web ui, and some in the version section of the status page.
Anyone seen any strangeness like this?

-W

--begin error funk
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 64
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 64
Warning: Cannot modify header information - headers already sent by (output
started at /etc/inc/globals.inc:64) in /usr/local/www/guiconfig.inc on line
48 Warning: Cannot modify header information - headers already sent by
(output started at /etc/inc/globals.inc:64) in /usr/local/www/guiconfig.inc
on line 49 Warning: Cannot modify header information - headers already sent
by (output started at /etc/inc/globals.inc:64) in
/usr/local/www/guiconfig.inc on line 50 Warning: Cannot modify header
information - headers already sent by (output started at
/etc/inc/globals.inc:64) in /usr/local/www/guiconfig.inc on line 51
Warning: Cannot modify header information - headers already sent by (output
started at /etc/inc/globals.inc:64) in /usr/local/www/guiconfig.inc on line
52 Warning: Cannot modify header information - headers already sent by
(output started at /etc/inc/globals.inc:64) in /usr/local/www/guiconfig.inc
on line 55 Warning: session_start(): Cannot send session cache limiter -
headers already sent (output started at /etc/inc/globals.inc:64) in
/etc/inc/auth.inc on line 1359


2Warning: 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 64
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 64
transparent

XML Parsing Error: unexpected parser state Location:
jar:file:///C:/Program%20Files/Mozilla%20Firefox/browser/omni.ja!/chrome/browser/content/browser/aboutNetError.xhtml
Line Number 389, Column 68:
&connectionFailure.longDesc;
---^

---end error funk---

Wade Blackwell
Solutions Architect
(D) 805.457.8825
(C) 805.400.8485
(S) coc.wadeblackwell
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] Why no dnssec in dnsmasq by default?

2015-08-26 Thread Adrian Zaugg

On 24.08.15 20:35, Chris Buechler wrote:
> On Sun, Aug 23, 2015 at 9:28 AM, Adrian Zaugg  wrote:
>> why it is not enabled by default?
... and because all the DNS servers used as forwarders must support
DNSSEC too for it work.

And thank you for your answer, Chris.

Regards, Adrian.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold