<br>Thanks Matt,�<div><br></div><div>now I know.</div><div><br></div><div>Anyway, trying, based on this new information you guys gave me, I figured out that having<b> /etc/security/limits.conf</b></div><div>with:</div><div>
<br></div><div><div><b>rabbitmq �soft �nofile 10000</b></div><div><b>rabbitmq �hard �nofile 65000</b></div><div><b>root �soft �nofile 10000</b></div><div><b>root �hard �nofile 65000</b></div></div><div><br></div><div>Editing�<b style="background-color:rgb(255,255,255)"><font face="arial, helvetica, sans-serif">/etc/pam.d/common-session{,-noninteractive}</font></b><span style="font-family:verdana,geneva,helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">�adding:</span></div>
<div><b style="background-color:rgb(255,255,255)"><font face="arial, helvetica, sans-serif">session required pam_limits.so</font></b>
</div><div><span style="font-family:verdana,geneva,helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><br></span></div><div>And editing the <b>/etc/init.d/rabbit-server</b> file making root the user to execute the script (<b>START_PROG="start-stop-daemon -v --chuid <font face="'arial black', sans-serif" color="#ff0000">root </font>--start --exec"</b>) I got to see the rabbitmq limit.conf value on �the management site, which I couldn't see before.....</div>
<div><br></div><div>I know it is rough... <b>I do not recommend doing this </b>but it is just to check that limits.conf works.</div><div><br></div><div>I installed everything from zero, again. On a brand new machine. And it works.... Now it works.... without doing anything strange.</div>
<div>I modify the limits.conf file and I see it on the management plugin site. It is incredible... I still don't know what is wrong on the other machine, but it works on this new one.</div><div><br></div><div>Cheers.</div>
<div><br></div><div><br></div><div>G.</div><div><br></div><div><br><div class="gmail_quote">2012/4/18 Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">matthias@rabbitmq.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 18/04/12 10:56, Gonzalo Fernandez wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
In another machine, same system different rabbit version (2.7.1 insteasd<br>
of 2.8.1) it worked perfectly.<br>
Simon said that the version could not be the problem.<br>
<br>
"No. RabbitMQ only ever *reports* on the FD limits it is seeing, it<br>
doesn't impose any more. And this code has not changed from 2.7.1 to 2.8.1"<br></div>
*<br>
*<div class="im"><br>
I can't scratch my head any longer...<br>
<br>
Has anyone had this problem before? Any thoughts?<br>
</div></blockquote>
<br>
There was a change between 2.7.1 and 2.8.0 that may have caused this. The startup scripts on debian-like systems now use 'start-stop-daemon' instead of 'su', which resolved the long outstanding problem of rabbit sometimes preventing the OS from shutting down. Needs investigating.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
</font></span></blockquote></div><br></div>