Re: [fetchmail-users] query state=2 (SOCKET)

[Matthias A. <mat...@gm...>]

"Roberto Meyer" <rob...@gm...> writes:

> 2006/9/13, Rob MacGregor <rob...@gm...>:
>
>> On 9/12/06, Roberto Meyer <rob...@gm...> wrote:
>> >
>> > Still having problems with it, I decided to put tcpdump in action. The
>> > problem is I don't really know much about it. I read the man pages and
>> > understood a little about flags, etc. but don't know a lot of tcp/ip.
>> >
>> > I've attached the output of two connections triggered at the same time
>> > for two different users through cron jobs. One of them was successful,
>> > the other one failed with a socket, status=2 result.
>> >
>> > The command I issued was:
>> > "tcpdump -v -s1500 -i eth0 -n tcp port 110 -w /tmp/tcpdump.raw"
>> >
>> > I've attached the 'text' version of it which I rescued through
>> > "tcpdump -r /tmp/tcpdump.raw"
>>
>> Separating the 2 is, sadly, not possible.  If you could capture one
>> working run and one failed run then I *may* be able to help work out
>> what's going wrong.  It would help to have the binary pcap of the
>> failed run, though obviously you'd need to change passwords
>> immediately afterwards (or before and after) for security reasons.
>
> Finally I got a couple of errors with single connections.

Please update fetchmail (newer versions have fewer bugs and better error
reporting) and if the problem persists, run:

env LC_ALL=C fetchmail -vvv --nodetach --nosyslog -d0

to obtain a more detailed log. However, it still looks like the problem
is outside fetchmail to me.

-- 
Matthias Andree