FusionAuth randomly failing

NewIntellectual

I am running a self-hosted development instance of FusionAuth on AWS (t3a.micro). (I am hosting the Postgres database separately on RDS.) Eventually it stops listening on port 9011, breaking my test site. Part of the log is pasted below.

The problem appears to be the automatic removal of the node (why?) Supposedly a replacement is created but evidently it's no longer properly operating.

Help?

2021-01-07 2:14:21.952 AM INFO  com.inversoft.jdbc.hikari.DataSourceProvider - Connecting to PostgreSQL database at [jdbc:postgresql://OMITTED]
2021-01-07 2:14:21.954 AM WARN  com.zaxxer.hikari.HikariConfig - HikariPool-1 - idleTimeout has been set but has no effect because the pool is operating as a fixed size pool.
2021-01-07 2:14:21.956 AM INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2021-01-07 2:14:22.050 AM INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2021-01-07 2:14:23.474 AM INFO  com.inversoft.scheduler.DefaultScheduler - Starting up scheduler
2021-01-07 2:14:23.475 AM INFO  com.inversoft.scheduler.DefaultScheduler - Scheduler is running
2021-01-07 2:14:24.718 AM INFO  io.fusionauth.api.service.system.NodeService - Node [e7791e33-15f2-40e1-a09a-8b8bfb37a62e] with address [http://OMITTED:9011] removed because i
t has not checked in for the last [4672] seconds. Bye node.
2021-01-07 2:14:24.730 AM INFO  io.fusionauth.api.service.system.NodeService - Node [e7791e33-15f2-40e1-a09a-8b8bfb37a62e] added with address [http://OMITTED:9011]
2021-01-07 2:14:25.171 AM INFO  io.fusionauth.api.service.system.NodeService - Node [e7791e33-15f2-40e1-a09a-8b8bfb37a62e] promoted to master at [2021-01-07T02:14:25.171148Z], the p
revious master Node [c3072cb1-53f2-46a0-8bb0-320ad31a8dc5] had not checked in since [2021-01-07T00:55:48.632Z]
Jan 07, 2021 2:14:33 AM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom
WARNING: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [7,823] milliseconds.
07-Jan-2021 02:14:33.645 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-9011"]
07-Jan-2021 02:14:33.670 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["https-jsse-nio-9013"]
07-Jan-2021 02:14:33.674 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-127.0.0.1-9019"]
07-Jan-2021 02:14:33.677 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 18729 ms

dan

Hmmm. I don't think that the node being removed message is the issue. I think it is something similar to https://fusionauth.io/community/forum/topic/703/fusionauth-not-installing-on-google-cloud-platfrom-vm-instance where the t3a.micro has too many demands on the memory.

What else is running on the box?

NewIntellectual

I thought that might be a possibility and later tried a t3a.small (vs. t3a.micro) in a new install. So far that's has been working. (As far as anything else on the box - nothing. I like to dedicate at least one VM per major system.)