Power User

@gean-ivamoto Hmm. Seems like a good feature request. Can you please file one here: https://github.com/FusionAuth/fusionauth-issues/issues/

@brad Interesting. The error message Connection is not available, request timed out after 155614ms makes me suspicious, but I hear you.

I'm not familiar with the performance characteristics of Aurora, to be honest. We definitely have some folks running FusionAuth with that as their database, but it isn't typical and is not listed as a supported database.

You could try tweaking some of the database connection pool settings mentioned here: https://fusionauth.io/docs/reference/configuration

I'd also suggest googling around to see whether anyone else has issues with Hikari (our connection pool software) and the version/engine of Aurora that you are using.

Finally, if you have a plan that includes engineering support, I'd encourage you to open a support ticket.

Hi @brad ,

From here, it looks like the database was unavailable or FusionAuth ran out of connections.

@brad said in FusionAuth server completely locked up:

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

This can be caused by lambdas or connectors that are too slow to respond or are blocked from responding. It also can happen if FusionAuth is under extreme load and the database is undersized.

@kasir-barati Makes sense. Thanks for the feedback!

@kasir-barati Can you be more specific about your question?

@whuysentruit

Sure, we welcome feature requests from the community! Members can upvote them and we review the upvotes when considering future development.

Here's the GitHub repo to file the issue in: https://github.com/FusionAuth/fusionauth-issues/issues/

Please feel free to reference this forum post and give as many details as you can. This helps us understand the use case.

More about our roadmap process: https://fusionauth.io/docs/operate/roadmap/roadmap

Hiya @kasir-barati , welcome to the FusionAuth community!

Is there any kind of docker env or java env to pass to the container while creating it to create the api key automatically while creating container.

Unfortunately no. You can create a kickstart.json which has a single key. That's the recommended way to bootstrap FusionAuth if you want to manage everything through Terraform afterwards. Because you are correct, you'll need an API key.

We have a terraform guide we're about to publish, but you can view it here: https://github.com/FusionAuth/fusionauth-site/pull/2323/files . That is not fully reviewed, but should still be helpful to read.

Can you explain why you don't want to use Kickstart at all?

@jswgger007 Hmmm. That's weird.

What happens if you put console.log(process.env.FUSIONAUTH_ISSUER); right a t the top of the file?

Seems like the environment variable isn't being picked up for some reason.

What type of system are you using (windows, mac, linux, etc)?

@lambio hmmm. That code value changing seems to indicate that the authorization code grant isn't completing. This might cause the behavior you are seeing (because the tokens never get stored in the browser).

Are you running both systems on localhost? Are you using docker?

Sharing a bit more about what the system looks like would be helpful.

Another thing you can do is enable debugging in your fusionauth application configuration (go to the admin panel, edit your application, enable debugging) and then viewing the event log (go to system -> event log) as you try a login. That might be helpful info to share as well.

Thanks @daniel-lohse.

This additional info would be helpful:

• Type and version of your database
• Any negative issues you see, unless this is only a worrisome event log entry
• Any behavior you see that triggers these (if you have replication steps)

And I can file an issue.