Re: Fedora 12 not releasing ports

On Tue, 29 Jun 2010 16:48:13 -0700 Jack Lauman wrote: > Upon rebooting the server ports 110 and 25 are not seen by netstat but > are seen by the tomcat application and the app aborts stating that the > ports are in use. That sounds to me like tomcat is allocating the port twice and failing on t

Re: Fedora 12 not releasing ports

On Wed, Jun 30, 2010 at 02:48, Jack Lauman wrote: > Yes.. and chkconfig portreserve off > > Upon rebooting the server ports 110 and 25 are not seen by netstat but > are seen by the tomcat application and the app aborts stating that the > ports are in use. > > They only way I can get the app to lo

Re: Fedora 12 not releasing ports

I removed the portreserve rpm and it works fine now. Jack On 6/29/2010 4:32 PM, Doron Bar Zeev wrote: > > > On Wed, Jun 30, 2010 at 02:16, Jack Lauman > wrote: > > Tried that... doesn't make any difference whatsoever. If I use > portreleast pop3 manually th

Re: Fedora 12 not releasing ports

Yes.. and chkconfig portreserve off Upon rebooting the server ports 110 and 25 are not seen by netstat but are seen by the tomcat application and the app aborts stating that the ports are in use. They only way I can get the app to load to to "manually" run portrelease regardless of whether the

Re: Fedora 12 not releasing ports

On Wed, Jun 30, 2010 at 02:16, Jack Lauman wrote: > Tried that... doesn't make any difference whatsoever. If I use > portreleast pop3 manually the port will release and the tomcat > application can start. > > did you try service portreserve stop ? -- users mailing list users@lists.fedoraproject.

Re: Fedora 12 not releasing ports

Tried that... doesn't make any difference whatsoever. If I use portreleast pop3 manually the port will release and the tomcat application can start. Jack On 6/29/2010 4:01 PM, Doron Bar Zeev wrote: > > > On Tue, Jun 29, 2010 at 18:34, Jack Lauman > wrote: > > >

Re: Fedora 12 not releasing ports

netstat -noa netstat -tap Nothing is using ports 110 or 25. All other IP4 services work fine, ie. SSH, SFTP, telnet, etc. If I launch Dovecot manually the server will listen on port 110. The only way tomcat and desknow will launch successfully is if I issue the following commands before starti

Re: Fedora 12 not releasing ports

On Tue, Jun 29, 2010 at 18:34, Jack Lauman wrote: > > > When I start tomcat I get an error the port 110 is in use. Dovecot is > not enabled, netstat doesn't show port 110 in use. > > If I run "portrelease" on ports POP3, SMTP & 3306 manually prior Tomcat > startup and DeskNow runs normally. > >

Re: Fedora 12 not releasing ports

On Tue, 2010-06-29 at 08:34 -0700, Jack Lauman wrote: > When I start tomcat I get an error the port 110 is in use. Dovecot is > not enabled, netstat doesn't show port 110 in use. Perhaps something not sensibly handling you having IPv4 and IPv4 networking? What options did you try with netstat to

Fedora 12 not releasing ports

I have Fedora 12 and Tomcat 6.0.28 running a CRM application called DeskNow. When I start tomcat I get an error the port 110 is in use. Dovecot is not enabled, netstat doesn't show port 110 in use. If I run "portrelease" on ports POP3, SMTP & 3306 manually prior Tomcat startup and DeskNow runs