Re: amvault segmentation fault

Dennis,

The attached patch fix the crash.

You have log corruption because of amdump and amvault running 
simultaneously.
Jean-Louis

On 05/15/2012 08:20 AM, Dennis Benndorf wrote:
> Am 15.05.2012 14:14, schrieb Jean-Louis Martineau:
>> On 05/15/2012 07:54 AM, Dennis Benndorf wrote:
>>>
>>> Log file /usr/local/etc/amanda/daily/catalog/log.20120506180002.0 
>>> stamped 20120506180002, expecting 20120505180458!
>> I never saw amanda print this message.
>
> This happens when amvault starts and amdump is not finished, so I 
> think they both write in the same log-file. But this has happened a 
> few times ago, mostly when our monthly backups take more than 24hours.
>
>
>> Can you run gdb again and get the value of the second argument to 
>> g_string_chunk_insert_const.
> How do I do that?
>
>
>>
>> Send me /usr/local/etc/amanda/daily/catalog/log.20120506180002.0 and 
>> /usr/local/etc/amanda/daily/catalog/log.20120505180458.0
>>

amvault segmentation fault

Hello @all,

after updating our backup server to Ubuntu Server 12.04 and recompiling 
amanda 3.3.1 amvault fails with segmentation fault everytime it is 
started. Might this have something to do with the removal of 
g_queue_free_full, which was needed to compile it? Which logfiles do you 
need?

Best regards,
Dennis

The canary has died, again.

It turns out I have been running on 4.0.0alpha-4692 for a while, all the
newer ones have a broken build:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../config -I../gnulib -fno-strict-aliasing
-D_GNU_SOURCE -
pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -Wextra -Wparentheses -Wdeclaration-
after-statement -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat
-Wformat-security 
-Wsign-compare -Wfloat-equal -Wold-style-definition -Wno-strict-aliasing -Wno-unknown-pragmas
-g -O2 -fno-
strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -MT util.lo -MD -MP -MF .deps/util.Tpo
-c util.c  
-fPIC -DPIC -o .libs/util.o
util.c: In function 'portable_readdir':
util.c:1150:9: error: #pragma GCC diagnostic not allowed inside functions
util.c:1151:9: error: #pragma GCC diagnostic not allowed inside functions
util.c:1152:5: warning: missing initializer
util.c:1152:5: warning: (near initialization for 'mutex.unused')
util.c:1153:9: error: #pragma GCC diagnostic not allowed inside functions
make[3]: *** [util.lo] Error 1
make[3]: Leaving directory `/home/amanda/amanda-4.0.0alpha.svn.4700/common-src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/amanda/amanda-4.0.0alpha.svn.4700/common-src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/amanda/amanda-4.0.0alpha.svn.4700'
make: *** [all] Error 2

Sorry to disturb the party. I was rather enjoying it myself. 

Cheers, Gene

Specified file list matches multiple dumps

Hello,

I have a problem with amrecover:

  amrecover> add cpio.ry
  Added file /cpio.ry
  amrecover> list
  TAPE Set1-2011-18:1;Set1K-2011-13:15,16;Set1K-2011-14:1,2,3,4,5,6,7,8,9,10 LEVEL
   0 DATE 2012-01-01-03-08-50
          /cpio.ry
  amrecover> extract

  Extracting files using tape drive changer on host uxrs74.
  The following tapes are needed: Set1-2011-18 Set1K-2011-13 Set1K-2011-14

  Extracting files using tape drive changer on host uxrs74.
  Load tape Set1-2011-18 now
  Continue [?/Y/n/s/d]? y
  Specified file list matches multiple dumps; cannot continue recovery
  Got no header and data from server, check in amidxtaped.*.debug and amandad.*.debug files on server
  amrecover> 

Set1-2011-18 is the original tape, the DLE dump resides on this tape
only. Set1K-2011-13 and Set1K-2011-14 are the copies made with
amvault. I had to enable splitting in order to use amvault, so the
dump is split in several 40G-sized parts. And some of these parts are
on one tape and the other on the next tape.

I didn't split in fixed-size parts before, so this might be a cause of
the problem too.

Adding/removing Disks?

Failed tapes

what is the proper way to delete a particlur backup ( slot )

What is the proper way to delete a particular backup slot and free the space it's holding?

I've tried 'amadmin DailySet1 delete ...' to remove 'slot1', but the files are still there in 'slot1'.  

Is it ok to 'rm -rf' in the slot folder?  Are these files referenced anywhere else?  I don't want to accidently
corrupt the install.

I was hoping there was a way to remove these files in a backup type independent way.  Eg.  I'd prefer not to have
to log into AWS to delete S3 backups, etc.

Best regards,
Kervin

Adevsoft Inc
Business Software Development
http://adevsoft.com/

Device type "s3" is not known

After building from trunk to fix a few other issues, I started configuring Amazon S3 support.  

But amlabel reported...
"Device type "s3" is not known"

Similar to this issue...
https://forums.zmanda.com/archive/index.php/t-2581.html

To fix this I did...

make distclean
yum install libcurl-devel perl-WWW-Curl
./configure --enable-s3-device
make

I believe part of the underlying issue is that the autoconf tests do not seem to warn about missing headers
like libcurl, etc.

Best regards,
Kervin

Adevsoft Inc
Business Software Development
http://adevsoft.com/

amrecover fails with "TypeError in method 'debug'..."

Hi,

I'm following the simple recovery example from the wiki...
http://wiki.zmanda.com/index.php/GSWA/Recovering_Files

Worked though all the issues but now I'm at the 'extract' and I'm getting an error...

amrecover - amidxtaped closed the connection
amrecover - can't talk to tape server: (null)

Further inspection of /var/log/messages gives...

amidxtaped[2784]: TypeError in method 'debug', argument 1 of type 'char *'

I've found someone had run into this issue before 'June 2011'...
http://archives.zmanda.com/amanda-archives/viewtopic.php?t=6929&sid=f2141406dc79480edd30a1200443e9a6

They mentioned patching a Perl script but I haven't found the one they're referring to.

Does anyone have instructions on how to fix or workaround this issue?

I'm using 3.3.1 built from source on an update to date Amazon Linux install.

Best regards,
Kervin

Adevsoft Inc
Business Software Development
http://adevsoft.com/

Re: amrecover failure [RESOLVED]

amrecover failure