Did you remember to HUP inetd after changing inetd.conf? Also, check your system logs to see if inetd had a problem with your entry. Don't worry about your .amandahosts yet, if it was having a problem with that you would be getting a different error similar to "access as amanda not allowed from user@localhost"
Frank --On Monday, April 15, 2002 18:38:17 +0100 Axel Schaefer <[EMAIL PROTECTED]> wrote: > Hi amanda-users. > > I'm new to Amanda and want to use it for some backups. In the first (and yet the >only) case, the backup server is equals the backup client. I know, that my question >is a FAQ, but the Answers on FAQ-O-MATIC didn't solve the problem (so, this is a > NEWBIE-ALERT! =;-)). > > If I try to use: > > amanda@linux:> amcheck -c DailySet1 > > the following error appears: > > /----------------------------------------------------------------- >| Amanda Backup Client Hosts Check >| -------------------------------- >| WARNING: localhost: selfcheck request timed out. Host down? >| Client check: 1 host checked in 30.007 seconds, 1 problem found >| >| (brought to you by Amanda 2.4.2p2) > \----------------------------------------------------------------- > > I've checked the inetd.conf, and I think, that the amanda.conf in >/etc/amanda/DailySet1 is OK. I only set new paths to the infofile, logdir, indexdir, >tapelist. > The .amandahosts (in var/lib/amanda) shows this: > > amanda@ll11:~> less .amandahosts > localhost amanda > localhost root > > I've commented out both lines and tried it with only root-access and amanda-access. >IIRC, amanda uses one line for the client (root) and one line for the server >(amanda). So it seems OK, if localhost amanda is set (isn't it?). > > I'm a bit irritated if the the server-client works properly, when it's is on one >computer. Can you help? > > Thanks. > AxxL -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
