[nas] 1.4.2b runtime problems

[Jon Trulson]

On Thu, 18 Oct 2001, Matt Schalit wrote:

> Date: Thu, 18 Oct 2001 00:36:51 -0700
> From: Matt Schalit <mschalit at pacbell.net>
> To: nas at radscan.com
> Subject: Re: [nas] 1.4.2b runtime problems
> 
> Jon Trulson wrote:
> > 
> > On Wed, 17 Oct 2001, Matt Schalit wrote:
> 
> > > Hi folks,
> > >
> > >   I built and installed nas-1.4.2b on UnixWare 7.1.1.
> > > When I go to test the system in X, using a terminal
[...]

> > rather than nasd... X listens on port 6000 and nasd on 8000, so I'm not
> > really sure how that can happen...
> 
> 
> I think you're right about it connecting to the X server somehow.
> When the X server wasn't running, I just got the message that
>      auinfo: unable to connect to audio server.
> 

	Weird.


> >         Does a netstat -a show you anything useful?
> 
> Once I've run nasd -aa &, I can see is listening
> on port 8000.
> 

	Well, that's good anyway... So why are the clients (I
presume) attempting to connect to 6000? hmm.

>  
> 
> > >   What'd I do wrong?  If it helps at all, here's
> > > what nasd reported when I started it:
> > >
> > 
> >         doesn't look like the client (auinfo) even made it to nasd.  
> > very strange.
> > 
> >         What does it do when you aren't running an X server?  Any diff?
> 
> 
> 
> I ran nasd -aa & and then tried all these without X:
> 

     auinfo -audio :0 ?  Probably won't matter....

>    auinfo -audio yoda:0
>    auinfo -audio tcp/yoda:0
> 
>    auinfo -audio yoda:8000
>    auinfo -audio tcp/yoda:8000
> 
>    auinfo -audio 10.1.1.1:0
>    auinfo -audio tcp/10.1.1.1:0
> 
>    auinfo -audio 10.1.1.1:8000
>    auinfo -audio tcp/10.1.1.1:8000
> 
> 
> All them returned the same error:
>     auinfo: unable to connect to audio server.

	Did 'nasd -v -d 99' show any connect attempts?  What happens if
you do a 'telnet localhost 8000'?  does nasd react?  I'm just throwing
things out here, as I stopped at UnixWare 2.03 (which I'm still running
BTW).  It works fine there...  Not sure where else to go here other than
start debugging (maybe starting with truss) and see if the library really
is trying to get to port 6000, and why...  I've never seen or heard of
this problem before...

[...]

-- 
Jon Trulson    mailto:jon at radscan.com
ID: 1A9A2B09, FP: C23F328A721264E7 B6188192EC733962
PGP keys at http://radscan.com/~jon/PGPKeys.txt
#include <std/disclaimer.h>
Bad Color Temperature, Too much Peach.