I did restart xinetd again for good measure, and no dice. inetd is not running: # ps -e | grep inet 1613 ? 00:00:00 xinetd <end> netstat -ap --ip does *not* show amanda. Maybe we are getting somewhere... Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 localhost:smtp *:* LISTEN 331/master udp 0 0 *:bootps *:* 220/dhcpd raw 0 0 *:icmp *:* 7 220/dhcpd
There is postfix and dhcp, but no amanda. What should this be telling me? -----Original Message----- From: Christopher McCrory [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 4:42 PM To: amanda-users Cc: Jeff Stewart Subject: Re: amcheck works with inetd, fails with xinetd Hello... could you be: running inetd and xinetd at the same time? one is holding the port open... not have restarted xinetd? does a 'netstat -ap --ip' show amanda? netstat -ap --ip| grep aman ... udp 0 0 *:amanda *:* 10362/xinetd ... Jeff Stewart wrote: > It didn't change the outcome if I set the user to amanda or the group = > disk. Also, I do have a amidxtape entry, I just forgot to put it in the > original entry: > amidxtape 10083/tcp > Do I need a port entry in xinetd if its in /etc/services? > Here are the results of nmap: > Port State Service > 22/tcp open ssh > 10082/tcp open amandaidx > 10083/tcp open amidxtape > Is this all I should see? /var/log/xinetd.log is not very helpful. > Developing a desk-shaped bruise on my forehead, > Jeff > > > -----Original Message----- > From: Stephen Carville [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 14, 2002 1:50 PM > To: Jeff Stewart > Cc: [EMAIL PROTECTED] > Subject: Re: amcheck works with inetd, fails with xinetd > > > On Thu, 14 Feb 2002, Jeff Stewart wrote: > > - Apologies if this has been asked before. I've searched google and the list > - archives and have not found an answer that works for me. > - On a SuSE 7.3 box, amcheck is working fine when I run inetd, but is > failing > - when I run xinetd. I'm getting everybody's favorite error: selfcheck > request > - timed out. > - Since it is working with inetd but not with xinetd, it should be a problem > - with xinetd.conf, right? I am not getting any errors in /var/log/messages, > - and debug files are being created in /tmp/amanda. > - I definitely need this working with xinetd instead of inted. > - Thanks, > - Jeff Stewart > > Dunno if this matters but I set the user on all three services to > 'amanda'. Also you do not have amidxtape in /etc/services and no port > specified in xinetd.conf. > > Maybe add an explicit 'disable = no' ? AFAIK this is the default but > maybe SUSE changed that. > > - inetd.conf is: > - amandaidx stream tcp nowait root /usr/lib/amanda/amindexd amindexd > - amidxtape stream tcp nowait root /usr/lib/amanda/amidxtaped amidxtaped > - amanda dgram udp wait amanda /usr/lib/amanda/amandad amandad > - > - xinetd.conf is: > - defaults > - { > - log_type = FILE /var/log/xinetd.log > - log_on_success = HOST EXIT DURATION > - log_on_failure = HOST ATTEMPT RECORD > - instances = 2 > - } > - service amandaidx > - { > - socket_type = stream > - protocol = tcp > - wait = no > - user = root > - server = /usr/lib/amanda/amindexd > - } > - service amidxtape > - { > - socket_type = stream > - protocol = tcp > - wait = no > - user = root > - server = /usr/lib/amanda/amidxtaped > - } > - service amanda > - { > - socket_type = dgram > - protocol = udp > - wait = yes > - user = amanda > - server = /usr/lib/amanda/amandad > - } > - > - /etc/services is: > - amanda 10080/tcp > - amanda 10080/udp > - amandaidx 10082/tcp > - > - > > -- > -- Stephen Carville > UNIX and Network Administrator > DPSI (formerly Ace USA Flood Services) > 310-342-3602 > [EMAIL PROTECTED] > -- Christopher McCrory "The guy that keeps the servers running" [EMAIL PROTECTED] http://www.pricegrabber.com Linux: Because rebooting is for adding new hardware
