Hi @flamber,
Here is the diagnostic info:
{
"browser-info": {
"language": "en-US",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.90 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10",
"java.vendor": "Private Build",
"java.vendor.url": "http://java.oracle.com/",
"java.version": "1.8.0_222",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "25.222-b10",
"os.name": "Linux",
"os.version": "4.15.0-65-generic",
"user.language": "en",
"user.timezone": "Etc/UTC"
},
"metabase-info": {
"databases": [
"mysql"
],
"hosting-env": "unknown",
"application-database": "mysql",
"run-mode": "prod",
"version": {
"tag": "v0.33.3",
"date": "2019-09-20",
"branch": "release-0.33.x",
"hash": "86d32bf"
},
"settings": {
"report-timezone": "Pacific/Auckland"
}
}
}
We’re using MySQL 5.7.27 for our internal metadata db.
This is what we see in the Metabase logs at the same time as getting the error:
[6234cbc5-c879-4a2e-98c6-eceda734afb1] 2019-10-03T12:18:52+13:00 ERROR metabase.driver.sql-jdbc.execute Failed to set timezone:
SQLException:
Message: (conn=90) Unknown or incorrect time zone: 'Pacific/Auckland'
SQLState: HY000
Error Code: 1298
[6234cbc5-c879-4a2e-98c6-eceda734afb1] 2019-10-03T12:18:52+13:00 DEBUG metabase.middleware.log POST /api/dataset 200 [ASYNC: completed] 117.7 ms (9 DB calls) Jetty threads: 2/50 (4 idle, 0 queued) (85 total active threads) Queries in flight: 0
[6234cbc5-c879-4a2e-98c6-eceda734afb1] 2019-10-03T12:18:58+13:00 DEBUG metabase.middleware.log GET /api/database/2/autocomplete_suggestions 200 32.8 ms (6 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (85 total active threads) Queries in flight: 0
[6234cbc5-c879-4a2e-98c6-eceda734afb1] 2019-10-03T12:18:59+13:00 DEBUG metabase.middleware.log GET /api/database/2/autocomplete_suggestions 200 19.2 ms (6 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (85 total active threads) Queries in flight: 0
[6234cbc5-c879-4a2e-98c6-eceda734afb1] 2019-10-03T12:19:13+13:00 WARN metabase.util.encryption Cannot decrypt encrypted string. Have you changed or forgot to set MB_ENCRYPTION_SECRET_KEY? 0 > -32 ("java.util.Arrays.copyOfRange(Arrays.java:3519)"
"buddy.core.bytes$slice.invokeStatic(bytes.clj:47)"
"buddy.core.bytes$slice.invokePrim(bytes.clj)"
"buddy.core.crypto$fn__23094.invokeStatic(crypto.clj:485)"
"buddy.core.crypto$fn__23094.invoke(crypto.clj:478)"
"clojure.lang.MultiFn.invoke(MultiFn.java:229)"
"buddy.core.crypto$decrypt.invokeStatic(crypto.clj:572)"
"buddy.core.crypto$decrypt.invoke(crypto.clj:559)"
"--> util.encryption$decrypt.invokeStatic(encryption.clj:65)"
"util.encryption$decrypt.invoke(encryption.clj:57)"
"util.encryption$maybe_decrypt.invokeStatic(encryption.clj:108)"
"util.encryption$maybe_decrypt.doInvoke(encryption.clj:96)"
"models.setting.cache$restore_cache_BANG_.invokeStatic(cache.clj:122)"
"models.setting.cache$restore_cache_BANG_.invoke(cache.clj:118)"
"models.setting$fn__18970$set_string_BANG___18975$fn__18976.invoke(setting.clj:283)"
"models.setting$fn__18970$set_string_BANG___18975.invoke(setting.clj:268)"
"models.setting$set_timestamp_BANG_.invokeStatic(setting.clj:343)"
"models.setting$set_timestamp_BANG_.invoke(setting.clj:340)"
"models.setting$set_BANG_.invokeStatic(setting.clj:386)"
"models.setting$set_BANG_.invoke(setting.clj:374)"
"models.setting$setting_fn$fn__19016.invoke(setting.clj:459)"
"metabot.instance$update_last_checkin_BANG_.invokeStatic(instance.clj:63)"
"metabot.instance$update_last_checkin_BANG_.invoke(instance.clj:60)"
"metabot.instance$check_and_update_instance_status_BANG_.invokeStatic(instance.clj:117)"
"metabot.instance$check_and_update_instance_status_BANG_.invoke(instance.clj:108)"
"metabot.instance$start_instance_monitor_BANG_$fn__55191.invoke(instance.clj:132)")
This error did only start happening after we upgraded to v0.33, however that may just be a coincidence as we also have our old 0.29.3 environment running in parallel (so we could test out 0.33 before switching over) and we are also seeing the issue on 0.29.3.
I’ve just had another play with a few more of our questions and have found some that don’t use SELECT *
that also exhibit the problem. For example, this question that selects some specific fields gives me the error if I try to add on more field to the SELECT statement:
SELECT m.company_name, p.first_name, p.last_name, DATE_FORMAT(pf.createdAt, '%a, %d-%b-%Y') AS agreement_created_date, job_title, department_name
FROM `personfile` pf
JOIN member m ON pf.member_id = m.id
JOIN person p ON pf.person_id = p.id
WHERE pf.`type` = 'employment-agreement'
AND pf.createdAt BETWEEN DATE_ADD(NOW(), INTERVAL -1 WEEK) AND NOW()
AND m.package_id <> 1
ORDER BY pf.member_id;
And sorry, I should have said that I see the error when I try to run the edited question even before saving.
Hopefully this info helps, let me know if there’s anything else I can provide you with.
Thanks