This is getting more and more weird. I just build a 3rd server, same
distro. It would also appear to work fine. I removed amanda from the
failing server and re-installed. Didn't seem to make any difference.
The two new ones both seem happy with calcsize, but the original still
isn't :-(
--
I have just built another server, same specs as the one that is failing.
I have rebooted both. The new one when I do amcheck -c produces a
selcheck.exclude log in /var/log/amanda and a selfcheck.debug in the
client directory.
The server that is failing produces neither. All I got was
Amanda
On Feb 2, 2008 6:42 PM, Glen Eustace <[EMAIL PROTECTED]> wrote:
> When things fail, I don't even get a sendsize log file and for the days
> it succeeded the estimate is pretty good. The amandad log file would
> indicate that the client was told to run sendsize but no indication of
> why it didn't r
On Feb 1, 2008 6:38 AM, Tony van der Hoff <[EMAIL PROTECTED]> wrote:
> Meanwhile, and maybe easier to diagnose, I find:
>
> [EMAIL PROTECTED]:~$ sudo ammt -t /dev/nht0 status
> tapedev /dev/nht0 is offline or has no loaded tape.
> /dev/nht0 status failed: Success
>
> Whereas:
>
> [EMAIL PROTECTED]:
Generally this kind of intermittent failure is caused by timeouts that
are too low. Try increasing the timeouts.
http://wiki.zmanda.com/index.php/Results_missing
I have had a look at this page, good stuff but unfortunately not too
helpful at this stage.
When things fail, I don't even get
On Feb 2, 2008 3:00 PM, Glen Eustace <[EMAIL PROTECTED]> wrote:
> A couple of weeks back, I added a new server to our network. It is
> running fedora 8 - amanda-2.5.2p1, the backups failed from day 1. Then
> mysteriously for about 4 days they worked and now they don't again.
>
> amcheck says ever
Jeremy Mordkoff wrote:
I'm running amanda 2.4.4 on my server
one of my client systems got upgraded to 2.5.1 and now I can't back it
up. The client seems happy, but the server logs a timeout on sendsize.
They should be able work together.
Is there a workaround besides downgrading amanda
A couple of weeks back, I added a new server to our network. It is
running fedora 8 - amanda-2.5.2p1, the backups failed from day 1. Then
mysteriously for about 4 days they worked and now they don't again.
amcheck says everything is fine, but the dump fails.
The only message I get is
agree-
I'm running amanda 2.4.4 on my server
one of my client systems got upgraded to 2.5.1 and now I can't back it up. The
client seems happy, but the server logs a timeout on sendsize.
Is there a workaround besides downgrading amanda on this one client?
JLM
