[24130]: pid 26873: exit status 1
This is obviously showing some type of inetd issue, but I am at a loss
to determine what it is. I also ran tcpdump while attempting to
connect, analyzed the output, and found it to be most unhelpful.
I sincerely appreciate any help that can be offered.
Eric Helms
Well, thanks to John and Alexandre, and the archived users list, I was
able to restore my lost files with restore.static (thanks be). I just
upgraded to 2.4.2. Now, however, I need to make amrecover work, and
upon running amrecover (default config, DailySet1) I get this screen
output:
220
"John R. Jackson" wrote:
SCNF DailySet1
Is "DailySet1" the name of your Amanda configuration? Amrecover
(amindexd) is known to mis-behave when given a bad config name (it's on
my TODO list).
If that doesn't help, run amindexd by hand, **as the Amanda user**,
with the "-t" option, e.g.:
Hello. I am writing in regards to an issue that has got me stumped with
regards to amrecover. What I would like to do is restore a backup from
a different system to my system because of disk space constraints. My
system is RedHat 7, the system that I need the backup of is RH 6.2. The
The backup that I need restored is 20010213.sda5.0 from deepblue ...
... the files located in /var/log/amanda/DailySet1/index/deepblue/sda5,
which are 20010213_0 (0 byte file) and 20010213_0.gz. ...
Huh? 20010213_0 is zero bytes? That's why amrecover is not happy.
Something went wrong
Jean-Louis Martineau wrote:
backup server. I ran the restore on a Linux box with the 2.4 kernel, hoping that
this
would alleviate the 2GB file size limitation, but so far the output/errors
continue.
Once again, thanks for your help.
Each chunk contains the absolute path of the
to be. Thank
you.
Eric Helms
