Socket error

[Igor Ivanov]

Hi Juli,

In one case there are some other errors just before this is started to
happen (see below). I'm running the original 0.8.0 without modifications on
CentOS 6.5. File descriptors exhausted direction makes a perfect sense, I
will try to troubleshoot the machine.

Thanks,
Igor

1404394847.316949 [/wanproxy/proxy/proxy-socks0/connector] INFO: Connect
failed: <Error>/0 [Success]
1404394853.339667 [/wanproxy/proxy/proxy-socks0/connector] INFO: Connect
failed: <Error>/0 [Success]
1404394858.494985 [/wanproxy/proxy/proxy-socks0/connector] INFO: Connect
failed: <Error>/0 [Success]
1404394860.860666 [/socket/address] ERR: bool
socket_address::operator()(int, int, int, const std::string&): Could not
look up [localhost]:3302: System error
1404394860.860733 [/socket] ERR: Action* Socket::connect(const
std::string&, EventCallback*): Invalid name for connect: [localhost]:3302
1404394860.860794 [/wanproxy/proxy/proxy0/connector] INFO: Connect failed:
<Error>/22 [Invalid argument]



On Thu, Jul 10, 2014 at 8:56 PM, Juli Mallett <juli at clockworksquid.com>
wrote:

> Igor,
>
> Are those the only errors you're seeing?  When that starts to happen for
> me, it's on systems where I've run out of file descriptors and the
> getprotobyname code wants to read /etc/services and can't.  Or you could be
> hitting some kind of bug in your libc's getprotobyname under pressure.  Or
> I could've screwed something up :)  I don't *think* you're actually going
> through libuinet to do getprotobyname, though, unless you've made local
> changes.  Are you at all comfortable with truss or something like?  (Which
> OS are you on?)  It'd be good to see exactly what is failing and why.
>
> Thanks,
> Juli.
>
>
> On Thu, Jul 10, 2014 at 9:14 AM, Igor Ivanov <iivanovforever at gmail.com>
> wrote:
>
>> Dear all,
>>
>> After running WANProxy (0.8.0) for some time I started to notice
>> following errors on the server side:
>>
>> 1403673349.946080 /socket ERR: static Socket* Socket::create(Socket
>> Address Family, Socket Type, const std::string&, const std::string&):
>> Invalid protocol: tcp
>> 1403673349.946171 /wanproxy/proxy/proxy0/connector INFO: Connect failed:
>> <Error>/0 Success
>>
>> Once they appear, it seems I can't use the solution anymore and need to
>> restart it.
>>
>> Looking at libuinet code (where the error comes from) it seems the
>> "getprotobyname" API fails, however, my /etc/protocols file looks good and
>> does have a valid entry for "tcp" protocol.
>>
>> Any thoughts?
>>
>> Thanks,
>> Igor
>>
>> _______________________________________________
>> wanproxy mailing list
>> wanproxy at lists.wanproxy.org
>> http://lists.wanproxy.org/listinfo.cgi/wanproxy-wanproxy.org
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wanproxy.org/pipermail/wanproxy-wanproxy.org/attachments/20140710/5d0038e1/attachment.htm>