Monday, 6 April 2015

hostName: hostName is not a properly formed host name.

I saw this exception earlier: -

hostName: hostName is not a properly formed host name.

when creating a WAS profile: -

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -create -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/management -profileName Dmgr01 -nodeName Dmgr -isDefault -enableAdminSecurity true -adminUserName wasadmin -adminPassword passw0rd

Initially I was stumped, as the command doesn't specify a hostname.

Then I thought about it …..

…. and looked at the hostname of my server: -

hostname

mta2015_1.uk.ibm.com

and remembered that, whilst instantiating a VM in the cloud earlier, I was told off for using a hostname containing an underscore character.

I changed the hostname to be more in keeping with my target - IBM ODM 8.7 i.e. to: -


and, quelle surprise, all is now well :-)

2 comments:

Almyr said...

Thanks, worked well for me.

Dave Hay said...

Great news, thanks for letting me know

Yay, VMware Fusion and macOS Big Sur - no longer "NAT good friends" - forgive the double negative and the terrible pun ...

After macOS 11 Big Sur was released in 2020, VMware updated their Fusion product to v12 and, sadly, managed to break Network Address Trans...