"Svend Sorensen" <[EMAIL PROTECTED]> writes:
> chg-zd-mtx is missing a line for the configured prefix. It has a line
> for @exec_prefix@, but if that wasn't specified during configure, it
> defaults to @[EMAIL PROTECTED] This results in the following block after
> `make`.
Heh, I just ran across
Jean-Louis Martineau <[EMAIL PROTECTED]> writes:
> Paul Lussier wrote:
>>> You should add a spindle for dle on the same physical disk, it can be
>>> a lot faster.
>>>
>> I don't understand this statement. Could you clarify please?
>>
> man amanda
> search for spindle
> All DLE of a physic
Olivier Nicole wrote at 15:14 +0700 on Oct 12, 2007:
> Hi,
>
> I just upgraded amanda-client and gtar:
>
> gtar-1.18_1 GNU version of the traditional tar archiver
> amanda-client-2.5.1p3_1,1 The Advanced Maryland Automatic Network Disk
> Archiver
>
> on a 5.5 server
>
> Free
Thanks for reporting that!
There were actually two more changers with this bug -- I've attached
an updated patch, and will commit it shortly.
Dustin
--
Storage Software Engineer
http://www.zmanda.com
chg-prefix.patch
Description: Binary data
Paul Lussier wrote:
You should add a spindle for dle on the same physical disk, it can be
a lot faster.
I don't understand this statement. Could you clarify please?
man amanda
search for spindle
All DLE of a physical disk should have the same spindle (>0).
It's generally faster to run
chg-zd-mtx is missing a line for the configured prefix. It has a line
for @exec_prefix@, but if that wasn't specified during configure, it
defaults to @[EMAIL PROTECTED] This results in the following block after
`make`.
# source utility functions and values from configure
exec_prefix=${pre
Thanks Jean-Louis.
We have created a VPN for our backup LAN, linking a number of machines over the
internet. Using Bastille firewall we define tun0 as an internal interface on
the client machine and then permit UDP_SERVICE_INTERNAL=10080.
This is confirmed by ([EMAIL PROTECTED]:~)# nmap -sU -P0
Jean-Louis Martineau <[EMAIL PROTECTED]> writes:
> Paul Lussier wrote:
>>
>> Can you point me to where in the docs this is mentioned?
>
> It's not documented, it's not a server limit, it's a client limit we
> added do be sure amandad will eventually terminate.
Ahh, that's why I never knew about i
Paul Lussier wrote:
Jean-Louis Martineau <[EMAIL PROTECTED]> writes:
Why you never posted the error in the amandad debug file?
I thought I had. I've got etimeout set to 72000, so seeing it timeout
near 21000 set off alarms for me.
On 2007-10-12 15:45, Paul Lussier wrote:
---
amanda have a timeout of 6 hours (21600 seconds).
Can you point me to where in the docs this is mentioned? I've never
seen this menioned before (though I wasn't really looking for it) and
I can't seem to find it anywhere right now (running on n
Jean-Louis Martineau <[EMAIL PROTECTED]> writes:
> Why you never posted the error in the amandad debug file?
I thought I had. I've got etimeout set to 72000, so seeing it timeout
near 21000 set off alarms for me.
> ---
It's not a dtimeout problem.
The socket can't be connected, do you have a firewall between client and
server?
Jean-Louis
Rob Dyke wrote:
Hello List,
One of my backup clients started failing recently. All other clients are fine.
Using /var/lib/amanda/cwnbackup/amdump.1 from Fri Oct 12 13:13
Hello List,
One of my backup clients started failing recently. All other clients are fine.
Using /var/lib/amanda/cwnbackup/amdump.1 from Fri Oct 12 13:13:17 BST 2007
ns5:/etc0 driver: (aborted:could not connect to data
port: Connection timed out)(too many dumper retry)
ns
Why you never posted the error in the amandad debug file?
---
amandad: time 21603.544: /usr/local/libexec/sendsize timed out waiting
for REP data
amandad: time 21603.781: sending NAK pkt:
<
ERROR timeout on reply pip
Hi,
I just upgraded amanda-client and gtar:
gtar-1.18_1 GNU version of the traditional tar archiver
amanda-client-2.5.1p3_1,1 The Advanced Maryland Automatic Network Disk Archiver
on a 5.5 server
FreeBSD ufo.cs.ait.ac.th 5.5-RELEASE-p15 FreeBSD 5.5-RELEASE-p15 #7: Wed Oct 3
10:17:29 I
Jean-Louis Martineau <[EMAIL PROTECTED]> writes:
> If sendsize is not running, it's because it crashed.
Hmm, it's definitely not running, but I don't see any trace of a crash.
Is there more verbose logging that can be turned on somewhere?
> I don't understand why amandad finish before sendsize,
16 matches
Mail list logo
