<HTML><BODY>
<div>Hi</div>
<div id="AOLMsgPart_2_a8900999-6d82-4d67-8ed2-bfe4c1b69ffa">
<div>
<br>
I had a strange inability to login one of my users, she got this error in /<span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">var</span></span></span></span>/log/<span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">nxserver</span></span></span></span>.log:<br>
<span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">NX</span></span></span></span>> 105 <span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">NX</span></span></span></span>> 1004 Error: <span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">NX</span></span></span></span> Agent exited with exit status 1.<br>
<br>
In the .<span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">nx</span></span></span></span>/C-*/errors I get:<br>
Loop: PANIC! Call to bind failed for media TCP port 8005. Error is 98 'Address already in use'.<br>
<br>
<br>
I looked to see which program use port 8005 and found <span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">tomcat5</span></span></span></span>, which is a <span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">servlet</span></span></span></span> engine. <br>
<br>
In the end she tried once more to login, before I shut down <span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">tomcat</span></span></span></span>, and succeeded to login.<br>
<br>
<br>
This problem was very problematic, since for some time the user couldn't login, while every other user could login. And this port, it took me some time to find out what it belongs to. And then before I did anything the problem resolved by itself. I don't understand why it wanted <span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">tomcat</span></span></span></span>'s port, and why it couldn't select an other port, and recover by itself. I looked for similar looking ports (800X), and not all users have them just a few of them. One user have <span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">nxagent</span></span></span></span> listen on 8002, and a bunch of <span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">gnome-ses</span></span></span></span>, <span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">gmone-set</span></span></span></span>... in a CLOSE_WAIT on the same port. An other user have <span class="correction" id=""><span class="correction" id=""><span class="correction" id=""><span class="correction" id="">totem-moz</span></span></span></span> (CLOSE_WAIT) on 8000. Since <span class="correction" id=""><span class="correction" id="">nxagent</span></span> have exited with status 1, I think <span class="correction" id=""><span class="correction" id="">nxagent</span></span> tried to open on port 8005. I did a re<span class="correction" id="">bo</span>ot prior. So maybe the <span class="correction" id=""><span class="correction" id="">tomcat</span></span> was shut down before the reboot, then <span class="correction" id="">free<span class="correction" id="">nx</span></span> used port 8005 and remembered to use it, then there was a reboot, and after the reboot <span class="correction" id=""><span class="correction" id="">tomcat</span></span> was up again, then on login <span class="correction" id="">nxagent</span> couldn't g<span class="correction" id="">et</span> the same port again. <br>
<br>
This reminds me that every user that was active during the reboot, had a problem to login, one failed login, and next login succeed. So, I think free<span class="correction" id="">nx</span> doesn't handle reboot well - it should logout all its users before the reboot, I think. But that is an other issue, beside that port issue.<br>
</div>
<div class="AOLPromoFooter">
<hr style="margin-top: 10px;">
<a target="_blank" href="http://pr.atwola.com/promoclk/100122638x1081283466x1074645346/aol?redir=http%3A%2F%2Fwww%2Eaim%2Ecom%2Ffun%2Fmail%2F"><b>Check Out the new free AIM(R) Mail</b></a> -- 2 GB of storage and industry-leading spam and email virus protection.<br>
</div>
</div>
<!-- end of AOLMsgPart_2_a8900999-6d82-4d67-8ed2-bfe4c1b69ffa -->
</BODY></HTML>