[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #NJE-906346]: LDM Log Time Zone Issue



Justin,

> Ok, I understand:
> 
> address@hidden ulog]$ gcc test_gmtime.c -o gmtime_test
> address@hidden ulog]$ ./gmtime_test
> Dec 11 20:22:34
> address@hidden ulog]$ date
> Tue Dec 11 20:22:36 UTC 2012
> 
> I also ran 'test0 -l -'
> 
> address@hidden ulog]$ ./test0 -l -
> ulog[20859]
> Dec 11 20:23:30 ulog[20859] UNKNOWN: 0 Alert
> Dec 11 20:23:30 ulog[20859] UNKNOWN: 0 Crit
> Dec 11 20:23:30 ulog[20859] ERROR: 0 Err
> Dec 11 20:23:30 ulog[20859] WARN: 0 Warning
> Dec 11 20:23:30 ulog[20859] NOTE: 0 Notice
> Dec 11 20:23:30 ulog[20859] INFO: 0 Info 1 "Success" 2 string 3.141500 4
> Dec 11 20:23:30 ulog[20859] DEBUG: 0 Debug
> Dec 11 20:23:30 ulog[20859] NOTE: 1 Notice
> Dec 11 20:23:30 ulog[20859] UNKNOWN: 2 Alert
> Dec 11 20:23:30 ulog[20859] UNKNOWN: 2 Crit
> Dec 11 20:23:30 ulog[20859] ERROR: 2 Err
> Dec 11 20:23:30 ulog[20859] WARN: 2 Warning
> Dec 11 20:23:30 ulog[20859] NOTE: 2 Notice
> Dec 11 20:23:30 ulog[20859] INFO: 2 Info 1 "Success" 2 string 3.141500 4
> Dec 11 20:23:30 ulog[20859] UNKNOWN: 3 Alert
> Dec 11 20:23:30 ulog[20859] ERROR: 4 Err
> Dec 11 20:23:30 ulog[20859] WARN: 4 Warning
> Dec 11 20:23:30 ulog[20859] NOTE: 4 Notice
> Dec 11 20:23:30 ulog[20859] INFO: 4 Info 1 "Success" 2 string 3.141500 4
> Dec 11 20:23:30 ulog[20859] DEBUG: 4 Debug
> Dec 11 20:23:30 ulog[20859] ERROR: serror 1 2 string 3.141500 4: No such
> file or directory
> Dec 11 20:23:30 ulog[20859] NOTE: Local: Dec 11 20:23:30  (20)
> Dec 11 20:23:30 ulog[20859] NOTE:   UTC: Dec 11 20:23:30  (20)
> Dec 11 20:23:30 ulog[20859] NOTE: Local: Dec 11 20:23:30  (20)
> Dec 11 20:23:30 ulog[20859] NOTE:   UTC: Dec 11 20:23:30  (20)
> 
> Looks like it is correctly using UTC.

Good. That means that the gmtime() system function works correctly.

> Could there be something odd going on with syslogd?

Rreplacement of the timestamp in log messages by the system logging daemon 
would be consistent with observed behavior. The bracketing of the timestamp 
with asterisks is further evidence that this is being done.

It seems odd, but I think we should adopt it as a working hypothesis.

Does the LDM utility ulogger(1) exist? If not, then go into thr directory 
"src/ulog" and execute the command "make ulogger".

Then, execute the command "ulogger -l- test". Is the timestamp in UTC? Is so, 
then this is further evidence of misbehavior by the system logging daemon.

> I really appreciate the time you're taking to help me with this.
> 
> Justin

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NJE-906346
Department: Support LDM
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.