How to upgrade from 2.11.5 to 3.0.0

[NiTRoeSE]

Hi,.. I have noticed that the latest image (3.0.0) not work.. What is the recommended or working way to get the new version running wihout loosing projects / jobs / keys etc ?

I start the container following way..

sudo docker run --rm -p 4440:4440 \
  -e EXTERNAL_SERVER_URL=https://my.url \
  -e SMTP_HOST=myemailhost \
  -e SMTP_PORT=25 \
  -e SMTP_DEFAULT_FROM=myemail \
  -e RUNDECK_ADMIN_PASSWORD=mypassword \
  -v /docker/rundeck_cron_manager/data/rundec_ssh:/var/lib/rundeck/.ssh/ \
  -v /docker/rundeck_cron_manager/data/rundec_etc:/etc/rundeck \
  -v /docker/rundeck_cron_manager/data/rundec_var:/var/rundeck \
  -v /docker/rundeck_cron_manager/data/rundec_mysql:/var/lib/mysql \
  -v /docker/rundeck_cron_manager/data/rundec_var_log:/var/log/rundeck \
  -v /docker/rundeck_cron_manager/data/rundec_logs:/var/lib/rundeck/logs \
  -v /docker/rundeck_cron_manager/data/rundec_var_storage:/var/lib/rundeck/var/storage \
  -v /docker/rundeck_cron_manager/data/rundec_opt_plugins:/opt/rundeck-plugins \
  --name rundeck -t jordan/rundeck:latest

Since new version container starts but gives following errors:

Starting Supervisor...
It can take anywhere from 30 seconds up to a few minutes for the UI
to become available depending on your container/host VM resources.
All further output is stdout/stderr from the supervisor process.

2018-08-03 13:51:34,450 CRIT Supervisor running as root (no user in config file)
2018-08-03 13:51:34,451 WARN For [program:rundeck], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
2018-08-03 13:51:34,451 WARN For [program:mysql], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
2018-08-03 13:51:34,451 INFO Included extra file "/etc/supervisor/conf.d/rundeck.conf" during parsing
2018-08-03 13:51:34,459 INFO RPC interface 'supervisor' initialized
2018-08-03 13:51:34,459 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2018-08-03 13:51:34,459 INFO supervisord started with pid 408
2018-08-03 13:51:35,461 INFO spawned: 'fatalservice' with pid 411
2018-08-03 13:51:35,462 INFO spawned: 'rundeck' with pid 412
2018-08-03 13:51:35,464 INFO spawned: 'mysql' with pid 413
READY
03.08.2018 13:51:35.474 - Starting mysql
Starting MariaDB database server: mysqld03.08.2018 13:51:35.543 - Starting rundeckd2018-08-03 13:51:36,545 INFO success: fatalservice entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-03 13:51:36,545 INFO success: rundeck entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-03 13:51:36,545 INFO success: mysql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
.
2018-08-03 13:51:40,551 INFO exited: rundeck (exit status 0; expected)
2018-08-03 13:51:41,553 INFO spawned: 'rundeck' with pid 727
03.08.2018 13:51:41.575 - Starting rundeckd2018-08-03 13:51:42,575 INFO success: rundeck entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-03 13:51:46,583 INFO exited: rundeck (exit status 0; expected)
2018-08-03 13:51:47,585 INFO spawned: 'rundeck' with pid 777
03.08.2018 13:51:47.604 - Starting rundeckd2018-08-03 13:51:48,606 INFO success: rundeck entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-03 13:51:52,612 INFO exited: rundeck (exit status 0; expected)
2018-08-03 13:51:53,615 INFO spawned: 'rundeck' with pid 825
03.08.2018 13:51:53.638 - Starting rundeckd2018-08-03 13:51:54,639 INFO success: rundeck entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-03 13:51:58,647 INFO exited: rundeck (exit status 0; expected)
2018-08-03 13:51:59,649 INFO spawned: 'rundeck' with pid 873
03.08.2018 13:51:59.670 - Starting rundeckd2018-08-03 13:52:00,672 INFO success: rundeck entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-03 13:52:04,678 INFO exited: rundeck (exit status 0; expected)
2018-08-03 13:52:05,681 INFO spawned: 'rundeck' with pid 921
03.08.2018 13:52:05.702 - Starting rundeckd2018-08-03 13:52:06,703 INFO success: rundeck entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-03 13:52:10,711 INFO exited: rundeck (exit status 0; expected)
2018-08-03 13:52:11,713 INFO spawned: 'rundeck' with pid 971
03.08.2018 13:52:11.732 - Starting rundeckd2018-08-03 13:52:12,734 INFO success: rundeck entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-03 13:52:16,788 INFO exited: rundeck (exit status 0; expected)

The Container itself dont die but webinterface never comes up..

Thanks in advanced

[jjethwa]

Hi @NiTRoeSE

Sorry to hear about your issue. It looks like the Rundeck process is failing to start properly. Can you provide the service.log entries?

[NiTRoeSE]

Hi Jordan, sorry for late reply.. but there was a weekend ;) Only entry in service.log which appears after i fire up the 3.0.0 container is:

Error:Could not find or load main class .var.lib.rundeck

All other entries of this file are from the working 2.11.5 Container.

[jjethwa]

Hi @NiTRoeSE

Hmm, that's a weird error. Can you try using the 3.0.0 tag? The latest tag is unstable, so you might have pulled a work in progress 😛

[NiTRoeSE]

Hi @jjethwa, i have tested it with 3.0.0 and at the moment with 3.0.1 but it doesn't work. Rundeck process can't start properly, it´s the same error message like 3.0.0. Error:Could not find or load main class .var.lib.rundeck

Any Ideas how to get the container running without loose of projects etc ?

[jjethwa]

Hi @NiTRoeSE

This is a really weird one. Just to check, are you able to start a fresh 3.0.1 container (no volumes) without an issue? If so, the next step would be starting up a container with new empty volumes then exporting your projects from the old to the new.

It could be something related to the /etc/rundeck/profile too. There were breaking changes there. You could try testing by backing up the current profile, copying this one: https://github.com/jjethwa/rundeck/blob/master/content/opt/rundeck-defaults/profile and trying to start 3.0.1 again.

[NiTRoeSE]

Thanks for the tip with the profile, but this alone have not fixed the startup from rundeck for me. Finally i have deleted the whole content of : /docker/rundeck_cron_manager/data/rundec_etc:/etc/rundeck-volume (which also contains the profile)... after that container starts successfully and all projects and jobs are present and runs fine so far.

Thanks @jjethwa for your help :)

/ closed

[ozsk]

@NiTRoeSE removing /etc/rundeck directory also works for me. Thanks.

[rsmartins78]

I have the same problem here, from version 2.11.4 to 3.0.13, error 'Could not find or load main class .var.lib.rundeck' in service.log

With no volumes in /etc/rundeck, the error persists.

[jjethwa]

Hi @rsmartins78

What volumes are you using?

[jjethwa]

Closing as no more updates