I run a script every that that does some preprocessing, and then runs
amdump, then does some post processing.
I need to determine if the run was successful and most important if the
amdump completed successful.
How can I determine the status of an amdump run?
How do others handle this?
On Thu, Jul 17, 2008 at 10:35 AM, McGraw, Robert P [EMAIL PROTECTED] wrote:
How can I determine the status of an amdump run?
Amdump has a rather detailed exit status.
See http://wiki.zmanda.com/man/amdump.8.html
Dustin
--
Storage Software Engineer
http://www.zmanda.com
It seem that the local man page did not have anything about exit codes for
amdump, but the zmanda man pages did. I believe I got what I needed.
Thanks and sorry to have bothered the group.
Robert
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of
On Thu, Jul 17, 2008 at 12:55 PM, McGraw, Robert P [EMAIL PROTECTED] wrote:
It seem that the local man page did not have anything about exit codes for
amdump, but the zmanda man pages did. I believe I got what I needed.
We just added that to the manpages a while ago, so no worries.
Dustin
--
hi...
A selfcheck log on the client does not exist.
when I compare the logfile on the non working client, to a working
client, it looks like amanda does not process the UDP packages it
receives..
greetz
olli
Am Mittwoch, den 16.07.2008, 15:12 -0400 schrieb Dustin J. Mitchell:
The debug logs
I am setting up a new sun server running Solaris 10. I think I have set
things up correctly. I am getting the error: WARNING: xx.yy.zz:
selfcheck request failed: timeout waiting for ACK.
I have searched the archives and tried everything suggested.
2 things I notice:
1. my
I figured it out. I looked at the /var/adm/messages logs and it told me to run
the command:
inetconv -i /etc/inet/inet.conf, since I had made changes in the inetd.conf
file. That got rid of the no ACK error. Then amcheck told me what host name was
actually being used so I changed the
