files and tasks don...
 
Notifications
Clear all

files and tasks don't work on RHEL install

1 Posts
1 Users
0 Reactions
446 Views
(@diito)
Joined: 11 months ago
Posts: 22
Topic starter  

I've been pulling my hair out trying to figure out why files and tasks don't work on my RHEL (Rocky 8) install.  I've followed the installation directions and made sure I didn't miss anything (I didn't).

The relevant log entry for files seems to be:

Caused by: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms.

Tasks:

 

0:18:08.878 [main] WARN  c.z.c.t.c.ServiceDiscoverHttpClient - Unable to retrieve the config hikari-max-pool-size from consul
00:18:08.882 [main] WARN  c.z.c.t.c.ServiceDiscoverHttpClient - Unable to retrieve the config hikari-min-idle-connections from consul
00:18:09.947 [main] ERROR com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Exception during pool initialization.
org.postgresql.util.PSQLException: Connection to 127.78.0.16:20000 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
       at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:342)
       at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:54)
       at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:253)
       at org.postgresql.Driver.makeConnection(Driver.java:434)
       at org.postgresql.Driver.connect(Driver.java:291)
       at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138)
       at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:359)
       at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
       at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:470)
       at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561)
       at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:100)
       at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:112)
       at io.ebeaninternal.server.core.DefaultContainer.checkDataSource(DefaultContainer.java:252)
       at io.ebeaninternal.server.core.DefaultContainer.createServer(DefaultContainer.java:89)
       at io.ebeaninternal.server.core.DefaultContainer.createServer(DefaultContainer.java:29)
       at io.ebean.DatabaseFactory.createInternal(DatabaseFactory.java:136)
       at io.ebean.DatabaseFactory.create(DatabaseFactory.java:85)
       at io.ebean.DatabaseFactory.createWithContextClassLoader(DatabaseFactory.java:111)
       at com.zextras.carbonio.tasks.dal.DatabaseConnectionManager.getEbeanDatabase(DatabaseConnectionManager.java:46)
       at com.zextras.carbonio.tasks.dal.repositories.impl.DbInfoRepositoryEbean.isDatabaseInitialized(DbInfoRepositoryEbean.java:35)
       at com.zextras.carbonio.tasks.dal.DatabaseInitializer.initialize(DatabaseInitializer.java:31)
       at com.zextras.carbonio.tasks.Boot.main(Boot.java:26)
Caused by: java.net.ConnectException: Connection refused

 

They definitely seem related some some issue with HikariPool


   
Quote