Technical Blog Post
Abstract
Message Broker agent: Brokers not shown in TEP under the broker agent item
Body
The message broker agent is starting fine but the java sub-process needed for monitoring brokers can't start and so no brokers can be shown in TEP. This is due to permissions of some temporary files in /tmp directory.
The temporary files mentioned have names similar to the following (actual names depend on instance name of the KQI agent and on the installation path of the monitored message broker):
kqijtemp_<inst>__opt_IIB_ibm_mqsi_9.0.0.2
kqijtemp_<inst>__opt_IIB_ibm_mqsi_9.0.0.2__BeforeMqsiprofile
kqijtemp_<inst>__opt_IIB_ibm_mqsi_9.0.0.2__BeforeMqsimqsetenv
kqijtemp_<inst>__opt_IIB_ibm_mqsi_9.0.0.2__BeforeRunJava
If you run KQI agent for the first time and you use root user, the files under /tmp will be generated by root user. So these files cannot be written by other users.
When you switch to a non-root user (start agent with non-root user), KQI agent will encounter a problem because it can not open the existing temporary files kqijtemp_<inst>__opt_IIB_ibm_mqsi_9.0.0.2 in write mode.
And that will cause java sub-process startup to fail.
To resolve this issue, you just need to remove KQI related files under /tmp before restarting it.
To know more about those temporary files and their usage you can access the published technote
http://www-01.ibm.com/support/docview.wss?uid=swg21686070
Subscribe and follow us for all the latest information directly on your social feeds:
|
|
 |
|
| Check out all our other posts and updates: | |
| Academy Blogs: | https://goo.gl/U7cYYY |
| Academy Videos: | https://goo.gl/TLfMoF |
| Academy Google+: | https://goo.gl/HnTs0w |
| Academy Twitter : | https://goo.gl/AhR8CL |
UID
ibm11084719