An update:
Been working this since the original email - backups are everything, you
know. Thanks in part to Mr. John Hein and Bill Nolf (a guy here where I
work), I decided to run the same backup scheme using ufsdump, and that
seems to have corrected the problem. Note that I am using 2.5.0p2.
John E Hein wrote:
This has been working for me for the past 4+ years. But if I ever
start hitting the ~64 KiB udp per socket limit, something else will
have to be tried (as described in the above message).
As of Amanda 2.5.1, we have added bsdtcp auth which uses tcp exclusively. As a result,
Hi all,
My first post here. I have perused all resources I know of to answer
this question, but results have been very limited. Forgive me if this
question has been posed and answer prior, but I cannot find the answer.
My issue is a sendsize timeout error. When it happens, amstatus shows
the
--On January 5, 2006 4:49:53 PM +0100 Paul Bijnens
<[EMAIL PROTECTED]> wrote:
Michael Loftis wrote:
Paul asked for the logs, it seems like there's an amanda bug. The units
Yes, indeed, there is a bug in Amanda!
You have 236 DLE's for that host, and from my reading of the code
the REQue
Michael Loftis wrote:
Paul asked for the logs, it seems like there's an amanda bug. The units
Yes, indeed, there is a bug in Amanda!
You have 236 DLE's for that host, and from my reading of the code
the REQuest UDP packet is limited to 32K instead of 64K (see planner.c
lines 1377-1383) (Ne
--On January 4, 2006 7:20:50 PM -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote:
Asking questions about things I know nothing ... :)
Are you using iptables?
If so, have you installed and configured the ??conntrack?? module?
Paul asked for the logs, it seems like there's an amanda bug. The uni
On Wed, Jan 04, 2006 at 03:38:56PM -0700, Michael Loftis wrote:
>
>
> --On January 4, 2006 4:30:53 PM -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote:
>
>
> >You can find comments on the problem here:
> >
> > http://tinyurl.com/ca7pv
>
>
> OK hmm something REALLY odd is happening. For t
--On January 4, 2006 4:30:53 PM -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote:
You can find comments on the problem here:
http://tinyurl.com/ca7pv
OK hmm something REALLY odd is happening. For the DLEs that failed
there are multiple sendsize requests... one in the main/first
On Wed, Jan 04, 2006 at 02:01:36PM -0700, Michael Loftis wrote:
> I added about half a dozen or so DLEs (splitting an existing one) and since
> that time I get estimate timeout errors for some other DLEs on this host
> (daily run snippet attached) ... i suspect I'm hitting a UD
I added about half a dozen or so DLEs (splitting an existing one) and since
that time I get estimate timeout errors for some other DLEs on this host
(daily run snippet attached) ... i suspect I'm hitting a UDP packet limit
maybe, but...I'm really drawing a blank. I've turned up
Tom Brown wrote:
actually digging around in /tmp/amanda i have come accross files with
amandad.DATE.debug and a few of them apper to end like this
amandad: time 111.846: dgram_recv: timeout after 10 seconds
amandad: time 111.846: waiting for ack: timeout, retrying
amandad: time 121.846: dgram_rec
Have a look on that client in /tmp/amanda, look for the files
sendsize.DATETIME.debug and see how long the estimate did take.
The first line of the file is the start time and the last line is the
finish time. How long did it really take? You many have to
change the "etimeout" parameter in amanda.
Have a look on that client in /tmp/amanda, look for the files
sendsize.DATETIME.debug and see how long the estimate did take.
The first line of the file is the start time and the last line is the
finish time. How long did it really take? You many have to
change the "etimeout" parameter in amanda.
Tom Brown wrote:
Failure errors are
hostname/dev/rd/c0d0p3 lev 0 FAILED [Estimate timeout from hostname]
...
Does anyone know how to debug these timeout type issues as i have been
using amanda for about 3 years now and have not encountered this before.
Have a look on that client in /tmp/amanda
Hi
Clients are all RH 7.3 or WhiteBox respin 2
Server is 2.4.4p4 running on whitebox respin 2
My amchecks un fine and without issue however i have come in on 2
morning snow to find that some of the clients failed. The actual fails
have occurred on different clients, ie some that failed 2 nights a
Hi,
Hope some one can help with this little problem.
We have amanda backing up various Samba shares and some local Linux
partitions. This has been working reliably for quite some time now. We
are currently using amanda-2.4.4 and samba-2.2.8
Recently amanda is reporting data timeout errors
Hi,
Hope some one can help with this little problem.
We have amanda backing up various Samba shares and some local Linux
partitions. This has been working reliably for quite some time now. We
are currently using amanda-2.4.4 and samba-2.2.8
Recently amanda is reporting data timeout
Hi all,
I've been backing up about 12 linux and solaris boxes with amanda 2.4.2
for a years now. Finally i got new ibm eservers to replace the old pcs 2
some of my linux servers were on and the move was wonderful, that is,
except for amanda.
2 of the servers moved are backup up fine with no change
Jeremy Wadsack ([EMAIL PROTECTED]):
> I am getting consistent timeout errors on a couple hosts. This doesn't
> occur when I run amcheck, just during a dump. I'm using tar on all
> hosts, so it's not a Linux dump issue. These two hosts are conspicuous
> because they ar
I am getting consistent timeout errors on a couple hosts. This doesn't
occur when I run amcheck, just during a dump. I'm using tar on all
hosts, so it's not a Linux dump issue. These two hosts are conspicuous
because they are old (so kernel, libraries and software all could be
ou
20 matches
Mail list logo
