Hi,
I had Amanda server running for half year and I want to add a client
these days.
However, after I installed the client and tried to run amcheck, the
server pop-up an error
"WARNING: client.machine: selfcheck request timed out. Host down?"
When I checked the error log on the client, I got
For the record, I finally figured out what the problem was. (!!!)
In /etc/services on the problematic clients, I had all of my custom ports listed, as
well as the default ports (10080, etc).
I had the default ports (10080 TCP/UP) at the very bottom, below all of my custom
ports. I moved the de
On Mon, Jul 28, 2003 at 04:58:29PM -0500, Martin, Jeremy wrote:
> My amanda server is having problems connecting to a client. It's working great with
> a number of other clients, but this one client keeps trying to frustrate me.
> [awesomely complete situation report deleted]
>
> Any ideas of oth
lication bug: dumper(20085) has SIGCHLD set to
SIG_IGN but calls wait().
Jul 28 05:55:16 theisland kernel: (see the NOTES section of 'man 2 wait'). Workaround
activated.
However I've done some Google searches and these appear to be harmless, plus the fact
that the other servers are be
On Wed, Oct 10, 2001 at 09:13:17AM -0500, Lee Fedor wrote:
>
> service amanda
> {
> disable = no
> socket_type = dgram
> protocol= udp
> wait= yes
> user= dump
> gro
> IIRC, a SIGHUP isn't enough to restart xinetd. You actually have to do
> '/etc/init.d/xinetd restart'. Yes, it's annoying.
xinetd wants SIGUSR1 to reread the configuration files
I was sighupping xinetd instead of stop/starting it.
Once I did that, it worked great.
Thanks everyone,
Lee
> On Wed, Oct 10, 2001 at 09:13:17AM -0500, Lee Fedor wrote:
> >
> > service amanda
> > {
> > disable = no
> > socket_type = dgram
> >
On Wed, 10 Oct 2001 at 9:13am, Lee Fedor wrote
> I have setup everything on my redhat 7.1 client
> for backups, but it isn't listening on 10080.
> (amanda-2.4.2p2)
>
> I have sigHUP'd xinetd several times while tweaking
> on this file, but still can't get the port to show
> up on netstat Hav
well, I know where the problem has to lie.
I just don't know what I am doing wrong, or
how to fix it.
I have setup everything on my redhat 7.1 client
for backups, but it isn't listening on 10080.
(amanda-2.4.2p2)
I have sigHUP'd xinetd several times while tweaking
on this file, but still can't
First of all, do I understand correctly that you're trying to planner
by hand? Although that can be done for debugging purposes, it is
certainly not a recommended procedure. For one thing, it will leave
pieces partially done (a "log" file) that you'll have to clean up or
the next real run will f
I was just checking over the strace's for amcheck and planner, and noticed,
that amcheck makes a chdir call to change workin dir to /etc/amanda/DailySet1
when trying to open the amanda.conf file. Planner on the other hand makes no
such call, and therefore lacks the ability to see "amanda.conf" whi
Default location for Amanda to look for configuration files is in
/usr/local/etc/amanda. Unless you explictly defined another location
during your build via the configure command. If nothing else works,
try running amcheck using a trace program. For Solaris, "truss amcheck
DailySet1" or for Lin
Does anyone else have problem with planner not reading the config file? I can
see in the planner output that it's looking in /etc/amanda which is 664 and
has a copy of amanda.conf as well as /etc/amanda/DailySet1 which is where I'm
assuming it's looking. Planner should be able to read and execute
13 matches
Mail list logo
