You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by benchu yao <ya...@gmail.com> on 2019/11/05 06:22:52 UTC
The historical session in the database is 8 hours behind the actual
time.
The historical session in the database is 8 hours behind the actual time.
And this time difference does not seem to be affected by system time and
mysql time.
I want to know the reason for this time difference.
Thank you
Re: The historical session in the database is 8 hours behind the
actual time.
Posted by benchu yao <ya...@gmail.com>.
Thank you,I will check the time zone configuration again.
Nick Couchman <vn...@apache.org> 于2019年11月8日周五 上午8:41写道：
> On Wed, Nov 6, 2019 at 9:22 AM benchu yao <ya...@gmail.com> wrote:
>
>> So, can you confirm that this is not an accident?
>>
>> The data in the database will always be UTC time, the same as GUAC_TIME.
>>
>>
> No, that is not what Mike said. What he said is the time is stored in the
> database in UTC, whereas the GUAC_TIME token will be the local time of the
> server. If the server happens to be using UTC for its local clock, this
> *may* be the same, but if the server has another timezone set, it *may not*
> be UTC, and may be something else.
>
> -Nick
>
>>
Re: The historical session in the database is 8 hours behind the
actual time.
Posted by Nick Couchman <vn...@apache.org>.
On Wed, Nov 6, 2019 at 9:22 AM benchu yao <ya...@gmail.com> wrote:
> So, can you confirm that this is not an accident?
>
> The data in the database will always be UTC time, the same as GUAC_TIME.
>
>
No, that is not what Mike said. What he said is the time is stored in the
database in UTC, whereas the GUAC_TIME token will be the local time of the
server. If the server happens to be using UTC for its local clock, this
*may* be the same, but if the server has another timezone set, it *may not*
be UTC, and may be something else.
-Nick
>
Re: The historical session in the database is 8 hours behind the
actual time.
Posted by benchu yao <ya...@gmail.com>.
So, can you confirm that this is not an accident?
The data in the database will always be UTC time, the same as GUAC_TIME.
Mike Jumper <mj...@apache.org> 于2019年11月6日周三 下午5:21写道：
> On Tue, Nov 5, 2019, 18:44 benchu yao <ya...@gmail.com> wrote:
>
>> I use docker to deploy guacamole and guacd.
>> The time in the docker container is correct, the mysql time is correct,
>> the system time is correct, and the online session and historical session
>> time displayed by the guacamole web interface is also correct. However, the
>> historical session start time and end time in the database are 8 hours
>> later than the real time. For example, it is 10 o'clock, but the database
>> time is 2 o'clock.
>> At the same time, the parameter token ${GUAC_TIME} is also wrong, and its
>> time is the same as the database time.
>>
>
> The time stored in the database is in UTC, not local time.
>
> As for the GUAC_TIME token, this will be in the local timezone of the
> server, which may well also be UTC.
>
> If the timezone you are otherwise expecting is 8 hours away from UTC, then
> the behavior you describe is correct.
>
> - Mike
>
>
Re: The historical session in the database is 8 hours behind the
actual time.
Posted by Mike Jumper <mj...@apache.org>.
On Tue, Nov 5, 2019, 18:44 benchu yao <ya...@gmail.com> wrote:
> I use docker to deploy guacamole and guacd.
> The time in the docker container is correct, the mysql time is correct,
> the system time is correct, and the online session and historical session
> time displayed by the guacamole web interface is also correct. However, the
> historical session start time and end time in the database are 8 hours
> later than the real time. For example, it is 10 o'clock, but the database
> time is 2 o'clock.
> At the same time, the parameter token ${GUAC_TIME} is also wrong, and its
> time is the same as the database time.
>
The time stored in the database is in UTC, not local time.
As for the GUAC_TIME token, this will be in the local timezone of the
server, which may well also be UTC.
If the timezone you are otherwise expecting is 8 hours away from UTC, then
the behavior you describe is correct.
- Mike
Re: The historical session in the database is 8 hours behind the
actual time.
Posted by benchu yao <ya...@gmail.com>.
I use docker to deploy guacamole and guacd.
The time in the docker container is correct, the mysql time is correct, the
system time is correct, and the online session and historical session time
displayed by the guacamole web interface is also correct. However, the
historical session start time and end time in the database are 8 hours
later than the real time. For example, it is 10 o'clock, but the database
time is 2 o'clock.
At the same time, the parameter token ${GUAC_TIME} is also wrong, and its
time is the same as the database time.
Steven Pollock <ja...@gmail.com> 于2019年11月6日周三 上午2:27写道：
> I wonder if that's the same problem we are seeing (hasn't been resolved
> yet)
>
>
> Regards,
>
> -Steve
>
> (415) 320-1102 <https://www.google.com/voice/#phones>
>
>
> On Tue, Nov 5, 2019 at 6:33 AM Nick Couchman <vn...@apache.org> wrote:
>
>> On Tue, Nov 5, 2019 at 1:23 AM benchu yao <ya...@gmail.com> wrote:
>>
>>> The historical session in the database is 8 hours behind the actual
>>> time.
>>> And this time difference does not seem to be affected by system time and
>>> mysql time.
>>>
>>
>> What do you mean by this? You've offered this assertion, but little
>> detail about why you think system time and database time are not related?
>> Does the 8 hours have any commonality to your offset from GMT?
>>
>>
>>> I want to know the reason for this time difference.
>>>
>>
>> You'll have to provide some more detail to allow us to help you diagnose
>> the issue. I'm not currently seeing the problem in my environment, but I
>> also am not using MySQL. It's possibly a bug, but also possibly something
>> with your configuration. Please provide detail.
>>
>> -Nick
>>
>>>
Re: The historical session in the database is 8 hours behind the
actual time.
Posted by Steven Pollock <ja...@gmail.com>.
I wonder if that's the same problem we are seeing (hasn't been resolved yet)
Regards,
-Steve
(415) 320-1102 <https://www.google.com/voice/#phones>
On Tue, Nov 5, 2019 at 6:33 AM Nick Couchman <vn...@apache.org> wrote:
> On Tue, Nov 5, 2019 at 1:23 AM benchu yao <ya...@gmail.com> wrote:
>
>> The historical session in the database is 8 hours behind the actual time.
>> And this time difference does not seem to be affected by system time and
>> mysql time.
>>
>
> What do you mean by this? You've offered this assertion, but little
> detail about why you think system time and database time are not related?
> Does the 8 hours have any commonality to your offset from GMT?
>
>
>> I want to know the reason for this time difference.
>>
>
> You'll have to provide some more detail to allow us to help you diagnose
> the issue. I'm not currently seeing the problem in my environment, but I
> also am not using MySQL. It's possibly a bug, but also possibly something
> with your configuration. Please provide detail.
>
> -Nick
>
>>
Re: The historical session in the database is 8 hours behind the
actual time.
Posted by Nick Couchman <vn...@apache.org>.
On Tue, Nov 5, 2019 at 1:23 AM benchu yao <ya...@gmail.com> wrote:
> The historical session in the database is 8 hours behind the actual time.
> And this time difference does not seem to be affected by system time and
> mysql time.
>
What do you mean by this? You've offered this assertion, but little detail
about why you think system time and database time are not related? Does
the 8 hours have any commonality to your offset from GMT?
> I want to know the reason for this time difference.
>
You'll have to provide some more detail to allow us to help you diagnose
the issue. I'm not currently seeing the problem in my environment, but I
also am not using MySQL. It's possibly a bug, but also possibly something
with your configuration. Please provide detail.
-Nick
>