I just received a fatal taper error in last night's backup. The error is:
Wed Sep 5 08:59:23 2012: thd-840d870: taper: critical (fatal): Part numbers do
not match! at /local/amanda/amanda-3.3.2/lib/amanda/perl/Amanda/Taper/Scribe.pm
line 877
Amanda::Taper::Scribe::_xmsg_part_done('Ama
>> ...
>>I did installed 2.5.0p2 client with same options that mentioned above
>> wiki page. Then I started the launch daeomns for bsdudp, For some reason I
>> am seeinng follwing error in logs on
>>
>>com.apple.launchd[1] org.amanda.amandad.basdudp getpwnam("amandabackup")
>> failed
>>
>> ...
>> > > I have downloded the tar file and built myself. i didnt find any
>> > > xinetd.files, I created one directory by myself xinetd.d and created file
>> > > for amanda
>>
>> ... does your OS use a different mechanism for this ?
>> Solaris uses /etc/inetd.conf, I thought MAC used xinetd
>> ...
>> I have resolved the problem but not sure how.
>>
>> I changed
>>
>> device-property "BLOCK_SIZE" "1024k"
>>
>> to
>>
>> device-property "BLOCK_SIZE" "1 mbytes"
>>
>> and I rebooted the system.
>>
>> My amflush is running with out the errors.
>> ...
I did a little checki
I have setup a test configuration because of the issue I'm seeing on a
Solaris 10/x86 amanda 3.2.1 server/client. Auth is set to "local".
The error from the amanda report is:
planner: ERROR xxx.math.utah.edu NAK: timeout on reply pipe
The test configuration has 11 DLEs. If I let the sendsize
>> ...
>> We just tried it for the first time and saw the same thing.
>> What is your disklist config?
>> ...
The disklist looks like:
host.math.utah.edu "C:/Documents and Settings" zwc-compress 1
The amanda.conf has (among other settings):
define dumptype global {
index yes
maxdump
I've got ZWC installed on a couple of Windows XP boxes. The one thing
I notice is that the level zero and level one backups are always about
the same size and the file counts are approximately the same. This
leads me to believe that I am getting full dumps every time. Any
hints on what might be
>> ...
>> The gtar devs finally accepted something to help with this problem:
>> --no-check-device.
>> ...
Thanks, I hadn't caught the addition of that option. That also
reminds me that the problem isn't the inode number, but the device
number which was the problem.
Pieter
I started using ZFS in a big way over a year ago on our main file
server. Since there is no ufsdump replacement to use with ZFS, I
elected to use GNU tar. I know this doesn't yet cover backing up
things like ACLs, but we don't use them in our very heterogeneous
environment. The main idea I had w
>> ...
>> Can you try the attached patch for the vstrallocf problem.
>> ...
That corrected the problem for both IRIX and OSF/1 for me.
Pieter
>> ...
>> cc-1084 cc: ERROR File = /usr/include/sys/socket.h, Line = 66
>> The indicated declaration has an invalid combination of type specifiers.
>>
>> typedef int socklen_t;
>> ...
I'm guessing that Jean-Francois' release of IRIX is probably newer
than the one I have (IRIX 6.5.4m here).
>> ...
>> First go at amanda-2.5.2 on a system running irix-6.5.x
>> and compile fails with the error:
>> ...
This is the case on both IRIX and OSF/1. These compilers can't
handle:
#define vstrallocf(...) debug_vstrallocf(__FILE__,__LINE__,__VA_ARGS__)
The patch for sockaddr_storage se
12 matches
Mail list logo