500 Access not allowed: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
m (Add "Network Communication" category)
(reformat, use header template)
Line 1: Line 1:
{{Troubleshooting Category|Amrecover}}{{Troubleshooting Category|Error Messages}}{{Troubleshooting Category|Network Communication}}
{{Troubleshooting Header}}
{{Troubleshooting Problem}}
=Problem=
On running [[amrecover]], you receive the following error message:
On running [[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
Line 7: Line 7:
  500 Access not allowed
  500 Access not allowed


{{Troubleshooting Solution}}
=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.
  ''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.

Revision as of 23:18, 22 May 2007



This article is a part of the Troubleshooting collection.

Problem

On running amrecover, 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.