Upgrade from 3.3.0 to 5.3.0

14 views
Skip to first unread message

Ivneet Singh Wahi

unread,
Jun 12, 2024, 9:08:57 AMJun 12
to rundeck-discuss
Performed an upgrade from 3.3.0 to 5.3.0 using yum upgrade.
Now rundeck application is not getting started and below is the error for the same
Database is maintained in a file:  rundeckdb.mv.db

Logs: Service.log 2019-01-21 19:23:46.956 ERROR --- [tp1588609461-29] rundeck.controllers.EditOptsController : Invalid ...skipping... at org.springframework.boot.web.servlet.ServletContextInitializerBeans.addServletContextInitializerBeans(ServletContextInitializerBeans.java:98) ~[spring-boot-2.7.18.jar!/:2.7.18] at org.springframework.boot.web.servlet.ServletContextInitializerBeans.<init>(ServletContextInitializerBeans.java:86) ~[spring-boot-2.7.18.jar!/:2.7.18] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.getServletContextInitializerBeans(ServletWebServerApplicationContext.java:262) ~[spring-boot-2.7.18.jar!/:2.7.18]
rundeck.logs

[2024-06-11T00:45:09,008] ERROR quartzjobs.ExecutionJob [quartzScheduler_Worker-2] - Unable to start Job execution: Job "refresh_materialized_views_cron" {{Job 543d9088-1396-470c-8f73-4d5070e042e2}} is currently being executed {{Execution 45922}}
[2024-06-11T00:45:10,007] ERROR quartzjobs.ExecutionJob [quartzScheduler_Worker-7] - Unable to start Job execution: Job "refresh_materialized_views_cron" {{Job 543d9088-1396-470c-8f73-4d5070e0
...skipping...
        at org.springframework.boot.web.servlet.ServletContextInitializerBeans.getOrderedBeansOfType(ServletContextInitializerBeans.java:204) ~[spring-boot-2.7.18.jar!/:2.7.18]
        at org.springframework.boot.web.servlet.ServletContextInitializerBeans.addServletContextInitializerBeans(ServletContextInitializerBeans.java:98) ~[spring-boot-2.7.18.jar!/:2.7.18]
        at org.springframework.boot.web.servlet.ServletContextInitializerBeans.<init>(ServletContextInitializerBeans.java:86) ~[spring-boot-2.7.18.jar!/:2.7.18]
        at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.getServletContextInitializerBeans(ServletWebServerApplicationContext.java:262) ~[spring-boot-2.7.18.jar!/:2.7.18]
        at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.selfInitialize(ServletWebServerApplicationContext.java:236) ~[spring-boot-2.7.18.jar!/:2.7.18]
        at org.springframework.boot.web.embedded.jetty.ServletContextInitializerConfiguration.callInitializers(ServletContextInitializerConfiguration.java:65) ~[spring-boot-2.7.18.jar!/:2.7.18]
        at org.springframework.boot.web.embedded.jetty.ServletContextInitializerConfiguration.configure(ServletContextInitializerConfiguration.java:54) ~[spring-boot-2.7.18.jar!/:2.7.18]
        at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:498) ~[jetty-webapp-9.4.53.v20231009.jar!/:9.4.53.v20231009]


rundeck-config.properties file content 

loglevel.default=INFO
rdeck.base=/var/lib/rundeck
rss.enabled=false

grails.serverURL=https://hostname:443
dataSource.dbCreate = update
dataSource.url = jdbc:h2:file:/var/lib/rundeck/data/rundeckdb;DB_CLOSE_ON_EXIT=FALSE;NON_KEYWORDS=MONTH,HOUR,MINUTE,YEAR,SECONDS
grails.plugin.databasemigration.updateOnStart=false
dataSource.properties.maximumPoolSize=100
#dataSource.driverClassName=org.mariadb.jdbc.Driver

# Encryption for key storage
#rundeck.storage.provider.1.type=db
#rundeck.storage.provider.1.path=keys

#rundeck.storage.converter.1.type=jasypt-encryption
#rundeck.storage.converter.1.path=keys
#rundeck.storage.converter.1.config.encryptorType=custom
#rundeck.storage.converter.1.config.password=944f7b72a5c9fd5a
#rundeck.storage.converter.1.config.algorithm=PBEWITHSHA256AND128BITAES-CBC-BC
#rundeck.storage.converter.1.config.provider=BC

# Encryption for project config storage
#rundeck.projectsStorageType=db

#rundeck.config.storage.converter.1.type=jasypt-encryption
#rundeck.config.storage.converter.1.path=projects
#rundeck.config.storage.converter.1.config.password=944f7b72a5c9fd5a
#rundeck.config.storage.converter.1.config.encryptorType=custom
#rundeck.config.storage.converter.1.config.algorithm=PBEWITHSHA256AND128BITAES-CBC-BC
#rundeck.config.storage.converter.1.config.provider=BC

#rundeck.feature.repository.enabled=true

rundeck.log4j.config.file = /etc/rundeck/log4j2.properties
rundeck.fileUpload.plugin.type=filesystem-temp




rac...@rundeck.com

unread,
Jun 12, 2024, 9:31:53 AMJun 12
to rundeck-discuss
Hi,

There is a significant gap between 3.3.0 and 5.3.0; at some time (Rundeck 4.1), you will move the H2 database (see here), and another migration for 5.0 is documented here.

I recommend reverting to 3.3, exporting your data, and importing it into a fresh Rundeck 5.3.0 instance. However, the key recommendation is to run your Rundeck new instance against a "real backend" such as MySQL or PostgreSQL. H2 is only used for testing. This guide should help you.

Regards.
Reply all
Reply to author
Forward
0 new messages