Troubleshooting

Pages linked from here describe common problems with Amanda, their causes, and their solutions. The same article may be linked under several different categories for easier searching.

By Application

amandad

• Addr 0.0.0.0: hostname lookup failed

amcheck

• Access as localuser not allowed from remoteuser@remotehost
• Amcheck cannot login as the amanda user
• Configuration keyword expected
• Not an amanda tape
• Numerical argument out of domain
• Port NNNN is not secure
• Selfcheck request failed
• Why does amcheck fail while amdump succeeds?

amdump

• Tar dumps every file in a level-1 backup after a hardware change
• Amdump Only Creates Incremental Dumps in Holding Disk
• Amdump fails to create level 0 dumps
• Amdump is terribly slow
• Cannot overwrite active tape
• Data timeout
• Disk offline
• Dump returned 1
• Dump larger than available tape space
• Dump size is the same regardless of the backup level
• Dumps way too big, must skip incremental dumps
• Infofile update failed
• Memory allocation failed
• Mesg read: Connection reset by peer
• Planner: ERROR amanda user is not allowed to execute the service noop
• Results missing
• Sendbackup error: no backup size line
• Tape Input-Output error
• Unexpected field value in snapshot file
• DUMP: Warning - block NNN is beyond the end of DEVICE
• planner: ERROR Request to AMANDA CLIENT failed: timeout waiting for ACK

amflush

• Tape Input-Output error

amrecover

• 500 Access not allowed
• Amrecover: wildcard characters in filenames
• Could not read config file
• EOF, check amidxtaped.debug
• No index records for host-disk
• Why does `amrecover` start over and over again, when I tell it to extract from tape?
• Why does amrecover erase files?

amrestore

• Amrestore: "$" character in the filename to be restored

Error Messages

Amanda's error messages can sometimes be misleading; this section is indexed by the text of the message.

• 500 Access not allowed
• Access as localuser not allowed from remoteuser@remotehost
• Addr 0.0.0.0: hostname lookup failed
• Amcheck cannot login as the amanda user
• Amdump fails to create level 0 dumps
• amtape: Could not load current slot.
• Can not read/write /var/lib/amanda/amandates: Permission denied
• Cannot overwrite active tape
• Changer problem: no slots available
• Client configured for auth=bsd while server requested 'bsdudp'
• Client does not support DUMPER-API
• Configuration keyword expected
• Could not read config file
• Could not run GLIB test program, checking why
• Data timeout
• Disk offline
• DUMP: Warning - block NNN is beyond the end of DEVICE
• Dump larger than available tape space
• Dump returned 1
• Dumps way too big, must skip incremental dumps
• EOF, check amidxtaped.debug
• Infofile update failed
• Memory allocation failed
• Mesg read: Connection reset by peer
• No index records for host-disk
• Planner: ERROR amanda user is not allowed to execute the service noop
• Results missing
• Selfcheck request failed
• Selfcheck request timed out
• Sendbackup error: no backup size line
• Tape Input-Output error
• Unexpected field value in snapshot file
• A TAPE ERROR OCCURRED: Could not find a tape to use

By Topic

Filenames

• Amrecover: wildcard characters in filenames
• Amrestore: "$" character in the filename to be restored

Build / Installation Problems

• Could not run GLIB test program, checking why

Network

• 500 Access not allowed
• Access as localuser not allowed from remoteuser@remotehost
• Client configured for auth=bsd while server requested 'bsdudp'
• Port NNNN is not secure
• Reverse DNS Gives an Incorrect Hostname For My Server or Client
• Selfcheck request failed
• Selfcheck request timed out

Restoring

• Amanda Configuration or Data is Lost in a Crash
• Why does amrecover erase files?

Tape Drives

• My Tape Drive is Malfunctioning
• Not an amanda tape
• Numerical argument out of domain

Tape Spanning

• Memory allocation failed

Tar

• Tar dumps every file in a level-1 backup after a hardware change