inplace upgrade Bitbucket 4.3.2 to 5.16.3 - Service can not be started

[Jörg Schmidt]

Hello,

We did the upgrade over the installer and option 3 on a test environment (Linux). Thereafter, the information from server.xml to bitbucket.properties transmitted in the new format and yet can not start the service.
Git has been brought to version 2.19.0.
JKS File was also rebuilt to avoid content errors or wrong / missing passwords.

server.port=8443
server.address=bitbucket-test.abcd.defg
#server.redirect-port=8443
server.connection-timeout=20000
server.compression.enabled=true
server.compression.mime-types=text/css,text/html,text/javascript,text/json,text/plain,text/xml,text/x-javascript,\application/javascript,application/json,application/x-javascript,application/vnd.git-lfs+json
server.proxy-port=1234
server.proxy-name=proxy.abcd.defg

server.secure=true
server.scheme=https
server.ssl.enabled=true
server.ssl.client-auth=want
server.ssl.protocol=TLS
server.ssl.key-alias=name
server.ssl.key-store-type=jks
server.ssl.key-store=/etc/https/name.jks
server.ssl.key-store-password=<password>
server.ssl.key-password=<password>

other test with port 7990 and redirected port 8443 and 

server.additional-connector.1.port=8443
server.additional-connector.1.address=bitbucket-test.abcd.defg
server.additional-connector.1.secure=true
server.additional-connector.1.scheme=https
server.additional-connector.1.ssl.enabled=true
server.additional-connector.1.ssl.client-auth=want
server.additional-connector.1.ssl.protocol=TLSv1.2
server.additional-connector.1.ssl.key-alias=name
server.additional-connector.1.ssl.key-store-type=jks
server.additional-connector.1.ssl.key-store=/etc/https/name.jks
#server.additional-connector.1.ssl.key-store=/var/atlassian/application-data/bitbucket_stage/shared/config/name.jks
server.additional-connector.1.ssl.key-store-password=<password>
server.additional-connector.1.ssl.key-password=<password>
server.additional-connector.1.proxy-port=1234
server.additional-connector.1.proxy-name=proxy.abcd.defg

Error Message logfile:

Description:
The Tomcat connector configured to listen on port 8443 failed to start. The port may already be in use or the connector may be misconfigured.

Action:
Verify the connector's configuration, identify and stop any process that's listening on port 8443, or configure this application to listen on another port.
2019-04-05 14:40:14,449 INFO [main] c.a.b.i.boot.log.BuildInfoLogger Bitbucket 5.16.3 has shut down

I have tested several ports, have worked only with the port entry alone in the properties file (as with a fresh installation).
Everything with the same result.

Did I miss something else? Bitbucket Home path is also correct, permissions same.

Thanks

Jörg