Having taken the default option to install WebSphere Application Server Network Deployment 7.0.0.0 ( then upgraded to 7.0.0.9 ) with a Deployment Manager profile, I'm now in the process of setting up said DM before federated an instance of WebSphere Portal 6.1.5.1 ( installed on the same node ) into the cell.
When I attempted to start the DM, using the command: -
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/startManager.sh
but this failed pretty darn quickly with: -
ADMU3011E: Server launched but failed initialization. startServer.log,
SystemOut.log(or job log in zOS) and other log files under
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr should
contain failure information.
When I looked in SystemOut.log, I saw: -
DCSV9403E: Received an illegal configuration argument. Parameter MulticastInterface, value: 127.0.1.1. Exception is java.lang.Exception: Network Interface 127.0.1.1 was not found in local machine network interface list. Make sure that the NetworkInterface property is properly configured!
Now my /etc/hosts currently looks like this: -
127.0.0.1 localhost
127.0.1.1 dmhw500.uk.ibm.com dmhw500
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
However, according to this Blog post, that might be the problem.
Following the recommendations in the posting, I changed the relevant part of /etc/hosts to: -
127.0.0.1 localhost dmhw500
127.0.1.1 dmhw500.uk.ibm.com dmhw500
and am now able to start the Deployment Manager.
Let's see how I get on ...
***UPDATE 28 December 2011***
Using WebSphere Application Server ND 7.0.0.17 on Ubuntu 11.10, I needed to further amend /etc/hosts to: -
127.0.0.1 localhost dmhw500 dmhw500.uk.ibm.com
127.0.1.1 dmhw500.uk.ibm.com dmhw500
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
in order to overcome these errors: -
[28/12/11 19:17:54:584 GMT] 00000000 HostNameMap W HMGR0064W: Resolution of IP Addresses for host name dmhw500.uk.ibm.com found only the loopback address. The loopback address will be used.
[28/12/11 19:17:55:006 GMT] 00000000 LogAdapter E DCSV9403E: Received an illegal configuration argument. Parameter MulticastInterface, value: 127.0.1.1. Exception is java.lang.Exception: Network Interface 127.0.1.1 was not found in local machine network interface list. Make sure that the NetworkInterface property is properly configured!
Once I did this, I was able to run startManager.sh etc.
***UPDATE 28 December 2011***
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV https://infosec.exchange/@davehay
Subscribe to:
Post Comments (Atom)
Reminder - installing podman and skopeo on Ubuntu 22.04
This follows on from: - Lest I forget - how to install pip on Ubuntu I had reason to install podman and skopeo on an Ubuntu box: - lsb_rel...
-
Why oh why do I forget this ? Running this command : - ldapsearch -h ad2012.uk.ibm.com -p 389 -D CN=bpmbind,CN=Users,DC=uk,DC=ibm,DC=com -w...
-
Error "ldap_sasl_interactive_bind_s: Unknown authentication method (-6)" on a LDAPSearch command ...Whilst building my mega Connections / Domino / Portal / Quickr / Sametime / WCM environment recently, I was using the LDAPSearch command tha...
-
Whilst building a new "vanilla" Kubernetes 1.25.4 cluster, I'd started the kubelet service via: - systemctl start kubelet.se...
1 comment:
Thanks for your inputs really appreciate it.
Post a Comment