OK. Done. Seems to be working.

I did my initial configure and make with the 3.3.3 that I already had. It erred 
out with

   libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../config -fno-strict-aliasing 
-D_GNU_SOURCE
   -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2
-fno-strict-aliasing -MT localcharset.lo -MD -MP -MF .deps/localcharset.Tpo -c localcharset.c -fPIC -DPIC -o .libs/localcharset.o
   In file included from localcharset.c:28:0:
   ./stdio.h:456:1: error: 'gets' undeclared here (not in a function)
     _GL_WARN_ON_USE (gets, "gets is a security hole - use fgets instead");
     ^
   make[4]: *** [localcharset.lo] Error 1

Rather than trying to fix that, I decided to just grab the latest 3.3.9 from Zmanda. That went through the configure, make and make install without any errors.

However, when I tried to run `amcheck daily`, I got three errors that I had to clean up. Two of them are issues with the installer, I believe.

The first was Amanda being more picky about my configuration. I used a couple of different dump types on localhost, and it turned out one of them had not included global and had a different setting for maxdumps. I fixed that in my amanda.conf.

The second was

   Can't locate lib.pm:   Permission denied at 
/usr/local/libexec/amanda/amcheck-device line 21.

`make install` created a new directory, /usr/local/share/perl/5.18.2, with a subdirectory, Amanda, containing all the Amanda executables. All of the directories in this path, beginning with 5.18.2, had been installed with permissions 700 and owner root:root. So, of course, Amanda wasn't allowed to see anything. I recursively changed all the directory permissions down through that path to 755. I've run into this before, with one or the other (or both) of 3.3.3 or 3.3.6. So, this problem has been around for a while.

The third was

   ERROR: localhost: [Can't get realpath of the security file 
'/etc/amanda-security.conf': No such
   file or directory]

`make install` had stuffed that file in /usr/local/etc/amanda/amanda-security.conf. I copied it to /etc, where Amanda was looking for it.

Now everything appears to be working, with Amanda upgraded from 3.3.3 to 3.3.9. The server check found my LTO6 tape library and checked the tapes, and the client check was able to connect to all clients (which are still running 3.3.3). Holding space looks good.

We recently upgrades our SSD drives from 500G to a pair of server class 1TB drives. That's our holding space and it means we can get nearly a whole LTO6 worth of data on SSD before pushing it out to tape. My backup cron runs fstrim on the SSDs after the backup has completed to maintain their speed during the next backup. This has worked really well; and, with the prices of SSDs coming down, it might be worth considering for anyone who is using LTO6 or greater and trying to keep up with their speed.


On 8/1/16 1:32 PM, Debra S Baddorf wrote:
On Aug 1, 2016, at 11:42 AM, Chris Hoogendyk <[email protected]> wrote:

I'm presuming I just rebuild Amanda, but thought I would post this as a 
question just to see if anyone else has run into this, see if the members of 
the list concur, and put it on record.

I'm running Amanda 3.3.3 on a Supermicro server with Ubuntu Server 12.04 LTS. 
Sunday I did a release update to 14.04 LTS. I spent most of the day 
straightening out Apache config files, Mailman configuration parameters, 
pam/ldap/smb authentication issues, and so on. I had naively assumed that 
Amanda would just work (after all, it always does ;-) ).

Anyway, this morning, my cron message came in with

   RuntimeError Usage: suppress_error_traceback(); at 
/usr/local/share/perl/5.14.2/Amanda/Debug.pm line 180.

And no backup.

When I ran `amcheck daily`, I got the same message.

The new perl is

   This is perl 5, version 18, subversion 2 (v5.18.2) built for 
x86_64-linux-gnu-thread-multi
   (with 44 registered patches, see perl -V for more detail)

I believe the perl in 12.04 was v5.14.2-6ubuntu2.5.

I didn't think those were different enough to cause trouble.

Anyway, if I simply rebuild Amanda, I'm assuming everything will be alright. I 
have always built Amanda from source and never used any packages, although I do 
use aptitude for virtually everything else. So, I still have the source and 
config.status from when I built it before.


—
I run RedHat and FreeBSD linuxes,  and I don’t know Ubuntu; maybe that makes a 
difference.  I always build from scratch, with just a   configure
  (where I can specify username, tape drive, and port ranges.  Then a make, and 
make install   and all is peachy.  When i’m testing patches, I’ve
gone back and forth multiple times in a day.

Deb Baddorf
Fermilab





---------------

Chris Hoogendyk

-
   O__  ---- Systems Administrator
  c/ /'_ --- Biology & Geosciences Departments
(*) \(*) -- 315 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst

<[email protected]>

---------------

Erdös 4



--
---------------

Chris Hoogendyk

-
   O__  ---- Systems Administrator
  c/ /'_ --- Biology & Geosciences Departments
 (*) \(*) -- 315 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst

<[email protected]>

---------------

Erdös 4

Reply via email to