Completely Stuck :-(

2000-11-24 Thread John Cartwright
Hi I'm hoping someone can shed some light on this one, basically I'm convinced amandad never runs from inetd, and I"ve spent days on this so far :-( I'm trying to install Amanda on a Solaris 8 x86 box, where the client and server are one and the same. Installation options were --with- user=a

Re: Completely Stuck :-(

2000-11-24 Thread John Cartwright
Hi Thanks to Paul and Martin for the advice, although it didn't solve the problem! I thought the indexing services were optional, anyway? - John

Re: Completely Stuck :-(

2000-11-24 Thread Joi Ellis
On Fri, 24 Nov 2000, John Cartwright wrote: >Date: Fri, 24 Nov 2000 09:52:55 -0500 >From: John Cartwright <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Completely Stuck :-( > >Hi > >I'm hoping someone can shed some light on this one, basically I'm

Re: Completely Stuck :-(

2000-11-27 Thread John R. Jackson
>I'm hoping someone can shed some light on this one, basically I'm >convinced amandad never runs from inetd, and I"ve spent days on this >so far :-( Then it's definitly time to ask :-). >and inetd has (on one line!): > >amanda dgram udp wait >amanda /opt/local/libexec/amandad

Re: Completely Stuck :-(

2000-11-28 Thread John Cartwright
Hi > This says, as you sort of suspected, that inetd is not able to run > amandad for some reason. It is, however listening on the port and so > forth, so that part's configured properly. Just to be sure: bash-2.03# lsof -i | grep am inetd 19686 root 11u IPv4 0xe1dfac2c0t0 UDP *:

Re: Completely Stuck :-(

2000-11-28 Thread Alexandre Oliva
On Nov 28, 2000, John Cartwright <[EMAIL PROTECTED]> wrote: > bash-2.03# lsof -i | grep am > inetd 19686 root 11u IPv4 0xe1dfac2c0t0 UDP *:amanda (Idle) See, it's not (LISTEN), which means inetd has disabled the service because of a previous failure. kill -HUP it and see if the st

Re: Completely Stuck :-(

2000-11-28 Thread John R. Jackson
>Just to be sure: > >bash-2.03# lsof -i | grep am >inetd 19686 root 11u IPv4 0xe1dfac2c0t0 UDP *:amanda (Idle) That's what my system looks like, too. To make my day and contradict Alexandre :-), lsof does not appear to report UDP ports as being in LISTEN state. So this looks OK.

Re: Completely Stuck :-(

2000-11-29 Thread John Cartwright
>> bash-2.03# lsof -i | grep am >> inetd 19686 root 11u IPv4 0xe1dfac2c0t0 UDP *:amanda (Idle) > > See, it's not (LISTEN), which means inetd has disabled the service > because of a previous failure. kill -HUP it and see if the state > changes. I hate to disagree with you, but in my

Re: Completely Stuck :-(

2000-11-29 Thread Alexandre Oliva
On Nov 29, 2000, John Cartwright <[EMAIL PROTECTED]> wrote: >> See, it's not (LISTEN), which means inetd has disabled the service > I hate to disagree with you, but in my experience Solaris always > reports UDP ports as idle. I stand corrected. Thank you and JJ for pointing out my mistake. --

Re: Completely Stuck :-(

2000-12-04 Thread John Cartwright
> OK, here's the next idea. Instead of running a script, run truss > directly by changing the inetd.conf line to this: > > amanda dgram udp waitbackup /bin/truss amandad >-fo /tmp/amandad.truss /opt/amanda/libexec/amandad > Hi This didn't work. In fact, on further invest

Re: Completely Stuck :-(

2000-12-04 Thread John R. Jackson
>... In fact, on further investigation, *nothing* works >from inetd unless its running as root! ... Yikes. After you send inetd a HUP (and wait a minute), is there anything of interest in /var/adm/messages? Do you actually have a user "amanda" (or whatever) defined? Is it local (/etc/passwd)