After upgrading from ASE 16.0 SP01 to SP02 PL01 I tried to start the new ASE Cockpit. Cockpit starts but the connection info like "Cockpit Web Console: https://dimotion:4283/cockpit" is missing:
============================
[sybase@dimotion bin]$ ./cockpit.sh
Starting Cockpit Server...
---------- SYSTEM INFO ----------
Home Directory: /opt/ase160/COCKPIT-4
Version: Cockpit Server 4 SP10
Node: dimotion(192.168.0.52)
Log Message level: WARN
Platform: linux
Bitwidth: 64
OS Name: Linux
OS Version: 3.10.0-229.14.1.el7.x86_64
OS Architecture: amd64
Available Processors: 6
Total Physical Memory: 19411 MB
Free Physical Memory: 8718 MB
java.library.path: /opt/ase160/COCKPIT-4/rtlib:/opt/ase160/COCKPIT-4/bin/sa16/linux64/lib64
Java Home: /opt/ase160/shared/SAPJRE-7_1_027_64BIT
Java Version: 1.7.0_71
Java VM Version: 7.1.027 25.11-b02
VM Process ID 31205@dimotion.sybase.local
VM Arguments: -Xms128m, -XX:MaxPermSize=128m, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=/opt/ase160/COCKPIT-4/log, -Dcom.sybase.home=/opt/ase160, -Dcom.sybase.ua.toplevel=/opt/ase160/COCKPIT-4, -Dcom.sybase.ua.home=/opt/ase160/COCKPIT-4, -Dcom.sybase.platform=linux, -Djava.library.path=/opt/ase160/COCKPIT-4/rtlib:/opt/ase160/COCKPIT-4/bin/sa16/linux64/lib64, -Djava.security.policy=/opt/ase160/COCKPIT-4/conf/java.policy, -Djava.util.logging.manager=com.sybase.ua.util.logging.bridge.JavaToLog4jLogManager, -Dcom.sybase.security.BootstrapConfigurationURL=file:////opt/ase160/COCKPIT-4/conf/csibootstrap.properties
Type help for more options
cockpit>
============================
A connection with the ASE Cockpit installation is not possible. Displaying the ports I get:
============================
cockpit> info -p
---------- SERVICE PORT CONFIGURATION ----------
Service Name Property Name Current Value In Use Address
------------ ------------- ------------- ------ -------
RMI port 4992 true dimotion
EmbeddedWebContainer http.port 4282 false ANY
EmbeddedWebContainer https.port 4283 false ANY
Tds tdsPort 4998 false ANY
SccSADataserver com.sybase.asa.server.port 4638 false ANY
Messaging messaging.db.port 4638 false ANY
Messaging messaging.port 4993 false ANY
Alert alert.database.port 4638 false ANY
cockpit>
============================
All ports are free, because an IQ Cockpit installation runs on the same machine with the identical ports. The agent status also looks OK:
============================
cockpit> status -a
Agent Home: /opt/ase160/COCKPIT-4
Connection URL: service:jmx:rmi:///jndi/rmi://dimotion:4992/agent
Status: RUNNING
cockpit>
============================
The upgrade itself works without any error or message. Am I missing something necessary during the upgrade?
Many thanks
Robert