Error in startup after upgrading to 1.51.2
-
Hello,
I was running version 1.48.3 and am trying to upgrade to 1.51.2 because of the vulnerability. After upgrading the version in my Dockerfile, and restarting the container, I am getting an error in the log file. My database is a Postgres database on Azure.
--------------------------------------------------------------------------------------------------------- --------------------------------- Starting FusionAuth version [1.51.2] ---------------------------------- --------------------------------------------------------------------------------------------------------- 2024-07-13 09:45:07.295 AM INFO io.fusionauth.api.plugin.guice.PluginModule - No plugins found 2024-07-13 09:45:10.149 AM INFO io.fusionauth.api.service.system.NodeService - Node [b936de13-c292-416e-acdb-8b18759cba97] started. 2024-07-13 09:45:17.500 AM INFO io.fusionauth.api.configuration.DefaultFusionAuthConfiguration - Loading FusionAuth configuration file [/usr/local/fusionauth/config/fusionauth.properties] 2024-07-13 09:45:17.501 AM INFO io.fusionauth.api.configuration.DefaultFusionAuthConfiguration - Dynamically set property [fusionauth-app.url] set to [http://localhost:9011] 2024-07-13 09:45:17.540 AM INFO com.inversoft.configuration.BasePropertiesFileInversoftConfiguration - - Overriding default value of property [database.mysql.enforce-utf8mb4] with value [true] - Overriding default value of property [fusionauth-app.runtime-mode] with value [production] - Overriding default value of property [search.type] with value [database] 2024-07-13 09:45:17.662 AM INFO com.inversoft.jdbc.hikari.DataSourceProvider - Connecting to PostgreSQL database at [jdbc:postgresql://invoicingapi-db-server.postgres.database.azure.com:5432/fusionauth] 2024-07-13 09:45:17.692 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. 2024-07-13 09:45:17.711 AM INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting... 2024-07-13 09:45:20.528 AM INFO com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.postgresql.jdbc.PgConnection@6579cdbb 2024-07-13 09:45:20.577 AM INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed. 2024-07-13 09:45:37.031 AM INFO com.inversoft.scheduler.DefaultScheduler - Starting up scheduler 2024-07-13 09:45:37.033 AM INFO com.inversoft.scheduler.DefaultScheduler - Scheduler is running 2024-07-13 09:45:37.203 AM ERROR com.inversoft.scheduler.LogAndRetainFailureHandler - The scheduled service [class io.fusionauth.api.service.cache.ApplicationCacheLoader] failed but will be re-run. org.apache.ibatis.exceptions.PersistenceException: ### Error querying database. Cause: org.postgresql.util.PSQLException: ERROR: column a.userinfo_populate_lambdas_id does not exist Position: 3467 ### The error may exist in io/fusionauth/api/domain/ApplicationMapper.xml ### The error may involve defaultParameterMap ### The error occurred while setting parameters
I'm not sure how to diagnose this issue. Is it obvious what has gone wrong?
-
@ronn316 if you want to use silent mode during the upgrade
https://fusionauth.io/docs/get-started/download-and-install/silent-mode
-
@ronn316 I believe there was an database change that was required in 1.50 https://fusionauth.io/docs/release-notes/#version-1-50-0
You will need to check the upgrade info
https://fusionauth.io/docs/operate/deploy/upgradespecifically the database migration in silent mode
https://fusionauth.io/docs/operate/deploy/upgrade#downtime-and-database-migrations -
@Alex-Patterson Hi. It's not clear to me exactly how to do the system upgrade. I'm running in Production mode. It says the following on your link: "In a production runtime mode, or with silent configuration enabled, the upgrade will occur automatically during startup."
So I shouldn't need to do anything.
-
@ronn316 if you want to use silent mode during the upgrade
https://fusionauth.io/docs/get-started/download-and-install/silent-mode
-
@Alex-Patterson That did the trick! Enabled silent mode in the fusionauth.properties file and no more errors.
-