Re: selfcheck timeout - host down
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
> group = dump
> server = /usr/lib/amanda/amandad
> port= 10080
> }
^
It's better to add amanda to /etc/services instead of using the port
number. Then kill xinetd and start it with debugging on
xinetd -d
and run amcheck, watching xinetd debug messages. This
should either work or give at least a detailed message.
--
Alles Gute / best wishes
Dietmar GoldbeckE-Mail: [EMAIL PROTECTED]
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization? Gandhi: I think it would be a good idea.
Re: selfcheck timeout - host down
> 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
Re: selfcheck timeout - host down
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
> > protocol= udp
> > wait= yes
> > user= dump
> > group = dump
> > server = /usr/lib/amanda/amandad
> > port= 10080
> > }
> ^
>
> It's better to add amanda to /etc/services instead of using the port
> number. Then kill xinetd and start it with debugging on
>
> xinetd -d
>
> and run amcheck, watching xinetd debug messages. This
> should either work or give at least a detailed message.
>
> --
> Alles Gute / best wishes
> Dietmar GoldbeckE-Mail: [EMAIL PROTECTED]
> Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
> Civilization? Gandhi: I think it would be a good idea.
Re: selfcheck timeout - host down
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 Have I put something in here
> wrong? Is there an obvious typo?
IIRC, a SIGHUP isn't enough to restart xinetd. You actually have to do
'/etc/init.d/xinetd restart'. Yes, it's annoying.
> service amanda
> {
> disable = no
> socket_type = dgram
> protocol= udp
> wait= yes
> user= dump
> group = dump
> server = /usr/lib/amanda/amandad
> port= 10080
> }
Just in case, this is what my /etc/xinetd.d/amanda file looks like:
service amanda
{
protocol= udp
socket_type = dgram
wait= yes
user= amanda
group = disk
server = /usr/local/libexec/amandad
server_args = amandad
}
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
selfcheck timeout - host down
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 get the port to show
up on netstat Have I put something in here
wrong? Is there an obvious typo?
This is a new server that was pressed into use
in an emergency, and cannot be rebooted without
causing a bunch of grief... :(
Thanks in advance for any help anyone can give me.
This is my xinetd.conf file:
defaults
{
instances = 60
log_type= SYSLOG authpriv
log_on_success = HOST PID
log_on_failure = HOST
}
service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= dump
group = dump
server = /usr/lib/amanda/amandad
port= 10080
}
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= dump
group = dump
server = /usr/lib/amanda/amandaidx
port= 10082
}
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= dump
group = dump
server = /usr/lib/amanda/amidxtape
port= 10083
}
#includedir /etc/xinetd.d
