Amcheck: selfcheck request timed out: Difference between revisions
Jump to navigation
Jump to search
Paul.bijnens (talk | contribs) m (up link) |
No edit summary |
||
| Line 1: | Line 1: | ||
; Error message | |||
AMANDA backup client hosts check | |||
-------------------------------- | |||
Warning: selfcheck request timed out. Host down? | |||
Client check: 1 host checked in 30.051 seconds, 1 problem found | |||
; Investigation | |||
This is Amanda backup client configuration error. To investigate the problem, take a look at the amandad debug file. | |||
In the backup client, locate the [[AMANDA_DBGDIR]] directory (usually /tmp/amanda) and find a file named amandad.DATETIME.debug in the directory. amandad will create this file whenever it starts. | |||
If this file does not exist, Amanda client process, amandad is not starting properly. It is also possible that the debug directory is not writeable by the dumpuser. Verify the permissions of /tmp/amanda. You may erase the directory and run amcheck again: the directory is created automatically. Also, Check the directory permissions of the parent directory /tmp (usually 1777: drwxrwxrwt). | |||
; Causes | |||
* Misconfigured inetd/xinetd/daemontools. If amandad was not started, check your inetd/xinetd/daemontools configuration. | |||
** Make sure you have added the Amanda services to /etc/services (or the NIS services map). | |||
** Make sure you signalled (x)inetd to reread its configuration (some systems may need rebooting). | |||
** Check the inetd man-page for possible differences between the standard inetd.conf format and the one in your system. | |||
** Pay special attention to typos in inetd.conf; error messages will probably appear in /var/adm/messages or /var/log/messages if you have typed the amandad program name incorrectly. | |||
** If you are building Amanda binaries on your own, make sure the dump user that has been specified at configure-time (--with-user=USERNAME) is listed in the (x)inetd config file. | |||
** Check whether the dump user has permission to run amandad, as well as any shared libraries amandad depends upon, by running the specified amandad command by hand, as the Amanda user. It should just time-out after 30 seconds waiting for a UDP packet. If you type anything, it will abort immediately, because it can't read a UDP packet from the keyboard. | |||
Use "netstat -a | grep amanda" to verify there is some program listening on the amanda/udp port. Another tool that can used for verification is [http://freshmeat.net/projects/lsof/ lsof]. | |||
*Slow NFS-server : If Amanda programs are NFS auto-mounted on the client, some clients may fail to mount the Amanda binaries in time for the check. | |||
*Firewall between backup server and client can cause selfcheck to timeout if the firewall is not configured correctly. | |||
---- | ---- | ||
See more [[amcheck issues]] | See more [[amcheck issues]] | ||
Revision as of 21:09, 27 December 2005
- Error message
AMANDA backup client hosts check -------------------------------- Warning: selfcheck request timed out. Host down? Client check: 1 host checked in 30.051 seconds, 1 problem found
- Investigation
This is Amanda backup client configuration error. To investigate the problem, take a look at the amandad debug file. In the backup client, locate the AMANDA_DBGDIR directory (usually /tmp/amanda) and find a file named amandad.DATETIME.debug in the directory. amandad will create this file whenever it starts.
If this file does not exist, Amanda client process, amandad is not starting properly. It is also possible that the debug directory is not writeable by the dumpuser. Verify the permissions of /tmp/amanda. You may erase the directory and run amcheck again: the directory is created automatically. Also, Check the directory permissions of the parent directory /tmp (usually 1777: drwxrwxrwt).
- Causes
- Misconfigured inetd/xinetd/daemontools. If amandad was not started, check your inetd/xinetd/daemontools configuration.
- Make sure you have added the Amanda services to /etc/services (or the NIS services map).
- Make sure you signalled (x)inetd to reread its configuration (some systems may need rebooting).
- Check the inetd man-page for possible differences between the standard inetd.conf format and the one in your system.
- Pay special attention to typos in inetd.conf; error messages will probably appear in /var/adm/messages or /var/log/messages if you have typed the amandad program name incorrectly.
- If you are building Amanda binaries on your own, make sure the dump user that has been specified at configure-time (--with-user=USERNAME) is listed in the (x)inetd config file.
- Check whether the dump user has permission to run amandad, as well as any shared libraries amandad depends upon, by running the specified amandad command by hand, as the Amanda user. It should just time-out after 30 seconds waiting for a UDP packet. If you type anything, it will abort immediately, because it can't read a UDP packet from the keyboard.
Use "netstat -a | grep amanda" to verify there is some program listening on the amanda/udp port. Another tool that can used for verification is lsof.
- Slow NFS-server : If Amanda programs are NFS auto-mounted on the client, some clients may fail to mount the Amanda binaries in time for the check.
- Firewall between backup server and client can cause selfcheck to timeout if the firewall is not configured correctly.
See more amcheck issues