Using docker-compose 10.1 Fix Pack 3 - waserver and waconsole wont start

[probalsil1]

I've been using the IWS 10.1 docker-compose and have recently tried to upgrade to the FP3 version. Neither the waserver nor waconsole will start. The errors seen are:

waserver error:
I: Running '/opt/wa/TWS/tws_tools/configureDb.sh --work_dir /tmp/wainst --log_dir /home/wauser/wadata --rdbmstype DB2 --dbhostname wa-db2 --dbport 50000 --dbuser db2inst1 --dbadminuser db2inst1 --dbname TWS --execsql TRUE --force true --dbpassword xxxxxxxx --dbadminuserpw xxxxxxxx'
WAINST226E You have supplied parameter: --sslpassword but you have not supplied parameter: --sslkeysfolder.
WAINST035I For more details see the installation log file: /opt/wa/logs/configureDb_10.1.0.03.log.
E: Error initializing server.
E: Error starting instance.

waconsole error:
I: Running '/opt/dwc/tools/configureDb.sh --work_dir /tmp/wainst --log_dir /home/wauser/wadata --rdbmstype DB2 --dbhostname wa-db2 --dbport 50000 --dbuser db2inst1 --dbadminuser db2inst1 --dbname DWC --execsql TRUE --force true --dbpassword xxxxxxxx --dbadminuserpw xxxxxxxx'
WAINST226E You have supplied parameter: --sslpassword but you have not supplied parameter: --sslkeysfolder.
WAINST035I For more details see the installation log file: /home/wauser/tmp/wa10.1.0.03/logs/configureDb_10.1.0.03.log.
E: Error configuring database.
E: Error configuring console.
E: Error starting instance.

Removing the ENV value for sslpassword (null value) from container causes the container causes nether container to be able to connect to the wa-db2 container.

[valerio-trenta]

Hello @probalsil1 ,

in upgrade, you also need to specify as an environment variable for your each one of your containers the following variable:

SSL_KEY_FOLDER=<path_to_the_folder_containing_all_your_default_certificates>

The SSL_PASSWORD specified as environment variable must be the password for the default certificates which were used in your previous version (FP1).

This step is not required in a fresh installation scenario.

[probalsil1]

I've tried both an upgrade and a fresh install. In both cases, I see the same problem. I'm not using certificates with this install/upgrade.

[valerio-trenta]

You need to provide your custom certificates with your own password when installing in a fresh scenario. Default certificates have been removed so if you want to perforrm an upgrade you need to specify the aforementioned env variables (SSL_KEY_FOLDER/SSL_PASSWORD) and provide default certificates as they were custom ones, whereas if you want to perform a fresh isntallation you still need to provide your own custom pem certificates and the SSL_PASSWORD env variable for such c ertificates.