Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JDBC driver? #364

Closed
lilyannh opened this issue Nov 7, 2019 · 4 comments
Closed

JDBC driver? #364

lilyannh opened this issue Nov 7, 2019 · 4 comments
Assignees
Labels
support Further information is requested or user requires assistance

Comments

@lilyannh
Copy link

lilyannh commented Nov 7, 2019

No suitable driver found for jdbc:postgres

Description

Trying to set up fusionauth app + search server on Ubuntu 18.04 (digital ocean), and connect to a database on an external (heroku, just during development) server. Downloaded and installed the package as per instructions here but I am getting the following error when starting fustionauth-app

From fusionauth-app-.log:
io.fusionauth.app.maintenance.FusionAuthMaintenanceModeWorkflow - Determine database status : ORDINARY_USER_CANNOT_CONNECT [No suitable driver found for jdbc:postgres://[host]:5432/[database]]

I tried installing https://packages.ubuntu.com/disco/libpostgresql-jdbc-java but that didn't change anything.

Any help would be appreciated!

@robotdan
Copy link
Member

robotdan commented Nov 8, 2019

We provide our own JDBC driver for postgresql so you shouldn't need to install anything else.

Can you provide any additional details about your configuration and the full log?

May be some additional details in issue #95 regarding connection to third party cloud managed databases services.

@lilyannh
Copy link
Author

lilyannh commented Nov 8, 2019

Here is the full log. There's not much to my configuration right now. I had spun up the empty Digital Ocean server just to test out FusionAuth & how it would hook into my existing dev db on Heroku. So it's literally just the FusionAuth install on that server. The Heroku box is running a graphql server and postgres with remote access via port 5432 allowed.

I was not aware of issue #95 but I do think that it affects me; I cannot create a database with the credentials provided by Heroku, and instead created a new schema called fusionauth with the needed tables. However based on the error message, it doesn't seem like this issue is coming into play yet.

07-Nov-2019 21:30:18.181 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
07-Nov-2019 21:30:18.613 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-9011"]
07-Nov-2019 21:30:18.638 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
07-Nov-2019 21:30:18.670 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["https-jsse-nio-9013"]
07-Nov-2019 21:30:19.230 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
07-Nov-2019 21:30:19.248 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-9019"]
07-Nov-2019 21:30:19.255 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
07-Nov-2019 21:30:19.256 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1422 ms
07-Nov-2019 21:30:19.269 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
07-Nov-2019 21:30:19.269 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.43
21:30:21,747 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
21:30:21,747 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
21:30:21,747 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:file:/usr/local/fusionauth/fusionauth-app/web/WEB-INF/lib/fusionauth-app-1.11.0.jar!/logback.xml]
21:30:21,766 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@459e4398 - URL [jar:file:/usr/local/fusionauth/fusionauth-app/web/WEB-INF/lib/fusionauth-app-1.11.0.jar!/logback.xml] is not of type file
21:30:21,801 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
21:30:21,820 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Will scan for changes in [jar:file:/usr/local/fusionauth/fusionauth-app/web/WEB-INF/lib/fusionauth-app-1.11.0.jar!/logback.xml] 
21:30:21,820 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Setting ReconfigureOnChangeTask scanning period to 1 minutes
21:30:21,821 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
21:30:21,828 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
21:30:21,841 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
21:30:21,884 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [io.fusionauth] to INFO
21:30:21,884 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [io.fusionauth] to false
21:30:21,884 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[io.fusionauth]
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.primeframework] to INFO
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.primeframework] to false
21:30:21,885 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[org.primeframework]
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.inversoft.migration] to INFO
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [com.inversoft.migration] to false
21:30:21,885 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[com.inversoft.migration]
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.inversoft.maintenance] to INFO
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [com.inversoft.maintenance] to false
21:30:21,885 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[com.inversoft.maintenance]
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [io.fusionauth.api.plugin.importer] to DEBUG
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [io.fusionauth.api.plugin.importer] to false
21:30:21,885 |-ERROR in ch.qos.logback.core.joran.action.AppenderRefAction - Could not find an appender named [FILE]. Did you define it below instead of above in the configuration file?
21:30:21,885 |-ERROR in ch.qos.logback.core.joran.action.AppenderRefAction - See http://logback.qos.ch/codes.html#appender_order for more details.
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.kafka.common.utils.AppInfoParser] to ERROR
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.apache.kafka.common.utils.AppInfoParser] to false
21:30:21,885 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[org.apache.kafka.common.utils.AppInfoParser]
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.kafka.clients.consumer.ConsumerConfig] to ERROR
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.apache.kafka.clients.consumer.ConsumerConfig] to false
21:30:21,885 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[org.apache.kafka.clients.consumer.ConsumerConfig]
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.kafka.clients.producer.ProducerConfig] to ERROR
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.apache.kafka.clients.producer.ProducerConfig] to false
21:30:21,885 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[org.apache.kafka.clients.producer.ProducerConfig]
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.kafka.clients.producer.KafkaProducer] to ERROR
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.apache.kafka.clients.producer.KafkaProducer] to false
21:30:21,885 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[org.apache.kafka.clients.producer.KafkaProducer]
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.kafka.clients.NetworkClient] to ERROR
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.apache.kafka.clients.NetworkClient] to false
21:30:21,885 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[org.apache.kafka.clients.NetworkClient]
21:30:21,885 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
21:30:21,886 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT]
21:30:21,886 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
21:30:21,886 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@1337d11 - Registering current configuration as safe fallback point

Nov 07, 2019 9:30:21 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Nov 07, 2019 9:30:23.481 PM INFO  io.fusionauth.api.configuration.PropertiesFileFusionAuthConfiguration - Loading FusionAuth configuration file [/usr/local/fusionauth/fusionauth-app/apache-tomcat/../../config/fusionauth.properties]
Nov 07, 2019 9:30:23.489 PM INFO  io.fusionauth.api.configuration.PropertiesFileFusionAuthConfiguration - Dynamically set property [fusionauth-app.public-url] set to [http://10.46.0.6:9011]
Nov 07, 2019 9:30:23.489 PM INFO  io.fusionauth.api.configuration.PropertiesFileFusionAuthConfiguration - FusionAuth Runtime Mode [Production]
Nov 07, 2019 9:30:24.203 PM INFO  io.fusionauth.api.configuration.PropertiesFileFusionAuthConfiguration - Loading FusionAuth configuration file [/usr/local/fusionauth/fusionauth-app/apache-tomcat/../../config/fusionauth.properties]
Nov 07, 2019 9:30:24.207 PM INFO  io.fusionauth.api.configuration.PropertiesFileFusionAuthConfiguration - Dynamically set property [fusionauth-app.public-url] set to [http://10.46.0.6:9011]
Nov 07, 2019 9:30:24.207 PM INFO  io.fusionauth.api.configuration.PropertiesFileFusionAuthConfiguration - FusionAuth Runtime Mode [Production]
Nov 07, 2019 9:30:24.408 PM INFO  io.fusionauth.app.maintenance.FusionAuthMaintenanceModeWorkflow - Determine database status : ORDINARY_USER_CANNOT_CONNECT [No suitable driver found for jdbc:postgres://ec2-23-21-148-223.compute-1.amazonaws.com:5432/dj4i4ahttu55g]
Nov 07, 2019 9:30:24.409 PM INFO  org.primeframework.mvc.servlet.PrimeServletContextListener - Initializing Prime
Nov 07, 2019 9:30:24.410 PM INFO  io.fusionauth.app.maintenance.guice.FusionAuthMaintenanceModeModule - 

---------------------------------------------------------------------------------------------------------
--------------------------------------- Entering Maintenance Mode ---------------------------------------
---------------------------------------------------------------------------------------------------------

Nov 07, 2019 9:30:24.518 PM INFO  io.fusionauth.api.configuration.PropertiesFileFusionAuthConfiguration - Loading FusionAuth configuration file [/usr/local/fusionauth/fusionauth-app/apache-tomcat/../../config/fusionauth.properties]
Nov 07, 2019 9:30:24.519 PM INFO  io.fusionauth.api.configuration.PropertiesFileFusionAuthConfiguration - Dynamically set property [fusionauth-app.public-url] set to [http://10.46.0.6:9011]
Nov 07, 2019 9:30:24.519 PM INFO  io.fusionauth.api.configuration.PropertiesFileFusionAuthConfiguration - FusionAuth Runtime Mode [Production]
Nov 07, 2019 9:30:24.527 PM INFO  com.inversoft.maintenance.MaintenanceModePoller - Poller started to Wait for configuration to be completed.

@robotdan
Copy link
Member

robotdan commented Nov 8, 2019

Ah, ok. I think I see the issue. The PostgreSQL jdbc connection is jdbc:postgresql and you have jdbc:postgresq.

https://jdbc.postgresql.org/documentation/80/connect.html

@robotdan robotdan self-assigned this Nov 8, 2019
@robotdan robotdan added the support Further information is requested or user requires assistance label Nov 8, 2019
@lilyannh
Copy link
Author

lilyannh commented Nov 9, 2019

Ah! What a dumb mistake. You are correct; all is working now. Since I had am using a fusionauth schema inside of an existing database (instead of a standalone fusionauth database), I had to also add ?currentSchema=fusionauth to the end of the connection string. Thanks for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Further information is requested or user requires assistance
Projects
None yet
Development

No branches or pull requests

2 participants