I had been using strmqm quite happily for days, but after reboot I got the following message when I tried to use strmqm.
April 2019 update…
Even making the recommended changes I still had the problem.
This post told me what to do – and it now works. I think /etc/security/limits.conf has limits when you are running su mode.
Late April 2019 update…
Another day one of my queue managers would not start.
QMGR .. failed to start.
The queue manager is associated with installation ‘Installation1’.
The queue manager ended for reason 545284129, ”.
There were no other messages, or entries in AMQERR01.LOG.
Running /opt/mqm/bin/mqconfig said every thing passed.
I logged off logged on again and it worked, sigh.
End of updates
The system resource RLIMIT_NOFILE is set at an unusually low level for IBM MQ.
IBM MQ queue manager ‘QMA’ starting.
The queue manager is associated with installation ‘Installation1’.
The queue manager ended for reason 545284129, ”.
Host(colinpaice) Installation(Installation1)
VRMF(9.1.0.0) QMgr(QMA)
Time(2018-10-06T05:40:36.942Z)
ArithInsert1(1024) ArithInsert2(10240)
CommentInsert1(RLIMIT_NOFILE)06/10/18 06:40:36 – Process(4665.1) User(colinpaice) Program(strmqm)
Host(colinpaice) Installation(Installation1)
VRMF(9.1.0.0) QMgr(QMA)
Time(2018-10-06T05:40:36.942Z)
ArithInsert1(1024) ArithInsert2(10240)
CommentInsert1(RLIMIT_NOFILE)
AMQ5657W: The system resource RLIMIT_NOFILE is set at an unusually low level
for IBM MQ.
EXPLANATION:
The system resource RLIMIT_NOFILE is currently set to 1024 which is below the
usual minimum level of 10240, recommended for IBM MQ.
ACTION:
If possible, increase the current setting to at least 10240.
mqm soft nofile 10240
I just added it to /etc/security/limits.conf file logged off, and logged on again and it worked!
2022 update
After I upgraded my Linux to 20.04, I got the message back again. After hunting around I found…
The limits in /etc/security/limits.conf were indeed being applied, but not to the graphical login. You need to add the following line to /etc/systemd/user.conf:
DefaultLimitNOFILE=65535
That change works, but only affecting the soft limit. Leaving us capped with a hard limit of 4096 still. In order to affect the hard limit, you must modify /etc/systemd/system.conf with the same changes.
For me the file had all fields commented out,
#DefaultLimitNOFILE=
so make the change, remove the # and reboot.
ColinPaice 
One thought on “strmqm command fails with 545284129 (and sometimes RMLIMIT_NOFILE message)”