You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to dotCMS User Group
I started getting the dotcms@dotcms_test FATAL: invalid value for parameter "TimeZone": "MST" error after updating a number of packages on my Linux. The error is logged in the Postgresql log file. The Postgresql uses "America/Denver" timezone. Is there a way to set dotCMS timezone to "America/Denver" in the docker compose YAML file?
Thanks,
Ivan
Ivan
unread,
Oct 18, 2024, 11:56:45 AMOct 18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to dotCMS User Group
Also, the dotCMS seems to initially start and I can access the site for about 10 seconds, but then it hangs and I start seeing the dotcms@dotcms_test FATAL: invalid value for parameter "TimeZone": "MST" exception in the Postgresql log. It looks like it finishes running some startup script that eventually causes the site to stop working and the error to apear.
Thanks,
Ivan
Ivan
unread,
Oct 18, 2024, 6:33:03 PMOct 18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to dotCMS User Group
RESOLVED: The culprit ended up being the tzdata package which is obviously related to the timezone. The new version 2024b-3 seems to break things and cause the FATAL: invalid value for parameter "TimeZone": "MST" error in dotcms. The solution was to "apt-mark hold tzdata" when doing my update of packages. The version 2024a-4 seems to be working fine and not causing the error.