I have scheduled free pulse to be send to slack but neither the scheduled nor the send slack now works. could some one please provide me a resolution
Hi @sumi.smartsense.com
Which version of Metabase? Post the Diagnostic Info from Admin > Troubleshooting.
What do you see in the log, when scheduled or clicking send now?
You might be seeing one of these issues, but without more information, then it’s hard to know:
https://github.com/metabase/metabase/issues/10088
https://github.com/metabase/metabase/issues/7986
{
“browser-info”: {
“language”: “en-US”,
“platform”: “Win32”,
“userAgent”: “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763”,
“vendor”: “”
},
“system-info”: {
“java.runtime.name”: “Java™ SE Runtime Environment”,
“java.runtime.version”: “1.8.0_181-b13”,
“java.vendor”: “Oracle Corporation”,
“java.vendor.url”: “http://java.oracle.com/”,
“java.version”: “1.8.0_181”,
“java.vm.name”: “Java HotSpot™ 64-Bit Server VM”,
“java.vm.version”: “25.181-b13”,
“os.name”: “Linux”,
“os.version”: “4.4.0-1092-aws”,
“user.language”: “en”,
“user.timezone”: “Etc/UTC”
},
“metabase-info”: {
“databases”: [
“mysql”
],
“hosting-env”: “unknown”,
“application-database”: “h2”,
“run-mode”: “prod”,
“version”: {
“tag”: “v1.33.3”,
“date”: “2019-09-20”,
“branch”: “enterprise-release-1.33.x”,
“hash”: “4755696”
},
“settings”: {
“report-timezone”: null
}
}
}
Log file:
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:10:27+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 13.8 ms (5 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:10:34+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 15.6 ms (6 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:10:36+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 13.8 ms (5 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:10:44+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 17.0 ms (6 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:10:55+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 18.3 ms (5 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:10:56+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 13.6 ms (5 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:11:12+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 14.6 ms (6 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:11:13+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 13.8 ms (6 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:11:18+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 20.0 ms (6 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:11:27+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 14.7 ms (5 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:11:33+05:30 ERROR metabase.public-settings.metastore Error validating token: Token is expired.
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:11:33+05:30 ERROR metabase.public-settings.metastore Error validating token: Token is expired.
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:11:33+05:30 ERROR metabase.public-settings.metastore Error validating token: Token is expired.
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:11:33+05:30 DEBUG metabase.middleware.log POST /api/dataset 200 [ASYNC: completed] 1.3 s (9 DB calls) Jetty threads: 2/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:02+05:30 ERROR metabase.public-settings.metastore Error validating token: Token is expired.
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:02+05:30 ERROR metabase.public-settings.metastore Error validating token: Token is expired.
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:02+05:30 ERROR metabase.public-settings.metastore Error validating token: Token is expired.
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:04+05:30 DEBUG metabase.middleware.log POST /api/dataset 200 [ASYNC: completed] 1.3 s (9 DB calls) Jetty threads: 2/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:39+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 15.4 ms (6 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (607 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:44+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 14.3 ms (6 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:56+05:30 DEBUG metabase.middleware.log GET /api/database/3/autocomplete_suggestions 200 15.1 ms (5 DB calls) Jetty threads: 3/50 (4 idle, 0 queued) (608 total active threads) Queries in flight: 0
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:57+05:30 ERROR metabase.public-settings.metastore Error validating token: Token is expired.
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:57+05:30 ERROR metabase.public-settings.metastore Error validating token: Token is expired.
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:57+05:30 ERROR metabase.public-settings.metastore Error validating token: Token is expired.
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:57+05:30 ERROR metabase.public-settings.metastore Error validating token: Token is expired.
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:59+05:30 ERROR metabase.driver.sql-jdbc.execute nil
[02ecc971-f4e8-4eb5-a11e-6823cc777296] 2019-11-14T14:12:59+05:30 WARN metabase.query-processor.middleware.process-userland-query Query failure {:status :failed,
@sumi.smartsense.com You’re using the Enterprise Edition, then you should get support via email (support AT metabase.com).
We are still exploring this edition and havent subscribed it. could you please suggest me a resolution here?
Did you read the two issues I referenced?
The log you posted, does not contain anything related to the pulse, as far as I can see. So that makes it difficult to know what’s going on with your setup.
One thing I notice is the very high thread count (608 total active threads).
And the Token is expired, which I guess would mean that you’re not using any of the Enterprise features? Then just use the open source version.
The only recommendation I can give without any logs is to upgrade to latest release.
@flamber I have seen through both the issues.
we are using the latest release as 1.33.3 . after tiggers for three hours there was no more pulse received. No logs also getting generation. Please suggest an alternative help.
@sumi.smartsense.com
Latest Enterprise Edition is 1.33.5.1: https://hub.docker.com/r/metabase/metabase-enterprise/tags
I think the problem might be solved in that version, since several fixes to stale database connections was fixed.
@sumi.smartsense.com Okay, so now you’re using Community Edition. There’s a reason why those two issues are still open. They have both been given Priority 1 and milestone 0.34, but that’s not always a guarantee it will be fixed by 0.34.0
EDIT: Have you tried upgrading to Java 11 - one of the issue comments says that fixed it for them.
@flamber That is still a unstable version as per website, so we will not be able to go ahead with it as of now. Please suggest a bit more feasible solution
@sumi.smartsense.com That’s outdated information - there’s a PR waiting for approval.
Java 9 and 10 are not supported anymore, and does not work with Metabase.