Troubleshooting: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
Line 40: Line 40:
The lookup order, eg. files dns (and/or ldap, nis, ...) so that hosts file
The lookup order, eg. files dns (and/or ldap, nis, ...) so that hosts file
is searched before name servers.
is searched before name servers.
=== Amanda user issues ====
; Issue: Cannot login as amanda user. Amcheck reports that it cannot login as amanda user
; Solution:
* Check if the amanda user default shell is valid and the shell is present in /etc/shells.
Some installation packages create amanda user with default shell as "/bin/false". Amanda
expects valid shell for amanda user.

Revision as of 03:13, 27 December 2005

What kind of trouble?

amcheck issues

amdump issues

amandad issues

amfetchdump issues

amlabel issues

amrecover issues

amrestore issues

amverify issues

Recovering amanda configuration

General networking

Issue
Amanda server and backup client are connected to the Internet via ADSL. It seems that when Amanda on the backup client does a DNS lookup for my Amanda server, it sees something like:
[email protected]

which is generated by the ISP. Since the machine has a static IP address, the really-long-and-annoying-hostname shouldn't change. How to use backup server's hostname actual hostname (amanda.mydomain.com) instead of the long ISP name?

Solution
  • Define the IP address in the hosts file (/etc/hosts) on the backup client

XXX.XXX.XXX.XXX amanda.mydomain.com

  • Change the name lookup order in /etc/nsswitch.conf file to
      hosts:      files dns

The lookup order, eg. files dns (and/or ldap, nis, ...) so that hosts file is searched before name servers.