RE: [pfSense Support] Incorrect System Log Order/Logging Bug?

2011-07-13 Thread Dimitri Rodis
>2011/7/13 Jim Pingle mailto:li...@pingle.org>>
>On 7/9/2011 9:17 PM, Dimitri Rodis wrote:
>> The system is and has been set to -8 (I am Pacific Daylight Time, USA), and 
>> hasn't been re/booted since the first boot on that build--and I >have 
>> reported this issue back in RC1 and it still appears to be an issue. It 
>> almost looks as if the check_reload_status (among a couple of others >that 
>> haven't shown up in the log yet) specifically always logs with the wrong 
>> timestamp.
>Are you actually using the GMT +/- zone or a named zone such as
>America/Los_Angeles?
>
>
>http://www.timeanddate.com/worldclock/
>
>;-)

See screen snip below.

 [cid:image001.png@01CC4162.4D0586B0]
<>

Re: [pfSense Support] Incorrect System Log Order/Logging Bug?

2011-07-13 Thread Michael Schuh
2011/7/13 Jim Pingle 

> On 7/9/2011 9:17 PM, Dimitri Rodis wrote:
> > The system is and has been set to -8 (I am Pacific Daylight Time, USA),
> and hasn't been re/booted since the first boot on that build--and I have
> reported this issue back in RC1 and it still appears to be an issue. It
> almost looks as if the check_reload_status (among a couple of others that
> haven't shown up in the log yet) specifically always logs with the wrong
> timestamp.
>
> Are you actually using the GMT +/- zone or a named zone such as
> America/Los_Angeles?
>
>
http://www.timeanddate.com/worldclock/

;-)


> The GMT+/- zones are often sources of such weirdness, the named Zones
> usually work best.
>
> Jim
>
> -
> To unsubscribe, e-mail: support-unsubscr...@pfsense.com
> For additional commands, e-mail: support-h...@pfsense.com
>
> Commercial support available - https://portal.pfsense.org
>
>


-- 
= = =  http://michael-schuh.net/  = = =
Projektmanagement - IT-Consulting - Professional Services IT
Michael Schuh
Postfach 10 21 52
66021 Saarbrücken
phone: 0681/8319664
mobil:  0175/5616453
@: m i c h a e l . s c h u h @ g m a i l . c o m

= = =  Ust-ID:  DE251072318  = = =


Re: [pfSense Support] Incorrect System Log Order/Logging Bug?

2011-07-13 Thread Jim Pingle
On 7/9/2011 9:17 PM, Dimitri Rodis wrote:
> The system is and has been set to -8 (I am Pacific Daylight Time, USA), and 
> hasn't been re/booted since the first boot on that build--and I have reported 
> this issue back in RC1 and it still appears to be an issue. It almost looks 
> as if the check_reload_status (among a couple of others that haven't shown up 
> in the log yet) specifically always logs with the wrong timestamp.

Are you actually using the GMT +/- zone or a named zone such as
America/Los_Angeles?

The GMT+/- zones are often sources of such weirdness, the named Zones
usually work best.

Jim

-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org



RE: [pfSense Support] Incorrect System Log Order/Logging Bug?

2011-07-09 Thread Dimitri Rodis
>On Fri, Jul 8, 2011 at 4:26 PM, Vick Khera  wrote:
>> On Fri, Jul 8, 2011 at 1:06 PM, Dimitri Rodis 
>>  wrote:
>>>
>>> I have my log set to show newest on top, and the log is "mostly" in 
>>> order, but notice how there are some entries that are in the middle 
>>> of this screenshot that are "newer" than everything else. (The 
>>> problem is that Jul 8
>>> 15:12:29 has not yet happened in my time zone, it is only shortly 
>>> after 10AM
>>> here..)
>>
>> What's your offset to GMT?  I'll guess +5 If the process started 
>> before the timezone was set, then you will see stuff like this.  Same 
>> if you alter the timezone after the process is started.
>>  They do not re-read the timezone file ever.
>>
>
>This. If you want everything to be on the right timezone you have to reboot 
>after setting it (or restart the services individually), that's always been 
>the case. The logs show in the order they were >logged, with the timestamp of 
>the process doing the logging.
>
>-

The system is and has been set to -8 (I am Pacific Daylight Time, USA), and 
hasn't been re/booted since the first boot on that build--and I have reported 
this issue back in RC1 and it still appears to be an issue. It almost looks as 
if the check_reload_status (among a couple of others that haven't shown up in 
the log yet) specifically always logs with the wrong timestamp.

-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org



Re: [pfSense Support] Incorrect System Log Order/Logging Bug?

2011-07-08 Thread Chris Buechler
On Fri, Jul 8, 2011 at 4:26 PM, Vick Khera  wrote:
> On Fri, Jul 8, 2011 at 1:06 PM, Dimitri Rodis
>  wrote:
>>
>> I have my log set to show newest on top, and the log is “mostly” in order,
>> but notice how there are some entries that are in the middle of this
>> screenshot that are “newer” than everything else. (The problem is that Jul 8
>> 15:12:29 has not yet happened in my time zone, it is only shortly after 10AM
>> here..)
>
> What's your offset to GMT?  I'll guess +5
> If the process started before the timezone was set, then you will see stuff
> like this.  Same if you alter the timezone after the process is started.
>  They do not re-read the timezone file ever.
>

This. If you want everything to be on the right timezone you have to
reboot after setting it (or restart the services individually), that's
always been the case. The logs show in the order they were logged,
with the timestamp of the process doing the logging.

-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org



Re: [pfSense Support] Incorrect System Log Order/Logging Bug?

2011-07-08 Thread Vick Khera
On Fri, Jul 8, 2011 at 1:06 PM, Dimitri Rodis  wrote:

> I have my log set to show newest on top, and the log is “mostly” in order,
> but notice how there are some entries that are in the middle of this
> screenshot that are “newer” than everything else. (The problem is that Jul 8
> 15:12:29 has not yet happened in my time zone, it is only shortly after 10AM
> here..)


What's your offset to GMT?  I'll guess +5

If the process started before the timezone was set, then you will see stuff
like this.  Same if you alter the timezone after the process is started.
 They do not re-read the timezone file ever.


Re: [pfSense Support] Incorrect System Log Order/Logging Bug?

2011-07-08 Thread David Burgess
On Fri, Jul 8, 2011 at 11:06 AM, Dimitri Rodis
 wrote:

> Can anyone else confirm what appears to be either a bug in the logging with 
> respect to the timestamps or a bug in the sorting of the log entries? (I 
> don’t know which)

I've seen it here and I suspect the problem is with the timestamps,
and the time zone not being applied to some of them. I was about to
take a screen shot of mine when I realized that none of my logs are
populated since updating to the latest snap yesterday :P

db

-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org