Search:

No problems - thanks for fixing it!

Kind Regards
Dave

Thanks for that. I tried the patch and that seems to fully resolve the issue. Many thanks for turning this round so quickly.

One other thing - I noticed that the rpm uninstall script was...

Thanks for this - that seems to work around the issue. I assume that's not the proper fix(!)?

Also - whilst I was building today , I had to add a section to packaging/rpm/amanda.spec.src to get...

Hi Jean-Louis

Thanks for that , I've enabled it, and I've been working on this today - and have now managed to reproduce this on a desktop VM using AWS S3 ( not EMC ATMOS ).

The steps I...

amrecover shows the directories which are created on the recovery filesystem, but then it just stops.

I've checked /var/log/messages - and nothing is shown. The OS is Centos 6.8 ( 64bit ).

I...

I have attached a similarly redacted amfetchdump log. I'm coming to the end of our day here, so I'll pick this up again tomorrow morning (UK) if you need any more info.

Once again, many thanks...

I've uploaded the logfile as a zip ( it wouldn't go as a plain txt file ). I've had to alter some elements of the log ( ip's, hostnames etc ) but it should be structurally unchanged.

Thanks for...

Ok - just tried that with no difference, it hangs in the same place.

I am running amrecover on the backup server , but I get the same issue if running it remotely. Note: We are using ssh authentication for amrecover.

Here's the process listing for amrecover:


...

We are using "client fast" compression.

I can't see the decompression program running ( I guess I should be looking for gzip? )

Here's the process list and all the stack traces I can get:


...

The data is compressed - but not encrypted

Thanks for that, here's the output:



(gdb) thread apply all bt

Thread 2 (Thread 0x7f335a4ec700 (LWP 5252)):
#0 0x0000003dd7a0e7cd in write () from /lib64/libpthread.so.0
#1 ...

Just to add - this behaviour was the same in 3.4.1. I upgraded to 3.4.3 to see if it would help, which it didn't.

We are using Amanda 3.4.3 with an "S3" tape ( actually implemented via EMC ATMOS - so using STORAGE_API "S3" ).

Backups are working fine, and we can recover files using amrecover when the tapes...