WAS _ initiate mbind: Invalid argument, mbindargument

WAS _ initiate mbind: Invalid argument, mbindargument

**************************************** ******************************** ***************************************

Original Works are from the blog of "Deep Blue blog". You are welcome to repost them. Please indicate the source when you repost them. Otherwise, the copyright will be held legally responsible.

Deep Blue blog: http://blog.csdn.net/huangyanlong/article/details/39697853

**************************************** **************************************** **************************************** ****

Environment: LINUX CentOS6.2, Oracle10.2.0.5, and WAS7.0

The message "mbind: Invalid argument" appears when was is started or disabled. Although it does not affect the startup or shutdown, you want to solve the problem for no reason.

Symptom

Start was

[root@hyl bin]# ./startServer.sh server1

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

ADMU0116I: Tool information is being logged in file

           /IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log

ADMU0128I: Starting tool with the AppSrv01 profile

ADMU3100I: Reading configuration for server: server1

ADMU3200I: Server launched. Waiting for initialization status.

mbind: Invalid argument

ADMU3000I: Server server1 open for e-business; process id is 1522

Disable was

[root@hyl bin]# ./stopServer.sh server1

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

mbind: Invalid argument

ADMU0116I: Tool information is being logged in file

           /IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/stopServer.log

ADMU0128I: Starting tool with the AppSrv01 profile

ADMU3100I: Reading configuration for server: server1

ADMU3201I: Server stop request issued. Waiting for stop status.

ADMU4000I: Server server1 stop completed.

Solution

It predicts that there may be conflicts between oracle and was over a port or other causes, resulting in the following prompt information.

It is inspired by oracle to solve this problem. A recent oracle problem occurred in a certain system environment. Some of the content is as follows:

SQL> startup

Mbind: Invalid argument

Mbind: Invalid argument

Mbind: Invalid argument

Mbind: Invalid argument

Mbind: Invalid argument

ORA-00443: background process "DBW1" did not start

This problem is that oracle conflicts with the numactl-0.9.6-3.25.28 package in the system, just uninstall

 

Then try to query the numactl package installation in the system, as shown in the following code:

[root@hyl bin]# rpm -qa | grep numactl
--Found installed numactl package
numactl-devel-2.0.3-9.el6.x86_64
numactl-2.0.3-9.el6.x86_64
--Try to unload numactl package
[root@hyl bin]# rpm -e numactl-devel-2.0.3-9.el6.x86_64
[root@hyl bin]# rpm -e numactl-2.0.3-9.el6.x86_64
--There is a dependency when uninstalling numactl-2.0.3-9.el6.x86 ʄ package. Don't think too much here, skip the step of uninstalling
error: Failed dependencies:
libnuma.so.1()(64bit) is needed by (installed) compat-openmpi-psm-1.4.3-1.el6.x86_64
libnuma.so.1()(64bit) is needed by (installed) libvirt-client-0.9.4-23.el6.x86_64
libnuma.so.1()(64bit) is needed by (installed) compat-openmpi-1.4.3-1.el6.x86_64
libnuma.so.1()(64bit) is needed by (installed) hwloc-1.1-0.1.el6.x86_64
libnuma.so.1()(64bit) is needed by (installed) numactl-devel-2.0.3-9.el6.x86_64
libnuma.so.1(libnuma_1.1)(64bit) is needed by (installed) compat-openmpi-psm-1.4.3-1.el6.x86_64
libnuma.so.1(libnuma_1.1)(64bit) is needed by (installed) libvirt-client-0.9.4-23.el6.x86_64
libnuma.so.1(libnuma_1.1)(64bit) is needed by (installed) compat-openmpi-1.4.3-1.el6.x86_64
libnuma.so.1(libnuma_1.1)(64bit) is needed by (installed) hwloc-1.1-0.1.el6.x86_64
libnuma.so.1(libnuma_1.2)(64bit) is needed by (installed) libvirt-client-0.9.4-23.el6.x86_64
libnuma.so.1(libnuma_1.2)(64bit) is needed by (installed) hwloc-1.1-0.1.el6.x86_64
numactl = 2.0.3-9.el6 is needed by (installed) numactl-devel-2.0.3-9.el6.x86_64
[root@hyl bin]# rpm -qa |grep numactl
--Query again, and you can see that the package has been successfully uninstalled: numactl-devel-2.0.3-9.el6.x86_
numactl-2.0.3-9.el6.x86_64

Verify again that the was startup and shutdown are completely normal and the conflict has been resolved. The following operations:

Start was

[root@hyl bin]# ./startServer.sh server1

ADMU0116I: Tool information is being logged in file

           /IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log

ADMU0128I: Starting tool with the AppSrv01 profile

ADMU3100I: Reading configuration for server: server1

ADMU3200I: Server launched. Waiting for initialization status.

ADMU3000I: Server server1 open for e-business; process id is 1789

Disable was

[root@hyl bin]# ./stopServer.sh server1

ADMU0116I: Tool information is being logged in file

           /IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/stopServer.log

ADMU0128I: Starting tool with the AppSrv01 profile

ADMU3100I: Reading configuration for server: server1

ADMU3201I: Server stop request issued. Waiting for stop status.

ADMU4000I: Server server1 stop completed. 

**************************************** ******************************** ***************************************

Original Works are from the blog of "Deep Blue blog". You are welcome to repost them. Please indicate the source when you repost them. Otherwise, the copyright will be held legally responsible.

Deep Blue blog: http://blog.csdn.net/huangyanlong/article/details/39697853

**************************************** **************************************** **************************************** ****

When the computer is turned on, the message "an invalid argument was encountered" is displayed.

"An invalid parameter is encountered ."
What kind of startup program should be reported? Is it caused by software installed recently? If so, try to uninstall or reinstall it.
If you are not sure which software program it is, open the "boot" menu and turn it off: press the "Windows" Key + R to open the "run" window, enter "msconfig" in the window to open the "Start System Configuration" window. In "start" and "service", close some startup programs and try again.

An invalid argument was encountered is displayed after the FireWire magic box is installed.

An invalid argument was encountered indicates that some of the files that have been checked out are invalid. If this problem occurs only in your file, instead of all files, please re-check and download the files.