500 Access not allowed: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
No edit summary
 
(man links)
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
e.g error run:
{{Troubleshooting Header}}
 
=Problem=
On running {{man|8|amrecover}}, you receive the following error message:
  [root@copper ~]# amrecover test -s silver.metal.com -t silver.metal.com
  [root@copper ~]# amrecover test -s silver.metal.com -t silver.metal.com
  AMRECOVER Version 2.5.0. Contacting server on silver.metal.com ...
  AMRECOVER Version 2.5.0. Contacting server on silver.metal.com ...
Line 6: Line 7:
  500 Access not allowed
  500 Access not allowed


Remedy:
=Solution=
 
* Make sure the /var/lib/amanda/.amandahosts file is having entry of the machine on which amrecover is run.
* Make sure the /var/lib/amanda/.amandahosts file is having entry of the machine on which amrecover is run.
e.g of .amandahosts file:
  ''machinename'' ''user-name''
  <machinename> user-name
Here the user-name is the user who is running amrecover i.e root.
Here the user-name is the user who is running amrecover i.e root.

Latest revision as of 22:54, 30 June 2008

This article is a part of the Troubleshooting collection.

Problem

On running amrecover(8), you receive the following error message:

[root@copper ~]# amrecover test -s silver.metal.com -t silver.metal.com
AMRECOVER Version 2.5.0. Contacting server on silver.metal.com ...
220 sles10 AMANDA index server (2.5.0) ready.
500 Access not allowed

Solution

  • Make sure the /var/lib/amanda/.amandahosts file is having entry of the machine on which amrecover is run.
machinename user-name

Here the user-name is the user who is running amrecover i.e root.