[Spread-users] Log timestamps aren't correct (timezone setting?)
Jonathan Stanton
jonathan at cnds.jhu.edu
Thu Nov 8 18:48:11 EST 2007
What was the correct time at the time of these logs? I.e was it locally (in your timezone)
15:45 or 21:45?
Did the Spread output change back and forth between the 15:x time and the 21:x time? Or
once it switched, all the remainder of the logs were using 21?
This is definitely strange as the example below for printing the membership shows the time
changing during a series of Alarm() calls that are in the same function (the ---- line has
one time and the "Configuration at.." line has a different time, but the code is identical
as seen below:
configuration.c:720
Alarm( PRINT, "--------------------\n" );
Alarm( PRINT, "Configuration at %s is:\n", My.name );
Alarm( PRINT, "Num Segments %d\n",config->num_segments );
for ( s=0; s < config->num_segments; s++ )
{
Conf_id_to_str( config->segments[s].bcast_address, ip );
Alarm( PRINT, "\t%d\t%-16s %hd\n",
config->segments[s].num_procs, ip,
config->segments[s].port );
for( p=0; p < config->segments[s].num_procs; p++)
{
ret = Conf_proc_by_id( config->segments[s].procs[p]->id,
&pr );
Conf_id_to_str( pr.id, ip );
Alarm( PRINT, "\t\t%-20s\t%-16s\n", pr.name, ip );
}
}
Alarm( PRINT, "====================" );
Thanks,
Jonathan
On Thu, Nov 08, 2007 at 01:58:40PM -0600, Matt Garman wrote:
> On Tue, Apr 03, 2007 at 11:20:56AM -0500, matthew.garman at gmail.com wrote:
> > The timestamps in my spread logs aren't correct. The time is off
> > by a constant factor. It appears that the time zone configuration
> > isn't set correctly.
> >
> > Does spread require special configuration for timezone?
>
> I'm still seeing this problem, even in the official 4.0.0 release
> version. Here's an excerpt from my log:
>
> /===========================================================================\
> | The Spread Toolkit.
> |
> ... [ splash screen trimmed for brevity ] ...
> | |
> | Version 4.00.00 Built 29/November/2006 |
> \===========================================================================/
> Conf_load_conf_file: using file: /usr/local/etc/spread.conf
> Successfully configured Segment 0 [192.168.1.255:4803] with 8 procs:
> server1: 192.168.1.1
> ... [ trimmed for brevity ] ...
> [Mon 05 Nov 2007 15:45:02] Setting SO_REUSEADDR to auto
> [Mon 05 Nov 2007 15:45:02] disabling Dangerous Monitor Commands!
> [Mon 05 Nov 2007 15:45:02] Set runtime directory to '/var/run/spread'
> [Mon 05 Nov 2007 15:45:02] Set group name to 'spread'
> [Mon 05 Nov 2007 15:45:02] Set user name to 'spread'
> Membership id is ( -1062683843, 1194299103)
> [Mon 05 Nov 2007 15:45:02] --------------------
> [Mon 05 Nov 2007 21:45:02] Configuration at lnxsvr7 is:
> [Mon 05 Nov 2007 21:45:02] Num Segments 1
> [Mon 05 Nov 2007 21:45:02] 3 192.168.1.255 4803
> [Mon 05 Nov 2007 21:45:02] server1 192.168.1.1
> [Mon 05 Nov 2007 21:45:02] server2 192.168.1.2
> [Mon 05 Nov 2007 21:45:02] server3 192.168.1.3
> [Mon 05 Nov 2007 21:45:02] ====================
>
> See how the timestamp jumps ahead from 15:45:02 to 21:45:02?
>
> Any thoughts?
>
> Thanks,
> matt
>
>
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
--
-------------------------------------------------------
Jonathan R. Stanton jonathan at cs.jhu.edu
Dept. of Computer Science
Johns Hopkins University
-------------------------------------------------------
More information about the Spread-users
mailing list