DSSI

Email Archive: dssi-devel (read-only)

Re: [DSSI] Time to GUI resolved!

From: Thorsten Wilms <t_w_@fr...> - 2005-07-09 12:11

On Wed, Jun 29, 2005 at 07:05:25PM +0200, Thorsten Wilms wrote:
> Hi!
> 
> DSSI GUIs take ages until they appear on screen on my system, 
> no matter if I use jack-dssi-host or om.
> With jack-dssi-host it takes about 20 seconds until it says 
> host:ready and another 20 seconds before a plugin window 
> appears.
> 
> It seems the host tries to contact 192.168.1.1 (my router), 
> even though it should look into /etc/hosts and be happy 
> with that. So after a long timeout, it finaly decides 
> to stick with the info from the hosts file.
> 
> /etc/hosts:
>   127.0.0.1 localhost charly
> 
> from /etc/host.conf
>   order hosts, bind


I also had an issue with a small number of URLs not being 
resolved, fun stuff like this, which happen only since  
some months and not when i'm on windows:

$ nslookup www.google.de
;; reply from unexpected source: 217.237.149.161#53, expected 192.168.1.1#53

$ nslookup google.de
Server:         192.168.1.1
Address:        192.168.1.1#53
Non-authoritative answer:
Name:   google.de
Address: 216.239.57.104


So I decided to try a public name server instead of relying 
on my router fetching name server adresses from my provider. 
Everything gets resolved again.

From starting jack-dssi-host to a plgin window appearing 
now takes 4 seconds max, instead of 40 like before.

But I still wonder why anything external is involved with  
resolving localhost. That's why I didn't think of a connection 
between the 2 issues, sorry for that.


---
Thorsten Wilms

Thread View

Thread	Author	Date
[DSSI] Time to GUI	Thorsten Wilms <t_w_@fr...>

Re: [DSSI] Time to GUI

From: Hans Fugal <hans@fu...> - 2005-06-29 18:26

Attachments: Message as HTML

check your /etc/nsswitch.conf, the hosts line.

On Wed, 29 Jun 2005 at 19:05 +0200, Thorsten Wilms wrote:
> Hi!
>=20
> DSSI GUIs take ages until they appear on screen on my system,=20
> no matter if I use jack-dssi-host or om.
> With jack-dssi-host it takes about 20 seconds until it says=20
> host:ready and another 20 seconds before a plugin window=20
> appears.
>=20
> It seems the host tries to contact 192.168.1.1 (my router),=20
> even though it should look into /etc/hosts and be happy=20
> with that. So after a long timeout, it finaly decides=20
> to stick with the info from the hosts file.
>=20
> /etc/hosts:
> 127.0.0.1 localhost charly
>=20
> from /etc/host.conf
> order hosts, bind
>=20
> There's a strace -tt file here:
> http://wrstud.uni-wuppertal.de/~ka0394/forum/strace_4.bz2
>=20
>=20
> So is the above intertation correct? Is there=20
> something wrong with DSSI (or at least 2 host=20
> implementations), or is my system/network misbehaving?
>=20
>=20
> ---
> Thorsten Wilms
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick
> _______________________________________________
> DSSI-devel mailing list
> DSSI-devel@lists.sourceforge.net /> > https://lists.sourceforge.net/lists/listinfo/dssi-devel
>=20

--=20
.O. Hans Fugal | De gustibus non disputandum est.
..O http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg
OOO | WindowMaker, gaim, UTF-8, RISC, JS Bach
---------------------------------------------------------------------
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460

Re: [DSSI] Time to GUI

From: Thorsten Wilms <t_w_@fr...> - 2005-06-29 18:43

On Wed, Jun 29, 2005 at 12:26:38PM -0600, Hans Fugal wrote:
> check your /etc/nsswitch.conf, the hosts line.

hosts: files dns

---
Thorsten Wilms

Re: [DSSI] Time to GUI

From: Hans Fugal <hans@fu...> - 2005-06-29 20:38

Attachments: Message as HTML

On Wed, 29 Jun 2005 at 20:42 +0200, Thorsten Wilms wrote:
> On Wed, Jun 29, 2005 at 12:26:38PM -0600, Hans Fugal wrote:
> > check your /etc/nsswitch.conf, the hosts line.
>=20
> hosts: files dns

Looks right. Oh well, it was just a wild guess.

--=20
.O. Hans Fugal | De gustibus non disputandum est.
..O http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg
OOO | WindowMaker, gaim, UTF-8, RISC, JS Bach
---------------------------------------------------------------------
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460

Re: [DSSI] Time to GUI

From: Steve Harris <S.Harris@ec...> - 2005-06-29 20:51

On Wed, Jun 29, 2005 at 07:05:25PM +0200, Thorsten Wilms wrote:
> /etc/hosts:
> 127.0.0.1 localhost charly
>
> from /etc/host.conf
> order hosts, bind
>
> There's a strace -tt file here:
> http://wrstud.uni-wuppertal.de/~ka0394/forum/strace_4.bz2
>
>
> So is the above intertation correct? Is there
> something wrong with DSSI (or at least 2 host
> implementations), or is my system/network misbehaving?

I would guess it has to be a combination of both. My knowledge of networky
stuff is rough, but I work with some netwroking researchers, so I'l ask
them if they have any ideas.

- Steve

Re: [DSSI] Time to GUI

From: Thorsten Wilms <t_w_@fr...> - 2005-06-30 07:42

On Wed, Jun 29, 2005 at 10:03:49PM +0100, Steve Harris wrote:
> What does route -n show?

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

Just route says this:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
. * 255.255.255.0 U 0 0 0 eth0
loopback localhost 255.0.0.0 UG 0 0 0 lo
default my.router 0.0.0.0 UG 0 0 0 eth0

---
Thorsten Wilms

Re: [DSSI] Time to GUI resolved!

From: Thorsten Wilms <t_w_@fr...> - 2005-07-09 12:11

On Wed, Jun 29, 2005 at 07:05:25PM +0200, Thorsten Wilms wrote:
> Hi!
>
> DSSI GUIs take ages until they appear on screen on my system,
> no matter if I use jack-dssi-host or om.
> With jack-dssi-host it takes about 20 seconds until it says
> host:ready and another 20 seconds before a plugin window
> appears.
>
> It seems the host tries to contact 192.168.1.1 (my router),
> even though it should look into /etc/hosts and be happy
> with that. So after a long timeout, it finaly decides
> to stick with the info from the hosts file.
>
> /etc/hosts:
> 127.0.0.1 localhost charly
>
> from /etc/host.conf
> order hosts, bind

I also had an issue with a small number of URLs not being
resolved, fun stuff like this, which happen only since
some months and not when i'm on windows:

$ nslookup www.google.de
;; reply from unexpected source: 217.237.149.161#53, expected 192.168.1.1#53

$ nslookup google.de
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
Name: google.de
Address: 216.239.57.104

So I decided to try a public name server instead of relying
on my router fetching name server adresses from my provider.
Everything gets resolved again.

From starting jack-dssi-host to a plgin window appearing
now takes 4 seconds max, instead of 40 like before.

But I still wonder why anything external is involved with
resolving localhost. That's why I didn't think of a connection
between the 2 issues, sorry for that.

---
Thorsten Wilms

Re: [DSSI] Time to GUI resolved!

From: Steve Harris <S.Harris@ec...> - 2005-07-11 09:05

On Sat, Jul 09, 2005 at 02:11:53 +0200, Thorsten Wilms wrote:
> But I still wonder why anything external is involved with
> resolving localhost. That's why I didn't think of a connection
> between the 2 issues, sorry for that.

No idea, but it must be a misconfiguration somewhere.

- Steve

Re: [DSSI] Time to GUI resolved!

From: Hans Fugal <hans@fu...> - 2005-07-11 14:30

Attachments: Message as HTML

Maybe you could post /etc/hosts and /etc/resolv.conf

On Sat, 9 Jul 2005 at 14:11 +0200, Thorsten Wilms wrote:
> On Wed, Jun 29, 2005 at 07:05:25PM +0200, Thorsten Wilms wrote:
> > Hi!
> >=20
> > DSSI GUIs take ages until they appear on screen on my system,=20
> > no matter if I use jack-dssi-host or om.
> > With jack-dssi-host it takes about 20 seconds until it says=20
> > host:ready and another 20 seconds before a plugin window=20
> > appears.
> >=20
> > It seems the host tries to contact 192.168.1.1 (my router),=20
> > even though it should look into /etc/hosts and be happy=20
> > with that. So after a long timeout, it finaly decides=20
> > to stick with the info from the hosts file.
> >=20
> > /etc/hosts:
> > 127.0.0.1 localhost charly
> >=20
> > from /etc/host.conf
> > order hosts, bind
>=20
>=20
> I also had an issue with a small number of URLs not being=20
> resolved, fun stuff like this, which happen only since =20
> some months and not when i'm on windows:
>=20
> $ nslookup www.google.de
> ;; reply from unexpected source: 217.237.149.161#53, expected 192.168.1.1=
#53
>=20
> $ nslookup google.de
> Server: 192.168.1.1
> Address: 192.168.1.1#53
> Non-authoritative answer:
> Name: google.de
> Address: 216.239.57.104
>=20
>=20
> So I decided to try a public name server instead of relying=20
> on my router fetching name server adresses from my provider.=20
> Everything gets resolved again.
>=20
> From starting jack-dssi-host to a plgin window appearing=20
> now takes 4 seconds max, instead of 40 like before.
>=20
> But I still wonder why anything external is involved with =20
> resolving localhost. That's why I didn't think of a connection=20
> between the 2 issues, sorry for that.
>=20
>=20
> ---
> Thorsten Wilms
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar happen=
ing
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted by H=
P,
> AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> DSSI-devel mailing list
> DSSI-devel@lists.sourceforge.net /> > https://lists.sourceforge.net/lists/listinfo/dssi-devel
>=20

--=20
.O. Hans Fugal | De gustibus non disputandum est.
..O http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg
OOO | WindowMaker, gaim, UTF-8, RISC, JS Bach
---------------------------------------------------------------------
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460

Re: [DSSI] Time to GUI resolved!

From: Thorsten Wilms <t_w_@fr...> - 2005-07-11 15:04

On Mon, Jul 11, 2005 at 08:30:48AM -0600, Hans Fugal wrote:
> Maybe you could post /etc/hosts and /etc/resolv.conf

hosts:
127.0.0.1 localhost charly

from hosts.conf:
order hosts, bind

resolve.conf:
nameserver 217.115.138.24
nameserver 194.164.6.112
nameserver 192.168.1.1

Before the change it was just:
nameserver 192.168.1.1

leaving it to my router to use the name server my provider
points to.

---
Thorsten Wilms

Re: [DSSI] Time to GUI resolved!

From: Hans Fugal <hans@fu...> - 2005-07-11 15:16

Attachments: Message as HTML

Odd - everything looks ok. I'm reminded that when I was using my dsl
modem for DNS I would get delays for many things (but never localhost
IIRC, which I may not), and the culprit was ipv6 and my router's
complete inability to deal with AAAA records properly. You might look
into whether you have ipv6 in the kernel (whether the module is actually
loaded or the interface up seems to be irrelevant), and consider
appending this to /etc/hosts:

# The following lines are desirable for IPv6 capable hosts
# (added automatically by netbase upgrade)
=20
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastfix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Good luck.

On Mon, 11 Jul 2005 at 17:04 +0200, Thorsten Wilms wrote:
> On Mon, Jul 11, 2005 at 08:30:48AM -0600, Hans Fugal wrote:
> > Maybe you could post /etc/hosts and /etc/resolv.conf
>=20
> hosts:
> 127.0.0.1 localhost charly
>=20
> from hosts.conf:
> order hosts, bind
>=20
> resolve.conf:
> nameserver 217.115.138.24
> nameserver 194.164.6.112
> nameserver 192.168.1.1
>=20
>=20
> Before the change it was just:
> nameserver 192.168.1.1
>=20
> leaving it to my router to use the name server my provider=20
> points to.
>=20
>=20
> ---
> Thorsten Wilms
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar happen=
ing
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted by H=
P,
> AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> DSSI-devel mailing list
> DSSI-devel@lists.sourceforge.net /> > https://lists.sourceforge.net/lists/listinfo/dssi-devel
>=20

--=20
.O. Hans Fugal | De gustibus non disputandum est.
..O http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg
OOO | WindowMaker, gaim, UTF-8, RISC, JS Bach
---------------------------------------------------------------------
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460

Re: [DSSI] Time to GUI resolved!

From: Thorsten Wilms <t_w_@fr...> - 2005-07-11 15:35

On Mon, Jul 11, 2005 at 09:16:27AM -0600, Hans Fugal wrote:
> Odd - everything looks ok. I'm reminded that when I was using my dsl
> modem for DNS I would get delays for many things (but never localhost
> IIRC, which I may not), and the culprit was ipv6 and my router's
> complete inability to deal with AAAA records properly. You might look
> into whether you have ipv6 in the kernel (whether the module is actually
> loaded or the interface up seems to be irrelevant), and consider
> appending this to /etc/hosts:

No ipv6 here.
Have I mentioned that ping never had a problem resolving localhost
(or charly)? Always worked without a noticeable delay.

> Good luck.

Well, thanks. :)

---
Thorsten Wilms

Re: [DSSI] Time to GUI resolved!

From: Sean Bolton <smbolton@jp...> - 2005-07-11 20:07

On Jul 11, 2005, at 2:04 AM, Steve Harris wrote:
> On Sat, Jul 09, 2005 at 02:11:53 +0200, Thorsten Wilms wrote:
>> But I still wonder why anything external is involved with
>> resolving localhost. That's why I didn't think of a connection
>> between the 2 issues, sorry for that.
>
> No idea, but it must be a misconfiguration somewhere.

... or it could be a glibc bug. I'm tty confident my system is
correctly configured to use files before DNS, but I still get
the delay in any app that creates a liblo server when the
link between my machine and the DNS server(s) specified in
resolv.conf is down. Digging further, I find that the delay
occurs during the call to getnameinfo(), and there's a note in
the glibc 2.3.3 BUGS file saying:

[ *] Some of the functions which also handled IPv6 are currently
broken.
IPv6 and IPv4 lookups occasionally happen when not needed. This
happens in getaddrinfo() and getnameinfo(). IPv4 handling of
these functions is OK though and there are patches available to
fix
the IPv6 code as well.

"IPv4 handling of these functions is OK" but "IPv4 lookups occasionally
happen when not needed"? Not sure what that means.

Anyway, I've dug about as far as I have time for. For the time being,
I find commenting out the getnameinfo() call liblo's src/server.c
provides
an effective if IPv6-unfriendly workaround :-/.

-Sean

DSSI

Email Archive: dssi-devel (read-only)

Thread View

About SourceForge

Find Software

Develop Software

Community

Help