[Users] Socket Errors

[Martin Burns]

Thanks for your reply Bogdan,

There is definitely both UDP and TCP listening:

Starting openser: openserListening on
             udp: xx.xx.xx.xxx [xx.xx.xx.xxx]:5060
             tcp: xx.xx.xx.xxx [xx.xx.xx.xxx]:5060
Aliases:
......

Is it possible that there is simply too many messages for the server to
handle?

At the moment the server is configured with:

children=20
tcp_children=2

and an ngrep suggests quite a few messages per second.

Thanks

Martin

On 2/5/07, Bogdan-Andrei Iancu <bogdan at voice-system.ro> wrote:
>
> Hi Martin,
>
> the last error you posted says you want to forward something using UDP
> (proto 1), but there is no listen socket for UDP.
> can you check is there is no UDP listen configured on your openser?
>
> regards,
> bogdan
>
> Martin Burns wrote:
>
> > We have over 4 proxies running openser-1.1.0-notls. Recently we
> > started to see the following error in the logs of one of the proxies:
> >
> > Feb  4 06:46:21 proxy01 /usr/local/sbin/openser[4670]: ERROR:
> > udp_send: sendto(sock,0xb3c35898,594,0,0xb3c257f4,16): Invalid
> > argument(22)
> > Feb  4 06:46:21 proxy01 /usr/local/sbin/openser[4670]: CRITICAL:
> > invalid sendtoparameters one possible reason is the server is bound to
> > localhost and attempts to send to the net
> > Feb  4 06:46:21 proxy01 /usr/local/sbin/openser[4670]: msg_send:
> > ERROR: udp_send failed
> > Feb  4 06:46:21 proxy01 /usr/local/sbin/openser[4670]:
> > ERROR:tm:t_forward_nonack: sending request failed
> >
> > Now the errors suggests a binding to localhost, however our
> > openser.cfg has the following:
> >
> > listen=eth0:5060
> >
> > After a brief search we came across a couple of over people having a
> > similar problem. Once of the suggested fixes was to add a mhomed=1
> > line to the cfg.
> >
> > Well we tried this (even though we are not multi homed) and the error
> > changed to:
> >
> > Feb  5 02:54:09 proxy01 /usr/local/sbin/openser[2209]: ERROR:
> > get_out_socket: connect failed: Invalid argument
> > Feb  5 02:54:09 proxy01 /usr/local/sbin/openser[2209]: ERROR:
> > get_out_socket: no socket found
> > Feb  5 02:54:09 proxy01 /usr/local/sbin/openser[2209]:
> > ERROR:tm:add_uac: can't fwd to af 2, proto 1  (no corresponding
> > listening socket)
> > Feb  5 02:54:09 proxy01 /usr/local/sbin/openser[2209]:
> > ERROR:tm:t_forward_nonack: failure to add branches
> >
> > Does anyone have any suggestions or ideas as to what is causing this
> > error.
> >
> > Thanks
> >
> > mburns
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >Users mailing list
> >Users at openser.org
> >http://openser.org/cgi-bin/mailman/listinfo/users
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20070205/1d9b41ed/attachment.htm>