Hello,
if i start within sametime 11 or 12 meeting a chat ...
a chat client will get a meeting chat window with the name of the meeting and its time started.
This is not a big problem, but i got questions why is the time different > chat startet 11.19 am
Meeting name = TEST-V12 2023-02-24 10:19
Chat time = 11:19 AM
I already updated inside the docker file .env the timezone entry to TZ=Europe/Berlin, but this did not change anything.
If i check sametime logs - i will also see that the log-time for the community pod/container is one hour behind.
sametime-jibri-1 | Jibri 2023-02-24 11:26:57.436 FINE: [19]
sametime-jvb-1 | JVB 2023-02-24 11:27:00.092 INFO: [22]
sametime-nginx-1 | {"time_local":"24/Feb/2023:11:27:04 +0100","remote_......
sametime-community-1 | stconfig 2023-02-24 10:27:05.099 FINEST 70 --- ....
sametime-community-1 | stconfig 2023-02-24 10:27:05.099 FINEST 70 --- 140580369684288 : stDdaConfigTimerEvent
sametime-community-1 | stusers 2023-02-24 10:27:07.334 FINEST 89 --- ......
Any idea where the time difference comes from ? or how to change the date/time on community pod/container ?
@Alexander Novak
thank you for the screen shots
however if you really want to know why you are seeing in "your environment" please open a case with
so that we can troubleshoot / investigate.
I just did the same test on my test environment and I do not see the time difference that you are displaying here.
Hello.
I don't know if this will fix it, but please check if the following settings are in your time zone.
** .env file
TZ=America/NewYork
** OS time zone in docker host
If the problem is not resolved, we still recommend opening the case.
Regards,
Shigemitsu Tanaka
Hello,
i already set the timezone in the docker .env file, but still the same difference.
TZ=Europe/Berlin
local os time = 13:36
community/mux/proxy container time= 12:36
jibri/jigasi container time = 13:36
I think that the timezone parameter will not be set within all containers and if i check the notes.ini within the community container i find the parameter Timezone=0
docker exec -it st-community-1 cat notes.ini
I will open a hcl case
@Alexander Novak
a) times are stored/sent in UTC across the clients, servers, etc. The display in the chat(s) (chat messages, etc) are going to be converted to local time based on the users settings.
b) all nway chats have a "topic name" which is just a string ... for a meeting, we have to generate a unique "topic name" and we use the start time of the meeting in the UTC timezone as a way to uniquely name the nway chat for this meeting ... we understand that this can cause user confusion because the string on the screen doesn't match the client timezone. The conversion of the UTC to a time happens on the server side. The local (container) time of the prosody and/or community server may have a role in this conversion.
c) we do not have a way (in our configuration) to control the date/time settings of the containers - the TZ setting in .env is NOT used for this.
In short, this is working as designed, but we recognize the potential for user confusion in this scenario
An enhancement request has been created
Please vote: https://domino-ideas.hcltechsw.com/ideas/STC-I-495
