You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by "Yakovlev N." <ya...@krvostok.ru> on 2016/11/07 12:22:37 UTC
OM 3.1.4 time zone Europe/Moscow
Hello,
It's used OM 3.1.4 + Centos 7.
When creating events with Notification type - iCal the invite.ics file
attached to email has an incorrect invitation time that it is less by one
hour from time zone Europe/Moscow. Also these corresponding events are
shown in Outlook calendar incorrectly.
iCal works good if for example Europe/Minsk time zone is set.
There is the Europe/Moscow time zone on Centos:
# timedatectl status
Local time: Пн 2016-11-07 14:22:05 MSK
Universal time: Пн 2016-11-07 11:22:05 UTC
RTC time: Пн 2016-11-07 11:52:05
Time zone: Europe/Moscow (MSK, +0300)
-------------------------------------------------
# rpm -qa | grep tzdata*
tzdata-2016h-1.el7.noarch
joda-time-2.2-3.tzdata2013c.el7.noarch
tzdata-java-2016h-1.el7.noarch
-----------------------------------------------
# java -jar tzupdater.jar -V
tzupdater version 2.1.0-b04
JRE tzdata version: tzdata2016h
------------------------------------------------
Is there any idea where is the problem?
Best regards
Nikolay
RE: OM 3.1.4 time zone Europe/Moscow
Posted by "Yakovlev N." <ya...@krvostok.ru>.
I’ve attached invite.ics.
Is it OK to share?
From: Maxim Solodovnik [mailto:solomax666@gmail.com]
Sent: Monday, November 7, 2016 4:03 PM
To: Openmeetings user-list
Subject: Re: OM 3.1.4 time zone Europe/Moscow
What TZ is in ICS file?
could you share *.ics attachment?
On Mon, Nov 7, 2016 at 7:22 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
Hello,
It's used OM 3.1.4 + Centos 7.
When creating events with Notification type - iCal the invite.ics file attached to email has an incorrect invitation time that it is less by one hour from time zone Europe/Moscow. Also these corresponding events are shown in Outlook calendar incorrectly.
iCal works good if for example Europe/Minsk time zone is set.
There is the Europe/Moscow time zone on Centos:
# timedatectl status
Local time: Пн 2016-11-07 14:22:05 MSK
Universal time: Пн 2016-11-07 11:22:05 UTC
RTC time: Пн 2016-11-07 11:52:05
Time zone: Europe/Moscow (MSK, +0300)
-------------------------------------------------
# rpm -qa | grep tzdata*
tzdata-2016h-1.el7.noarch
joda-time-2.2-3.tzdata2013c.el7.noarch
tzdata-java-2016h-1.el7.noarch
-----------------------------------------------
# java -jar tzupdater.jar -V
tzupdater version 2.1.0-b04
JRE tzdata version: tzdata2016h
------------------------------------------------
Is there any idea where is the problem?
Best regards
Nikolay
--
WBR
Maxim aka solomax
RE: OM 3.1.4 time zone Europe/Moscow
Posted by "Yakovlev N." <ya...@krvostok.ru>.
OK
-----Original Message-----
From: Maxim Solodovnik [mailto:solomax666@gmail.com]
Sent: Tuesday, November 8, 2016 12:18 PM
To: Openmeetings user-list
Subject: Re: OM 3.1.4 time zone Europe/Moscow
Thanks for the update!
Would appreciate if you can share investigation results :)
On Tue, Nov 8, 2016 at 12:50 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
> Local Java is Version 8 Update 111 (build 1.8.0_111-b14), the latest
> Java Platform.
>
> Time zone on the local PC is Europe/Moscow.
>
> But you are right and the reason should be looked for in the local
> computer not in OM.
>
> I has just made one more experiment.
>
> If I use a web-client to connect to the e-mail (not Outlook) the
> calendar in the web client (Zimbra) has correct time assigned to a meet.
>
> If I download these emails to Outlook then one shows incorrect time in
> its calendar.
>
> OK, further I will look for a solution independently.
>
>
>
> Thanks for reply,
>
> Nikolay
>
>
>
> From: Maxim Solodovnik [mailto:solomax666@gmail.com]
> Sent: Monday, November 7, 2016 4:56 PM
>
>
> To: Openmeetings user-list
> Subject: Re: OM 3.1.4 time zone Europe/Moscow
>
>
>
> Really weird,
>
>
>
> just tried to create event in my Thunderbird (Ubuntu 16.10 all
> updates)
>
> Europe/Moscow 17:00-18:00
>
>
>
> I have Asia/Novosibirsk TZ (GMT +7, MSK + 4)
>
> Thunderbird shows event time as 20:00-21:00
>
> It is clearly wrong :(
>
> Will try to update local java and double-check
>
>
>
> On Mon, Nov 7, 2016 at 8:22 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
>
> Ics file as text
>
>
>
> BEGIN:VCALENDAR
>
> PRODID:-//Events Calendar//iCal4j 1.0//EN
>
> VERSION:2.0
>
> CALSCALE:GREGORIAN
>
> METHOD:CANCEL
>
> BEGIN:VTIMEZONE
>
> TZID:Europe/Moscow
>
> TZURL:http://tzurl.org/zoneinfo/Europe/Moscow
>
> X-LIC-LOCATION:Europe/Moscow
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+023017
>
> TZOFFSETTO:+023017
>
> TZNAME:MMT
>
> DTSTART:18800101T000000
>
> RDATE:18800101T000000
>
> END:STANDARD
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+023017
>
> TZOFFSETTO:+023119
>
> TZNAME:MMT
>
> DTSTART:19160703T002943
>
> RDATE:19160703T002943
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+023119
>
> TZOFFSETTO:+033119
>
> TZNAME:MST
>
> DTSTART:19170701T232841
>
> RDATE:19170701T232841
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+033119
>
> TZOFFSETTO:+023119
>
> TZNAME:MMT
>
> DTSTART:19171228T002841
>
> RDATE:19171228T002841
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+023119
>
> TZOFFSETTO:+043119
>
> TZNAME:MDST
>
> DTSTART:19180531T222841
>
> RDATE:19180531T222841
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+043119
>
> TZOFFSETTO:+033119
>
> TZNAME:MST
>
> DTSTART:19180916T002841
>
> RDATE:19180916T002841
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+033119
>
> TZOFFSETTO:+043119
>
> TZNAME:MDST
>
> DTSTART:19190531T222841
>
> RDATE:19190531T222841
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+043119
>
> TZOFFSETTO:+0400
>
> TZNAME:MSD
>
> DTSTART:19190701T002841
>
> RDATE:19190701T002841
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0400
>
> TZOFFSETTO:+0300
>
> TZNAME:MSK
>
> DTSTART:19190816T000000
>
> RDATE:19190816T000000
>
> RDATE:19211001T000000
>
> RDATE:19811001T000000
>
> RDATE:19821001T000000
>
> RDATE:19831001T000000
>
> RDATE:19840930T030000
>
> RDATE:19850929T030000
>
> RDATE:19860928T030000
>
> RDATE:19870927T030000
>
> RDATE:19880925T030000
>
> RDATE:19890924T030000
>
> RDATE:19900930T030000
>
> RDATE:19920926T220000
>
> RDATE:19930926T030000
>
> RDATE:19940925T030000
>
> RDATE:19950924T030000
>
> RDATE:19961027T030000
>
> RDATE:19971026T030000
>
> RDATE:19981025T030000
>
> RDATE:19991031T030000
>
> RDATE:20001029T030000
>
> RDATE:20011028T030000
>
> RDATE:20021027T030000
>
> RDATE:20031026T030000
>
> RDATE:20041031T030000
>
> RDATE:20051030T030000
>
> RDATE:20061029T030000
>
> RDATE:20071028T030000
>
> RDATE:20081026T030000
>
> RDATE:20091025T030000
>
> RDATE:20101031T030000
>
> RDATE:20141026T020000
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0400
>
> TZNAME:MSD
>
> DTSTART:19210214T230000
>
> RDATE:19210214T230000
>
> RDATE:19810401T000000
>
> RDATE:19820401T000000
>
> RDATE:19830401T000000
>
> RDATE:19840401T000000
>
> RDATE:19850331T020000
>
> RDATE:19860330T020000
>
> RDATE:19870329T020000
>
> RDATE:19880327T020000
>
> RDATE:19890326T020000
>
> RDATE:19900325T020000
>
> RDATE:19920328T230000
>
> RDATE:19930328T020000
>
> RDATE:19940327T020000
>
> RDATE:19950326T020000
>
> RDATE:19960331T020000
>
> RDATE:19970330T020000
>
> RDATE:19980329T020000
>
> RDATE:19990328T020000
>
> RDATE:20000326T020000
>
> RDATE:20010325T020000
>
> RDATE:20020331T020000
>
> RDATE:20030330T020000
>
> RDATE:20040328T020000
>
> RDATE:20050327T020000
>
> RDATE:20060326T020000
>
> RDATE:20070325T020000
>
> RDATE:20080330T020000
>
> RDATE:20090329T020000
>
> RDATE:20100328T020000
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0400
>
> TZOFFSETTO:+0500
>
> TZNAME:MSM
>
> DTSTART:19210320T220000
>
> RDATE:19210320T220000
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0500
>
> TZOFFSETTO:+0400
>
> TZNAME:MSD
>
> DTSTART:19210831T230000
>
> RDATE:19210831T230000
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0200
>
> TZNAME:EET
>
> DTSTART:19221001T010000
>
> RDATE:19221001T010000
>
> RDATE:19910929T040000
>
> END:STANDARD
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0200
>
> TZOFFSETTO:+0300
>
> TZNAME:MSK
>
> DTSTART:19300621T010000
>
> RDATE:19300621T010000
>
> RDATE:19920119T030000
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0300
>
> TZNAME:EEST
>
> DTSTART:19910331T020000
>
> RDATE:19910331T020000
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0400
>
> TZNAME:MSK
>
> DTSTART:20110327T020000
>
> RDATE:20110327T020000
>
> END:STANDARD
>
> END:VTIMEZONE
>
> BEGIN:VEVENT
>
> DTSTAMP:20161107T114923Z
>
> DTSTART;TZID=Europe/Moscow:20161107T144400
>
> DTEND;TZID=Europe/Moscow:20161107T154400
>
> SUMMARY:New Event
>
> DESCRIPTION:
>
> SEQUENCE:0
>
> LOCATION:
>
> TRANSP:OPAQUE
>
> UID:20161107T114528Z-uidGen@192.168.122.1
>
> ATTENDEE;ROLE=REQ-PARTICIPANT;CN=yakovlev_nd@krvostok.ru:mailto:yakovl
> ev_
>
> nd@krvostok.ru
>
> ORGANIZER;CN=admin:mailto:nik@krvostok.ru
>
> END:VEVENT
>
> END:VCALENDAR
>
>
>
> From: Maxim Solodovnik [mailto:solomax666@gmail.com]
> Sent: Monday, November 7, 2016 4:03 PM
> To: Openmeetings user-list
> Subject: Re: OM 3.1.4 time zone Europe/Moscow
>
>
>
> What TZ is in ICS file?
>
> could you share *.ics attachment?
>
>
>
> On Mon, Nov 7, 2016 at 7:22 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
>
> Hello,
>
>
>
> It's used OM 3.1.4 + Centos 7.
>
> When creating events with Notification type - iCal the invite.ics file
> attached to email has an incorrect invitation time that it is less by
> one hour from time zone Europe/Moscow. Also these corresponding
> events are shown in Outlook calendar incorrectly.
>
> iCal works good if for example Europe/Minsk time zone is set.
>
>
>
> There is the Europe/Moscow time zone on Centos:
>
>
>
> # timedatectl status
>
> Local time: Пн 2016-11-07 14:22:05 MSK
>
> Universal time: Пн 2016-11-07 11:22:05 UTC
>
> RTC time: Пн 2016-11-07 11:52:05
>
> Time zone: Europe/Moscow (MSK, +0300)
>
> -------------------------------------------------
>
> # rpm -qa | grep tzdata*
>
> tzdata-2016h-1.el7.noarch
>
> joda-time-2.2-3.tzdata2013c.el7.noarch
>
> tzdata-java-2016h-1.el7.noarch
>
> -----------------------------------------------
>
> # java -jar tzupdater.jar -V
>
> tzupdater version 2.1.0-b04
>
> JRE tzdata version: tzdata2016h
>
> ------------------------------------------------
>
>
>
> Is there any idea where is the problem?
>
>
>
> Best regards
>
> Nikolay
>
>
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
--
WBR
Maxim aka solomax
Re: OM 3.1.4 time zone Europe/Moscow
Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks for the update!
Would appreciate if you can share investigation results :)
On Tue, Nov 8, 2016 at 12:50 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
> Local Java is Version 8 Update 111 (build 1.8.0_111-b14), the latest Java
> Platform.
>
> Time zone on the local PC is Europe/Moscow.
>
> But you are right and the reason should be looked for in the local computer
> not in OM.
>
> I has just made one more experiment.
>
> If I use a web-client to connect to the e-mail (not Outlook) the calendar in
> the web client (Zimbra) has correct time assigned to a meet.
>
> If I download these emails to Outlook then one shows incorrect time in its
> calendar.
>
> OK, further I will look for a solution independently.
>
>
>
> Thanks for reply,
>
> Nikolay
>
>
>
> From: Maxim Solodovnik [mailto:solomax666@gmail.com]
> Sent: Monday, November 7, 2016 4:56 PM
>
>
> To: Openmeetings user-list
> Subject: Re: OM 3.1.4 time zone Europe/Moscow
>
>
>
> Really weird,
>
>
>
> just tried to create event in my Thunderbird (Ubuntu 16.10 all updates)
>
> Europe/Moscow 17:00-18:00
>
>
>
> I have Asia/Novosibirsk TZ (GMT +7, MSK + 4)
>
> Thunderbird shows event time as 20:00-21:00
>
> It is clearly wrong :(
>
> Will try to update local java and double-check
>
>
>
> On Mon, Nov 7, 2016 at 8:22 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
>
> Ics file as text
>
>
>
> BEGIN:VCALENDAR
>
> PRODID:-//Events Calendar//iCal4j 1.0//EN
>
> VERSION:2.0
>
> CALSCALE:GREGORIAN
>
> METHOD:CANCEL
>
> BEGIN:VTIMEZONE
>
> TZID:Europe/Moscow
>
> TZURL:http://tzurl.org/zoneinfo/Europe/Moscow
>
> X-LIC-LOCATION:Europe/Moscow
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+023017
>
> TZOFFSETTO:+023017
>
> TZNAME:MMT
>
> DTSTART:18800101T000000
>
> RDATE:18800101T000000
>
> END:STANDARD
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+023017
>
> TZOFFSETTO:+023119
>
> TZNAME:MMT
>
> DTSTART:19160703T002943
>
> RDATE:19160703T002943
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+023119
>
> TZOFFSETTO:+033119
>
> TZNAME:MST
>
> DTSTART:19170701T232841
>
> RDATE:19170701T232841
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+033119
>
> TZOFFSETTO:+023119
>
> TZNAME:MMT
>
> DTSTART:19171228T002841
>
> RDATE:19171228T002841
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+023119
>
> TZOFFSETTO:+043119
>
> TZNAME:MDST
>
> DTSTART:19180531T222841
>
> RDATE:19180531T222841
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+043119
>
> TZOFFSETTO:+033119
>
> TZNAME:MST
>
> DTSTART:19180916T002841
>
> RDATE:19180916T002841
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+033119
>
> TZOFFSETTO:+043119
>
> TZNAME:MDST
>
> DTSTART:19190531T222841
>
> RDATE:19190531T222841
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+043119
>
> TZOFFSETTO:+0400
>
> TZNAME:MSD
>
> DTSTART:19190701T002841
>
> RDATE:19190701T002841
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0400
>
> TZOFFSETTO:+0300
>
> TZNAME:MSK
>
> DTSTART:19190816T000000
>
> RDATE:19190816T000000
>
> RDATE:19211001T000000
>
> RDATE:19811001T000000
>
> RDATE:19821001T000000
>
> RDATE:19831001T000000
>
> RDATE:19840930T030000
>
> RDATE:19850929T030000
>
> RDATE:19860928T030000
>
> RDATE:19870927T030000
>
> RDATE:19880925T030000
>
> RDATE:19890924T030000
>
> RDATE:19900930T030000
>
> RDATE:19920926T220000
>
> RDATE:19930926T030000
>
> RDATE:19940925T030000
>
> RDATE:19950924T030000
>
> RDATE:19961027T030000
>
> RDATE:19971026T030000
>
> RDATE:19981025T030000
>
> RDATE:19991031T030000
>
> RDATE:20001029T030000
>
> RDATE:20011028T030000
>
> RDATE:20021027T030000
>
> RDATE:20031026T030000
>
> RDATE:20041031T030000
>
> RDATE:20051030T030000
>
> RDATE:20061029T030000
>
> RDATE:20071028T030000
>
> RDATE:20081026T030000
>
> RDATE:20091025T030000
>
> RDATE:20101031T030000
>
> RDATE:20141026T020000
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0400
>
> TZNAME:MSD
>
> DTSTART:19210214T230000
>
> RDATE:19210214T230000
>
> RDATE:19810401T000000
>
> RDATE:19820401T000000
>
> RDATE:19830401T000000
>
> RDATE:19840401T000000
>
> RDATE:19850331T020000
>
> RDATE:19860330T020000
>
> RDATE:19870329T020000
>
> RDATE:19880327T020000
>
> RDATE:19890326T020000
>
> RDATE:19900325T020000
>
> RDATE:19920328T230000
>
> RDATE:19930328T020000
>
> RDATE:19940327T020000
>
> RDATE:19950326T020000
>
> RDATE:19960331T020000
>
> RDATE:19970330T020000
>
> RDATE:19980329T020000
>
> RDATE:19990328T020000
>
> RDATE:20000326T020000
>
> RDATE:20010325T020000
>
> RDATE:20020331T020000
>
> RDATE:20030330T020000
>
> RDATE:20040328T020000
>
> RDATE:20050327T020000
>
> RDATE:20060326T020000
>
> RDATE:20070325T020000
>
> RDATE:20080330T020000
>
> RDATE:20090329T020000
>
> RDATE:20100328T020000
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0400
>
> TZOFFSETTO:+0500
>
> TZNAME:MSM
>
> DTSTART:19210320T220000
>
> RDATE:19210320T220000
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0500
>
> TZOFFSETTO:+0400
>
> TZNAME:MSD
>
> DTSTART:19210831T230000
>
> RDATE:19210831T230000
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0200
>
> TZNAME:EET
>
> DTSTART:19221001T010000
>
> RDATE:19221001T010000
>
> RDATE:19910929T040000
>
> END:STANDARD
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0200
>
> TZOFFSETTO:+0300
>
> TZNAME:MSK
>
> DTSTART:19300621T010000
>
> RDATE:19300621T010000
>
> RDATE:19920119T030000
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0300
>
> TZNAME:EEST
>
> DTSTART:19910331T020000
>
> RDATE:19910331T020000
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0400
>
> TZNAME:MSK
>
> DTSTART:20110327T020000
>
> RDATE:20110327T020000
>
> END:STANDARD
>
> END:VTIMEZONE
>
> BEGIN:VEVENT
>
> DTSTAMP:20161107T114923Z
>
> DTSTART;TZID=Europe/Moscow:20161107T144400
>
> DTEND;TZID=Europe/Moscow:20161107T154400
>
> SUMMARY:New Event
>
> DESCRIPTION:
>
> SEQUENCE:0
>
> LOCATION:
>
> TRANSP:OPAQUE
>
> UID:20161107T114528Z-uidGen@192.168.122.1
>
> ATTENDEE;ROLE=REQ-PARTICIPANT;CN=yakovlev_nd@krvostok.ru:mailto:yakovlev_
>
> nd@krvostok.ru
>
> ORGANIZER;CN=admin:mailto:nik@krvostok.ru
>
> END:VEVENT
>
> END:VCALENDAR
>
>
>
> From: Maxim Solodovnik [mailto:solomax666@gmail.com]
> Sent: Monday, November 7, 2016 4:03 PM
> To: Openmeetings user-list
> Subject: Re: OM 3.1.4 time zone Europe/Moscow
>
>
>
> What TZ is in ICS file?
>
> could you share *.ics attachment?
>
>
>
> On Mon, Nov 7, 2016 at 7:22 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
>
> Hello,
>
>
>
> It's used OM 3.1.4 + Centos 7.
>
> When creating events with Notification type - iCal the invite.ics file
> attached to email has an incorrect invitation time that it is less by one
> hour from time zone Europe/Moscow. Also these corresponding events are
> shown in Outlook calendar incorrectly.
>
> iCal works good if for example Europe/Minsk time zone is set.
>
>
>
> There is the Europe/Moscow time zone on Centos:
>
>
>
> # timedatectl status
>
> Local time: Пн 2016-11-07 14:22:05 MSK
>
> Universal time: Пн 2016-11-07 11:22:05 UTC
>
> RTC time: Пн 2016-11-07 11:52:05
>
> Time zone: Europe/Moscow (MSK, +0300)
>
> -------------------------------------------------
>
> # rpm -qa | grep tzdata*
>
> tzdata-2016h-1.el7.noarch
>
> joda-time-2.2-3.tzdata2013c.el7.noarch
>
> tzdata-java-2016h-1.el7.noarch
>
> -----------------------------------------------
>
> # java -jar tzupdater.jar -V
>
> tzupdater version 2.1.0-b04
>
> JRE tzdata version: tzdata2016h
>
> ------------------------------------------------
>
>
>
> Is there any idea where is the problem?
>
>
>
> Best regards
>
> Nikolay
>
>
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
--
WBR
Maxim aka solomax
RE: OM 3.1.4 time zone Europe/Moscow
Posted by "Yakovlev N." <ya...@krvostok.ru>.
Local Java is Version 8 Update 111 (build 1.8.0_111-b14), the latest Java Platform.
Time zone on the local PC is Europe/Moscow.
But you are right and the reason should be looked for in the local computer not in OM.
I has just made one more experiment.
If I use a web-client to connect to the e-mail (not Outlook) the calendar in the web client (Zimbra) has correct time assigned to a meet.
If I download these emails to Outlook then one shows incorrect time in its calendar.
OK, further I will look for a solution independently.
Thanks for reply,
Nikolay
From: Maxim Solodovnik [mailto:solomax666@gmail.com]
Sent: Monday, November 7, 2016 4:56 PM
To: Openmeetings user-list
Subject: Re: OM 3.1.4 time zone Europe/Moscow
Really weird,
just tried to create event in my Thunderbird (Ubuntu 16.10 all updates)
Europe/Moscow 17:00-18:00
I have Asia/Novosibirsk TZ (GMT +7, MSK + 4)
Thunderbird shows event time as 20:00-21:00
It is clearly wrong :(
Will try to update local java and double-check
On Mon, Nov 7, 2016 at 8:22 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
Ics file as text
BEGIN:VCALENDAR
PRODID:-//Events Calendar//iCal4j 1.0//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:Europe/Moscow
TZURL:http://tzurl.org/zoneinfo/Europe/Moscow
X-LIC-LOCATION:Europe/Moscow
BEGIN:STANDARD
TZOFFSETFROM:+023017
TZOFFSETTO:+023017
TZNAME:MMT
DTSTART:18800101T000000
RDATE:18800101T000000
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:+023017
TZOFFSETTO:+023119
TZNAME:MMT
DTSTART:19160703T002943
RDATE:19160703T002943
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+023119
TZOFFSETTO:+033119
TZNAME:MST
DTSTART:19170701T232841
RDATE:19170701T232841
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+033119
TZOFFSETTO:+023119
TZNAME:MMT
DTSTART:19171228T002841
RDATE:19171228T002841
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+023119
TZOFFSETTO:+043119
TZNAME:MDST
DTSTART:19180531T222841
RDATE:19180531T222841
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+043119
TZOFFSETTO:+033119
TZNAME:MST
DTSTART:19180916T002841
RDATE:19180916T002841
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+033119
TZOFFSETTO:+043119
TZNAME:MDST
DTSTART:19190531T222841
RDATE:19190531T222841
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+043119
TZOFFSETTO:+0400
TZNAME:MSD
DTSTART:19190701T002841
RDATE:19190701T002841
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0400
TZOFFSETTO:+0300
TZNAME:MSK
DTSTART:19190816T000000
RDATE:19190816T000000
RDATE:19211001T000000
RDATE:19811001T000000
RDATE:19821001T000000
RDATE:19831001T000000
RDATE:19840930T030000
RDATE:19850929T030000
RDATE:19860928T030000
RDATE:19870927T030000
RDATE:19880925T030000
RDATE:19890924T030000
RDATE:19900930T030000
RDATE:19920926T220000
RDATE:19930926T030000
RDATE:19940925T030000
RDATE:19950924T030000
RDATE:19961027T030000
RDATE:19971026T030000
RDATE:19981025T030000
RDATE:19991031T030000
RDATE:20001029T030000
RDATE:20011028T030000
RDATE:20021027T030000
RDATE:20031026T030000
RDATE:20041031T030000
RDATE:20051030T030000
RDATE:20061029T030000
RDATE:20071028T030000
RDATE:20081026T030000
RDATE:20091025T030000
RDATE:20101031T030000
RDATE:20141026T020000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0300
TZOFFSETTO:+0400
TZNAME:MSD
DTSTART:19210214T230000
RDATE:19210214T230000
RDATE:19810401T000000
RDATE:19820401T000000
RDATE:19830401T000000
RDATE:19840401T000000
RDATE:19850331T020000
RDATE:19860330T020000
RDATE:19870329T020000
RDATE:19880327T020000
RDATE:19890326T020000
RDATE:19900325T020000
RDATE:19920328T230000
RDATE:19930328T020000
RDATE:19940327T020000
RDATE:19950326T020000
RDATE:19960331T020000
RDATE:19970330T020000
RDATE:19980329T020000
RDATE:19990328T020000
RDATE:20000326T020000
RDATE:20010325T020000
RDATE:20020331T020000
RDATE:20030330T020000
RDATE:20040328T020000
RDATE:20050327T020000
RDATE:20060326T020000
RDATE:20070325T020000
RDATE:20080330T020000
RDATE:20090329T020000
RDATE:20100328T020000
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+0400
TZOFFSETTO:+0500
TZNAME:MSM
DTSTART:19210320T220000
RDATE:19210320T220000
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+0500
TZOFFSETTO:+0400
TZNAME:MSD
DTSTART:19210831T230000
RDATE:19210831T230000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
TZNAME:EET
DTSTART:19221001T010000
RDATE:19221001T010000
RDATE:19910929T040000
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
TZNAME:MSK
DTSTART:19300621T010000
RDATE:19300621T010000
RDATE:19920119T030000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0300
TZOFFSETTO:+0300
TZNAME:EEST
DTSTART:19910331T020000
RDATE:19910331T020000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0400
TZNAME:MSK
DTSTART:20110327T020000
RDATE:20110327T020000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20161107T114923Z
DTSTART;TZID=Europe/Moscow:20161107T144400
DTEND;TZID=Europe/Moscow:20161107T154400
SUMMARY:New Event
DESCRIPTION:
SEQUENCE:0
LOCATION:
TRANSP:OPAQUE
UID:20161107T114528Z-uidGen@192.168.122.1 <ma...@192.168.122.1>
ATTENDEE;ROLE=REQ-PARTICIPANT;CN=yakovlev_nd@krvostok.ru:mailto:yakovlev_
nd@krvostok.ru
ORGANIZER;CN=admin:mailto:nik@krvostok.ru
END:VEVENT
END:VCALENDAR
From: Maxim Solodovnik [mailto:solomax666@gmail.com]
Sent: Monday, November 7, 2016 4:03 PM
To: Openmeetings user-list
Subject: Re: OM 3.1.4 time zone Europe/Moscow
What TZ is in ICS file?
could you share *.ics attachment?
On Mon, Nov 7, 2016 at 7:22 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
Hello,
It's used OM 3.1.4 + Centos 7.
When creating events with Notification type - iCal the invite.ics file attached to email has an incorrect invitation time that it is less by one hour from time zone Europe/Moscow. Also these corresponding events are shown in Outlook calendar incorrectly.
iCal works good if for example Europe/Minsk time zone is set.
There is the Europe/Moscow time zone on Centos:
# timedatectl status
Local time: Пн 2016-11-07 14:22:05 MSK
Universal time: Пн 2016-11-07 11:22:05 UTC
RTC time: Пн 2016-11-07 11:52:05
Time zone: Europe/Moscow (MSK, +0300)
-------------------------------------------------
# rpm -qa | grep tzdata*
tzdata-2016h-1.el7.noarch
joda-time-2.2-3.tzdata2013c.el7.noarch
tzdata-java-2016h-1.el7.noarch
-----------------------------------------------
# java -jar tzupdater.jar -V
tzupdater version 2.1.0-b04
JRE tzdata version: tzdata2016h
------------------------------------------------
Is there any idea where is the problem?
Best regards
Nikolay
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
Re: OM 3.1.4 time zone Europe/Moscow
Posted by Maxim Solodovnik <so...@gmail.com>.
Really weird,
just tried to create event in my Thunderbird (Ubuntu 16.10 all updates)
Europe/Moscow 17:00-18:00
I have Asia/Novosibirsk TZ (GMT +7, MSK + 4)
Thunderbird shows event time as 20:00-21:00
It is clearly wrong :(
Will try to update local java and double-check
On Mon, Nov 7, 2016 at 8:22 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
> Ics file as text
>
>
>
> BEGIN:VCALENDAR
>
> PRODID:-//Events Calendar//iCal4j 1.0//EN
>
> VERSION:2.0
>
> CALSCALE:GREGORIAN
>
> METHOD:CANCEL
>
> BEGIN:VTIMEZONE
>
> TZID:Europe/Moscow
>
> TZURL:http://tzurl.org/zoneinfo/Europe/Moscow
>
> X-LIC-LOCATION:Europe/Moscow
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+023017
>
> TZOFFSETTO:+023017
>
> TZNAME:MMT
>
> DTSTART:18800101T000000
>
> RDATE:18800101T000000
>
> END:STANDARD
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+023017
>
> TZOFFSETTO:+023119
>
> TZNAME:MMT
>
> DTSTART:19160703T002943
>
> RDATE:19160703T002943
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+023119
>
> TZOFFSETTO:+033119
>
> TZNAME:MST
>
> DTSTART:19170701T232841
>
> RDATE:19170701T232841
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+033119
>
> TZOFFSETTO:+023119
>
> TZNAME:MMT
>
> DTSTART:19171228T002841
>
> RDATE:19171228T002841
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+023119
>
> TZOFFSETTO:+043119
>
> TZNAME:MDST
>
> DTSTART:19180531T222841
>
> RDATE:19180531T222841
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+043119
>
> TZOFFSETTO:+033119
>
> TZNAME:MST
>
> DTSTART:19180916T002841
>
> RDATE:19180916T002841
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+033119
>
> TZOFFSETTO:+043119
>
> TZNAME:MDST
>
> DTSTART:19190531T222841
>
> RDATE:19190531T222841
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+043119
>
> TZOFFSETTO:+0400
>
> TZNAME:MSD
>
> DTSTART:19190701T002841
>
> RDATE:19190701T002841
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0400
>
> TZOFFSETTO:+0300
>
> TZNAME:MSK
>
> DTSTART:19190816T000000
>
> RDATE:19190816T000000
>
> RDATE:19211001T000000
>
> RDATE:19811001T000000
>
> RDATE:19821001T000000
>
> RDATE:19831001T000000
>
> RDATE:19840930T030000
>
> RDATE:19850929T030000
>
> RDATE:19860928T030000
>
> RDATE:19870927T030000
>
> RDATE:19880925T030000
>
> RDATE:19890924T030000
>
> RDATE:19900930T030000
>
> RDATE:19920926T220000
>
> RDATE:19930926T030000
>
> RDATE:19940925T030000
>
> RDATE:19950924T030000
>
> RDATE:19961027T030000
>
> RDATE:19971026T030000
>
> RDATE:19981025T030000
>
> RDATE:19991031T030000
>
> RDATE:20001029T030000
>
> RDATE:20011028T030000
>
> RDATE:20021027T030000
>
> RDATE:20031026T030000
>
> RDATE:20041031T030000
>
> RDATE:20051030T030000
>
> RDATE:20061029T030000
>
> RDATE:20071028T030000
>
> RDATE:20081026T030000
>
> RDATE:20091025T030000
>
> RDATE:20101031T030000
>
> RDATE:20141026T020000
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0400
>
> TZNAME:MSD
>
> DTSTART:19210214T230000
>
> RDATE:19210214T230000
>
> RDATE:19810401T000000
>
> RDATE:19820401T000000
>
> RDATE:19830401T000000
>
> RDATE:19840401T000000
>
> RDATE:19850331T020000
>
> RDATE:19860330T020000
>
> RDATE:19870329T020000
>
> RDATE:19880327T020000
>
> RDATE:19890326T020000
>
> RDATE:19900325T020000
>
> RDATE:19920328T230000
>
> RDATE:19930328T020000
>
> RDATE:19940327T020000
>
> RDATE:19950326T020000
>
> RDATE:19960331T020000
>
> RDATE:19970330T020000
>
> RDATE:19980329T020000
>
> RDATE:19990328T020000
>
> RDATE:20000326T020000
>
> RDATE:20010325T020000
>
> RDATE:20020331T020000
>
> RDATE:20030330T020000
>
> RDATE:20040328T020000
>
> RDATE:20050327T020000
>
> RDATE:20060326T020000
>
> RDATE:20070325T020000
>
> RDATE:20080330T020000
>
> RDATE:20090329T020000
>
> RDATE:20100328T020000
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0400
>
> TZOFFSETTO:+0500
>
> TZNAME:MSM
>
> DTSTART:19210320T220000
>
> RDATE:19210320T220000
>
> END:DAYLIGHT
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0500
>
> TZOFFSETTO:+0400
>
> TZNAME:MSD
>
> DTSTART:19210831T230000
>
> RDATE:19210831T230000
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0200
>
> TZNAME:EET
>
> DTSTART:19221001T010000
>
> RDATE:19221001T010000
>
> RDATE:19910929T040000
>
> END:STANDARD
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0200
>
> TZOFFSETTO:+0300
>
> TZNAME:MSK
>
> DTSTART:19300621T010000
>
> RDATE:19300621T010000
>
> RDATE:19920119T030000
>
> END:STANDARD
>
> BEGIN:DAYLIGHT
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0300
>
> TZNAME:EEST
>
> DTSTART:19910331T020000
>
> RDATE:19910331T020000
>
> END:DAYLIGHT
>
> BEGIN:STANDARD
>
> TZOFFSETFROM:+0300
>
> TZOFFSETTO:+0400
>
> TZNAME:MSK
>
> DTSTART:20110327T020000
>
> RDATE:20110327T020000
>
> END:STANDARD
>
> END:VTIMEZONE
>
> BEGIN:VEVENT
>
> DTSTAMP:20161107T114923Z
>
> DTSTART;TZID=Europe/Moscow:20161107T144400
>
> DTEND;TZID=Europe/Moscow:20161107T154400
>
> SUMMARY:New Event
>
> DESCRIPTION:
>
> SEQUENCE:0
>
> LOCATION:
>
> TRANSP:OPAQUE
>
> UID:20161107T114528Z-uidGen@192.168.122.1
>
> ATTENDEE;ROLE=REQ-PARTICIPANT;CN=yakovlev_nd@krvostok.ru:mailto:yakovlev_
>
> nd@krvostok.ru
>
> ORGANIZER;CN=admin:mailto:nik@krvostok.ru
>
> END:VEVENT
>
> END:VCALENDAR
>
>
>
> *From:* Maxim Solodovnik [mailto:solomax666@gmail.com]
> *Sent:* Monday, November 7, 2016 4:03 PM
> *To:* Openmeetings user-list
> *Subject:* Re: OM 3.1.4 time zone Europe/Moscow
>
>
>
> What TZ is in ICS file?
>
> could you share *.ics attachment?
>
>
>
> On Mon, Nov 7, 2016 at 7:22 PM, Yakovlev N. <ya...@krvostok.ru>
> wrote:
>
> Hello,
>
>
>
> It's used OM 3.1.4 + Centos 7.
>
> When creating events with Notification type - iCal the invite.ics file
> attached to email has an incorrect invitation time that it is less by one
> hour from time zone Europe/Moscow. Also these corresponding events are
> shown in Outlook calendar incorrectly.
>
> iCal works good if for example Europe/Minsk time zone is set.
>
>
>
> There is the Europe/Moscow time zone on Centos:
>
>
>
> # timedatectl status
>
> Local time: Пн 2016-11-07 14:22:05 MSK
>
> Universal time: Пн 2016-11-07 11:22:05 UTC
>
> RTC time: Пн 2016-11-07 11:52:05
>
> Time zone: Europe/Moscow (MSK, +0300)
>
> -------------------------------------------------
>
> # rpm -qa | grep tzdata*
>
> tzdata-2016h-1.el7.noarch
>
> joda-time-2.2-3.tzdata2013c.el7.noarch
>
> tzdata-java-2016h-1.el7.noarch
>
> -----------------------------------------------
>
> # java -jar tzupdater.jar -V
>
> tzupdater version 2.1.0-b04
>
> JRE tzdata version: tzdata2016h
>
> ------------------------------------------------
>
>
>
> Is there any idea where is the problem?
>
>
>
> Best regards
>
> Nikolay
>
>
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
RE: OM 3.1.4 time zone Europe/Moscow
Posted by "Yakovlev N." <ya...@krvostok.ru>.
Ics file as text
BEGIN:VCALENDAR
PRODID:-//Events Calendar//iCal4j 1.0//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:Europe/Moscow
TZURL:http://tzurl.org/zoneinfo/Europe/Moscow
X-LIC-LOCATION:Europe/Moscow
BEGIN:STANDARD
TZOFFSETFROM:+023017
TZOFFSETTO:+023017
TZNAME:MMT
DTSTART:18800101T000000
RDATE:18800101T000000
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:+023017
TZOFFSETTO:+023119
TZNAME:MMT
DTSTART:19160703T002943
RDATE:19160703T002943
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+023119
TZOFFSETTO:+033119
TZNAME:MST
DTSTART:19170701T232841
RDATE:19170701T232841
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+033119
TZOFFSETTO:+023119
TZNAME:MMT
DTSTART:19171228T002841
RDATE:19171228T002841
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+023119
TZOFFSETTO:+043119
TZNAME:MDST
DTSTART:19180531T222841
RDATE:19180531T222841
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+043119
TZOFFSETTO:+033119
TZNAME:MST
DTSTART:19180916T002841
RDATE:19180916T002841
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+033119
TZOFFSETTO:+043119
TZNAME:MDST
DTSTART:19190531T222841
RDATE:19190531T222841
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+043119
TZOFFSETTO:+0400
TZNAME:MSD
DTSTART:19190701T002841
RDATE:19190701T002841
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0400
TZOFFSETTO:+0300
TZNAME:MSK
DTSTART:19190816T000000
RDATE:19190816T000000
RDATE:19211001T000000
RDATE:19811001T000000
RDATE:19821001T000000
RDATE:19831001T000000
RDATE:19840930T030000
RDATE:19850929T030000
RDATE:19860928T030000
RDATE:19870927T030000
RDATE:19880925T030000
RDATE:19890924T030000
RDATE:19900930T030000
RDATE:19920926T220000
RDATE:19930926T030000
RDATE:19940925T030000
RDATE:19950924T030000
RDATE:19961027T030000
RDATE:19971026T030000
RDATE:19981025T030000
RDATE:19991031T030000
RDATE:20001029T030000
RDATE:20011028T030000
RDATE:20021027T030000
RDATE:20031026T030000
RDATE:20041031T030000
RDATE:20051030T030000
RDATE:20061029T030000
RDATE:20071028T030000
RDATE:20081026T030000
RDATE:20091025T030000
RDATE:20101031T030000
RDATE:20141026T020000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0300
TZOFFSETTO:+0400
TZNAME:MSD
DTSTART:19210214T230000
RDATE:19210214T230000
RDATE:19810401T000000
RDATE:19820401T000000
RDATE:19830401T000000
RDATE:19840401T000000
RDATE:19850331T020000
RDATE:19860330T020000
RDATE:19870329T020000
RDATE:19880327T020000
RDATE:19890326T020000
RDATE:19900325T020000
RDATE:19920328T230000
RDATE:19930328T020000
RDATE:19940327T020000
RDATE:19950326T020000
RDATE:19960331T020000
RDATE:19970330T020000
RDATE:19980329T020000
RDATE:19990328T020000
RDATE:20000326T020000
RDATE:20010325T020000
RDATE:20020331T020000
RDATE:20030330T020000
RDATE:20040328T020000
RDATE:20050327T020000
RDATE:20060326T020000
RDATE:20070325T020000
RDATE:20080330T020000
RDATE:20090329T020000
RDATE:20100328T020000
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+0400
TZOFFSETTO:+0500
TZNAME:MSM
DTSTART:19210320T220000
RDATE:19210320T220000
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+0500
TZOFFSETTO:+0400
TZNAME:MSD
DTSTART:19210831T230000
RDATE:19210831T230000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
TZNAME:EET
DTSTART:19221001T010000
RDATE:19221001T010000
RDATE:19910929T040000
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
TZNAME:MSK
DTSTART:19300621T010000
RDATE:19300621T010000
RDATE:19920119T030000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0300
TZOFFSETTO:+0300
TZNAME:EEST
DTSTART:19910331T020000
RDATE:19910331T020000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0400
TZNAME:MSK
DTSTART:20110327T020000
RDATE:20110327T020000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20161107T114923Z
DTSTART;TZID=Europe/Moscow:20161107T144400
DTEND;TZID=Europe/Moscow:20161107T154400
SUMMARY:New Event
DESCRIPTION:
SEQUENCE:0
LOCATION:
TRANSP:OPAQUE
UID:20161107T114528Z-uidGen@192.168.122.1
ATTENDEE;ROLE=REQ-PARTICIPANT;CN=yakovlev_nd@krvostok.ru:mailto:yakovlev_
nd@krvostok.ru
ORGANIZER;CN=admin:mailto:nik@krvostok.ru
END:VEVENT
END:VCALENDAR
From: Maxim Solodovnik [mailto:solomax666@gmail.com]
Sent: Monday, November 7, 2016 4:03 PM
To: Openmeetings user-list
Subject: Re: OM 3.1.4 time zone Europe/Moscow
What TZ is in ICS file?
could you share *.ics attachment?
On Mon, Nov 7, 2016 at 7:22 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
Hello,
It's used OM 3.1.4 + Centos 7.
When creating events with Notification type - iCal the invite.ics file attached to email has an incorrect invitation time that it is less by one hour from time zone Europe/Moscow. Also these corresponding events are shown in Outlook calendar incorrectly.
iCal works good if for example Europe/Minsk time zone is set.
There is the Europe/Moscow time zone on Centos:
# timedatectl status
Local time: Пн 2016-11-07 14:22:05 MSK
Universal time: Пн 2016-11-07 11:22:05 UTC
RTC time: Пн 2016-11-07 11:52:05
Time zone: Europe/Moscow (MSK, +0300)
-------------------------------------------------
# rpm -qa | grep tzdata*
tzdata-2016h-1.el7.noarch
joda-time-2.2-3.tzdata2013c.el7.noarch
tzdata-java-2016h-1.el7.noarch
-----------------------------------------------
# java -jar tzupdater.jar -V
tzupdater version 2.1.0-b04
JRE tzdata version: tzdata2016h
------------------------------------------------
Is there any idea where is the problem?
Best regards
Nikolay
--
WBR
Maxim aka solomax
Re: OM 3.1.4 time zone Europe/Moscow
Posted by Maxim Solodovnik <so...@gmail.com>.
What TZ is in ICS file?
could you share *.ics attachment?
On Mon, Nov 7, 2016 at 7:22 PM, Yakovlev N. <ya...@krvostok.ru> wrote:
> Hello,
>
>
>
> It's used OM 3.1.4 + Centos 7.
>
> When creating events with Notification type - iCal the invite.ics file
> attached to email has an incorrect invitation time that it is less by one
> hour from time zone Europe/Moscow. Also these corresponding events are
> shown in Outlook calendar incorrectly.
>
> iCal works good if for example Europe/Minsk time zone is set.
>
>
>
> There is the Europe/Moscow time zone on Centos:
>
>
>
> # timedatectl status
>
> Local time: Пн 2016-11-07 14:22:05 MSK
>
> Universal time: Пн 2016-11-07 11:22:05 UTC
>
> RTC time: Пн 2016-11-07 11:52:05
>
> Time zone: Europe/Moscow (MSK, +0300)
>
> -------------------------------------------------
>
> # rpm -qa | grep tzdata*
>
> tzdata-2016h-1.el7.noarch
>
> joda-time-2.2-3.tzdata2013c.el7.noarch
>
> tzdata-java-2016h-1.el7.noarch
>
> -----------------------------------------------
>
> # java -jar tzupdater.jar -V
>
> tzupdater version 2.1.0-b04
>
> JRE tzdata version: tzdata2016h
>
> ------------------------------------------------
>
>
>
> Is there any idea where is the problem?
>
>
>
> Best regards
>
> Nikolay
>
>
>
--
WBR
Maxim aka solomax