Re: [Wrapper-user] Wrapper unable to bind listner to port

[Leif M. <le...@ta...>]

Bashiro,
What platform are you running on?  The wrapper has stopped, yes.
It was not able to bind to any of the port in that range.  The odds that
they are all actually in use is pretty much nil.  Most likely this is some
kind of a permission problem with the account running the Wrapper.

I remember something like this quite a while back on a Solaris
system.  But am not sure the details of how it was resolved.

Cheers,
Leif

Bashiro wrote:
> Hello,
>
> Why do the wrapper write this in the log:
>
>
>
> FATAL  | wrapperp | 2007/10/18 23:42:05 | unable to bind listener to any port in the range 32000-32999. (An attempt was made to access a socket in a way forbidden by its access permissions. (0x271d))
>
> STATUS | wrapper  | 2007/10/18 23:42:06 | <-- Wrapper Stopped
>
>
>
>
>
> DOES THIS MEANS WRAPPER HAS COMPLETELY STOPPED ?
>
> HOW DO I CORRECT THIS ERROR?
>
>
>
> Thanks for any help
>
> bashiro
>
> _______________________________________________
> No banners. No pop-ups. No kidding.
> Make My Way  your home on the Web - http://www.myway.com
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>