Re: Xinetd not starting amanda
On Wed, Mar 12, 2003 at 11:02:15PM -0500, Gene Heskett said: > It appears you have everything covered with the possible exception > of the .amandahosts file. If you configured with it, then the > allowable hosts must be listed in this file. Its discussed in the > docs. Also, make sure that the reverse lookup is correct using > "dig -x 192.168.8.50". If that fails, you'll need to fix your > named records for that domain. It was both of those problems. I had only whacked in a DNS entry because of the error that was being generated, and hadn't thought about reverse DNS at the time. After running amcheck again, I got the error about the .amandahosts file, created it, and it all seems to be fine. All I need to do now is run a test backup sequence and everything should be good :-) Thanks. -- Adam Smith Information Technology Officer SAGE Automation Ltd. [EMAIL PROTECTED] http://www.sageautomation.com
Re: Xinetd not starting amanda
On Wed March 12 2003 22:01, Adam Smith wrote:
>On Mon, Mar 10, 2003 at 12:10:47PM -0600, Rebecca Pakish Crum
> said:
>
>I am having some similar problems relating to this thread, in
> regards to loading the three services below, and running 'amcheck
> ' on FreeBSD 5.0. I have installed both
> amanda-client-2.4.3, and amanda-server-2.4.3.
>
>> Can you do a chkconfig --list and see the amanda services listed
>> under xinetd based services and are they turned on? Do you have
>> amanda, amandaidx and amidxtape files in your xinetd.d
>> directory, and do they all look something like this
>> (respectively):
>
>In regards to xinetd, I have not had any experience. I looked at
> the xinetd.conf man page, and it said the configs outlined below
> need to be in the /usr/local/etc/xinetd.conf file. If they are
> specified in that file, xinetd can see them, because when any of
> the services are broken (ie an invalid option specified) xinetd
> spits out errors.
>
>My services are specified exactly as below, except the group is
> different and the option 'disable = no' exists for all three.
>
>xinetd appears to load without errors, and I can not see any
> amanda processes loaded (but this appears to be the nature of
> Xinetd.) I tried to telnet to my amanda server on ports 10080,
> 10082 and 10083, but only ports 10082 and 10083 responded
> (amandaidx and amidxtape.) Is this the correct behaviour?
> Amandad does not seem to work correctly (unless it's not supposed
> to load.)
>
>> service amanda
>> {
>> protocol= udp
>> socket_type = dgram
>> wait= yes
>> user= amanda
>> group = disk
>> groups = yes
>> server = /usr/local/libexec/amandad
>> }
>> service amandaidx
>> {
>> protocol= tcp
>> socket_type = stream
>> wait= no
>> user= amanda
>> group = disk
>> groups = yes
>> server = /usr/local/libexec/amindexd
>> }
>> service amidxtape
>> {
>> protocol= tcp
>> socket_type = stream
>> wait= no
>> user= amanda
>> group = disk
>> groups = yes
>> server = /usr/local/libexec/amidxtaped
>> }
>
>These are the results I now get from running amcheck:
>
>
>[EMAIL PROTECTED] /data/amanda]$ amcheck normal
>Amanda Tape Server Host Check
>-
>Holding disk /data/amanda/holdingdisk: 44031578 KB disk space
> available, that's plenty amcheck-server: slot 1: date X
> label tape00 (first labelstr match) NOTE: skipping tape-writable
> test
>Tape tape00 label ok
>NOTE: info dir
> /data/amanda/normal/curinfo/testies.sageautomation.com: does not
> exist NOTE: info dir
> /data/amanda/normal/curinfo/megatron.sageautomation.com: does not
> exist Server check took 0.147 seconds
>
>Amanda Backup Client Hosts Check
>
>ERROR: testies.sageautomation.com: [addr 192.168.8.50: hostname
> lookup failed] WARNING: megatron.sageautomation.com: selfcheck
> request timed out. Host down? Client check: 2 hosts checked in
> 30.053 seconds, 2 problems found
>
>(brought to you by Amanda 2.4.3)
It appears you have everything covered with the possible exception
of the .amandahosts file. If you configured with it, then the
allowable hosts must be listed in this file. Its discussed in the
docs. Also, make sure that the reverse lookup is correct using
"dig -x 192.168.8.50". If that fails, you'll need to fix your
named records for that domain.
You should get something like this for that command:
---
[EMAIL PROTECTED] root]# dig -x 192.168.1.3
; <<>> DiG 9.2.1 <<>> -x 192.168.1.3
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36320
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1,
ADDITIONAL: 1
;; QUESTION SECTION:
;3.1.168.192.in-addr.arpa. IN PTR
;; ANSWER SECTION:
3.1.168.192.in-addr.arpa. 86400 IN PTR coyote.coyote.den.
;; AUTHORITY SECTION:
1.168.192.in-addr.arpa. 86400 IN NS gene.coyote.den.
;; ADDITIONAL SECTION:
gene.coyote.den.86400 IN A 192.168.1.1
;; Query time: 18 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Wed Mar 12 23:00:36 2003
;; MSG SIZE rcvd: 108
---
>The host 'testies.sageautomation.com' exists, and is resolvable
> (internally.) The host 'megatron.sageautomation.com' exists and
> resolves internally, but it has no amanda services loaded on it,
> so its error messages are correct.
>
>Why am I getting a hostname lookup error for a host that exists
> when the host is resolvable?
>
>
>Thanks for your help.
>
>
>Regards,
--
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED] 512M
99.24% setiathome rank, not too shabby for a WV hillbilly
Re: Xinetd not starting amanda
On Mon, Mar 10, 2003 at 12:10:47PM -0600, Rebecca Pakish Crum said:
I am having some similar problems relating to this thread, in regards to
loading the three services below, and running 'amcheck ' on FreeBSD
5.0. I have installed both amanda-client-2.4.3, and amanda-server-2.4.3.
> Can you do a chkconfig --list and see the amanda services listed under xinetd based
> services and are they turned on? Do you have amanda, amandaidx and amidxtape files
> in your xinetd.d directory, and do they all look something like this (respectively):
In regards to xinetd, I have not had any experience. I looked at the
xinetd.conf man page, and it said the configs outlined below need to be in
the /usr/local/etc/xinetd.conf file. If they are specified in that file,
xinetd can see them, because when any of the services are broken (ie an
invalid option specified) xinetd spits out errors.
My services are specified exactly as below, except the group is different
and the option 'disable = no' exists for all three.
xinetd appears to load without errors, and I can not see any amanda
processes loaded (but this appears to be the nature of Xinetd.) I tried to
telnet to my amanda server on ports 10080, 10082 and 10083, but only ports
10082 and 10083 responded (amandaidx and amidxtape.) Is this the correct
behaviour? Amandad does not seem to work correctly (unless it's not
supposed to load.)
> service amanda
> {
> protocol= udp
> socket_type = dgram
> wait= yes
> user= amanda
> group = disk
> groups = yes
> server = /usr/local/libexec/amandad
> }
> service amandaidx
> {
> protocol= tcp
> socket_type = stream
> wait= no
> user= amanda
> group = disk
> groups = yes
> server = /usr/local/libexec/amindexd
> }
> service amidxtape
> {
> protocol= tcp
> socket_type = stream
> wait= no
> user= amanda
> group = disk
> groups = yes
> server = /usr/local/libexec/amidxtaped
> }
These are the results I now get from running amcheck:
[EMAIL PROTECTED] /data/amanda]$ amcheck normal
Amanda Tape Server Host Check
-
Holding disk /data/amanda/holdingdisk: 44031578 KB disk space available, that's plenty
amcheck-server: slot 1: date Xlabel tape00 (first labelstr match)
NOTE: skipping tape-writable test
Tape tape00 label ok
NOTE: info dir /data/amanda/normal/curinfo/testies.sageautomation.com: does not exist
NOTE: info dir /data/amanda/normal/curinfo/megatron.sageautomation.com: does not exist
Server check took 0.147 seconds
Amanda Backup Client Hosts Check
ERROR: testies.sageautomation.com: [addr 192.168.8.50: hostname lookup failed]
WARNING: megatron.sageautomation.com: selfcheck request timed out. Host down?
Client check: 2 hosts checked in 30.053 seconds, 2 problems found
(brought to you by Amanda 2.4.3)
The host 'testies.sageautomation.com' exists, and is resolvable (internally.)
The host 'megatron.sageautomation.com' exists and resolves internally,
but it has no amanda services loaded on it, so its error messages are
correct.
Why am I getting a hostname lookup error for a host that exists when the
host is resolvable?
Thanks for your help.
Regards,
--
Adam Smith
Information Technology Officer
SAGE Automation Ltd.
[EMAIL PROTECTED]
http://www.sageautomation.com
RE: Xinetd not starting amanda
>Hallo all
>when checking if amanda is listening on the correct ports.
>netstat -a | grep -i amanda
>
>any ideas how I can trouble shoot further?
>According to me evereything there must work
Can you do a chkconfig --list and see the amanda services listed under xinetd based
services and are they turned on? Do you have amanda, amandaidx and amidxtape files in
your xinetd.d directory, and do they all look something like this (respectively):
service amanda
{
protocol= udp
socket_type = dgram
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
service amandaidx
{
protocol= tcp
socket_type = stream
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
protocol= tcp
socket_type = stream
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
And the amanda services are listed in /etc/services? What version of RedHat are you
using?
Re: Xinetd not starting amanda
On Mon, 2003-03-10 at 06:44, Mozzi wrote:
> Hallo all
> when checking if amanda is listening on the correct ports.
> netstat -a | grep -i amanda
>
> any ideas how I can trouble shoot further?
> According to me evereything there must work
Here are some thoughts - I hope they help you. I'm making many rash
assumptions here, like your operating system (!) and exactly *what* your
problem is!!! It would be helpful to have had a bit more info to go
on...
1) First, compare your xinetd startup-file with mine (I'm using
RedHat8.0, and my file is /etc/xinetd.d/amanda):
[EMAIL PROTECTED]:/root-> cat /etc/xinetd.d/amanda
# default: on
# description: Amanda tape backup
service amanda
{
disable = no
socket_type = dgram
protocol= udp
user= amanda
group = backup
server = /usr/local/libexec/amandad
wait= yes
}
2) Restart xinetd, mostly just for good measure. As root, on my
RedHat8.0 system, this goes like:
/sbin/service xinetd restart
If you issue "ps aux" (again, RH8.0 and similar) you should see a line
that looks something like:
root 544 0.0 0.3 2100 912 ?SMar04 0:00 xinetd
-stayalive -reuse -pidfile /var/run/xinetd.pid
This shows that xinetd is running. Remember, xinetd is a
'super-server', which launches other programs (like amandad). Your
"netstat" command will NOT show amanda listening, because it's not; it's
xinetd that listens and starts amanda.
3) Verify that xinetd is able to "see" your amanda. For me, I invoke a
console-based configuration tool, and simply see that amanda shows up in
the listing:
ntsysv
4) At this point, you should be ready to try amcheck. Read the
documentation. Find where your amanda logs are stored and read them.
On my RH8.0 system, my amandad lives in /usr/local/libexec, and I find
it handy to use this to see if amandad is getting started by xinetd:
ls -ul /usr/local/libexec/amandad
The time that shows will be the last access-time; if it doesn't match
when you just tried your amcheck run, then it's not amanda that's
failing - it's not even getting started! Check (or temporarily remove)
firewalling. If you're using tcpwrappers, take those out of the picture
too (ie blank /etc/hosts.allow and /etc/hosts.deny).
There - I've tried to help you. But again, it's hard when you don't
provide your OS, and your problem!! Usually I would simply hit "delete"
upon seeing a posting like yours...
-Gord
--
Gordon Pritchard, P.Eng. | Institute of Electrical and
Research Labs Manager| Electronics Engineers
Simon Fraser University, Surrey | Quarter Century Wireless Ass'n
[EMAIL PROTECTED] | Telephone Pioneers of America
phone: 604.586.6186
Re: Xinetd not starting amanda
I'm assuming that you are running this on a linux box.. so here are some things to check: 1. In the xinetd service file, disable should = no 2. If There is an 'id' field it has to match up with the name of the service in /etc/services. 3. If there is not an 'id' field the name of your file has to match the name of the above-mentioned service. 4. You can run xinetd with a '-d' option for debugging. 5. type 'ipchains -L' and 'iptables -L'. If there are any lines that show up as REJECT or DENY you may have to change your firewall rules on the machine. A message that this isn't supported by your kernel is okay. 6. If you do have firewall rules, make sure you are also allowing connections to port 111. Hope this helps.. -Bryan On Monday, March 10, 2003, at 08:44 AM, Mozzi wrote: Hallo all when checking if amanda is listening on the correct ports. netstat -a | grep -i amanda any ideas how I can trouble shoot further? According to me evereything there must work Mozzi
Re: Xinetd not starting amanda
On Mon, 2003-03-10 at 08:44, Mozzi wrote: > Hallo all > when checking if amanda is listening on the correct ports. > netstat -a | grep -i amanda > > any ideas how I can trouble shoot further? > According to me evereything there must work > Do you have "disable = no" in your amanda service config? --a > > Mozzi
