Wednesday, 11 October 2017

CWMCB0130E when trying to stop an IBM BPM 8.6 Deployment Environment

I saw this today: -

/opt/ibm/WebSphere/AppServer/bin/BPMConfig.sh -stop -profile Dmgr01 -de De1

Logging to file /opt/ibm/WebSphere/AppServer/logs/config/BPMConfig_20171011-093452.log.
User name of the deployment environment administrator: wasadmin
Password of the deployment environment administrator:          
 
CWMCB0130E: The option is not valid. This option can be used only on the deployment manager machine. Machine is bpm86.uk.ibm.com, install root is /opt/ibm/WebSphere/AppServer.
CWMCB0130E: The option is not valid. This option can be used only on the deployment manager machine. Machine is bpm86.uk.ibm.com, install root is /opt/ibm/WebSphere/AppServer.
The 'BPMConfig.sh -stop -profile Dmgr01 -de De1 -username wasadmin -password ********' command failed. For more information, see the log file /opt/ibm/WebSphere/AppServer/logs/config/BPMConfig_20171011-093452.log.


all of which occurred because the DHCP server embedded within VMware Fusion, in it's infinite wisdom, decided to change the IP address of the VM from 192.168.153.130 to 192.168.153.133.

This was easily fixed by forcing the VM to have a static, rather than dynamic, hostname: -

vi  /etc/sysconfig/network-scripts/ifcfg-eno16777736

changing from: -

TYPE="Ethernet"
BOOTPROTO="dhcp"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
NAME="eno16777736"
UUID="1599eaad-7b6c-4d26-b603-16d9aac53fd1"
DEVICE=ens33
ONBOOT="yes"
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes


to: -

TYPE="Ethernet"
BOOTPROTO="static"
IPADDR=192.168.153.130
NETMASK=255.255.255.0
GATEWAY=192.168.153.2

DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
NAME="eno16777736"
UUID="1599eaad-7b6c-4d26-b603-16d9aac53fd1"
DEVICE=ens33
ONBOOT="yes"
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes




which I validated thusly: -

ping `hostname`

PING bpm86.uk.ibm.com (192.168.153.130) 56(84) bytes of data.
64 bytes from bpm86.uk.ibm.com (192.168.153.130): icmp_seq=1 ttl=64 time=0.011 ms
64 bytes from bpm86.uk.ibm.com (192.168.153.130): icmp_seq=2 ttl=64 time=0.069 ms
64 bytes from bpm86.uk.ibm.com (192.168.153.130): icmp_seq=3 ttl=64 time=0.034 ms
^C
--- bpm86.uk.ibm.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.011/0.038/0.069/0.023 ms


so now I can do this: -

/opt/ibm/WebSphere/AppServer/bin/BPMConfig.sh -stop -profile Dmgr01 -de De1

Logging to file /opt/ibm/WebSphere/AppServer/logs/config/BPMConfig_20171011-093840.log.
User name of the deployment environment administrator: wasadmin
Password of the deployment environment administrator:          
 
Stopping cluster SupCluster.
Stopping cluster AppCluster.
Stopping cluster MECluster.
The 'BPMConfig.sh -stop -profile Dmgr01 -de De1 -username wasadmin -password ********' command completed successfully.

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...