To confirm: Joe's explanation, uncomfortable as it, looks to be the correct
one. When the servers were powered off and restarted (so the gluster
processes /had/ to be restarted, the new ones started up and used the correct
time format.
The 'problem' clients were the ones which were running the
On Tuesday, December 10, 2013 11:23:11 AM Joe Julian wrote:
> If I were to hazard a guess, since the timestamp is not configurable and
> *is* UTC in 3.4, it would seem that any server that's logging in local time
> must not be running 3.4. Sure, it's installed, but the application hasn't
> been res
On 12/10/2013 10:57 AM, harry mangalam wrote:
On Tuesday, December 10, 2013 10:42:28 AM Vijay Bellur wrote:
> On 12/10/2013 10:14 AM, harry mangalam wrote:
> > Admittedly I should search the source, but I wonder if anyone
knows this
> > offhand.
> >
> > Background: of our 84 ROCKS (6.1)
On Tuesday, December 10, 2013 10:42:28 AM Vijay Bellur wrote:
> On 12/10/2013 10:14 AM, harry mangalam wrote:
> > Admittedly I should search the source, but I wonder if anyone knows this
> > offhand.
> >
> > Background: of our 84 ROCKS (6.1) -provisioned compute nodes, 4 have
> > picked up an 'adv
On Tuesday, December 10, 2013 12:49:25 PM Sharuzzaman Ahmat Raslan wrote:
> Hi Harry,
>
> Did you setup ntp on each of the node, and sync the time to one single
> source?
Yes, this is done by ROCKS and all the nodes have the identical time.
(2admins have checked repeatedly)
> Thanks.
>
> On Tue
On 12/10/2013 10:14 AM, harry mangalam wrote:
Admittedly I should search the source, but I wonder if anyone knows this
offhand.
Background: of our 84 ROCKS (6.1) -provisioned compute nodes, 4 have
picked up an 'advanced date' in the /var/log/glusterfs/gl.log file -
that date string is running ab
Hi Harry,
Did you setup ntp on each of the node, and sync the time to one single
source?
Thanks.
On Tue, Dec 10, 2013 at 12:44 PM, harry mangalam wrote:
> Admittedly I should search the source, but I wonder if anyone knows this
> offhand.
>
>
>
> Background: of our 84 ROCKS (6.1) -provisioned
Admittedly I should search the source, but I wonder if anyone knows this
offhand.
Background: of our 84 ROCKS (6.1) -provisioned compute nodes, 4 have picked
up an 'advanced date' in the /var/log/glusterfs/gl.log file - that date
string is running about 5-6 hours ahead of the system date and
