Re: Almost permanently problem "dns lookup for xxxx timed out"

2012-01-17 Thread Marcin Mirosław

W dniu 2012-01-17 17:04, Tomasz Sterna pisze:

Dnia 2012-01-17, wto o godzinie 15:39 +0100, Marcin Mirosław pisze:

Mon Jan 16 17:14:39 2012 [notice] dns lookup for gmail.com timed out

[...]

and all remain gmail's users are marked as "remote-server-not-found"


Something is definitely wrong with DNS resolution.
Is your machine setup any unusual? Any firewall rules active?

I tried without firewall too.

Which version of udns do you have?


Yup, here was the problem. I've got udns-0.1 but it wasn't problem. 
Problem was in CFLAGS, "-fpeel-loops" with -Os (and with -O3 also) gives 
broken binary (gcc-4.5.3). It looks everything works as should:)

Can i send you a beer? http://jastawiam.pl/
Regards,
Marcin




Re: Almost permanently problem "dns lookup for xxxx timed out"

2012-01-17 Thread Tomasz Sterna
Dnia 2012-01-17, wto o godzinie 15:39 +0100, Marcin Mirosław pisze:
> Mon Jan 16 17:14:39 2012 [notice] dns lookup for gmail.com timed out
[...]
> and all remain gmail's users are marked as "remote-server-not-found"

Something is definitely wrong with DNS resolution.
Is your machine setup any unusual? Any firewall rules active?
Which version of udns do you have?


> _xmpp-server._tcp.marcel.pl. SRV maraton.marcel.pl.:5269 0 0 (170)
> 15:30:43.554633 IP (tos 0x0, ttl 60, id 42320, offset 0, flags [none],
> proto UDP (17), length 250) 127.0.0.1.53 > 127.0.0.1.35090: 55598
> [...]
> So resolver answered, but s2s didn't got it

This is probably the root cause of your problems.


> There was no dns traffic in tame later than 15:30:43.
> This situation is mysterious for me.
> Is it possible to have more precise timestams in debug log? 

You would need to modify the debug macro.





Re: Almost permanently problem "dns lookup for xxxx timed out"

2012-01-17 Thread Marcin Mirosław
W dniu 17.01.2012 10:10, Tomasz Sterna pisze:
> Dnia 2012-01-16, pon o godzinie 18:19 +0100, Marcin Mirosław pisze:
>> 1. First case, gmail is unreachable, in s2s debug log there is:
>> [...]
>> Mon Jan 16 15:31:58 2012 out.c:117 creating new out packet queue for
>> 'mejor.pl/gmail.com'
>> Mon Jan 16 15:31:58 2012 out.c:125 queueing packet for 'mejor.pl/gmail.com
>> [...]
>> Mon Jan 16 15:31:58 2012 out.c:1177 dns resolve for
>> gmail.com@0x7f1fc3d5dc60 started
>> [...]
>> Mon Jan 16 15:31:58 2012 out.c:793 dns host added for
>> gmail.com@0x7f1fc3d5dc60: alt2.xmpp-server.l.google.com/5269 (20/0/842)
>> Mon Jan 16 15:31:58 2012 out.c:822 dns response for
>> gmail.com@0x7f1fc3d5dc60: SRV _xmpp-server._tcp.gmail.com[4]
>> alt3.xmpp-server.l.google.com/5269 (20/0)
>> Mon Jan 16 15:31:58 2012 out.c:793 dns host added for
>> gmail.com@0x7f1fc3d5dc60: alt3.xmpp-server.l.google.com/5269 (20/0/842)
>> Mon Jan 16 15:31:58 2012 out.c:1077 dns ttl for gmail.com@0x7f1fc3d5dc60
>> limited to 842
>> Mon Jan 16 15:31:58 2012 out.c:1088 dns request for
>> gmail.com@0x7f1fc3d5dc60: A alt1.xmpp-server.l.google.com
>> Mon Jan 16 15:31:58 2012 out.c:1249 read action on fd 11
>> sx (io.c:191) 11 ready for reading
> 
> This looks ok. What happens next?

Now I'm pasting from diffrent log (but symptoms was the same, gmail.com
was resolved).
Mon Jan 16 17:12:43 2012 out.c:815 dns response for
gmail.com@0x7f6e77e5dc60: SRV _xmpp-server._tcp.gmail.com 5 (110)
Mon Jan 16 17:12:43 2012 out.c:822 dns response for
gmail.com@0x7f6e77e5dc60: SRV _xmpp-server._tcp.gmail.com[0]
alt1.xmpp-server.l.google.com/5269 (20/0)
Mon Jan 16 17:12:43 2012 out.c:793 dns host added for
gmail.com@0x7f6e77e5dc60: alt1.xmpp-server.l.google.com/5269 (20/0/110)
Mon Jan 16 17:12:43 2012 out.c:822 dns response for
gmail.com@0x7f6e77e5dc60: SRV _xmpp-server._tcp.gmail.com[1]
alt2.xmpp-server.l.google.com/5269 (20/0)
Mon Jan 16 17:12:43 2012 out.c:793 dns host added for
gmail.com@0x7f6e77e5dc60: alt2.xmpp-server.l.google.com/5269 (20/0/110)
Mon Jan 16 17:12:43 2012 out.c:822 dns response for
gmail.com@0x7f6e77e5dc60: SRV _xmpp-server._tcp.gmail.com[2]
alt3.xmpp-server.l.google.com/5269 (20/0)
Mon Jan 16 17:12:43 2012 out.c:793 dns host added for
gmail.com@0x7f6e77e5dc60: alt3.xmpp-server.l.google.com/5269 (20/0/110)
Mon Jan 16 17:12:43 2012 out.c:822 dns response for
gmail.com@0x7f6e77e5dc60: SRV _xmpp-server._tcp.gmail.com[3]
alt4.xmpp-server.l.google.com/5269 (20/0)
Mon Jan 16 17:12:43 2012 out.c:793 dns host added for
gmail.com@0x7f6e77e5dc60: alt4.xmpp-server.l.google.com/5269 (20/0/110)
Mon Jan 16 17:12:43 2012 out.c:822 dns response for
gmail.com@0x7f6e77e5dc60: SRV _xmpp-server._tcp.gmail.com[4]
xmpp-server.l.google.com/5269 (5/0)
Mon Jan 16 17:12:43 2012 out.c:793 dns host added for
gmail.com@0x7f6e77e5dc60: xmpp-server.l.google.com/5269 (5/0/110)
Mon Jan 16 17:12:43 2012 out.c:1077 dns ttl for gmail.com@0x7f6e77e5dc60
limited to 110
Mon Jan 16 17:12:43 2012 out.c:1088 dns request for
gmail.com@0x7f6e77e5dc60: A alt1.xmpp-server.l.google.com
Mon Jan 16 17:12:43 2012 router.c:296 read action on fd 6
sx (io.c:191) 6 ready for reading
sx (io.c:197) tag 6 event 2 data 0x77e71dd0
Mon Jan 16 17:12:43 2012 router.c:44 reading from 6
Mon Jan 16 17:12:43 2012 router.c:69 read 1024 bytes
sx (io.c:216) passed 1024 read bytes
sx (chain.c:93) calling io read chain
sx (io.c:240) decoded read data (1024 bytes): r:client'
type='unavailable' id='1391' from='mar...@mejor.pl/Gajim_'
to='xxx...@gmail.com'>http://jabberd.jabberstudio.org/ns/component/1.0' from='mejor.pl'
to='gmail.com'>
sx (chain.c:119) calling nad read chain
sx (io.c:156) tag 6 event 6 data 0x77e6a7d0
Mon Jan 16 17:12:43 2012 router.c:205 got a packet
Mon Jan 16 17:12:43 2012 out.c:403 trying to find connection for 'gmail.com'
Mon Jan 16 17:12:43 2012 out.c:406 connection for 'gmail.com' not found
Mon Jan 16 17:12:43 2012 out.c:431 pending resolution
Mon Jan 16 17:12:43 2012 out.c:125 queueing packet for 'mejor.pl/gmail.com'
sx (io.c:92) completed nad: 
sx (chain.c:119) calling nad read chain
sx (io.c:156) tag 6 event 6 data 0x77e68f90
[...]
Mon Jan 16 17:12:43 2012 out.c:125 queueing packet for 'mejor.pl/jabbim.pl'
sx (io.c:92) completed nad: 
sx (chain.c:119) calling nad read chain
sx (io.c:156) tag 6 event 6 data 0x77e72c50
Mon Jan 16 17:12:43 2012 router.c:205 got a packet
Mon Jan 16 17:12:43 2012 out.c:403 trying to find connection for 'gmail.com'
Mon Jan 16 17:12:43 2012 out.c:406 connection for 'gmail.com' not found
Mon Jan 16 17:12:43 2012 out.c:431 pending resolution
Mon Jan 16 17:12:43 2012 out.c:125 queueing packet for 'mejor.pl/gmail.com'
Mon Jan 16 17:12:43 2012 main.c:583 read action on fd 5
[...]
Mon Jan 16 17:12:43 2012 out.c:1029 dns response for
gmail.com@0x7f6e77e5dc60: A alt1.xmpp-server.l.google.com 1 (300)
Mon Jan 16 17:12:43 2012 out.c:1037 dns response for
gmail.com@0x7f6e77e5dc60: A alt1.xmpp-server.l.google.com[0]
209.85.175.125/5269
Mon Jan 16 17:12:43 2012 out.c:739 dns result adde

Re: Almost permanently problem "dns lookup for xxxx timed out"

2012-01-17 Thread Tomasz Sterna
Dnia 2012-01-16, pon o godzinie 18:19 +0100, Marcin Mirosław pisze:
> 1. First case, gmail is unreachable, in s2s debug log there is:
> [...]
> Mon Jan 16 15:31:58 2012 out.c:117 creating new out packet queue for
> 'mejor.pl/gmail.com'
> Mon Jan 16 15:31:58 2012 out.c:125 queueing packet for 'mejor.pl/gmail.com
> [...]
> Mon Jan 16 15:31:58 2012 out.c:1177 dns resolve for
> gmail.com@0x7f1fc3d5dc60 started
> [...]
> Mon Jan 16 15:31:58 2012 out.c:793 dns host added for
> gmail.com@0x7f1fc3d5dc60: alt2.xmpp-server.l.google.com/5269 (20/0/842)
> Mon Jan 16 15:31:58 2012 out.c:822 dns response for
> gmail.com@0x7f1fc3d5dc60: SRV _xmpp-server._tcp.gmail.com[4]
> alt3.xmpp-server.l.google.com/5269 (20/0)
> Mon Jan 16 15:31:58 2012 out.c:793 dns host added for
> gmail.com@0x7f1fc3d5dc60: alt3.xmpp-server.l.google.com/5269 (20/0/842)
> Mon Jan 16 15:31:58 2012 out.c:1077 dns ttl for gmail.com@0x7f1fc3d5dc60
> limited to 842
> Mon Jan 16 15:31:58 2012 out.c:1088 dns request for
> gmail.com@0x7f1fc3d5dc60: A alt1.xmpp-server.l.google.com
> Mon Jan 16 15:31:58 2012 out.c:1249 read action on fd 11
> sx (io.c:191) 11 ready for reading

This looks ok. What happens next?


> 2. Second case, i restarted s2s daemon and i get similar behavior on
> client "remote-server-not-found". This time there is no messages like
> "out.c:822 dns response for gmail.com@0x7f1fc3d5dc60: SRV
> _xmpp-server._tcp.gmail.com[4] alt3.xmpp-server.l.google.com/5269
> (20/0)" in s2s debug log.

Looks like your resolver is failing.


> Mon Jan 16 16:53:56 2012 out.c:793 dns host added for
> marcel.pl@0x7fe5d27b01a0: maraton.marcel.pl/5269 (0/0/2901)
> Mon Jan 16 16:53:56 2012 out.c:1077 dns ttl for marcel.pl@0x7fe5d27b01a0
> limited to 2901
> Mon Jan 16 16:53:56 2012 out.c:1088 dns request for
> marcel.pl@0x7fe5d27b01a0: A maraton.marcel.pl
> Mon Jan 16 16:53:56 2012 router.c:296 read action on fd 6
> sx (io.c:191) 6 ready for reading

Also looks good. What happens next?







Almost permanently problem "dns lookup for xxxx timed out"

2012-01-16 Thread Marcin Mirosław
Hello,
i've got problem to connect to some users. Problem is partly random and
partly permanent. It's not ease to describe all cases.
Permanently i can't connect to users in domain: gmail.com. On roster i
have info "remote-server-not-found", in s2s.log i have "dns lookup for
gmail.com timed out".
1. First case, gmail is unreachable, in s2s debug log there is:
[...]
sx (io.c:240) decoded read data (1024 bytes): http://jabberd.jabberstudio.org/ns/component/1.0' from='mejor.pl'
to='gmail.com'>
Mon Jan 16 15:31:58 2012 out.c:403 trying to find connection for 'gmail.com'
Mon Jan 16 15:31:58 2012 out.c:406 connection for 'gmail.com' not found
Mon Jan 16 15:31:58 2012 out.c:412 no dns for gmail.com, preparing for
resolution
Mon Jan 16 15:31:58 2012 out.c:440 requesting resolution for gmail.com
Mon Jan 16 15:31:58 2012 out.c:1177 dns resolve for
gmail.com@0x7f1fc3d5dc60 started
Mon Jan 16 15:31:58 2012 out.c:839 dns request for
gmail.com@0x7f1fc3d5dc60: SRV xmpp-server
Mon Jan 16 15:31:58 2012 out.c:117 creating new out packet queue for
'mejor.pl/gmail.com'
Mon Jan 16 15:31:58 2012 out.c:125 queueing packet for 'mejor.pl/gmail.com
[...]
Mon Jan 16 15:31:58 2012 out.c:1177 dns resolve for
gmail.com@0x7f1fc3d5dc60 started
Mon Jan 16 15:31:58 2012 out.c:839 dns request for
gmail.com@0x7f1fc3d5dc60: SRV xmpp-server
[...]
Mon Jan 16 15:31:58 2012 out.c:815 dns response for
gmail.com@0x7f1fc3d5dc60: SRV _xmpp-server._tcp.gmail.com 5 (842)
Mon Jan 16 15:31:58 2012 out.c:822 dns response for
gmail.com@0x7f1fc3d5dc60: SRV _xmpp-server._tcp.gmail.com[0]
alt4.xmpp-server.l.google.com/5269 (20/0)
Mon Jan 16 15:31:58 2012 out.c:793 dns host added for
gmail.com@0x7f1fc3d5dc60: alt4.xmpp-server.l.google.com/5269 (20/0/842)
Mon Jan 16 15:31:58 2012 out.c:822 dns response for
gmail.com@0x7f1fc3d5dc60: SRV _xmpp-server._tcp.gmail.com[1]
xmpp-server.l.google.com/5269 (5/0)
Mon Jan 16 15:31:58 2012 out.c:793 dns host added for
gmail.com@0x7f1fc3d5dc60: xmpp-server.l.google.com/5269 (5/0/842)
Mon Jan 16 15:31:58 2012 out.c:822 dns response for
gmail.com@0x7f1fc3d5dc60: SRV _xmpp-server._tcp.gmail.com[2]
alt1.xmpp-server.l.google.com/5269 (20/0)
Mon Jan 16 15:31:58 2012 out.c:793 dns host added for
gmail.com@0x7f1fc3d5dc60: alt1.xmpp-server.l.google.com/5269 (20/0/842)
Mon Jan 16 15:31:58 2012 out.c:822 dns response for
gmail.com@0x7f1fc3d5dc60: SRV _xmpp-server._tcp.gmail.com[3]
alt2.xmpp-server.l.google.com/5269 (20/0)
Mon Jan 16 15:31:58 2012 out.c:793 dns host added for
gmail.com@0x7f1fc3d5dc60: alt2.xmpp-server.l.google.com/5269 (20/0/842)
Mon Jan 16 15:31:58 2012 out.c:822 dns response for
gmail.com@0x7f1fc3d5dc60: SRV _xmpp-server._tcp.gmail.com[4]
alt3.xmpp-server.l.google.com/5269 (20/0)
Mon Jan 16 15:31:58 2012 out.c:793 dns host added for
gmail.com@0x7f1fc3d5dc60: alt3.xmpp-server.l.google.com/5269 (20/0/842)
Mon Jan 16 15:31:58 2012 out.c:1077 dns ttl for gmail.com@0x7f1fc3d5dc60
limited to 842
Mon Jan 16 15:31:58 2012 out.c:1088 dns request for
gmail.com@0x7f1fc3d5dc60: A alt1.xmpp-server.l.google.com
Mon Jan 16 15:31:58 2012 out.c:1249 read action on fd 11
sx (io.c:191) 11 ready for reading
sx (io.c:197) tag 11 event 2 data 0xc3d9e7a0
Mon Jan 16 15:31:58 2012 out.c:1401 reading from 11
Mon Jan 16 15:31:58 2012 out.c:1445 read 186 bytes
sx (io.c:216) passed 186 read bytes
sx (chain.c:93) calling io read chain

2. Second case, i restarted s2s daemon and i get similar behavior on
client "remote-server-not-found". This time there is no messages like
"out.c:822 dns response for gmail.com@0x7f1fc3d5dc60: SRV
_xmpp-server._tcp.gmail.com[4] alt3.xmpp-server.l.google.com/5269
(20/0)" in s2s debug log.

3. Let me talk about other domain "marcel.pl". Sometimes i can connect
to users, next i restart jabberd (or s2s daemon) and then i can't
connect to them. Then i do e.g. 4 restarts and i can connect to them agains.
In case i can connect to them i've got in s2s debug log section:
Mon Jan 16 16:53:56 2012 out.c:815 dns response for
marcel.pl@0x7fe5d27b01a0: SRV _xmpp-server._tcp.marcel.pl 1 (2901)
Mon Jan 16 16:53:56 2012 out.c:822 dns response for
marcel.pl@0x7fe5d27b01a0: SRV _xmpp-server._tcp.marcel.pl[0]
maraton.marcel.pl/5269 (0/0)
Mon Jan 16 16:53:56 2012 out.c:793 dns host added for
marcel.pl@0x7fe5d27b01a0: maraton.marcel.pl/5269 (0/0/2901)
Mon Jan 16 16:53:56 2012 out.c:1077 dns ttl for marcel.pl@0x7fe5d27b01a0
limited to 2901
Mon Jan 16 16:53:56 2012 out.c:1088 dns request for
marcel.pl@0x7fe5d27b01a0: A maraton.marcel.pl
Mon Jan 16 16:53:56 2012 router.c:296 read action on fd 6
sx (io.c:191) 6 ready for reading
sx (io.c:197) tag 6 event 2 data 0xd27c

In case "remote-server-not-found" i've got in s2s debug log only "dns
lookup for marcel.pl timed out".


In all cases i tried with and without firewall, with resolver set to
127.0.0.1 (bind) and set to 8.8.8.8 (google). I didn't notice any
diffrence. I can provide full debug log, strace log, but i would prefer
to not disclose jid of users from my roster.
All test i did wiyh loc