| Author |
Message
|
| Vincent Vega |
 Posted: Wed Sep 23, 2015 11:14 pm Post subject: IIB 10 Multi-instance. Execvp failed! name bipMQTT errno 2 |
 |
|
Novice
Joined: 27 Sep 2012
Posts: 18
Location: Kiev, Ukraine
|
Hi all
I want to implement multi-instance IIB in Active-Passive mode. This is my environment:
I have two PureApp servers where I have already installed MQ 8.0.0.3 and IIB 10.0.0.1:
OS
| Code: |
bash-4.3$ uname -sa
AIX pega-app-prod10 1 7 0002499CD400
bash-4.3$ uname -sv
AIX 7
bash-4.3$ oslevel -r
7100-03 |
MQ Configuration
| Code: |
bash-4.3$ dspmqver -i
Name: WebSphere MQ
Version: 8.0.0.3
Level: p800-003-150612
BuildType: IKAP - (Production)
Platform: WebSphere MQ for AIX
Mode: 64-bit
O/S: AIX 7.1
InstName: Installation1
InstDesc:
Primary: Yes
InstPath: /usr/mqm
DataPath: /var/mqm
MaxCmdLevel: 802
LicenseType: Production
bash-4.3$ dspmq -x
QMNAME(QM01) STATUS(Running)
INSTANCE(pega-app-prod10.delta) MODE(Active)
INSTANCE(pega-app-dr10.delta) MODE(Standby)
|
IIB Configuration
| Code: |
bash-4.3$ mqsireportbroker BK01
BIP8927I: Integration node name 'BK01'
Last mqsistart path = '/opt/IBM/iib-10.0.0.1/server'
mqsiprofile install path = '/opt/IBM/iib-10.0.0.1/server'
Work path = '/var/mqsi'
Integration node UUID = 'c5d221aa-61fd-11e5-9cf4-0a1e84460000'
Process id = '9699404'
Queue Manager = 'QM01'
User lil path = ''
User exit path = ''
Active user exits = ''
LDAP principal = ''
LDAP credentials = ''
ICU converter path = ''
Trusted (fastpath) Queue Manager application = 'false'
Configuration change timeout = '300' seconds
Internal configuration timeout = '60' seconds
Statistics major interval = '60' minutes
Operation mode = 'advanced'
Fixpack capability level = '' (effective level 'unrestricted')
Integration node registry format = 'v10.0'
Administration security = 'active'
Multi-instance integration node = 'true'
Shared Work Path = '/esb/IIB/mqsi'
Start as WebSphere MQ Service = 'undefined'
HTTP listener port = '7080'
Cache manager policy = 'disabled'
Cache manager port range = '2800-2819'
Integration registry hostname = ''
Default integration node CCSID = '1208'
bash-4.3$ mqsilist
BIP1295I: Integration node 'BK01' is an active multi-instance or High Availability integration node that is running on queue manager 'QM01'.
BIP8071I: Successful command completion. |
I installed it by default and did not any additional configurations. When I opened broker data catalog I saw that stderr and stdout files increases every minute. These are files:
stderr
| Code: |
2015-09-23 21:16:51.907492 AdminAgent started. Process ID : 21299378 Broker is: BK01
Exception in thread "Thread-5" 2015-09-23 21:16:53.779 31 <com.ibm.broker.plugin.MbRecoverableException class:ContainerServices method:throwException source:BIPmsgs key:12096 >
2015-09-23 21:16:53.784 31 at com.ibm.broker.connector.ContainerServices.throwMbRecoverableException(Unknown Source)
2015-09-23 21:16:53.784 31 at com.ibm.broker.connector.mqtt.MQTTInputConnector.start(MQTTInputConnector.java:302)
Exception in thread "Thread-5" 2015-09-23 21:16:54.029 31 <com.ibm.broker.plugin.MbRecoverableException class:ContainerServices method:throwException source:BIPmsgs key:12096 >
2015-09-23 21:16:54.030 31 at com.ibm.broker.connector.ContainerServices.throwMbRecoverableException(Unknown Source)
2015-09-23 21:16:54.030 31 at com.ibm.broker.connector.mqtt.MQTTInputConnector.start(MQTTInputConnector.java:302) |
stdout
| Code: |
Redirecting stdout to /esb/IIB/mqsi/components/BK01/stdout
Redirecting stderr to /esb/IIB/mqsi/components/BK01/stderr
2015-09-23 21:17:18.126770 AdminAgent started. Process ID : 5373970 Broker is: BK01
Execvp failed! name bipMQTT errno 2
Execvp failed! name bipMQTT errno 2
Execvp failed! name bipMQTT errno 2
Execvp failed! name bipMQTT errno 2
Execvp failed! name bipMQTT errno 2
Execvp failed! name bipMQTT errno 2
Execvp failed! name bipMQTT errno 2
Execvp failed! name bipMQTT errno 2 |
What is this and how to fix these errors? |
|
| Back to top |
|
 |
| stoney |
| Posted: Thu Sep 24, 2015 1:10 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2013
Posts: 140
|
| Quote: |
| Execvp failed! name bipMQTT errno 2 |
On AIX, errno 2 is ENOENT which translates to no such file or directory.
This suggests that your IIB installation does not have a file <install root>/server/bin/mosquitto/bipMQTT.
Alternatively, that executable exists but it cannot be started - for example, incorrect permissions, or missing library dependencies.
Did you install IIB using the PureApp automation?
It might be best to raise a PMR so that we can investigate what went wrong with the installation.
| Quote: |
class:ContainerServices method:throwException source:BIPmsgs key:12096 >
2015-09-23 21:16:53.784 31 at com.ibm.broker.connector.ContainerServices.throwMbRecoverableException(Unknown Source)
2015-09-23 21:16:53.784 31 at com.ibm.broker.connector.mqtt.MQTTInputConnector.start(MQTTInputConnector.java:302)
Exception in thread "Thread-5" 2015-09-23 21:16:54.029 31 <com.ibm.broker.plugin.MbRecoverableException |
These error messages are occurring because bipMQTT cannot be started, and so we cannot establish a connection to it. |
|
| Back to top |
|
|
| Vincent Vega |
| Posted: Thu Sep 24, 2015 2:13 am Post subject: |
|
|
Novice
Joined: 27 Sep 2012
Posts: 18
Location: Kiev, Ukraine
|
Thank you stoney.
Yes, I installed IIB from the PureApp pattern. I made this pattern so it can have mistakes  I have never worked with PureApp before. But IIB works fine except this error.
I have bipMQTT file. Permissions are ok.
| Code: |
bash-4.3# ls -l /opt/IBM/iib-10.0.0.1/server/bin/mosquitto/
total 480
-rwxr-xr-x 1 mqbrkrs mqbrkrs 241822 May 22 20:38 bipMQTT
|
When I try to run bipMQTT I catch this mistake:
| Code: |
bash-4.3# ./opt/IBM/iib-10.0.0.1/server/bin/mosquitto/bipMQTT
1443089487: mosquitto version 1.4 (build date 2015-02-19 06:27:53GMT) starting
1443089487: Using default config.
1443089487: Opening ipv4 listen socket on port 1883.
1443089487: Opening ipv6 listen socket on port 1883.
1443089487: Error: Invalid user 'mosquitto'.
|
I create user 'mosquitto' but I still have the same mistake
I will try open PMR |
|
| Back to top |
|
|
| smuktineni |
| Posted: Thu Aug 31, 2017 6:56 am Post subject: |
|
|
Apprentice
Joined: 28 Aug 2003
Posts: 33
Location: Omaha
|
Any update this? We have the same issue as detailed here and we are at IIB 10.0.0.7 on Aix 7.2 and every Integration Node has this error. If there is a known resolution I would avoid opening a PMR.
By the way we only have the error in stdout and all file permissions look good.
| Code: |
| Execvp failed! name bipMQTT errno 2 |
Our stderr has a different listing of below which is mostly unrelated to above error.
| Code: |
2017-08-23 10:55:50.600453 AdminAgent started. Process ID : 11403546 Broker is: IIB10IN
2017-08-23 10:55:51.059 1 SLF4J: Class path contains multiple SLF4J bindings.
2017-08-23 10:55:51.065 1 SLF4J: Found binding in [jar:file:/opt/IBM/mqsi/iib-10.0.0.7/server/classes/slf4j-log4j12-1.7.21.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2017-08-23 10:55:51.066 1 SLF4J: Found binding in [jar:file:/opt/IBM/mqsi/iib-10.0.0.7/server/classes/adminagent/slf4j-jdk14-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2017-08-23 10:55:51.067 1 SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2017-08-23 10:55:51.104 1 SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] |
Thanks in advance
_________________
-Satish |
|
| Back to top |
|
|
| Vincent Vega |
| Posted: Thu Aug 31, 2017 7:06 am Post subject: |
|
|
Novice
Joined: 27 Sep 2012
Posts: 18
Location: Kiev, Ukraine
|
Currently I don't have this issue. But I don't remember how I fixed it, it was two years ago:)
I think I can share my pattern. If you're using PureApp probably it will help you |
|
| Back to top |
|
|
| smuktineni |
| Posted: Fri Feb 23, 2018 3:27 pm Post subject: |
|
|
Apprentice
Joined: 28 Aug 2003
Posts: 33
Location: Omaha
|
we opened a PMR and below was the reply and it worked after I disabled MQTT and restarted Broker (Node)
I checked our Aix, IPV6 was enabled, but not configured.
We are at IIB 10.0.0.10, MQ 8.0.0.6, both on Aix 7.2
| Quote: |
| There are known issues with MQTT and IPv6. Usually the /etc/hosts file and your IPv6 settings are out of synch, such as an IPv6 entry in the hosts file when IPv6 is not enabled. Normally the IPv6 thing doesn't cause the process to not start, but it prevents connections. If you are not using MQTT, you can disable it with this command: |
| Code: |
| mqsichangeproperties IBNODE -b pubsub -o MQTTServer -n enabled -v false |
Hope that helps.
_________________
-Satish |
|
| Back to top |
|
|
|
|
