Hi, I have amanda-2.4.2p2 up and running for quite some time. It's working fine. Every now and then I fall across some funny behaviour when adding new clients to a configuration. This happens on linux machines (redhat 7.x) using xinetd.
To allow access to the amanda service via xinetd I add a file /etc/xinetd.d/amanda with appropriate entries. I restart xinetd of course. Then I would like to mount amanda's home from some other linux machine where amanda is already doing well. So I export /usr/amanda from the other machine and mount it on the new machine. No problem so far. Then I add the necessary entries on the amanda server in the disklist file and run amcheck on this config afterwards to see if it works. I get a 'host timed out' error on the machine I want to add and when I have a look in the logfile on that host I see: (...) Nov 19 08:03:19 xxx xinetd[18451]: Deactivating service amanda due to excessive incoming connections. Restarting in 30 seconds. Nov 19 08:03:49 xxx xinetd[18451]: Activating service amanda (...) I tried to play with the available options in the /etc/xinetd.d/amanda file first, but that did not help (maybe I did it the wrong way). Obviously I can get around the problem, when I do not mount /usr/amanda from the other machine but compile amanda on the new machine and install it locally. Then my amcheck reports 'everything ok' and the backup will run. So, it's not a showstopper for my backup. I'm simply wondering why this is happening. Any ideas? Kind regards, Urte --
