Connection error connecting to Snowflake

I have a trial Metabase setup going in AWS ElasticBeanstalk that is failing with a very odd error message:

JDBC driver internal error: exception creating result java.lang.NoClassDefFoundError: Could not initialize class net.snowflake.client.jdbc.internal.apache.arrow.memory.RootAllocator at net.snowflake.client.jdbc.SnowflakeResultSetSerializableV1.create(SnowflakeResultSetSerializableV1.java:577). {:message "JDBC driver internal error: exception creating result java.lang.NoClassDefFoundError: Could not initialize class net.snowflake.client.jdbc.internal.apache.arrow.memory.RootAllocator at net.snowflake.client.jdbc.SnowflakeResultSetSerializableV1.create(SnowflakeResultSetSerializableV1.java:577)."

I can confirm we have connectivity to Snowflake because if I use an incorrect username or password, it says so. If I try a bad hostname it will also give me a timeout error.

Hi @scubabear68
Post "Diagnostic Info" from Admin > Troubleshooting.

"browser-info": {
"language": "en-US",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6 Safari/605.1.15",
"vendor": "Apple Computer, Inc."
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "17.0.4.1+9-LTS",
"java.vendor": "Amazon.com Inc.",
"java.vendor.url": "Amazon Corretto Production-ready distribution of OpenJDK",
"java.version": "17.0.4.1",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "17.0.4.1+9-LTS",
"os.name": "Linux",
"os.version": "4.14.291-218.527.amzn2.x86_64",
"user.language": "en",
"user.timezone": "UTC"
},
"metabase-info": {
"databases": [
"h2"
],
"hosting-env": "unknown",
"application-database": "h2",
"application-database-details": {
"database": {
"name": "H2",
"version": "1.4.197 (2018-03-18)"
},
"jdbc-driver": {
"name": "H2 JDBC Driver",
"version": "1.4.197 (2018-03-18)"
}
},
"run-mode": "prod",
"version": {
"date": "2022-09-29",
"tag": "v0.44.4",
"branch": "release-x.44.x",
"hash": "382d728"
},
"settings": {
"report-timezone": null
}
}
}

@scubabear68 I'm not sure why you haven't followed our guides:
https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-elastic-beanstalk
But change to Java 11, and you absolutely do not want to use H2 as the application database on EB, since you'll lose all data on instance cycle.

Thanks, will try and let you know. Using H2 just now because we are playing around with it, will move to Postgres if we do a more serious eval.

Thank you, that worked perfectly. And I even went ahead and created a postgres metabase database in place of H2. Thanks for the quick responses.