All Apps and Add-ons

Splunk DB Connect getting time zone issue

joey77
Engager

Hi folks,

I have been trying to test Splunk DB connect on my local machine before deploying it live.
I've installed a mysql instance, so I can test the connection.

So trying to set up my first connection as a test.
But I always get this error message:

The server time zone value 'Est' is
unrecognized or represents more than
one time zone. You must configure
either the server or JDBC driver (via
the 'serverTimezone' configuration
property) to use a more specifc time
zone value if you want to utilize time
zone support.

I'm using splunk 8.0.1, java 8, mysql 8, splunk db connect 3.

0 Karma
1 Solution

joey77
Engager

I've solve my problem with this: ?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC

at the end of the URL used to connect to DB

View solution in original post

0 Karma

joey77
Engager

I've solve my problem with this: ?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC

at the end of the URL used to connect to DB

0 Karma

rajasekhar14
Path Finder

did you install mysql on the same sever where you install the db-connect app?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Fuel Your Journey: What’s Waiting for You at the .conf26 Acceleration Station

Navigating the show floor at .conf26 isn't just about keynotes and technical breakout sessions; it's also ...

Join the Final Session of the Data Management & Federation Bootcamp Series

Over the past three sessions of the Data Management & Federation Bootcamp Series, we've explored how to build ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...