Re: Looking for a *replacement* for Amanda...

[Robert Heller]

OK, the Debian devs decided to disable S3 support in the Debian build...

I'm rebuilding them now (with S3 enabled) [yes, I have already installed 
Bacula's libs3].

At Wed,  7 Aug 2024 12:00:51 -0400 (EDT) Robert Heller  
wrote:

> 
> At Wed, 7 Aug 2024 17:10:42 +0200 li...@xunil.at wrote:
> 
> > 
> > Am 05.08.24 um 20:01 schrieb Charles Curley:
> > > On Mon,  5 Aug 2024 11:04:59 -0400 (EDT)
> > > Robert Heller  wrote:
> > > 
> > >> I *need* an automated network-based backup system, at least for my
> > >> home LAN -- I have 6 ARM SBCs that I want to make automated daily
> > >> backups of.  I have used Amanda in the past, but Amanda is now
> > >> broken, so I need to find a replacement.
> > > 
> > > I have heard good things about bacula. It is available for Debian 12
> > > (bookworm) and is in testing.
> > 
> > I went to Bacula for 2 new customers.
> > Bit of a learning curve ... it's designed for big environments.
> > 
> > Big plus: web gui "Bacularis". And the postgres-DB behind all the features.
> > 
> > Bacula CE should also contain a AWS S3 driver (I googled that quickly 
> > ... no further expertise).
> 
> I am not seeing any reference to AWS S3 in the version installed via apt...
> 
> > 
> > Side note to Amanda and S3: I worked around that by using Kopia as 
> > "second transporter": write to virtual tapes on disk via Amanda, then 
> > sync those to S3 via Kopia. Not very elegant, but does the trick in some 
> > environments.
> 
> Would need a local backuo disk -- not an option for my environments...
> 
> > 
> > 
> >
> > 
> 

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

Re: Looking for a *replacement* for Amanda...

[Robert Heller]

At Wed, 7 Aug 2024 17:10:42 +0200 li...@xunil.at wrote:

> 
> Am 05.08.24 um 20:01 schrieb Charles Curley:
> > On Mon,  5 Aug 2024 11:04:59 -0400 (EDT)
> > Robert Heller  wrote:
> > 
> >> I *need* an automated network-based backup system, at least for my
> >> home LAN -- I have 6 ARM SBCs that I want to make automated daily
> >> backups of.  I have used Amanda in the past, but Amanda is now
> >> broken, so I need to find a replacement.
> > 
> > I have heard good things about bacula. It is available for Debian 12
> > (bookworm) and is in testing.
> 
> I went to Bacula for 2 new customers.
> Bit of a learning curve ... it's designed for big environments.
> 
> Big plus: web gui "Bacularis". And the postgres-DB behind all the features.
> 
> Bacula CE should also contain a AWS S3 driver (I googled that quickly 
> ... no further expertise).

I am not seeing any reference to AWS S3 in the version installed via apt...

> 
> Side note to Amanda and S3: I worked around that by using Kopia as 
> "second transporter": write to virtual tapes on disk via Amanda, then 
> sync those to S3 via Kopia. Not very elegant, but does the trick in some 
> environments.

Would need a local backuo disk -- not an option for my environments...

> 
>   
>  
> 

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
   

Re: Looking for a *replacement* for Amanda...

[Stefan G. Weichinger]

Am 05.08.24 um 20:01 schrieb Charles Curley:

On Mon,  5 Aug 2024 11:04:59 -0400 (EDT)
Robert Heller  wrote:


I *need* an automated network-based backup system, at least for my
home LAN -- I have 6 ARM SBCs that I want to make automated daily
backups of.  I have used Amanda in the past, but Amanda is now
broken, so I need to find a replacement.


I have heard good things about bacula. It is available for Debian 12
(bookworm) and is in testing.


I went to Bacula for 2 new customers.
Bit of a learning curve ... it's designed for big environments.

Big plus: web gui "Bacularis". And the postgres-DB behind all the features.

Bacula CE should also contain a AWS S3 driver (I googled that quickly 
... no further expertise).


Side note to Amanda and S3: I worked around that by using Kopia as 
"second transporter": write to virtual tapes on disk via Amanda, then 
sync those to S3 via Kopia. Not very elegant, but does the trick in some 
environments.

Re: Looking for a *replacement* for Amanda...

[Charles Curley]

On Mon,  5 Aug 2024 11:04:59 -0400 (EDT)
Robert Heller  wrote:

> I *need* an automated network-based backup system, at least for my
> home LAN -- I have 6 ARM SBCs that I want to make automated daily
> backups of.  I have used Amanda in the past, but Amanda is now
> broken, so I need to find a replacement.

I have heard good things about bacula. It is available for Debian 12
(bookworm) and is in testing.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 and arm64

[Robert Heller]

The original debs were build *without* the man pages due to a missing build 
dep.  I have rebuild the arm64 deps and I will rebuild the amd64 tonight.

At Sat,  3 Aug 2024 20:35:56 -0400 (EDT) Robert Heller  
wrote:

> 
> Files available at http://files.deepsoft.com/Other/Amanda-3.5.4-Debian12/
> 
> Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 (x86_64) and arm64 
> (aarch64)
> 
> Built using a x86_64 vm with a vanila Debian 12 (bookworm) installed 
> (qemu-system-x86_64) on a Rpi 5 host, running  Debian 12 (bookworm) and on 
> the Rpi 5 running  Debian 12 (bookworm).
> 
> The files were signed with the Deepwoods Software key, available from 
> http://files.deepsoft.com/RPM-GPG-KEY-Deepwoods-Software
> 
> 
> 

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
   

Looking for a *replacement* for Amanda...

[Robert Heller]

Amanda 3.5 no longer works -- its support for Amazon S3 is non-functional.

Amanda 3.3.3 won't build with Debian 12 without major rewriting. Amanda 3.3.3 
does properly support Amazon S3, at least on older operating systems (eg 
CentOS 7 -- now EOL).

I *need* an automated network-based backup system, at least for my home LAN -- 
I have 6 ARM SBCs that I want to make automated daily backups of.  I have used 
Amanda in the past, but Amanda is now broken, so I need to find a replacement.

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

Re: Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 and arm64

[Robert Heller]

At Mon,  5 Aug 2024 08:45:25 -0400 (EDT) Robert Heller  
wrote:

> 
> 
> At Mon, 5 Aug 2024 07:43:14 +0200 li...@xunil.at wrote:
> 
> > 
> > Am 04.08.24 um 18:51 schrieb Robert Heller:
> > > Amazon S3 still does not work :-(
> > 
> > I didn't really expect it to work ...
> > 
> > The community edition simply seems to be neglected for years now.
> > 
> > Sad, but true.
> > 
> > I have issues on github that are many years open and unresolved, 52 open 
> > issues right now. They simply don't care.
> 
> I'm going to build 3.3.3 -- it needs patching to compile it with openssl3.

Getting Amanda 3.3.3 to build under Debian 12 is looking like bear.  Too many 
core libraries have moved on, so there are many places where the code 
breaks...

Sigh.  I am going to abandan using Amanda and write my own backup system or 
find some something else...

> 
> > 
> > 
> > 
> 

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
 

Re: Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 and arm64

[Robert Heller]

At Mon, 5 Aug 2024 07:43:14 +0200 li...@xunil.at wrote:

> 
> Am 04.08.24 um 18:51 schrieb Robert Heller:
> > Amazon S3 still does not work :-(
> 
> I didn't really expect it to work ...
> 
> The community edition simply seems to be neglected for years now.
> 
> Sad, but true.
> 
> I have issues on github that are many years open and unresolved, 52 open 
> issues right now. They simply don't care.

I'm going to build 3.3.3 -- it needs patching to compile it with openssl3.

> 
> 
> 

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
  

Re: Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 and arm64

[Stefan G. Weichinger]

Am 04.08.24 um 18:51 schrieb Robert Heller:

Amazon S3 still does not work :-(


I didn't really expect it to work ...

The community edition simply seems to be neglected for years now.

Sad, but true.

I have issues on github that are many years open and unresolved, 52 open 
issues right now. They simply don't care.

Re: Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 and arm64

[Robert Heller]

Amazon S3 still does not work :-(

At Sun, 4 Aug 2024 18:09:12 +0200 sgw  wrote:

> 
> Am 04.08.24 um 02:35 schrieb Robert Heller:
> > Files available at http://files.deepsoft.com/Other/Amanda-3.5.4-Debian12/
> > 
> > Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 (x86_64) and arm64 
> > (aarch64)
> > 
> > Built using a x86_64 vm with a vanila Debian 12 (bookworm) installed
> > (qemu-system-x86_64) on a Rpi 5 host, running  Debian 12 (bookworm) and on
> > the Rpi 5 running  Debian 12 (bookworm).
> > 
> > The files were signed with the Deepwoods Software key, available from
> > http://files.deepsoft.com/RPM-GPG-KEY-Deepwoods-Software
> 
> Wow, great. Thanks for your work.
> 
> Looking forward to reports from users using it :-)
> 
>   
>   
> 

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
 

Amanda 3.5.4 and Amazon S3 problems...

[Robert Heller]

Has *anyone* managed to *successfully* use Amanda 3.5.4 with a Amazon S3 based 
tape changer?

It is still not working.

I am thinking of getting the sources for Amanda 3.3.3 (which does work with 
Amazon S3 based tape changers -- I had it working just fine with CentOS 7).

The error in the taper debug log is:

Sun Aug 04 12:11:38.017564217 2024: pid 5996: thd-0x5556391dba00: taper: PUT 
https://s3.amazonaws.com/deepwoods-home-backups/slot-000%2Fspecial-tapestart 
failed with 403/SignatureDoesNotMatch
Sun Aug 04 12:11:38.019440513 2024: pid 5996: thd-0x5556391dba00: taper: Device 
s3:deepwoods-home-backups/slot-000/ error 



-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

  

Re: Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 and arm64

[Stefan G. Weichinger]

Am 04.08.24 um 02:35 schrieb Robert Heller:

Files available at http://files.deepsoft.com/Other/Amanda-3.5.4-Debian12/

Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 (x86_64) and arm64 
(aarch64)

Built using a x86_64 vm with a vanila Debian 12 (bookworm) installed
(qemu-system-x86_64) on a Rpi 5 host, running  Debian 12 (bookworm) and on
the Rpi 5 running  Debian 12 (bookworm).

The files were signed with the Deepwoods Software key, available from
http://files.deepsoft.com/RPM-GPG-KEY-Deepwoods-Software


Wow, great. Thanks for your work.

Looking forward to reports from users using it :-)

Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 and arm64

[Robert Heller]

Files available at http://files.deepsoft.com/Other/Amanda-3.5.4-Debian12/

Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 (x86_64) and arm64 
(aarch64)

Built using a x86_64 vm with a vanila Debian 12 (bookworm) installed 
(qemu-system-x86_64) on a Rpi 5 host, running  Debian 12 (bookworm) and on 
the Rpi 5 running  Debian 12 (bookworm).

The files were signed with the Deepwoods Software key, available from 
http://files.deepsoft.com/RPM-GPG-KEY-Deepwoods-Software



-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
  

Re: amanda as NAS, running on a bpi-m5

[gene heskett]

On 2/14/24 15:33, Winston Sorfleet wrote:
Glad to see you're still alive and kicking Gene.  While hardly 
Amanda-specific, given you're likely to be doing a lot more writes 
(backups) than reads (restores), you probably want to give some thought 
your file system choice (I'd think XFS maybe) and operating parameters 
accordingly.  Not to mention your NFS sync options.  You might even want 
to tune your Ethernet MTU particularly if you're pre-compressing via 
Amanda comp-tar.


File systemwise I'm fam with ext4, and my experience with NFS has been 
poor at best. I've been using sshfs shares fot about 20 years now, no 
surprises, unlike NFS and samba/cifs. XFS might be tried if I could 
actually find something that explains the diffs down to the dirt under 
its fingernails level.


Do you have a link to something educational in that arena?

Thanks Winston.


On 2024-02-14 04:21, gene heskett wrote:

Greetings All;

Due to the simultainious failure of a pair of 2T seacrates, spinning 
rust, which p'd me off so bad there is now only one spinning rust 
drive left here at the Heskett Ranchete's 8 or 9 machine network.


So I've been out of the amanda users category for a couple years.

So here's a description of what I am building:

A 5 drive slot bare drive cage, top slot occupied by a bpi-m5 running 
a full desktop armbian install, but headless.
Slots 2 & 3 will be occupied by a pair of 4T SSD's and a pair of 2T 
gigastone SSD's for 12T worth of vtapes.
the 4th slot will have at least one, maybe 2, 1T samsung SSD's. Or 2 
mote 2T gigastones since I have them
two separate subdirs on each of these 2 drives, one for amandas 
database on 1 drive, and a copy on the other drive, done by rsync as 
the second line of the cron trigger'd nightly amanda backup and 2nd 
dir on each as a 2 drive lvm for a holding disk.


This will all run on a 5V10A psu in slot 5. A 7 port usb3 hub glued to 
the side of the drive cage and startech usb-3 to sata-III adapters 
will complete the wiring mess. One cat5 connected to the bpi-m5 & 
plugged into my main net switch.  The amanda will be the arm64 version 
from the debian bookworm repos.


So get out your anti-aircraft battery's and shoot me down! What did I 
miss IOW?


Yeah, thru the magic of the cath lab at WVU-Ruby, I am still here, 
doing my thing with 3d printers these days, and my next b-day if I 
make it to October will be my 90th.


Many thanks, take care, stay warm and well everyone.

Cheers, Gene Heskett, CET.

.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: amanda as NAS, running on a bpi-m5

[Winston Sorfleet]

Glad to see you're still alive and kicking Gene.  While hardly 
Amanda-specific, given you're likely to be doing a lot more writes 
(backups) than reads (restores), you probably want to give some thought 
your file system choice (I'd think XFS maybe) and operating parameters 
accordingly.  Not to mention your NFS sync options.  You might even want 
to tune your Ethernet MTU particularly if you're pre-compressing via 
Amanda comp-tar.


On 2024-02-14 04:21, gene heskett wrote:

Greetings All;

Due to the simultainious failure of a pair of 2T seacrates, spinning 
rust, which p'd me off so bad there is now only one spinning rust 
drive left here at the Heskett Ranchete's 8 or 9 machine network.


So I've been out of the amanda users category for a couple years.

So here's a description of what I am building:

A 5 drive slot bare drive cage, top slot occupied by a bpi-m5 running 
a full desktop armbian install, but headless.
Slots 2 & 3 will be occupied by a pair of 4T SSD's and a pair of 2T 
gigastone SSD's for 12T worth of vtapes.
the 4th slot will have at least one, maybe 2, 1T samsung SSD's. Or 2 
mote 2T gigastones since I have them
two separate subdirs on each of these 2 drives, one for amandas 
database on 1 drive, and a copy on the other drive, done by rsync as 
the second line of the cron trigger'd nightly amanda backup and 2nd 
dir on each as a 2 drive lvm for a holding disk.


This will all run on a 5V10A psu in slot 5. A 7 port usb3 hub glued to 
the side of the drive cage and startech usb-3 to sata-III adapters 
will complete the wiring mess. One cat5 connected to the bpi-m5 & 
plugged into my main net switch.  The amanda will be the arm64 version 
from the debian bookworm repos.


So get out your anti-aircraft battery's and shoot me down! What did I 
miss IOW?


Yeah, thru the magic of the cath lab at WVU-Ruby, I am still here, 
doing my thing with 3d printers these days, and my next b-day if I 
make it to October will be my 90th.


Many thanks, take care, stay warm and well everyone.

Cheers, Gene Heskett, CET.

amanda as NAS, running on a bpi-m5

[gene heskett]

Greetings All;

Due to the simultainious failure of a pair of 2T seacrates, spinning 
rust, which p'd me off so bad there is now only one spinning rust drive 
left here at the Heskett Ranchete's 8 or 9 machine network.


So I've been out of the amanda users category for a couple years.

So here's a description of what I am building:

A 5 drive slot bare drive cage, top slot occupied by a bpi-m5 running a 
full desktop armbian install, but headless.
Slots 2 & 3 will be occupied by a pair of 4T SSD's and a pair of 2T 
gigastone SSD's for 12T worth of vtapes.
the 4th slot will have at least one, maybe 2, 1T samsung SSD's. Or 2 
mote 2T gigastones since I have them
two separate subdirs on each of these 2 drives, one for amandas database 
on 1 drive, and a copy on the other drive, done by rsync as the second 
line of the cron trigger'd nightly amanda backup and 2nd dir on each as 
a 2 drive lvm for a holding disk.


This will all run on a 5V10A psu in slot 5. A 7 port usb3 hub glued to 
the side of the drive cage and startech usb-3 to sata-III adapters will 
complete the wiring mess. One cat5 connected to the bpi-m5 & plugged 
into my main net switch.  The amanda will be the arm64 version from the 
debian bookworm repos.


So get out your anti-aircraft battery's and shoot me down! What did I 
miss IOW?


Yeah, thru the magic of the cath lab at WVU-Ruby, I am still here, doing 
my thing with 3d printers these days, and my next b-day if I make it to 
October will be my 90th.


Many thanks, take care, stay warm and well everyone.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: Amanda 3.5.3-1.fc38 aborts dump on EOF error to planner

[Lou Hafer]

Jose,

Indeed I would be interested! Certainly worth a try.

 Thanks,
  Lou


On 2023-07-25 9:34 a.m., Jose M Calhariz wrote:

Hi,

If I understand well your problem I found it in 3.5.1 and I have a
patch that fix it, from the previous owner of amanda.  The patch is
being in used by amanda in Debian for several years.

I can publish the patch here if you are interested.

Kind regards
Jose M Calhariz


On Wed, Jul 19, 2023 at 09:34:21AM -0700, Lou Hafer wrote:

Nuno,

 Thanks for the reply! And apologies for being not quite clear.

 I'm quite sure the offending hosts are powered down, so no chance of
partial response. When I look at the planner..debug log, I can
see sendsize requests going out to the hosts that are powered up and
responsive, and I can see their responses arrive. There are two hosts
powered down, gallifrey and jpt. The requests go out to gallifrey, then jpt.
When the request to gallifrey times out, planner sees 255 status from SSH
and aborts with the EOF error. Doesn't even wait around for the timeout on
jpt.

 If I go back and look at some old logs, I can see planner continue past
the `EOF on read' error. So I'm really starting to think this is a new bug
in 3.5.3.

 For what it's worth, I'd interpret your error,

ERROR Request to MACHINE failed: Connection refused

as the machine was powered up and responsive but actively refused the
connection for some reason.

 I'm puzzled by another thing: we're using the same version of amanda
(3.5.3) and I run backups to disk, no tape drive involved, but I've never
seen the error you mention in April: backup aborts after first machine/disk
in disklist. The obvious difference is Fedora 37 versus Fedora 38, but
really that shouldn't cause this much difference in behaviour.

 Bah! Sometimes staying up-to-date is a bit painful. I'll see if anyone
else chimes in before I report this as a bug.

 Spent two weeks in Porto and the Douro Valley in Fall 2022. Loved the
country!

 Lou


On 2023-07-19 2:17 a.m., Nuno Dias wrote:

   Hi Lou,

   I'm using the same version as you, although in Fedora 37
amanda-3.5.3-1.fc37.x86_64 and I don't see that behaviour, I have some
machines that are down and the rest of the backups were made.

   In my case I have this

planner: ERROR Request to MACHINE failed: Connection refused

   From what you wrote, it seems gallifrey.ivriel is not down is
responding, but has some problems reporting the size.

   Maybe this page will help

https://www.zmanda.com/knowledge-base/eof-on-read-error-from-a-client/

   Although if is aborting all the planner it seems a bug, or there are
other reasons for aborting all the planner, maybe checking if the
etimeout  is not very low.

Cheers,
Nuno

On Tue, 2023-07-18 at 13:50 -0700, Lou Hafer wrote:

Folks,

   I've been using amanda for several years on a simple home
network.
Hosts are often powered down. Up through amanda 3.5.2, this worked
like
a charm. If the host didn't respond, it was simply skipped. Hosts
that
responded were properly backed up.

   With amanda 3.5.3, the behaviour has changed. If a host doesn't
respond to the planner size request, the planner aborts the entire
backup with the error

     planner: ERROR Request to gallifrey.ivriel failed:
     EOF on read from gallifrey.ivriel

I've confirmed that my configuration is generally correct --- as long
as
all hosts in the disklist respond to the size request, the backup
succeeds.

Is this a bug? Do I need to change some parameter in my configuration
to
persuade planner to soldier on? Any thoughts would be appreciated.

   As context, this problem came about with an upgrade from Fedora
37
to Fedora 38, with a matching upgrade from amanda 3.5.2 to amanda
3.5.3.

   Thanks,
   Lou

Re: Amanda 3.5.3-1.fc38 aborts dump on EOF error to planner

[Lou Hafer]

Nuno,

Thanks for the reply! And apologies for being not quite clear.

I'm quite sure the offending hosts are powered down, so no chance 
of partial response. When I look at the planner..debug log, I 
can see sendsize requests going out to the hosts that are powered up and 
responsive, and I can see their responses arrive. There are two hosts 
powered down, gallifrey and jpt. The requests go out to gallifrey, then 
jpt. When the request to gallifrey times out, planner sees 255 status 
from SSH and aborts with the EOF error. Doesn't even wait around for the 
timeout on jpt.


If I go back and look at some old logs, I can see planner continue 
past the `EOF on read' error. So I'm really starting to think this is a 
new bug in 3.5.3.


For what it's worth, I'd interpret your error,

ERROR Request to MACHINE failed: Connection refused

as the machine was powered up and responsive but actively refused the 
connection for some reason.


I'm puzzled by another thing: we're using the same version of 
amanda (3.5.3) and I run backups to disk, no tape drive involved, but 
I've never seen the error you mention in April: backup aborts after 
first machine/disk in disklist. The obvious difference is Fedora 37 
versus Fedora 38, but really that shouldn't cause this much difference 
in behaviour.


Bah! Sometimes staying up-to-date is a bit painful. I'll see if 
anyone else chimes in before I report this as a bug.


Spent two weeks in Porto and the Douro Valley in Fall 2022. Loved 
the country!


Lou


On 2023-07-19 2:17 a.m., Nuno Dias wrote:

  Hi Lou,

  I'm using the same version as you, although in Fedora 37
amanda-3.5.3-1.fc37.x86_64 and I don't see that behaviour, I have some
machines that are down and the rest of the backups were made.

  In my case I have this

   planner: ERROR Request to MACHINE failed: Connection refused

  From what you wrote, it seems gallifrey.ivriel is not down is
responding, but has some problems reporting the size.

  Maybe this page will help

https://www.zmanda.com/knowledge-base/eof-on-read-error-from-a-client/

  Although if is aborting all the planner it seems a bug, or there are
other reasons for aborting all the planner, maybe checking if the
etimeout  is not very low.

Cheers,
Nuno

On Tue, 2023-07-18 at 13:50 -0700, Lou Hafer wrote:

Folks,

  I've been using amanda for several years on a simple home
network.
Hosts are often powered down. Up through amanda 3.5.2, this worked
like
a charm. If the host didn't respond, it was simply skipped. Hosts
that
responded were properly backed up.

  With amanda 3.5.3, the behaviour has changed. If a host doesn't
respond to the planner size request, the planner aborts the entire
backup with the error

    planner: ERROR Request to gallifrey.ivriel failed:
    EOF on read from gallifrey.ivriel

I've confirmed that my configuration is generally correct --- as long
as
all hosts in the disklist respond to the size request, the backup
succeeds.

Is this a bug? Do I need to change some parameter in my configuration
to
persuade planner to soldier on? Any thoughts would be appreciated.

  As context, this problem came about with an upgrade from Fedora
37
to Fedora 38, with a matching upgrade from amanda 3.5.2 to amanda
3.5.3.

  Thanks,
  Lou

Re: Amanda 3.5.3-1.fc38 aborts dump on EOF error to planner

[Nuno Dias]

 Hi Lou,

 I'm using the same version as you, although in Fedora 37 
amanda-3.5.3-1.fc37.x86_64 and I don't see that behaviour, I have some
machines that are down and the rest of the backups were made.

 In my case I have this

  planner: ERROR Request to MACHINE failed: Connection refused

 From what you wrote, it seems gallifrey.ivriel is not down is
responding, but has some problems reporting the size.

 Maybe this page will help

https://www.zmanda.com/knowledge-base/eof-on-read-error-from-a-client/

 Although if is aborting all the planner it seems a bug, or there are
other reasons for aborting all the planner, maybe checking if the
etimeout  is not very low.

Cheers,
Nuno 

On Tue, 2023-07-18 at 13:50 -0700, Lou Hafer wrote:
> Folks,
> 
>      I've been using amanda for several years on a simple home
> network. 
> Hosts are often powered down. Up through amanda 3.5.2, this worked
> like 
> a charm. If the host didn't respond, it was simply skipped. Hosts
> that 
> responded were properly backed up.
> 
>  With amanda 3.5.3, the behaviour has changed. If a host doesn't 
> respond to the planner size request, the planner aborts the entire 
> backup with the error
> 
>    planner: ERROR Request to gallifrey.ivriel failed:
>    EOF on read from gallifrey.ivriel
> 
> I've confirmed that my configuration is generally correct --- as long
> as 
> all hosts in the disklist respond to the size request, the backup
> succeeds.
> 
> Is this a bug? Do I need to change some parameter in my configuration
> to 
> persuade planner to soldier on? Any thoughts would be appreciated.
> 
>  As context, this problem came about with an upgrade from Fedora
> 37 
> to Fedora 38, with a matching upgrade from amanda 3.5.2 to amanda
> 3.5.3.
> 
>  Thanks,
>  Lou
> 

-- 
Nuno Dias 
LIP

Amanda 3.5.3-1.fc38 aborts dump on EOF error to planner

[Lou Hafer]

Folks,

I've been using amanda for several years on a simple home network. 
Hosts are often powered down. Up through amanda 3.5.2, this worked like 
a charm. If the host didn't respond, it was simply skipped. Hosts that 
responded were properly backed up.


With amanda 3.5.3, the behaviour has changed. If a host doesn't 
respond to the planner size request, the planner aborts the entire 
backup with the error


  planner: ERROR Request to gallifrey.ivriel failed:
  EOF on read from gallifrey.ivriel

I've confirmed that my configuration is generally correct --- as long as 
all hosts in the disklist respond to the size request, the backup succeeds.


Is this a bug? Do I need to change some parameter in my configuration to 
persuade planner to soldier on? Any thoughts would be appreciated.


As context, this problem came about with an upgrade from Fedora 37 
to Fedora 38, with a matching upgrade from amanda 3.5.2 to amanda 3.5.3.


Thanks,
Lou

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Robert Heller]

At Sat, 10 Jun 2023 08:25:45 -0600 Orion Poplawski  wrote:

> 
> On 6/10/23 06:13, Robert Heller wrote:
> > At Fri, 9 Jun 2023 23:35:23 -0400 Deb Baddorf  
> > wrote:
> > 
> >>
> >> Time Machine is built into current Mac OSes. It 
> >> wants its own disk, which should be a bit (or a lot) bigger than the one 
> >> you are backing up.  I don’t think it can 
> >> backup to another machine. It works well, since 
> >> it’s baked in.
> > 
> > This does me no good. I don't have any way of adding a second disk to this
> > machine (and I don't really want to). All of my other backups go to a 
> > "server"
> > (my main desktop machine) and the fulls get uploaded to off-site storage
> > (Amazon Glacier).
> > 
> 
> As myself and others have said, Time Machine can backup to network 
> volumes, either Apple (netatalk) or CIFS (samba).

And I really would not have to deal with either netatalk or samba, ESP. for a
one-of (both are something of a pain-in-the-ass to set up). (Actually, MacOSX
can *also* do NFS, which is a *native* UNIX/Linux network file sharing
protocol.)

> 

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
  

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Orion Poplawski]

On 6/10/23 06:13, Robert Heller wrote:

At Fri, 9 Jun 2023 23:35:23 -0400 Deb Baddorf  wrote:



Time Machine is built into current Mac OSes. It wants its own disk, which 
should be a bit (or a lot) bigger than the one you are backing up.  I 
don’t think it can backup to another machine. It works well, since 
it’s baked in.


This does me no good. I don't have any way of adding a second disk to this
machine (and I don't really want to). All of my other backups go to a "server"
(my main desktop machine) and the fulls get uploaded to off-site storage
(Amazon Glacier).



As myself and others have said, Time Machine can backup to network 
volumes, either Apple (netatalk) or CIFS (samba).


--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Robert Heller]

At Fri, 9 Jun 2023 23:35:23 -0400 Deb Baddorf  wrote:

> 
> Time Machine is built into current Mac OSes. It wants its own disk, 
> which should be a bit (or a lot) bigger than the one you are backing up.  I 
> don’t think it can backup to another machine. It works well, since 
> it’s baked in.

This does me no good. I don't have any way of adding a second disk to this
machine (and I don't really want to). All of my other backups go to a "server"
(my main desktop machine) and the fulls get uploaded to off-site storage
(Amazon Glacier).

> 
> Deb 
> 
> > On Jun 8, 2023, at 10:36 PM, Robert Heller  wrote:
> > I know nothing about "Time Machine".  Will it backup to a Linux 
> > machine?
> > 
> > At Thu, 8 Jun 2023 17:39:47 -0600 Orion Poplawski  wrote:
> > 
> >> 
> >> On 6/8/23 09:50, Robert Heller wrote:
> >>> Already doing that.
> >>> I'm beginning to think that I need to find some other way of backing up 
> >>> this
> >>> machine, or maybe just not back it up at all (it is just a build box and 
> >>> has
> >>> nothing on it that is not available either elsewhere on my LAN (eg the
> >>> subversion tree on my main desktop) or out on the Internet (eg the O/S and
> >>> XCode at Apple.com or via Mac Ports).
> >> 
> >> Why not Time Machine?
> > 
> > -- 
> > Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
> > Deepwoods Software-- Custom Software Services
> > http://www.deepsoft.com/  -- Linux Administration Services
> > hel...@deepsoft.com   -- Webhosting Services
> 
> 
> 

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

 

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Deb Baddorf]

Time Machine is built into current Mac OSes. It wants its own disk, which 
should be a bit (or a lot) bigger than the one you are backing up.  I don’t 
think it can backup to another machine. It works well, since it’s baked in.

Deb 

> On Jun 8, 2023, at 10:36 PM, Robert Heller  wrote:
> I know nothing about "Time Machine".  Will it backup to a Linux machine?
> 
> At Thu, 8 Jun 2023 17:39:47 -0600 Orion Poplawski  wrote:
> 
>> 
>> On 6/8/23 09:50, Robert Heller wrote:
>>> Already doing that.
>>> I'm beginning to think that I need to find some other way of backing up this
>>> machine, or maybe just not back it up at all (it is just a build box and has
>>> nothing on it that is not available either elsewhere on my LAN (eg the
>>> subversion tree on my main desktop) or out on the Internet (eg the O/S and
>>> XCode at Apple.com or via Mac Ports).
>> 
>> Why not Time Machine?
> 
> -- 
> Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
> Deepwoods Software-- Custom Software Services
> http://www.deepsoft.com/  -- Linux Administration Services
> hel...@deepsoft.com   -- Webhosting Services

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Orion Poplawski]

On 6/9/23 00:51, Hauke Fath wrote:

On Thu,  8 Jun 2023 20:57:38 -0400 (EDT), Robert Heller wrote:

I know nothing about "Time Machine".  Will it backup to a Linux machine?


We use Time Machine at work to back up Macs to a Samba share, so yes.

It is user-operable, and you can restore from the rescue system for
desaster recovery.

I replaced backup to TSM with Time Machine (modernish macOS does not
allow full disk access for command-line applications, which made
scheduled backups impossible), and am very happy with it.


You can also use netatalk to setup an Apple file share - I've had better 
luck with that than CIFS, but maybe support for that has improved since 
last I checked.


--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Robert Heller]

At Thu, 8 Jun 2023 21:31:50 -0600 Charles Curley 
 wrote:

> 
> On Thu,  8 Jun 2023 20:57:38 -0400 (EDT)
> Robert Heller  wrote:
> 
> > I know nothing about "Time Machine".  Will it backup to a Linux
> > machine?
> 
> Yes. You need Apple networking so the Linux machine will fake a Mac. On
> Debian, that would be the netatalk package. That also pulls in avahi
> (bonjour implementation), so your Mac will find the server
> automatically.
> 
> However, if you encrypt the backup, the files on the Linux machine are
> opaque, meaning you can't extract a file on the Linux machine. I have
> not experimented with an unencrypted backup.
> 
> This is how I back up my iPhone, since Apple won't release iPhone
> backup software for Linux.
> 
> You could also mount a Samba share on your Mac.

I did some poking around, and it looks like I could automount a NFS file 
system as well.  I'd rather not mess with Samba or netatalk.

> 

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Charles Curley]

On Thu, 8 Jun 2023 21:31:50 -0600
Charles Curley  wrote:

> However, if you encrypt the backup, the files on the Linux machine are
> opaque, meaning you can't extract a file on the Linux machine. I have
> not experimented with an unencrypted backup.

Or maybe not. Take a look at the Debian package tmfs.
https://github.com/abique/tmfs I haven't used it.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Hauke Fath]

On Thu,  8 Jun 2023 20:57:38 -0400 (EDT), Robert Heller wrote:
> I know nothing about "Time Machine".  Will it backup to a Linux machine?

We use Time Machine at work to back up Macs to a Samba share, so yes.

It is user-operable, and you can restore from the rescue system for 
desaster recovery.

I replaced backup to TSM with Time Machine (modernish macOS does not 
allow full disk access for command-line applications, which made 
scheduled backups impossible), and am very happy with it.

Cheerio,
Hauke

-- 
Hauke Fath
Linnéweg 7
64342 Seeheim-Jugenheim
Germany

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Charles Curley]

On Thu,  8 Jun 2023 20:57:38 -0400 (EDT)
Robert Heller  wrote:

> I know nothing about "Time Machine".  Will it backup to a Linux
> machine?

Yes. You need Apple networking so the Linux machine will fake a Mac. On
Debian, that would be the netatalk package. That also pulls in avahi
(bonjour implementation), so your Mac will find the server
automatically.

However, if you encrypt the backup, the files on the Linux machine are
opaque, meaning you can't extract a file on the Linux machine. I have
not experimented with an unencrypted backup.

This is how I back up my iPhone, since Apple won't release iPhone
backup software for Linux.

You could also mount a Samba share on your Mac.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Robert Heller]

I know nothing about "Time Machine".  Will it backup to a Linux machine?

At Thu, 8 Jun 2023 17:39:47 -0600 Orion Poplawski  wrote:

> 
> On 6/8/23 09:50, Robert Heller wrote:
> > 
> > Already doing that.
> > 
> > I'm beginning to think that I need to find some other way of backing up this
> > machine, or maybe just not back it up at all (it is just a build box and has
> > nothing on it that is not available either elsewhere on my LAN (eg the
> > subversion tree on my main desktop) or out on the Internet (eg the O/S and
> > XCode at Apple.com or via Mac Ports).
> 
> Why not Time Machine?
> 

-- 
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
   

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Orion Poplawski]

On 6/8/23 09:50, Robert Heller wrote:
> 
> Already doing that.
> 
> I'm beginning to think that I need to find some other way of backing up this
> machine, or maybe just not back it up at all (it is just a build box and has
> nothing on it that is not available either elsewhere on my LAN (eg the
> subversion tree on my main desktop) or out on the Internet (eg the O/S and
> XCode at Apple.com or via Mac Ports).

Why not Time Machine?

-- 
Orion Poplawski
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Jim Lawson]

I concur with your complaint.

You need to have the Finder show hidden files 
(https://www.macworld.com/article/671158/how-to-show-hidden-files-on-a-mac.html)
 so you can navigate to /opt/local/bin/gtar and add it to Full Disk Access.

In the Finder dialog that pops up when you click on '+' in Full Disk Access, 
type 'Command' + 'Shift' + '.'  (simultaneously) then navigate to the root of 
your filesystem containing /opt and from there you can get to the gtar 
application and add it to applications allowed Full Disk Access.

Backing up Macs as part of a site-wide process using Amanda is possible (I do 
it with Amanda 3.5.3 on a daily basis for OSX 11.7 and 12.6), but it's far from 
intuitive and requires knowledge of Apple idiosyncrasies that aren't well 
documented, and of course, isn't integrated well with the rest of MacOS. I tend 
to restrict it to backing up user files (mostly text) that I can work with on 
non-Mac systems.

I've never actually tried restoring anything from these backups. I use 
TimeMachine backups (to an OpenBSD server) for all my Mac-specific binaries.

> On Jun 8, 2023, at 8:44 AM, Robert Heller  wrote:
> 
> 
> That does not seem possible.  As far as Security & Privacy -> Full Disk 
> Access 
> is concerned, /opt/local/bin/gnutar does not exist and there does not seem to 
> be any way of getting there -- it only gives a limited number of places to 
> point and click on. (I really *hate* pointy-clicky UIs and hate it when a 
> computer treats me like a 2 year old.)
> 
> 
> 
> At Thu, 8 Jun 2023 08:22:09 -0700 Jim Lawson  wrote:
> 
>> 
>> I think you need the program that actually reads the files (in this case, 
>> /opt/local/bin/gtar) added to Full Disk Access.
>> 
>>> On Jun 8, 2023, at 7:40 AM, Robert Heller  wrote:
>>> 
>>> 
>>> It already is there.
>>> 
>>> At Thu, 8 Jun 2023 08:31:15 -0600 Pieter Bowman  
>>> wrote:
>>> 
>>>> 
>>>> Unfortunately, I have retired, so don't have access to systems running 
>>>> amanda on macOS/MacOSX.
>>>> 
>>>> However, I can suggest that the problem you are seeing is because of 
>>>> System Integrity Protection (SIP). You will need to add the executable 
>>>> amandad to System Settings -> Privacy & Security -> Full Disk Access.
>>>> 
>>>> Pieter
>>>> 
>>>> On 6/7/23 5:43 AM, Robert Heller wrote:
>>>>> Is there some "trick" to getting Amanda (3.5.1) to run properly under 
>>>>> MacOSX
>>>>> 10.15?  I recently added a new (to me) machine to my LAN and want to be 
>>>>> able
>>>>> to take regular backups of it.  I is an older model MacBook Pro (mid 2012
>>>>> vintage), running Amanda (3.5.1) to run properly under MacOSX 10.15 (the 
>>>>> last
>>>>> version of MacOSX that will run on this machine.  I just plan on using it 
>>>>> as a
>>>>> "build box", compiling my Open Source software.  All of the rest of my
>>>>> machines, consisting on one AMD (x86_64) desktop (running Ubuntu 22.04 
>>>>> LTS)
>>>>> and an assortment of ARM SBCs (Raspberry Pis, Banana Pis, etc.) all 
>>>>> running
>>>>> Debian 10 and they all run Amanda (3.5.1) and Amanda is working fine 
>>>>> backing
>>>>> up all of these machines.  I'd like to add the MacBook Pro.  I built 
>>>>> Amanda
>>>>> 3.5.1 from source on the MacBook Pro and installed it under /usr/local, 
>>>>> but
>>>>> Amanda has been "failing" on the MacBook Pro every night for about a week.
>>>>> 
>>>>> Here is the error log:
>>>>> 
>>>>> sendbackup: start [pipin:/System/Volumes/Data level 0]
>>>>> sendbackup: info BACKUP=/opt/local/bin/gtar
>>>>> sendbackup: info RECOVER_CMD=/opt/local/bin/gtar -xpGf - ...
>>>>> sendbackup: info end
>>>>> ? /opt/local/bin/gtar: ./Library/Application Support/com.apple.TCC: 
>>>>> Warning: Cannot open: Operation not permitted
>>>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Autosave Information: 
>>>>> Warning: Cannot open: Operation not permitted
>>>>> ? /opt/local/bin/gtar: ./Users/heller/Library/PersonalizationPortrait: 
>>>>> Warning: Cannot open: Operation not permitted
>>>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Reminders: Warning: Cannot 
>>>>> open: O

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Robert Heller]

Already doing that.

I'm beginning to think that I need to find some other way of backing up this
machine, or maybe just not back it up at all (it is just a build box and has
nothing on it that is not available either elsewhere on my LAN (eg the
subversion tree on my main desktop) or out on the Internet (eg the O/S and
XCode at Apple.com or via Mac Ports).

At Thu, 8 Jun 2023 17:40:31 +0200 Exuvo  wrote:

> 
> Either that or switch to using amgtar which has the s bit set.
> 
> On Thu, 8 Jun 2023, 17:27 Jim Lawson,  wrote:
> 
> > I think you need the program that actually reads the files (in this case,
> > /opt/local/bin/gtar) added to Full Disk Access.
> >
> > > On Jun 8, 2023, at 7:40 AM, Robert Heller  wrote:
> > >
> > >
> > > It already is there.
> > >
> > > At Thu, 8 Jun 2023 08:31:15 -0600 Pieter Bowman 
> > wrote:
> > >
> > >>
> > >> Unfortunately, I have retired, so don't have access to systems running
> > >> amanda on macOS/MacOSX.
> > >>
> > >> However, I can suggest that the problem you are seeing is because of
> > >> System Integrity Protection (SIP). You will need to add the executable
> > >> amandad to System Settings -> Privacy & Security -> Full Disk Access.
> > >>
> > >> Pieter
> > >>
> > >> On 6/7/23 5:43 AM, Robert Heller wrote:
> > >>> Is there some "trick" to getting Amanda (3.5.1) to run properly under
> > MacOSX
> > >>> 10.15?  I recently added a new (to me) machine to my LAN and want to
> > be able
> > >>> to take regular backups of it.  I is an older model MacBook Pro (mid
> > 2012
> > >>> vintage), running Amanda (3.5.1) to run properly under MacOSX 10.15
> > (the last
> > >>> version of MacOSX that will run on this machine.  I just plan on using
> > it as a
> > >>> "build box", compiling my Open Source software.  All of the rest of my
> > >>> machines, consisting on one AMD (x86_64) desktop (running Ubuntu 22.04
> > LTS)
> > >>> and an assortment of ARM SBCs (Raspberry Pis, Banana Pis, etc.) all
> > running
> > >>> Debian 10 and they all run Amanda (3.5.1) and Amanda is working fine
> > backing
> > >>> up all of these machines.  I'd like to add the MacBook Pro.  I built
> > Amanda
> > >>> 3.5.1 from source on the MacBook Pro and installed it under
> > /usr/local, but
> > >>> Amanda has been "failing" on the MacBook Pro every night for about a
> > week.
> > >>>
> > >>> Here is the error log:
> > >>>
> > >>> sendbackup: start [pipin:/System/Volumes/Data level 0]
> > >>> sendbackup: info BACKUP=/opt/local/bin/gtar
> > >>> sendbackup: info RECOVER_CMD=/opt/local/bin/gtar -xpGf - ...
> > >>> sendbackup: info end
> > >>> ? /opt/local/bin/gtar: ./Library/Application Support/com.apple.TCC:
> > Warning: Cannot open: Operation not permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Autosave Information:
> > Warning: Cannot open: Operation not permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/PersonalizationPortrait:
> > Warning: Cannot open: Operation not permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Reminders: Warning:
> > Cannot open: Operation not permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Safari: Warning: Cannot
> > open: Operation not permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Sharing: Warning: Cannot
> > open: Operation not permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Suggestions: Warning:
> > Cannot open: Operation not permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application
> > Support/AddressBook: Warning: Cannot open: Operation not permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application
> > Support/CallHistoryDB: Warning: Cannot open: Operation not permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application
> > Support/CallHistoryTransactions: Warning: Cannot open: Operation not
> > permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application
> > Support/FileProvider: Warning: Cannot open: Operation not permitted
> > >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application
> > Support/com.apple.TCC: Warning: Cannot o

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Robert Heller]

That does not seem possible.  As far as Security & Privacy -> Full Disk Access 
is concerned, /opt/local/bin/gnutar does not exist and there does not seem to 
be any way of getting there -- it only gives a limited number of places to 
point and click on. (I really *hate* pointy-clicky UIs and hate it when a 
computer treats me like a 2 year old.)



At Thu, 8 Jun 2023 08:22:09 -0700 Jim Lawson  wrote:

> 
> I think you need the program that actually reads the files (in this case, 
> /opt/local/bin/gtar) added to Full Disk Access.
> 
> > On Jun 8, 2023, at 7:40 AM, Robert Heller  wrote:
> > 
> > 
> > It already is there.
> > 
> > At Thu, 8 Jun 2023 08:31:15 -0600 Pieter Bowman  
> > wrote:
> > 
> >> 
> >> Unfortunately, I have retired, so don't have access to systems running 
> >> amanda on macOS/MacOSX.
> >> 
> >> However, I can suggest that the problem you are seeing is because of 
> >> System Integrity Protection (SIP). You will need to add the executable 
> >> amandad to System Settings -> Privacy & Security -> Full Disk Access.
> >> 
> >> Pieter
> >> 
> >> On 6/7/23 5:43 AM, Robert Heller wrote:
> >>> Is there some "trick" to getting Amanda (3.5.1) to run properly under 
> >>> MacOSX
> >>> 10.15?  I recently added a new (to me) machine to my LAN and want to be 
> >>> able
> >>> to take regular backups of it.  I is an older model MacBook Pro (mid 2012
> >>> vintage), running Amanda (3.5.1) to run properly under MacOSX 10.15 (the 
> >>> last
> >>> version of MacOSX that will run on this machine.  I just plan on using it 
> >>> as a
> >>> "build box", compiling my Open Source software.  All of the rest of my
> >>> machines, consisting on one AMD (x86_64) desktop (running Ubuntu 22.04 
> >>> LTS)
> >>> and an assortment of ARM SBCs (Raspberry Pis, Banana Pis, etc.) all 
> >>> running
> >>> Debian 10 and they all run Amanda (3.5.1) and Amanda is working fine 
> >>> backing
> >>> up all of these machines.  I'd like to add the MacBook Pro.  I built 
> >>> Amanda
> >>> 3.5.1 from source on the MacBook Pro and installed it under /usr/local, 
> >>> but
> >>> Amanda has been "failing" on the MacBook Pro every night for about a week.
> >>> 
> >>> Here is the error log:
> >>> 
> >>> sendbackup: start [pipin:/System/Volumes/Data level 0]
> >>> sendbackup: info BACKUP=/opt/local/bin/gtar
> >>> sendbackup: info RECOVER_CMD=/opt/local/bin/gtar -xpGf - ...
> >>> sendbackup: info end
> >>> ? /opt/local/bin/gtar: ./Library/Application Support/com.apple.TCC: 
> >>> Warning: Cannot open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Autosave Information: 
> >>> Warning: Cannot open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/PersonalizationPortrait: 
> >>> Warning: Cannot open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Reminders: Warning: Cannot 
> >>> open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Safari: Warning: Cannot 
> >>> open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Sharing: Warning: Cannot 
> >>> open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Suggestions: Warning: 
> >>> Cannot open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> >>> Support/AddressBook: Warning: Cannot open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> >>> Support/CallHistoryDB: Warning: Cannot open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> >>> Support/CallHistoryTransactions: Warning: Cannot open: Operation not 
> >>> permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> >>> Support/FileProvider: Warning: Cannot open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> >>> Support/com.apple.TCC: Warning: Cannot open: Operation not permitted
> >>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> >>> Support/com.apple.sharedfilelist: Warning: Cannot open: Operation no

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Jim Lawson]

I think you need the program that actually reads the files (in this case, 
/opt/local/bin/gtar) added to Full Disk Access.

> On Jun 8, 2023, at 7:40 AM, Robert Heller  wrote:
> 
> 
> It already is there.
> 
> At Thu, 8 Jun 2023 08:31:15 -0600 Pieter Bowman  
> wrote:
> 
>> 
>> Unfortunately, I have retired, so don't have access to systems running 
>> amanda on macOS/MacOSX.
>> 
>> However, I can suggest that the problem you are seeing is because of 
>> System Integrity Protection (SIP). You will need to add the executable 
>> amandad to System Settings -> Privacy & Security -> Full Disk Access.
>> 
>> Pieter
>> 
>> On 6/7/23 5:43 AM, Robert Heller wrote:
>>> Is there some "trick" to getting Amanda (3.5.1) to run properly under MacOSX
>>> 10.15?  I recently added a new (to me) machine to my LAN and want to be able
>>> to take regular backups of it.  I is an older model MacBook Pro (mid 2012
>>> vintage), running Amanda (3.5.1) to run properly under MacOSX 10.15 (the 
>>> last
>>> version of MacOSX that will run on this machine.  I just plan on using it 
>>> as a
>>> "build box", compiling my Open Source software.  All of the rest of my
>>> machines, consisting on one AMD (x86_64) desktop (running Ubuntu 22.04 LTS)
>>> and an assortment of ARM SBCs (Raspberry Pis, Banana Pis, etc.) all running
>>> Debian 10 and they all run Amanda (3.5.1) and Amanda is working fine backing
>>> up all of these machines.  I'd like to add the MacBook Pro.  I built Amanda
>>> 3.5.1 from source on the MacBook Pro and installed it under /usr/local, but
>>> Amanda has been "failing" on the MacBook Pro every night for about a week.
>>> 
>>> Here is the error log:
>>> 
>>> sendbackup: start [pipin:/System/Volumes/Data level 0]
>>> sendbackup: info BACKUP=/opt/local/bin/gtar
>>> sendbackup: info RECOVER_CMD=/opt/local/bin/gtar -xpGf - ...
>>> sendbackup: info end
>>> ? /opt/local/bin/gtar: ./Library/Application Support/com.apple.TCC: 
>>> Warning: Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Autosave Information: 
>>> Warning: Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/PersonalizationPortrait: 
>>> Warning: Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Reminders: Warning: Cannot 
>>> open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Safari: Warning: Cannot open: 
>>> Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Sharing: Warning: Cannot 
>>> open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Suggestions: Warning: Cannot 
>>> open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
>>> Support/AddressBook: Warning: Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
>>> Support/CallHistoryDB: Warning: Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
>>> Support/CallHistoryTransactions: Warning: Cannot open: Operation not 
>>> permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
>>> Support/FileProvider: Warning: Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
>>> Support/com.apple.TCC: Warning: Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
>>> Support/com.apple.sharedfilelist: Warning: Cannot open: Operation not 
>>> permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Caches/CloudKit: Warning: 
>>> Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Caches/com.apple.Safari: 
>>> Warning: Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: 
>>> ./Users/heller/Library/Caches/com.apple.ap.adprivacyd: Warning: Cannot 
>>> open: Operation not permitted
>>> ? /opt/local/bin/gtar: 
>>> ./Users/heller/Library/Containers/com.apple.CloudDocs.MobileDocumentsFileProvider:
>>>  Warning: Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: ./Users/heller/Library/Containers/com.apple.Safari: 
>>> Warning: Cannot open: Operation not permitted
>>> ? /opt/local/bin/gtar: 
>>> ./Users/heller/Library/Containers/com.apple

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Robert Heller]

It already is there.

At Thu, 8 Jun 2023 08:31:15 -0600 Pieter Bowman  wrote:

> 
> Unfortunately, I have retired, so don't have access to systems running 
> amanda on macOS/MacOSX.
> 
> However, I can suggest that the problem you are seeing is because of 
> System Integrity Protection (SIP). You will need to add the executable 
> amandad to System Settings -> Privacy & Security -> Full Disk Access.
> 
> Pieter
> 
> On 6/7/23 5:43 AM, Robert Heller wrote:
> > Is there some "trick" to getting Amanda (3.5.1) to run properly under MacOSX
> > 10.15?  I recently added a new (to me) machine to my LAN and want to be able
> > to take regular backups of it.  I is an older model MacBook Pro (mid 2012
> > vintage), running Amanda (3.5.1) to run properly under MacOSX 10.15 (the 
> > last
> > version of MacOSX that will run on this machine.  I just plan on using it 
> > as a
> > "build box", compiling my Open Source software.  All of the rest of my
> > machines, consisting on one AMD (x86_64) desktop (running Ubuntu 22.04 LTS)
> > and an assortment of ARM SBCs (Raspberry Pis, Banana Pis, etc.) all running
> > Debian 10 and they all run Amanda (3.5.1) and Amanda is working fine backing
> > up all of these machines.  I'd like to add the MacBook Pro.  I built Amanda
> > 3.5.1 from source on the MacBook Pro and installed it under /usr/local, but
> > Amanda has been "failing" on the MacBook Pro every night for about a week.
> >
> > Here is the error log:
> >
> > sendbackup: start [pipin:/System/Volumes/Data level 0]
> > sendbackup: info BACKUP=/opt/local/bin/gtar
> > sendbackup: info RECOVER_CMD=/opt/local/bin/gtar -xpGf - ...
> > sendbackup: info end
> > ? /opt/local/bin/gtar: ./Library/Application Support/com.apple.TCC: 
> > Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Autosave Information: 
> > Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/PersonalizationPortrait: 
> > Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Reminders: Warning: Cannot 
> > open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Safari: Warning: Cannot open: 
> > Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Sharing: Warning: Cannot 
> > open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Suggestions: Warning: Cannot 
> > open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> > Support/AddressBook: Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> > Support/CallHistoryDB: Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> > Support/CallHistoryTransactions: Warning: Cannot open: Operation not 
> > permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> > Support/FileProvider: Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> > Support/com.apple.TCC: Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Application 
> > Support/com.apple.sharedfilelist: Warning: Cannot open: Operation not 
> > permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Caches/CloudKit: Warning: 
> > Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Caches/com.apple.Safari: 
> > Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: 
> > ./Users/heller/Library/Caches/com.apple.ap.adprivacyd: Warning: Cannot 
> > open: Operation not permitted
> > ? /opt/local/bin/gtar: 
> > ./Users/heller/Library/Containers/com.apple.CloudDocs.MobileDocumentsFileProvider:
> >  Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Containers/com.apple.Safari: 
> > Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: 
> > ./Users/heller/Library/Containers/com.apple.archiveutility: Warning: Cannot 
> > open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Library/Metadata/CoreSpotlight: 
> > Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/heller/Pictures/Photos 
> > Library.photoslibrary: Warning: Cannot open: Operation not permitted
> > ? /opt/local/bin/gtar: ./Users/jaffe/Desktop: Warning: Cannot open: 
> > Operation no

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Exuvo]

-- resend as i forgot reply all --

Those errors seem like normal permission errors, if you su to amanda can you 
access those files?
If not i think you need to edit amanda-security.conf and uncomment some of the 
tar lines so tar runs as root with access to the files you want to backup.

Anton "exuvo" Olsson
ex...@exuvo.se

On 2023-06-07 13:43, Robert Heller wrote:

Is there some "trick" to getting Amanda (3.5.1) to run properly under MacOSX
10.15?  I recently added a new (to me) machine to my LAN and want to be able
to take regular backups of it.  I is an older model MacBook Pro (mid 2012
vintage), running Amanda (3.5.1) to run properly under MacOSX 10.15 (the last
version of MacOSX that will run on this machine.  I just plan on using it as a
"build box", compiling my Open Source software.  All of the rest of my
machines, consisting on one AMD (x86_64) desktop (running Ubuntu 22.04 LTS)
and an assortment of ARM SBCs (Raspberry Pis, Banana Pis, etc.) all running
Debian 10 and they all run Amanda (3.5.1) and Amanda is working fine backing
up all of these machines.  I'd like to add the MacBook Pro.  I built Amanda
3.5.1 from source on the MacBook Pro and installed it under /usr/local, but
Amanda has been "failing" on the MacBook Pro every night for about a week.

Here is the error log:

sendbackup: start [pipin:/System/Volumes/Data level 0]
sendbackup: info BACKUP=/opt/local/bin/gtar
sendbackup: info RECOVER_CMD=/opt/local/bin/gtar -xpGf - ...
sendbackup: info end
? /opt/local/bin/gtar: ./Library/Application Support/com.apple.TCC: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Autosave Information: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/PersonalizationPortrait: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Reminders: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Safari: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Sharing: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Suggestions: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application Support/AddressBook: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/CallHistoryDB: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/CallHistoryTransactions: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application Support/FileProvider: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/com.apple.TCC: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/com.apple.sharedfilelist: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Caches/CloudKit: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Caches/com.apple.Safari: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Caches/com.apple.ap.adprivacyd: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: 
./Users/heller/Library/Containers/com.apple.CloudDocs.MobileDocumentsFileProvider:
 Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Containers/com.apple.Safari: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: 
./Users/heller/Library/Containers/com.apple.archiveutility: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Metadata/CoreSpotlight: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Pictures/Photos Library.photoslibrary: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Desktop: Warning: Cannot open: Operation 
not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Documents: Warning: Cannot open: Operation 
not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Downloads: Warning: Cannot open: Operation 
not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Calendars: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Cookies: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/HomeKit: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/IdentityServices: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Mail: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Messages: Warning: Cannot open: 
Operation not permitted

Re: Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Exuvo]

-- resend as i forgot reply all --

Oh also check that the relevant executables have SGID bit set and correct users 
(user root, group amanda). Mine is under /usr/lib/amanda/application/amgtar but 
probably different location for you.
I have SGID set for amgtar ambsdtar amstar in that directory.
In /usr/lib/amanda/application/ the following has SGID to root set: ambind 
calcsize killpgrp rundump runtar.

Anton "exuvo" Olsson
ex...@exuvo.se

On 2023-06-07 21:53, Exuvo wrote:

Those errors seem like normal permission errors, if you su to amanda can you 
access those files?
If not i think you need to edit amanda-security.conf and uncomment some of the 
tar lines so tar runs as root with access to the files you want to backup.

Anton "exuvo" Olsson
    ex...@exuvo.se

On 2023-06-07 13:43, Robert Heller wrote:

Is there some "trick" to getting Amanda (3.5.1) to run properly under MacOSX
10.15?  I recently added a new (to me) machine to my LAN and want to be able
to take regular backups of it.  I is an older model MacBook Pro (mid 2012
vintage), running Amanda (3.5.1) to run properly under MacOSX 10.15 (the last
version of MacOSX that will run on this machine.  I just plan on using it as a
"build box", compiling my Open Source software.  All of the rest of my
machines, consisting on one AMD (x86_64) desktop (running Ubuntu 22.04 LTS)
and an assortment of ARM SBCs (Raspberry Pis, Banana Pis, etc.) all running
Debian 10 and they all run Amanda (3.5.1) and Amanda is working fine backing
up all of these machines.  I'd like to add the MacBook Pro.  I built Amanda
3.5.1 from source on the MacBook Pro and installed it under /usr/local, but
Amanda has been "failing" on the MacBook Pro every night for about a week.

Here is the error log:

sendbackup: start [pipin:/System/Volumes/Data level 0]
sendbackup: info BACKUP=/opt/local/bin/gtar
sendbackup: info RECOVER_CMD=/opt/local/bin/gtar -xpGf - ...
sendbackup: info end
? /opt/local/bin/gtar: ./Library/Application Support/com.apple.TCC: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Autosave Information: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/PersonalizationPortrait: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Reminders: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Safari: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Sharing: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Suggestions: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application Support/AddressBook: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/CallHistoryDB: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/CallHistoryTransactions: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application Support/FileProvider: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/com.apple.TCC: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/com.apple.sharedfilelist: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Caches/CloudKit: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Caches/com.apple.Safari: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Caches/com.apple.ap.adprivacyd: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: 
./Users/heller/Library/Containers/com.apple.CloudDocs.MobileDocumentsFileProvider:
 Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Containers/com.apple.Safari: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: 
./Users/heller/Library/Containers/com.apple.archiveutility: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Metadata/CoreSpotlight: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Pictures/Photos Library.photoslibrary: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Desktop: Warning: Cannot open: Operation 
not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Documents: Warning: Cannot open: Operation 
not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Downloads: Warning: Cannot open: Operation 
not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Calendars: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Cookies: Warning: Cann

Getting Amanda (3.5.1) to run properly under MacOSX 10.15

[Robert Heller]

Is there some "trick" to getting Amanda (3.5.1) to run properly under MacOSX 
10.15?  I recently added a new (to me) machine to my LAN and want to be able 
to take regular backups of it.  I is an older model MacBook Pro (mid 2012 
vintage), running Amanda (3.5.1) to run properly under MacOSX 10.15 (the last 
version of MacOSX that will run on this machine.  I just plan on using it as a 
"build box", compiling my Open Source software.  All of the rest of my 
machines, consisting on one AMD (x86_64) desktop (running Ubuntu 22.04 LTS) 
and an assortment of ARM SBCs (Raspberry Pis, Banana Pis, etc.) all running 
Debian 10 and they all run Amanda (3.5.1) and Amanda is working fine backing 
up all of these machines.  I'd like to add the MacBook Pro.  I built Amanda 
3.5.1 from source on the MacBook Pro and installed it under /usr/local, but 
Amanda has been "failing" on the MacBook Pro every night for about a week.

Here is the error log:

sendbackup: start [pipin:/System/Volumes/Data level 0]
sendbackup: info BACKUP=/opt/local/bin/gtar
sendbackup: info RECOVER_CMD=/opt/local/bin/gtar -xpGf - ...
sendbackup: info end
? /opt/local/bin/gtar: ./Library/Application Support/com.apple.TCC: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Autosave Information: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/PersonalizationPortrait: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Reminders: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Safari: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Sharing: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Suggestions: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application Support/AddressBook: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/CallHistoryDB: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/CallHistoryTransactions: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application Support/FileProvider: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/com.apple.TCC: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Application 
Support/com.apple.sharedfilelist: Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Caches/CloudKit: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Caches/com.apple.Safari: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Caches/com.apple.ap.adprivacyd: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: 
./Users/heller/Library/Containers/com.apple.CloudDocs.MobileDocumentsFileProvider:
 Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Containers/com.apple.Safari: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: 
./Users/heller/Library/Containers/com.apple.archiveutility: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Library/Metadata/CoreSpotlight: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/heller/Pictures/Photos Library.photoslibrary: 
Warning: Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Desktop: Warning: Cannot open: Operation 
not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Documents: Warning: Cannot open: Operation 
not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Downloads: Warning: Cannot open: Operation 
not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Calendars: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Cookies: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/HomeKit: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/IdentityServices: Warning: Cannot 
open: Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Mail: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Messages: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/PersonalizationPortrait: Warning: 
Cannot open: Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Reminders: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Safari: Warning: Cannot open: 
Operation not permitted
? /opt/local/bin/gtar: ./Users/jaffe/Library/Sharing: Warning: Ca

Re: amanda-3.5.3 problems

[Exuvo]

The empty man pages is because someone forgot to build the man pages when 
making the rest of the package.

Anton "exuvo" Olsson
   ex...@exuvo.se

On 2023-04-28 15:44, Nuno Dias wrote:

  Hi,

  After upgrading amanda from amanda-3.5.1 to amanda-3.5.3 using the rpm
from Fedora, I have this 2 problems, every man page of amanda is empty

for example ...
-
$ man amanda.conf

DUMMY

  Manual page amanda.conf(5) line 1/2 (END) (press h for help or q to
quit)
--

  The other problem is, if I use a disk as tape, every run of amdump
will fail after backup the first machine/disk in disklist, with this
error

x:/y   20230428141427 131m dump to tape done
x://   20230428141427 0  6244m terminated while
waiting for dumping

  The mail saying

FAIL driver xx //z 20230428141220 0 [can't do degraded dump
without holding disk]

  Downgrading to the previous version, this problems will not happen.

  The last problem do not happens if the tape is a real tape not a disk!

  I tested in Fedora 36 and Fedora 37 with the same results.

  My question is, anyone has this problems?

Thanks,
Nuno

amanda-3.5.3 problems

[Nuno Dias]

 Hi,

 After upgrading amanda from amanda-3.5.1 to amanda-3.5.3 using the rpm
from Fedora, I have this 2 problems, every man page of amanda is empty

for example ...
-
$ man amanda.conf

DUMMY

 Manual page amanda.conf(5) line 1/2 (END) (press h for help or q to
quit)
--

 The other problem is, if I use a disk as tape, every run of amdump 
will fail after backup the first machine/disk in disklist, with this
error

x:/y   20230428141427 131m dump to tape done 
x://   20230428141427 0  6244m terminated while
waiting for dumping

 The mail saying

FAIL driver xx //z 20230428141220 0 [can't do degraded dump
without holding disk]

 Downgrading to the previous version, this problems will not happen.

 The last problem do not happens if the tape is a real tape not a disk!

 I tested in Fedora 36 and Fedora 37 with the same results.

 My question is, anyone has this problems? 

Thanks,
Nuno
-- 
Nuno Dias 
LIP

Re: Amanda is crashing on [runtar invalid option: -]

[Jens Berg]

On 23.03.2023 14:47, Charles Curley wrote:

   #   property "CHECK-DEVICE" "YES"


If you have DLEs on external (USB) drives I strongly recommend to set 
this to "NO".
The property translates to the --check-device option of tar (on by 
default) what makes tar consider the device number when creating 
incremental archives. As that number might change on reboot you'll see 
in that case a full backup of all DLEs on a particular disk even though 
the data is unchanged.

Re: Amanda is crashing on [runtar invalid option: -]

[Olivier]

Nathan Stratton Treadway  writes:

>  I have had Amanda running for over a decade, yesterday I had no issue at
>  all but last night, my backups for Ubuntu machines started crashing
>  consistently with the error:
>  strange(?): runtar: error [runtar invalid option: -]
>
> The just-released amanda package upgrade seems to have a regression for
> GNUTAR DLEs; see:
> https://bugs.launchpad.net/debian/+source/amanda/+bug/2012536/

Thank you Nathan, that did the trick.

Now I have to understand what did the upgrade, these servers have no
automatic upgrade. But that is not and Amanda problem.

Olivier

Re: Amanda is crashing on [runtar invalid option: -]

[Charles Curley]

On Thu, 23 Mar 2023 13:02:33 +0700
Olivier  wrote:

> I have had Amanda running for over a decade,

I have also been running Amanda for a long time. When I implemented the
proposed work-around, I found I had no definition of amgtar.

Is there a preferred canonical (no wordplay intended) definition,
perhaps from more recent versions of Amanda?

After much digging around on the net, man pages, etc., here is what I
added to my amanda.conf. This may be useful to other folks.

--
# from the man page for amgtar

  # define application-tool app_amgtar {
  #   plugin "amgtar"
  #   property "ATIME-PRESERVE" "NO"
  #   property "CHECK-DEVICE" "YES"
  #   # property "GNUTAR-LISTDIR" "/path/to/listdir"
  #   # property "GNUTAR-PATH" "/bin/tar"
  #   property "GNUTAR-PATH" "/usr/bin/tar"
  #   property "ONE-FILE-SYSTEM" "YES"
  #   property "TAR-BLOCKSIZE" "20"
  #   property "SPARSE" "YES"
  #   property "ACLS" "NO"
  #   property "SELINUX" "NO"
  #   property "XATTRS" "NO"
  #   property "EXIT-HANDLING" "1=GOOD 2=BAD"
  #   # change a default NORMAL regex to a STRANGE regex.
  #   property "STRANGE" ": socket ignored$"
  #   # add three new IGNORE regex
  #   property append "IGNORE" ": Directory has been renamed"
  #   property append "IGNORE" "file changed as we read it$"
  # }

#define application-tool and dumptype for the amgtar application
define application-tool app_amgtar {
comment "amgtar"
plugin  "amgtar"
property "GNUTAR-PATH" "/usr/bin/tar"
#property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir"
#default from gnutar_list_dir setting in amanda-client.conf
}

--

A typical dumptype now looks like:

--

define dumptype root-tar {
global
# program "GNUTAR"
program "APPLICATION"
application "app_amgtar" # per 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032330
comment "root partitions dumped with tar"
compress none
priority low
index yes
}

--

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Amanda is crashing on [runtar invalid option: -]

[Nathan Stratton Treadway]

On Thu, Mar 23, 2023 at 2:07 AM Olivier  wrote:

> Hello,
>
> I have had Amanda running for over a decade, yesterday I had no issue at
> all but last night, my backups for Ubuntu machines started crashing
> consistently with the error:
> strange(?): runtar: error [runtar invalid option: -]
>

The just-released amanda package upgrade seems to have a regression for
GNUTAR DLEs; see:
https://bugs.launchpad.net/debian/+source/amanda/+bug/2012536/

Nathan

Amanda is crashing on [runtar invalid option: -]

[Olivier]

Hello,

I have had Amanda running for over a decade, yesterday I had no issue at
all but last night, my backups for Ubuntu machines started crashing
consistently with the error:
strange(?): runtar: error [runtar invalid option: -]

That even happens on a machine that is currently unused.

The sendbackup.debug:
Thu Mar 23 12:42:52.540023056 2023: pid 176238: thd-0x55a338876200: sendbackup: 
pid 176238 ruid 34 euid 34 version 3.5.1: start at Thu Mar 23 12:42:52 2023
Thu Mar 23 12:42:52.540038593 2023: pid 176238: thd-0x55a338876200: sendbackup: 
Version 3.5.1
Thu Mar 23 12:42:52.540203704 2023: pid 176238: thd-0x55a338876200: sendbackup: 
pid 176238 ruid 34 euid 34 version 3.5.1: rename at Thu Mar 23 12:42:52 2023
Thu Mar 23 12:42:52.540260443 2023: pid 176238: thd-0x55a338876200: sendbackup: 
  Parsed request as: program `GNUTAR'
Thu Mar 23 12:42:52.540265622 2023: pid 176238: thd-0x55a338876200: sendbackup: 
 disk `/home2/docker/volumes'
Thu Mar 23 12:42:52.540268838 2023: pid 176238: thd-0x55a338876200: sendbackup: 
 device `/home2/docker/volumes'
Thu Mar 23 12:42:52.540271771 2023: pid 176238: thd-0x55a338876200: sendbackup: 
 level 1
Thu Mar 23 12:42:52.540274728 2023: pid 176238: thd-0x55a338876200: sendbackup: 
 since NODATE
Thu Mar 23 12:42:52.540277637 2023: pid 176238: thd-0x55a338876200: sendbackup: 
 options `'
Thu Mar 23 12:42:52.540280674 2023: pid 176238: thd-0x55a338876200: sendbackup: 
     datapath `AMANDA'
Thu Mar 23 12:42:52.540314487 2023: pid 176238: thd-0x55a338876200: sendbackup: 
start: guppy1000:/home2/docker/volumes lev 1
Thu Mar 23 12:42:52.540326715 2023: pid 176238: thd-0x55a338876200: sendbackup: 
Spawning "/bin/gzip /bin/gzip --best" in pipeline
Thu Mar 23 12:42:52.540482259 2023: pid 176238: thd-0x55a338876200: sendbackup: 
gnutar: pid 176240: /bin/gzipThu Mar 23 12:42:52.540495845 2023: pid 176238: 
thd-0x55a338876200: sendbackup: pid 176240: /bin/gzip --best
Thu Mar 23 12:42:52.540532571 2023: pid 176238: thd-0x55a338876200: sendbackup: 
doing level 1 dump as listed-incremental from 
'/var/lib/amanda/gnutar-lists/guppy1000_home2_docker_volumes_0' to 
'/var/lib/amanda/gnutar-lists/guppy1000_home2_docker_volumes_1.new'
Thu Mar 23 12:42:52.541308063 2023: pid 176238: thd-0x55a338876200: sendbackup: 
Spawning "/usr/lib/amanda/runtar runtar normal /bin/tar --create --file - 
--directory /home2/docker/volumes --one-file-system --listed-incremental 
/var/lib/amanda/gnutar-lists/guppy1000_home2_docker_volumes_1.new --sparse 
--ignore-failed-read --totals ." in pipeline
Thu Mar 23 12:42:52.541356931 2023: pid 176241: thd-0x55a338876200: sendbackup: 
Dupped file descriptor 3 to 11
Thu Mar 23 12:42:52.541474547 2023: pid 176238: thd-0x55a338876200: sendbackup: 
gnutar: /usr/lib/amanda/runtar: pid 176242
Thu Mar 23 12:42:52.541498736 2023: pid 176238: thd-0x55a338876200: sendbackup: 
shm_ring_link /amanda_shm_control-176237-0
Thu Mar 23 12:42:52.541535955 2023: pid 176238: thd-0x55a338876200: sendbackup: 
am_sem_open 0x7f67cb7e6000 1
Thu Mar 23 12:42:52.541546592 2023: pid 176238: thd-0x55a338876200: sendbackup: 
am_sem_open 0x7f67cb7e5000 1
Thu Mar 23 12:42:52.541553997 2023: pid 176238: thd-0x55a338876200: sendbackup: 
am_sem_open 0x7f67cb7e4000 1
Thu Mar 23 12:42:52.541561135 2023: pid 176238: thd-0x55a338876200: sendbackup: 
am_sem_open 0x7f67cb7e3000 1
Thu Mar 23 12:42:52.541565219 2023: pid 176238: thd-0x55a338876200: sendbackup: 
shm_ring_producer_set_size
Thu Mar 23 12:42:52.542263918 2023: pid 176241: thd-0x55a338876200: sendbackup: 
Started index creator: "/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'"
Thu Mar 23 12:42:52.544787802 2023: pid 176238: thd-0x55a338876200: sendbackup: 
Started backup
Thu Mar 23 12:42:52.544826375 2023: pid 176238: thd-0x55a338887060: sendbackup: 
fd_to_shm_ring
Thu Mar 23 12:42:52.548988463 2023: pid 176238: thd-0x55a338876200: sendbackup: 
119: strange(?): runtar: error [runtar invalid option: -]
Thu Mar 23 12:42:52.549723621 2023: pid 176241: thd-0x55a338876200: sendbackup: 
Index created successfully
Thu Mar 23 12:42:53.550073702 2023: pid 176238: thd-0x55a338876200: sendbackup: 
critical (fatal): error [no backup size line]
/usr/lib/x86_64-linux-gnu/amanda/libamanda-3.5.1.so(+0x39067)[0x7f67cb820067]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_logv+0x21c)[0x7f67cb70355c]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log+0x93)[0x7f67cb703743]
/usr/lib/amanda/sendbackup(parse_backup_messages+0x46f)[0x55a33859273f]
/usr/lib/amanda/sendbackup(main+0x1332)[0x55a33858f512]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7f67cb4b9083]
/usr/lib/amanda/sendbackup(_start+0x2e)[0x55a338590d8e]

Note that the sendsize is fine.

Thank for any idea on what I should look for.

Best regards,

Olivier

Amanda Mailing List Troubles

[kovert]

On March 12, I moved the home of the mailing lists (behind the
scenes) and messed up one of the steps, so mail in past few days to the
amanda lists ended up being silently blackholed.  I've corrected this
and adjusted my procedures so it won't happen again and it this or other
problems would be caught sooner.

if you were waiting for a message to show up and it didn't, please resend.

My apologies for the inconvenience.

-Todd

Re: 2 CVEs in amanda-3.5.1

[Stefan G. Weichinger]

Am 22.01.23 um 09:25 schrieb Stefan G. Weichinger:


Just in case this hasn't yet been noticed by anyone upstream:

https://github.com/MaherAzzouzi/CVE-2022-37704

https://github.com/MaherAzzouzi/CVE-2022-37705

https://github.com/zmanda/amanda/issues/192


PRs on their way, as it seems:

https://github.com/zmanda/amanda/pull/197

https://github.com/zmanda/amanda/pull/198


I asked for distro packages, read this:

https://github.com/zmanda/amanda/issues/192#issuecomment-1427097294

Maybe it helps to cheer for the packages there (vote/like/ask there?).

2 CVEs in amanda-3.5.1

[Stefan G. Weichinger]

Just in case this hasn't yet been noticed by anyone upstream:

https://github.com/MaherAzzouzi/CVE-2022-37704

https://github.com/MaherAzzouzi/CVE-2022-37705

https://github.com/zmanda/amanda/issues/192

Re: Degraded dump in amanda 3.5.2

[Stefan G. Weichinger]

Am 18.01.23 um 14:09 schrieb Pablo Venini:

This is the amanda.conf

org "monitoreo10_diario"    # your organization name for 
reports

dumpuser "amandabackup" # the user to run dumps under
mailto "xxx...@y.zz"    # space separated list of operators at 
your site

dumpcycle 1week # the number of days in the normal dump cycle
tapecycle 8 # the number of tapes in rotation
runspercycle 7  # the number of amdump runs in dumpcycle days

define changer my_vtapes {
     tpchanger "chg-disk:/backups/amanda/vtape/diarios/monitoreo10_diario/"
     property "num-slot" "8"
     property "auto-create-slot" "yes"
}
dtimeout 1800   # number of idle seconds before a dump is aborted
ctimeout 30 # max number of secconds amcheck waits for each client
etimeout 300    # number of seconds per filesystem for estimates
define dumptype global {
    comment "Global definitions"
    auth "bsdtcp"
}
define dumptype gui-base {
    global
    program "GNUTAR"
    comment "gui base dumptype dumped with tar"
    compress none
    index yes
}
define tapetype HARDDISK {
    comment "Virtual Tapes"
    length 5 gbytes
}

define policy monitoreo10_diario {
     retention-tapes   7
     retention-days    0
     retention-recover 0
     retention-full    0
}

define storage monitoreo10_diario {
     policy "monitoreo10_diario" # the policy
     tapepool "monitoreo10_diario"   # the tape-pool
     tpchanger "my_vtapes"   # the changer
     runtapes 1  # number of tapes to be used in a single run of 
amdump

     tapetype "HARDDISK" # what kind of tape it is
     labelstr "monitoreo10_diario"   # label constraint regex: all 
tapes must match

     #autolabel
     #meta-autolabel
     taperscan "traditional"
     #max-dle-volume 100
     #taperalgo first
     #taper-parallel-write 1
}
storage "monitoreo10_diario"


Nothing stands out here.


includefile "advanced.conf"
includefile "/etc/amanda/template.d/dumptypes"
includefile "/etc/amanda/template.d/tapetypes"


What's in there? Maybe something crossfiring?

Maybe you also post the output of:

amadmin yourconf config

so we can see what is interpreted by amanda.

And try 3.5.1 maybe. I think noone knows about the bugs of 3.5.2 yet.

Re: Degraded dump in amanda 3.5.2

[Stefan G. Weichinger]

Am 18.01.23 um 14:12 schrieb Pablo Venini:
Yes, I was also thinking about installing 3.5.1; I installed 3.5.2 from 
RPM so I thought it was ok (I was reinstalling an old server wich ran 
3.3.9).


I tried your suggestion and if I run amdump for each DLE, the dumps are ok


Why don't you just set up a small holding disk?

I understand the intention to make it work without but I don't see the 
advantage of doing so.


Amanda is designed to use a holding disk, it's just recommended and best 
practice ;-)

Re: Degraded dump in amanda 3.5.2

[Pablo Venini]

Yes, I was also thinking about installing 3.5.1; I installed 3.5.2 from 
RPM so I thought it was ok (I was reinstalling an old server wich ran 
3.3.9).


I tried your suggestion and if I run amdump for each DLE, the dumps are ok


El 18/1/2023 a las 06:23, Stefan G. Weichinger escribió:

Am 18.01.23 um 01:47 schrieb Pablo Venini:
Hi Stefan, sorry for the delay in answering. This is a backup of the 
amanda server itself (configs, etc.), there is less than 100MB of 
information. What worries me is that if I use a holding disk without 
correcting the problem the dumps will go there instead of going to 
the vtapes.


Did you also test this config with amanda-3.5.1? 3.5.2 is rather 
untested, I think, as there are still no official packages available 
afaik.


I would define a small holding disk and see if that helps ... just for 
debug purposes. A vtape-setup also benefits from a holding disk, no 
reason to not use that with virtual tapes.


What if you only dump specific DLEs?

amdump myconf /etc

Re: Degraded dump in amanda 3.5.2

[Pablo Venini]

This is the amanda.conf

org "monitoreo10_diario"    # your organization name for reports
dumpuser "amandabackup" # the user to run dumps under
mailto "xxx...@y.zz"    # space separated list of operators at 
your site

dumpcycle 1week # the number of days in the normal dump cycle
tapecycle 8 # the number of tapes in rotation
runspercycle 7  # the number of amdump runs in dumpcycle days

define changer my_vtapes {
    tpchanger "chg-disk:/backups/amanda/vtape/diarios/monitoreo10_diario/"
    property "num-slot" "8"
    property "auto-create-slot" "yes"
}
dtimeout 1800   # number of idle seconds before a dump is aborted
ctimeout 30 # max number of secconds amcheck waits for each client
etimeout 300    # number of seconds per filesystem for estimates
define dumptype global {
   comment "Global definitions"
   auth "bsdtcp"
}
define dumptype gui-base {
   global
   program "GNUTAR"
   comment "gui base dumptype dumped with tar"
   compress none
   index yes
}
define tapetype HARDDISK {
   comment "Virtual Tapes"
   length 5 gbytes
}

define policy monitoreo10_diario {
    retention-tapes   7
    retention-days    0
    retention-recover 0
    retention-full    0
}

define storage monitoreo10_diario {
    policy "monitoreo10_diario" # the policy
    tapepool "monitoreo10_diario"   # the tape-pool
    tpchanger "my_vtapes"   # the changer
    runtapes 1  # number of tapes to be used in a single run of 
amdump

    tapetype "HARDDISK" # what kind of tape it is
    labelstr "monitoreo10_diario"   # label constraint regex: all 
tapes must match

    #autolabel
    #meta-autolabel
    taperscan "traditional"
    #max-dle-volume 100
    #taperalgo first
    #taper-parallel-write 1
}
storage "monitoreo10_diario"

includefile "advanced.conf"
includefile "/etc/amanda/template.d/dumptypes"
includefile "/etc/amanda/template.d/tapetypes"


El 18/1/2023 a las 06:19, Stefan G. Weichinger escribió:

Am 18.01.23 um 01:43 schrieb Pablo Venini:
Hi Nathan, do you know if there is any setting to cause amanda to be 
more verbose?


Another weird thing is that the report says:

NOTES:
   planner: tapecycle (7) <= runspercycle (7)

However the config is like this:

tapecycle 8 # the number of tapes in rotation
runspercycle 7  # the number of amdump runs in dumpcycle days

the value reported for tapecycle is different than the one configured.


Maybe you show your amanda.conf for a start. This sounds wrong, yes.

Re: Degraded dump in amanda 3.5.2

[Stefan G. Weichinger]

Am 18.01.23 um 01:47 schrieb Pablo Venini:
Hi Stefan, sorry for the delay in answering. This is a backup of the 
amanda server itself (configs, etc.), there is less than 100MB of 
information. What worries me is that if I use a holding disk without 
correcting the problem the dumps will go there instead of going to the 
vtapes.


Did you also test this config with amanda-3.5.1? 3.5.2 is rather 
untested, I think, as there are still no official packages available afaik.


I would define a small holding disk and see if that helps ... just for 
debug purposes. A vtape-setup also benefits from a holding disk, no 
reason to not use that with virtual tapes.


What if you only dump specific DLEs?

amdump myconf /etc

Re: Degraded dump in amanda 3.5.2

[Stefan G. Weichinger]

Am 18.01.23 um 01:43 schrieb Pablo Venini:
Hi Nathan, do you know if there is any setting to cause amanda to be 
more verbose?


Another weird thing is that the report says:

NOTES:
   planner: tapecycle (7) <= runspercycle (7)

However the config is like this:

tapecycle 8 # the number of tapes in rotation
runspercycle 7  # the number of amdump runs in dumpcycle days

the value reported for tapecycle is different than the one configured.


Maybe you show your amanda.conf for a start. This sounds wrong, yes.

Re: Degraded dump in amanda 3.5.2

[Pablo Venini]

Hi Stefan, sorry for the delay in answering. This is a backup of the 
amanda server itself (configs, etc.), there is less than 100MB of 
information. What worries me is that if I use a holding disk without 
correcting the problem the dumps will go there instead of going to the 
vtapes.


Pablo


El 5/1/2023 a las 08:06, Stefan G. Weichinger escribió:

Am 30.12.22 um 15:34 schrieb Pablo Venini:

Hi Nathan,

 no, (as far as I'm aware) I'm not using a 
holding disk as this is a vtape backup, the dumptype is as follows:


You could fix that by defining and using a holding disk.

Then a "degraded mode backup" should work.

The question is "why does it go into degraded mode" ?

I only quickly scan your config:

* your tapetype defines a tape with 5 GB

Would your DLEs each fit onto one vtape?

I think you should use a larger vtape ... and make sure that the full 
backup of each DLE fits onto one vtape.


A holding disk wouldn't hurt also: speed up things etc

Re: Degraded dump in amanda 3.5.2

[Pablo Venini]

Hi Nathan, do you know if there is any setting to cause amanda to be 
more verbose?


Another weird thing is that the report says:

NOTES:
  planner: tapecycle (7) <= runspercycle (7)

However the config is like this:

tapecycle 8 # the number of tapes in rotation
runspercycle 7  # the number of amdump runs in dumpcycle days

the value reported for tapecycle is different than the one configured.

Pablo



El 7/1/2023 a las 15:24, Nathan Stratton Treadway escribió:

On Fri, Dec 30, 2022 at 11:34:14 -0300, Pablo Venini wrote:

amcheck doesn't report errors

Hmmm.

As Stefan said, the key question is why Amanda is going into degraded
mode.  Normally when I have that happen it's because the target tape
wasn't available at the start of the amdump run, but that doesn't seem
to be the situation in your case.

But it seems like buried somewhere in your logs should be some futher
explanation of why Amanda is switching to degraded mode (apparently
mid-run)

Nathan




Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
  GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
  Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Re: Degraded dump in amanda 3.5.2

[Nathan Stratton Treadway]

On Fri, Dec 30, 2022 at 11:34:14 -0300, Pablo Venini wrote:
> amcheck doesn't report errors

Hmmm.

As Stefan said, the key question is why Amanda is going into degraded
mode.  Normally when I have that happen it's because the target tape
wasn't available at the start of the amdump run, but that doesn't seem
to be the situation in your case.

But it seems like buried somewhere in your logs should be some futher
explanation of why Amanda is switching to degraded mode (apparently
mid-run)

Nathan




Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Re: Degraded dump in amanda 3.5.2

[Kees Meijs | Nefos]

Hi,

On 05-01-2023 12:06, Stefan G. Weichinger wrote:

* your tapetype defines a tape with 5 GB

Would your DLEs each fit onto one vtape?

I think you should use a larger vtape ... and make sure that the full 
backup of each DLE fits onto one vtape.


Please note the length of vtapes is only used for the planner, not for 
the actual flushing (or direct dumping if a holding disk is not used).


Stefan is correct however: this length should still be enough (for the 
planner) for your largest DLE to fit in, given expected compression. It 
doesn't matter if the cumulative of all DLEs is a lot larger.


Cheers,
Kes

Re: Degraded dump in amanda 3.5.2

[Stefan G. Weichinger]

Am 30.12.22 um 15:34 schrieb Pablo Venini:

Hi Nathan,

     no, (as far as I'm aware) I'm not using a holding 
disk as this is a vtape backup, the dumptype is as follows:


You could fix that by defining and using a holding disk.

Then a "degraded mode backup" should work.

The question is "why does it go into degraded mode" ?

I only quickly scan your config:

* your tapetype defines a tape with 5 GB

Would your DLEs each fit onto one vtape?

I think you should use a larger vtape ... and make sure that the full 
backup of each DLE fits onto one vtape.


A holding disk wouldn't hurt also: speed up things etc

Re: Degraded dump in amanda 3.5.2

[Pablo Venini]

Hi Nathan,

    no, (as far as I'm aware) I'm not using a holding 
disk as this is a vtape backup, the dumptype is as follows:


define dumptype sm-encrypt-compress {
   gui-base
   comment "SM dumptype with compression and encryption"
   compress client fast
   encrypt client
   client_encrypt "/usr/sbin/amcryptsimple"
}


amcheck doesn't report errors


amcheck monitoreo10_diario
Amanda Tape Server Host Check
-
slot 1: volume 'monitoreo10_diario-1' is still active and cannot be 
overwritten

slot 2: volume 'monitoreo10_diario-2'
Will write to volume 'monitoreo10_diario-2' in slot 2.
NOTE: skipping tape-writable test
NOTE: info dir 
'/etc/amanda/monitoreo10_diario/curinfo/..zzz/_usr_libexec_amanda_application' 
does not exist

  it will be created on the next run
NOTE: index dir 
'/etc/amanda/monitoreo10_diario/index/..zzz/_usr_libexec_amanda_application' 
does not exist

  it will be created on the next run
NOTE: info dir 
'/etc/amanda/monitoreo10_diario/curinfo/..zzz/_var_lib_amanda' 
does not exist

  it will be created on the next run
NOTE: index dir 
'/etc/amanda/monitoreo10_diario/index/..zzz/_var_lib_amanda' 
does not exist

  it will be created on the next run
NOTE: info dir 
'/etc/amanda/monitoreo10_diario/curinfo/xxxx..zzz/_etc' does not 
exist

  it will be created on the next run
NOTE: index dir 
'/etc/amanda/monitoreo10_diario/index/..zzz/_etc' does not exist

  it will be created on the next run
Server check took 2.159 seconds
Amanda Backup Client Hosts Check

Client check: 1 host checked in 2.053 seconds.  0 problems found.
(brought to you by Amanda 3.5.2.git.6cec2349)


Pablo


El 29/12/2022 a las 19:33, Nathan Stratton Treadway escribió:

On Thu, Dec 29, 2022 at 17:17:56 -0300, Pablo Venini wrote:

Hi, I'm setting up a new backup server with amanda 3.5.2 on CentOS 7
with vtapes. I've setup the vtapes directories, created the job and
added the dlc, checked permissions, then run amcheck and it shows no
errors. However when I run amdump, only one of the dlc gets backed
up, the other ones give a "can't do degraded dump without holding
disk" error. The config is:

(I take it you are not attempting to configure any holding disk?)

What does "amcheck" report?


Nathan


Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
  GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
  Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Re: Degraded dump in amanda 3.5.2

[Nathan Stratton Treadway]

On Thu, Dec 29, 2022 at 17:17:56 -0300, Pablo Venini wrote:
> Hi, I'm setting up a new backup server with amanda 3.5.2 on CentOS 7
> with vtapes. I've setup the vtapes directories, created the job and
> added the dlc, checked permissions, then run amcheck and it shows no
> errors. However when I run amdump, only one of the dlc gets backed
> up, the other ones give a "can't do degraded dump without holding
> disk" error. The config is:

(I take it you are not attempting to configure any holding disk?)

What does "amcheck" report?


Nathan


Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Degraded dump in amanda 3.5.2

[Pablo Venini]

Hi, I'm setting up a new backup server with amanda 3.5.2 on CentOS 7 
with vtapes. I've setup the vtapes directories, created the job and 
added the dlc, checked permissions, then run amcheck and it shows no 
errors. However when I run amdump, only one of the dlc gets backed up, 
the other ones give a "can't do degraded dump without holding disk" 
error. The config is:


amanda.conf

org "monitoreo10_diario"    # your organization name for 
reports

dumpuser "amandabackup" # the user to run dumps under
mailto "y@x"    # space separated list of operators at your 
site

dumpcycle 1week # the number of days in the normal dump cycle
tapecycle 8 # the number of tapes in rotation
runspercycle 7  # the number of amdump runs in dumpcycle days

define changer my_vtapes {
    tpchanger "chg-disk:/backups/amanda/vtape/diarios/monitoreo10_diario/"
    property "num-slot" "8"
    property "auto-create-slot" "yes"
}
dtimeout 1800   # number of idle seconds before a dump is aborted
ctimeout 30 # max number of secconds amcheck waits for each client
etimeout 300    # number of seconds per filesystem for estimates
define dumptype global {
   comment "Global definitions"
   auth "bsdtcp"
}
define dumptype gui-base {
   global
   program "GNUTAR"
   comment "gui base dumptype dumped with tar"
   compress none
   index yes
}
define tapetype HARDDISK {
   comment "Virtual Tapes"
   length 5000 mbytes
}

define policy monitoreo10_diario {
    retention-tapes   8
    retention-days    0
    retention-recover 0
    retention-full    0
}

define storage monitoreo10_diario {
    policy "monitoreo10_diario" # the policy
    tapepool "monitoreo10_diario"   # the tape-pool
    tpchanger "my_vtapes"   # the changer
    runtapes 1  # number of tapes to be used in a single run of 
amdump

    tapetype "HARDDISK" # what kind of tape it is
    labelstr "monitoreo10_diario"   # label constraint regex: all 
tapes must match

    #autolabel
    #meta-autolabel
    taperscan "traditional"
    #max-dle-volume 100
    #taperalgo first
    #taper-parallel-write 1
}
storage "monitoreo10_diario"

includefile "advanced.conf"
includefile "/etc/amanda/template.d/dumptypes"
includefile "/etc/amanda/template.d/tapetypes"


disklist

zzz.yyy.xx /etc sm-encrypt-compress
zzz.yyy.xx /usr/local/bin sm-encrypt-compress
zzz.yyy.xx /var/lib/amanda sm-encrypt-compress
zzz.yyy.xx /usr/libexec/amanda/application sm-encrypt-compress


logs

ANALYZING ESTIMATES...
pondering zzz.yyy.xx:/usr/libexec/amanda/application... next_level0 
-19335 last_level -1 (due for level 0) (new disk, can't switch to 
degraded mode)
  curr level 0 nsize 300 csize 150 total size 249 total_lev0 150 
balanced-lev0size 21
pondering zzz.yyy.xx:/var/lib/amanda... next_level0 -19335 
last_level -1 (due for level 0) (new disk, can't switch to degraded mode)
  curr level 0 nsize 390 csize 195 total size 477 total_lev0 345 
balanced-lev0size 48
pondering zzz.yyy.xx:/usr/local/bin... next_level0 -19335 last_level 
-1 (due for level 0) (new disk, can't switch to degraded mode)
  curr level 0 nsize 10 csize 5 total size 515 total_lev0 350 
balanced-lev0size 48
pondering zzz.yyy.xx:/etc... next_level0 -19335 last_level -1 (due 
for level 0) (new disk, can't switch to degraded mode)
  curr level 0 nsize 31490 csize 15745 total size 16293 total_lev0 
16095 balanced-lev0size 2297



DUMP zzz.yyy.xx 9efefbfff3fffbf79f00 /etc 
20221208211442 19336 0 1970:1:1:0:0:0 31490 15745 15 1024 "Skipping: new 
disk can't be dumped in degraded mode"
DUMP zzz.yyy.xx 9efefbfff3fffbf79f00 
/var/lib/amanda 20221208211442 19336 0 1970:1:1:0:0:0 390 195 0 1024 
"Skipping: new disk can't be dumped in degraded mode"
DUMP zzz.yyy.xx 9efefbfff3fffbf79f00 
/usr/libexec/amanda/application 20221208211442 19336 0 1970:1:1:0:0:0 
300 150 0 1024 "Skipping: new disk can't be dumped in degraded mode"
DUMP zzz.yyy.xx 9efefbfff3fffbf79f00 
/usr/local/bin 20221208211442 19336 0 1970:1:1:0:0:0 10 5 0 1024 
"Skipping: new disk can't be dumped in degraded mode"



report


FAILURE DUMP SUMMARY:
zzz.yyy.xx /etc lev 0  FAILED [can't do degraded dump without 
holding disk]
zzz.yyy.xx /var/lib/amanda lev 0  FAILED [can't do degraded dump 
without holding disk]
zzz.yyy.xx /usr/libexec/amanda/application lev 0  FAILED [can't do 
degraded dump without holding disk]


DUMP SUMMARY:
                      DUMPER STATS   TAPER STATS
HOSTNAME      

Re: New Amanda Community release 3.5.2 Has Arrived! -- email bounce

[gene heskett]

On 9/30/22 02:32, Stefan G. Weichinger wrote:

Am 29.09.22 um 02:03 schrieb Nathan Stratton Treadway:

On Tue, Sep 13, 2022 at 16:11:15 -0400, Nathan Stratton Treadway wrote:

On Tue, Sep 13, 2022 at 17:29:41 +0200, Stefan G. Weichinger wrote:

I received:

"Your message to chris.hass...@betsol.com couldn't be delivered.

Chris.Hassell wasn't found at betsol.com."


(I just tried sending email to this email address.  My message was
accepted for delivery by the Betsol mail server, and I haven't received
any bounce message back [after waiting a few minutes].  So hopefully 
the

bounce you saw was just a temporary misconfiguration on the Betsol mail
server...(?) )


Ack -- I just discovered that my 9/13 test message did result in a
bounce message after all.  (The bounce message went to my spam
folder.)

I tried again just now, and his email address still bounced.

So it would seem that Chris is indeed no longer at Betsol  :(


Ah, that's bad. So again no more direct upstream contact at Betsol.

Still no packages provided by them for 3.5.2, still no activity at the 
Github-issues, etc etc


Sad.

Let's see who follows.

Thanks for the test, Nathan.

What follows is a four letter word.  fork. The question is how do we pay 
for a continuation of a better way to
do effective backups. And who is to be "in charge". IOW, do we let it 
fade away into the sunset for lack of
adequate support, or do we who have benefited from it, step up to the 
plate and make it a DIY project.


TANSTAAFL is the operative keyword here.  So who gets the bill for lunch?

.



Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: New Amanda Community release 3.5.2 Has Arrived! -- email bounce

[Stefan G. Weichinger]

Am 29.09.22 um 02:03 schrieb Nathan Stratton Treadway:

On Tue, Sep 13, 2022 at 16:11:15 -0400, Nathan Stratton Treadway wrote:

On Tue, Sep 13, 2022 at 17:29:41 +0200, Stefan G. Weichinger wrote:

I received:

"Your message to chris.hass...@betsol.com couldn't be delivered.

Chris.Hassell wasn't found at betsol.com."


(I just tried sending email to this email address.  My message was
accepted for delivery by the Betsol mail server, and I haven't received
any bounce message back [after waiting a few minutes].  So hopefully the
bounce you saw was just a temporary misconfiguration on the Betsol mail
server...(?) )


Ack -- I just discovered that my 9/13 test message did result in a
bounce message after all.  (The bounce message went to my spam
folder.)

I tried again just now, and his email address still bounced.

So it would seem that Chris is indeed no longer at Betsol  :(


Ah, that's bad. So again no more direct upstream contact at Betsol.

Still no packages provided by them for 3.5.2, still no activity at the 
Github-issues, etc etc


Sad.

Let's see who follows.

Thanks for the test, Nathan.

Re: New Amanda Community release 3.5.2 Has Arrived! -- email bounce

[Nathan Stratton Treadway]

On Tue, Sep 13, 2022 at 16:11:15 -0400, Nathan Stratton Treadway wrote:
> On Tue, Sep 13, 2022 at 17:29:41 +0200, Stefan G. Weichinger wrote:
> > I received:
> > 
> > "Your message to chris.hass...@betsol.com couldn't be delivered.
> > 
> > Chris.Hassell wasn't found at betsol.com."
> 
> (I just tried sending email to this email address.  My message was
> accepted for delivery by the Betsol mail server, and I haven't received
> any bounce message back [after waiting a few minutes].  So hopefully the
> bounce you saw was just a temporary misconfiguration on the Betsol mail
> server...(?) )

Ack -- I just discovered that my 9/13 test message did result in a
bounce message after all.  (The bounce message went to my spam
folder.)

I tried again just now, and his email address still bounced.

So it would seem that Chris is indeed no longer at Betsol  :(

Nathan



Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Re: Amanda Community release 3.5.2 - debian test packages

[gene heskett]

On 9/19/22 14:49, Charles Curley wrote:

On Fri, 16 Sep 2022 11:52:18 -0400
gene heskett  wrote:


The first thing I note is the use of port 5000, and I'm wondering
about the possibility of fighting
over the ports as Octoprint uses FQDN:5000 as its web server to
administer its designated 3d printer.

Gene, I don't know where you get port 5000. According to /etc/services,
IANA has assigned amanda ports 10080-10083 inclusive. And amanda uses
those only if you don't run amanda over ssh.

root@hawk:~# grep amanda /etc/services
amanda  10080/tcp       # amanda backup services
kamanda 10081/tcp       # amanda backup services 
(Kerberos)
amandaidx   10082/tcp       # amanda backup services
amidxtape   10083/tcp       # amanda backup services
root@hawk:~#

I got that directly from the download links accompanying propaganda 
page. I thought
it was strange at the time because all I've ever seen is your list 
above, until now.
If that page is in error, it s/b fixed.  Either that, or FF missfired. 
Rare, but it

has happened.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Re: Amanda Community release 3.5.2 - debian test packages

[Charles Curley]

On Fri, 16 Sep 2022 11:52:18 -0400
gene heskett  wrote:

> The first thing I note is the use of port 5000, and I'm wondering
> about the possibility of fighting
> over the ports as Octoprint uses FQDN:5000 as its web server to 
> administer its designated 3d printer.

Gene, I don't know where you get port 5000. According to /etc/services,
IANA has assigned amanda ports 10080-10083 inclusive. And amanda uses
those only if you don't run amanda over ssh.

root@hawk:~# grep amanda /etc/services 
amanda  10080/tcp   # amanda backup services
kamanda 10081/tcp   # amanda backup services 
(Kerberos)
amandaidx   10082/tcp   # amanda backup services
amidxtape   10083/tcp   # amanda backup services
root@hawk:~# 

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Amanda Community release 3.5.2 - debian test packages

[gene heskett]

On 9/19/22 03:19, Stefan G. Weichinger wrote:

Am 16.09.22 um 17:52 schrieb gene heskett:

The first thing I note is the use of port 5000, and I'm wondering 
about the possibility of fighting
over the ports as Octoprint uses FQDN:5000 as its web server to 
administer its designated 3d printer.


I expect its changeable, and I've done it to Octoprint just for test, 
works fine. But is that a potential
problem if octoprint is sitting idle on a client at the time amanda 
gets fired up? Something to check

out I think, Stefan. Thanks.


Where do you see that port 5000?

Not where, what. octoprint runs as a web server which you send a browser 
to localhost:5000
on the machine running it, or if remote from that machine, you can also 
use for instance,
rock64v2:5000, but you have to login to see what octoprint is doing..  
firefox has a couple

cows babout  insecure logins, but can be coerced to work,
The octoprint instance is for pi's, but in this case its actually 
running inside a named venv
on a rock64, old v2, running armbian jammy. I have two of those setup on 
my local network.


I just looked at a print I started on that machine 10 minutes ago.

I grep through the sources and I am not sure ...

my installation in a test VM seems to work so far, although not yet 
fully compatible to the Debian packages, as Jose mentioned


The supplied by debian clients always worked, up until I lost both 2T 
seagate
drives in the same week last october, / and /amandatapes. But I always 
drove
those clients with my own build as server. Debians definition of the box 
its

supposed to run in doesn't quite match my personal view of security.

But that is a different horse entirely.

The problem i'm concerned with is the new versions use of port 5000, when
there is a running instance of octoprint someplace on ones local network.
Octoprint can be moved, I've done it, but so I expect amanda can be too,
just haven't investigated the tarball I grabbed a couple days ago. Even 
at my age,

88 in a couple weeks, I still have other irons in the fire.

Take care & stay well Stefan.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Re: Amanda Community release 3.5.2 - debian test packages

[Stefan G. Weichinger]

Am 16.09.22 um 17:52 schrieb gene heskett:

The first thing I note is the use of port 5000, and I'm wondering about 
the possibility of fighting
over the ports as Octoprint uses FQDN:5000 as its web server to 
administer its designated 3d printer.


I expect its changeable, and I've done it to Octoprint just for test, 
works fine. But is that a potential
problem if octoprint is sitting idle on a client at the time amanda gets 
fired up? Something to check

out I think, Stefan. Thanks.


Where do you see that port 5000?

I grep through the sources and I am not sure ...

my installation in a test VM seems to work so far, although not yet 
fully compatible to the Debian packages, as Jose mentioned

Re: Amanda Community release 3.5.2 - debian test packages

[Stefan G. Weichinger]

Am 16.09.22 um 16:55 schrieb gene heskett:

On 9/16/22 07:28, Stefan G. Weichinger wrote:
I might rebuild later if needed, just wanted to share asap. Right now 
I am quite busy with X things.


.

I agree, Wayland in place of X needs all the help it can get.


I didn't mean X11 ;-)  .. wanted to say something like "busy with many 
things"


No issues with Wayland here, btw.

Re: Amanda Community release 3.5.2 - debian test packages

[gene heskett]

On 9/16/22 07:28, Stefan G. Weichinger wrote:

Am 02.08.22 um 17:26 schrieb Jose M Calhariz:


I am not doing progress in solving the autotools problems.

I copied debian directory from official Debian 3.5.1, refresh patches,
and "debuild".  I fails with alot of warnings and this relevant error:

automake: error: cannot open < config/amanda/file-list: No such file 
or directory

autoreconf: automake failed with exit status: 1
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path 
'*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' 
\) -a  -type f -exec md5sum {} + -o -type l -printf "symlink  %p

" > debian/autoreconf.after
dh_autoreconf: autoreconf -f -i returned exit code 1
make: *** [debian/rules:41: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit 
status 2

debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -ICVS -I.svn failed


I was able to build debian packages today. This is straight from the 
github repository, I only applied one patch to the 3.5.2 code to make 
it work (that patch is in 3.6 beta already).


I decide to share the packages all you amanda-users, just to get some 
testing and reviewing going:


https://oc.oops.co.at/nextcloud/s/kRbZ82ikQ4a8gjn

! these are no official upstream packages or so ! I cannot guarantee 
for anything :-) !


Looking forward to any test results or so. Pls only use these packages 
in TEST environments.


one more:

I remember differences between upstream and debian: backup user etc

I might rebuild later if needed, just wanted to share asap. Right now 
I am quite busy with X things.


.
The first thing I note is the use of port 5000, and I'm wondering about 
the possibility of fighting
over the ports as Octoprint uses FQDN:5000 as its web server to 
administer its designated 3d printer.


I expect its changeable, and I've done it to Octoprint just for test, 
works fine. But is that a potential
problem if octoprint is sitting idle on a client at the time amanda gets 
fired up? Something to check

out I think, Stefan. Thanks.

Take care and stay well.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Re: Amanda Community release 3.5.2 - debian test packages

[gene heskett]

On 9/16/22 07:28, Stefan G. Weichinger wrote:

Am 02.08.22 um 17:26 schrieb Jose M Calhariz:


I am not doing progress in solving the autotools problems.

I copied debian directory from official Debian 3.5.1, refresh patches,
and "debuild".  I fails with alot of warnings and this relevant error:

automake: error: cannot open < config/amanda/file-list: No such file 
or directory

autoreconf: automake failed with exit status: 1
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path 
'*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' 
\) -a  -type f -exec md5sum {} + -o -type l -printf "symlink  %p

" > debian/autoreconf.after
dh_autoreconf: autoreconf -f -i returned exit code 1
make: *** [debian/rules:41: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit 
status 2

debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -ICVS -I.svn failed


I was able to build debian packages today. This is straight from the 
github repository, I only applied one patch to the 3.5.2 code to make 
it work (that patch is in 3.6 beta already).


I decide to share the packages all you amanda-users, just to get some 
testing and reviewing going:


https://oc.oops.co.at/nextcloud/s/kRbZ82ikQ4a8gjn

! these are no official upstream packages or so ! I cannot guarantee 
for anything :-) !


Looking forward to any test results or so. Pls only use these packages 
in TEST environments.


one more:

I remember differences between upstream and debian: backup user etc

I might rebuild later if needed, just wanted to share asap. Right now 
I am quite busy with X things.


.
I agree, Wayland in place of X needs all the help it can get. I just 
pulled the 4, 3.6.0 branch files
but I'll have to start it up from scratch. Total loss of nearly 
everything last October.


Thank you Stefan

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Amanda Community release 3.5.2 - debian test packages

[Stefan G. Weichinger]

Am 02.08.22 um 17:26 schrieb Jose M Calhariz:


I am not doing progress in solving the autotools problems.

I copied debian directory from official Debian 3.5.1, refresh patches,
and "debuild".  I fails with alot of warnings and this relevant error:

automake: error: cannot open < config/amanda/file-list: No such file or 
directory
autoreconf: automake failed with exit status: 1
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.after
dh_autoreconf: autoreconf -f -i returned exit code 1
make: *** [debian/rules:41: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -ICVS -I.svn failed


I was able to build debian packages today. This is straight from the 
github repository, I only applied one patch to the 3.5.2 code to make it 
work (that patch is in 3.6 beta already).


I decide to share the packages all you amanda-users, just to get some 
testing and reviewing going:


https://oc.oops.co.at/nextcloud/s/kRbZ82ikQ4a8gjn

! these are no official upstream packages or so ! I cannot guarantee for 
anything :-) !


Looking forward to any test results or so. Pls only use these packages 
in TEST environments.


one more:

I remember differences between upstream and debian: backup user etc

I might rebuild later if needed, just wanted to share asap. Right now I 
am quite busy with X things.

Re: New Amanda Community release 3.5.2 Has Arrived! -- email bounce

[gene heskett]

On 9/15/22 03:08, Diego Zuccato wrote:

Il 14/09/2022 19:00, gene heskett ha scritto:

Waiting for 2T SSD's to become affordable, if they ever do.Depends on 
your definition of "affordable".


I bought 2 2TB NVMes at about 300€ each... But SSDs and NVMes have a 
quite "limited" life. Look at TBW numbers. Many SSDs and NVMes have 
some cache RAM for sectors that get rewritten very often, but backups 
tendo to be sequential so the cache is nearly useless. Once upon a 
time there were flash-backed ramdrives: controller + RAM + SSD + 
battery, all the flash contents fitted in the RAM, so the flash was 
never written unless the battery got discharged enough. Safe 
assumption: battery dicharging = host off = no ongoing writes. 
Needless to say the cost was really high and they where usually 
reserved for (parts of) databases.


This is where one needs to over-provision.  As an example, I have 
several rpi4 sized rigs
doing dedicated jobs. Using 8GB cards that were over 50% used got me 
card failures quick
enough to get my attention. These cards have internal housekeeping we 
can't see, designed
to equalize the wear. So as an experiment the next card I composed for 
the rpi4 was a 64Gigger.
This card gets way more than normal read/write traffic as it runs 
linuxcnc master, which is
updated several times a week as development goes on. That card, and the 
cards in 2 more
rock64's have been trouble free, the rpi4 for 4 years now, and my theory 
says its because
they are way over-provisioned, the card has room to do its housekeeping 
with zero outward
signs to let me know it is doing anything. Disk usage tools like df show 
no loss of capacity, yet
in a typical week up to 3 gigs of it is wiped and rewritten. And has 
been since raspian wheezy
on an rpi3. Same card. kernels and linuxcnc from git pulls, but that 
gets done on a 240G SSD
plugged into a usb adaptor with only the results being written to the 
u-sd. But the 240G is

now at 50% used. How much longer will it last? IDK.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: New Amanda Community release 3.5.2 Has Arrived! -- email bounce

[Diego Zuccato]

Il 14/09/2022 19:00, gene heskett ha scritto:


Waiting for 2T SSD's to become affordable, if they ever do.Depends on your definition of 
"affordable".


I bought 2 2TB NVMes at about 300€ each... But SSDs and NVMes have a 
quite "limited" life. Look at TBW numbers. Many SSDs and NVMes have some 
cache RAM for sectors that get rewritten very often, but backups tendo 
to be sequential so the cache is nearly useless. Once upon a time there 
were flash-backed ramdrives: controller + RAM + SSD + battery, all the 
flash contents fitted in the RAM, so the flash was never written unless 
the battery got discharged enough. Safe assumption: battery dicharging = 
host off = no ongoing writes. Needless to say the cost was really high 
and they where usually reserved for (parts of) databases.


--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

Re: New Amanda Community release 3.5.2 Has Arrived! -- email bounce

[gene heskett]

Greetings all;

On 9/14/22 07:39, Stefan G. Weichinger wrote:

Am 13.09.22 um 22:11 schrieb Nathan Stratton Treadway:


(I just tried sending email to this email address.  My message was
accepted for delivery by the Betsol mail server, and I haven't received
any bounce message back [after waiting a few minutes].  So hopefully the
bounce you saw was just a temporary misconfiguration on the Betsol mail
server...(?) )


Interesting, thanks for testing.

Did you get a reply already?

Would be great to know if someone at Betsol is responding to the 
community, and when we see installable packages from them.


.
That hasn't happened in a mailing list like time frame yet, typically a 
month or so.
That says amanda is nowhere near the front burner at Betsol. As an 
amanda user since
about the late 1998 time frame, I lament the day that the University of 
Maryland sold it

all those years ago.

I haven't restarted it since both 2T drives I'd just installed went tits 
down in the
night about 2 weeks apart last October. I will not stop berating seagate 
for the
cause of that debacle, an experiment in flying heads closer to the disk 
by filling
the drives with helium. In my day, any 8th grader knew you can't keep 
helium,
its small enough it walks thru a monel bottle, losing about 10% of it 
overnight.
The drives both failed when enough air got into the drive to raise the 
flying height

of the heads beyond where they could read or write the disks rust coating.
Here, there are no more spinning rust drives, Samsung SSD's are 5x 
faster. But
/home is now a separate controller with 4 1T Samsung drives in a raid-10 
config.
And I've yet to order 4 more, and another controller for use as amanda 
vtapes.


Waiting for 2T SSD's to become affordable, if they ever do.

Take care & stay well everybody.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Re: New Amanda Community release 3.5.2 Has Arrived! -- email bounce

[Nathan Stratton Treadway]

On Wed, Sep 14, 2022 at 13:32:08 +0200, Stefan G. Weichinger wrote:
> Am 13.09.22 um 22:11 schrieb Nathan Stratton Treadway:
> 
> >(I just tried sending email to this email address.  My message was
> >accepted for delivery by the Betsol mail server, and I haven't received
> >any bounce message back [after waiting a few minutes].  So hopefully the
> >bounce you saw was just a temporary misconfiguration on the Betsol mail
> >server...(?) )
> 
> Interesting, thanks for testing.
> 
> Did you get a reply already?

No, I haven't received any reply... (but also have not received any
bounce message).

> Would be great to know if someone at Betsol is responding to the
> community, and when we see installable packages from them.

(Yep, agreed.)

Nathan

Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Re: New Amanda Community release 3.5.2 Has Arrived! -- email bounce

[Stefan G. Weichinger]

Am 13.09.22 um 22:11 schrieb Nathan Stratton Treadway:


(I just tried sending email to this email address.  My message was
accepted for delivery by the Betsol mail server, and I haven't received
any bounce message back [after waiting a few minutes].  So hopefully the
bounce you saw was just a temporary misconfiguration on the Betsol mail
server...(?) )


Interesting, thanks for testing.

Did you get a reply already?

Would be great to know if someone at Betsol is responding to the 
community, and when we see installable packages from them.

Re: New Amanda Community release 3.5.2 Has Arrived! -- email bounce

[Nathan Stratton Treadway]

On Tue, Sep 13, 2022 at 17:29:41 +0200, Stefan G. Weichinger wrote:
> I received:
> 
> "Your message to chris.hass...@betsol.com couldn't be delivered.
> 
> Chris.Hassell wasn't found at betsol.com."

(I just tried sending email to this email address.  My message was
accepted for delivery by the Betsol mail server, and I haven't received
any bounce message back [after waiting a few minutes].  So hopefully the
bounce you saw was just a temporary misconfiguration on the Betsol mail
server...(?) )

Nathan 


Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Re: New Amanda Community release 3.5.2 Has Arrived!

[Stefan G. Weichinger]

Am 13.09.22 um 14:14 schrieb Stefan G. Weichinger:

@Chris ... any news? Could you pls provide packages, for example for 
Debian 11.x ?


thanks


I received:

"Your message to chris.hass...@betsol.com couldn't be delivered.

Chris.Hassell wasn't found at betsol.com."

Re: New Amanda Community release 3.5.2 Has Arrived!

[Stefan G. Weichinger]

Am 24.08.22 um 14:10 schrieb Stefan G. Weichinger:

Am 02.08.22 um 20:31 schrieb Nathan Stratton Treadway:

On Tue, Aug 02, 2022 at 12:30:07 -0400, gene heskett wrote:

And where do I get the debian approved versions of 3.5.2?


That's what Jose is attempting to create now... (So watch this thread
for news.)


We are :-)

Tried another build in my test VM today ... still does not work.

And still no packages (for current distributions) from upstream at 
https://www.zmanda.com/downloads/


@Chris ... any news? Could you pls provide packages, for example for 
Debian 11.x ?


thanks

Re: New Amanda Community release 3.5.2 Has Arrived!

[Stefan G. Weichinger]

Am 02.08.22 um 20:31 schrieb Nathan Stratton Treadway:

On Tue, Aug 02, 2022 at 12:30:07 -0400, gene heskett wrote:

And where do I get the debian approved versions of 3.5.2?


That's what Jose is attempting to create now... (So watch this thread
for news.)


We are :-)

Tried another build in my test VM today ... still does not work.

And still no packages (for current distributions) from upstream at 
https://www.zmanda.com/downloads/

Re: New Amanda Community release 3.5.2 Has Arrived!

[Nathan Stratton Treadway]

On Tue, Aug 02, 2022 at 12:30:07 -0400, gene heskett wrote:
> And where do I get the debian approved versions of 3.5.2? 

That's what Jose is attempting to create now... (So watch this thread
for news.)

Nathan



Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Re: New Amanda Community release 3.5.2 Has Arrived!

[gene heskett]

On 8/2/22 10:32, Jose M Calhariz wrote:

On Tue, Aug 02, 2022 at 12:27:26PM +0200, Stefan G. Weichinger wrote:

Am 02.08.22 um 10:06 schrieb Stefan G. Weichinger:

Am 02.08.22 um 09:44 schrieb gene heskett:

On 8/2/22 01:40, Winston Sorfleet wrote:

Much appreciated José, count me in as a beta tester.


Me too, but its been a while and this is a fairly fresh bullseye
install, and autogen
complains mightily, and quickly.

gene@coyote:~/src/amanda-tag-community-3.5.2$ ./autogen
See DEVELOPING for instructions on updating:
   * gettext macros
   * gnulib
   * libtool files
..creating file lists
..aclocal
config/amanda/libs.m4:160: warning: macro 'AM_PATH_GLIB_2_0' not
found in library
...aclocal patches
..autoconf
configure:46532: error: possibly undefined macro: AM_PATH_GLIB_2_0
    If this token and others are legitimate, please use
m4_pattern_allow.
    See the Autoconf documentation.
configure:46533: error: possibly undefined macro: AC_MSG_ERROR
autoconf failed

And the fix is?

build-essential., debhejper and friends are installed.

As far as I learned from Chris Hassell, the new packaging scripts should
build packages for Debian with:

./packaging/deb/buildpkg

I am trying that for the branch "tag-community-3.5.2" right now in a
Debian-11.4-VM.

There is quite a list of needed packages to install, Chris told me:

gcc g++ binutils gettext libtool autoconf automake bison flex swig
libglib2.0-dev libjson-glib-1.0 libjson-glib-dev libssl-dev
libcurl4-openssl-dev libncurses5-dev libreadline-dev perl-base
perl-modules libcpanplus-perl libio-socket-ssl-perl libswitch-perl
bsd-mailx mtx procps smbclient dump gnuplot-nox xinetd

and some extra:

xsltproc build-essential debhelper fakeroot dpkg-dev dh-make-perl git
make gawk grep tar passwd

pressing SEND now, my build is still running

I was able to build packages for 3.5.2 after applying the fix mentioned in

https://github.com/zmanda/amanda/issues/185

Installing the packages over the packages coming from the Debian
repositories seems a bit tricky:

the new packages use the user "amandabackup", so far it was "backup"

the path to amandad seems to change as well

I assume I can edit packaging/deb/rules to adjust that.

Unsure if that is a good thing to do.


The Debian packages from Zmanda follow the official documentation, the
Packages from Debian, aka now maintained by me, follow Debian
guidelines.  Upgrades between them is something that I do not try and
I do not expect good results.

There are patches to the build process and code to adapt the amanda
for the Debian guidelines.  I do my best to patch the documentation of
amanda on Debian, so there is no difference between what is
implemented and what is documented.


Kind regards
Jose M Calhariz

And where do I get the debian approved versions of 3.5.2? What is 
offered in the bullseye
repo's is an older 1.3.5.1-7 that has not worked for me. Un-resolvable 
Dependencies.  And
I was at one time, quite comfortable building from tarballs, been doing 
it since 1998.


But I had a complete meltdown last fall losing 20 years of history with 
the failure of

two new 2T seacrate drives in a 1 week span. End of spinning rust here.

So my rebuild is now 100% 1T Samsung SSD's, 4 in a raid10 for /home. 
With a .5Tb as /, + 1
500GB SSD for dump buffer, and I can get more of the 1T's for a raid10 
for amanda.  If I

can get it to work...

Thank you Jose, take care & stay well.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Re: New Amanda Community release 3.5.2 Has Arrived!

[Jose M Calhariz]

On Tue, Aug 02, 2022 at 06:27:24AM +0100, Jose M Calhariz wrote:
> On Mon, Aug 01, 2022 at 06:50:15PM +0100, Jose M Calhariz wrote:
> > On Mon, Aug 01, 2022 at 10:55:40AM +0200, Stefan G. Weichinger wrote:
> > > Am 29.07.22 um 04:11 schrieb Pavan Raj:
> > > > Hello Everyone,
> > > > 
> > > > We at Zmanda are pleased to announce the 3.5.2 release of Amanda
> > > > Community.
> > > 
> > > Nice to hear ...
> > > 
> > > anyone touched that yet?
> > > 
> > > Looking forward to that release packaged for Debian (most of my
> > > amanda-servers run Debian Linux).
> > 
> > Give me sometime to prepare non oficial Debian source packages for
> > Debian 11 and 10, so you can easily build for your servers.  This time
> > I would like some reports of success with 3.5.2 before upload an
> > official package to Debian unstable.
> 
> I have problems with the autotools to compile amanda 3.5.2 for a
> pre-offcial package for Debian, with alot of warnings about deprecated
> macros.  I will work on this.

I am not doing progress in solving the autotools problems.

I copied debian directory from official Debian 3.5.1, refresh patches,
and "debuild".  I fails with alot of warnings and this relevant error:

automake: error: cannot open < config/amanda/file-list: No such file or 
directory
autoreconf: automake failed with exit status: 1
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' 
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec 
md5sum {} + -o -type l -printf "symlink  %p
" > debian/autoreconf.after
dh_autoreconf: autoreconf -f -i returned exit code 1
make: *** [debian/rules:41: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -ICVS -I.svn failed



Kind regards
Jose M Calhariz






> 
> > 
> > 
> > 
> > > 
> > > On gentoo I am afraid I have to try to come up with an ebuild myself for 
> > > now
> > > (even the 3.6 beta doesn't come with an ebuild yet).
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > Kind regards
> > Jose M Calhariz
> > 
> 
> Kind regards
> Jose M Calhariz
> 
> 
> 



-- 
--
Não há fatos, só interpretações.
-- Friedrich Nietzsche


signature.asc
Description: PGP signature

Re: New Amanda Community release 3.5.2 Has Arrived!

[Jose M Calhariz]

On Tue, Aug 02, 2022 at 12:27:26PM +0200, Stefan G. Weichinger wrote:
> Am 02.08.22 um 10:06 schrieb Stefan G. Weichinger:
> > Am 02.08.22 um 09:44 schrieb gene heskett:
> > > On 8/2/22 01:40, Winston Sorfleet wrote:
> > > > Much appreciated José, count me in as a beta tester.
> > > > 
> > > 
> > > Me too, but its been a while and this is a fairly fresh bullseye
> > > install, and autogen
> > > complains mightily, and quickly.
> > > 
> > > gene@coyote:~/src/amanda-tag-community-3.5.2$ ./autogen
> > > See DEVELOPING for instructions on updating:
> > >   * gettext macros
> > >   * gnulib
> > >   * libtool files
> > > ..creating file lists
> > > ..aclocal
> > > config/amanda/libs.m4:160: warning: macro 'AM_PATH_GLIB_2_0' not
> > > found in library
> > > ...aclocal patches
> > > ..autoconf
> > > configure:46532: error: possibly undefined macro: AM_PATH_GLIB_2_0
> > >    If this token and others are legitimate, please use
> > > m4_pattern_allow.
> > >    See the Autoconf documentation.
> > > configure:46533: error: possibly undefined macro: AC_MSG_ERROR
> > > autoconf failed
> > > 
> > > And the fix is?
> > > 
> > > build-essential., debhejper and friends are installed.
> > 
> > As far as I learned from Chris Hassell, the new packaging scripts should
> > build packages for Debian with:
> > 
> > ./packaging/deb/buildpkg
> > 
> > I am trying that for the branch "tag-community-3.5.2" right now in a
> > Debian-11.4-VM.
> > 
> > There is quite a list of needed packages to install, Chris told me:
> > 
> > gcc g++ binutils gettext libtool autoconf automake bison flex swig
> > libglib2.0-dev libjson-glib-1.0 libjson-glib-dev libssl-dev
> > libcurl4-openssl-dev libncurses5-dev libreadline-dev perl-base
> > perl-modules libcpanplus-perl libio-socket-ssl-perl libswitch-perl
> > bsd-mailx mtx procps smbclient dump gnuplot-nox xinetd
> > 
> > and some extra:
> > 
> > xsltproc build-essential debhelper fakeroot dpkg-dev dh-make-perl git
> > make gawk grep tar passwd
> > 
> > pressing SEND now, my build is still running
> 
> I was able to build packages for 3.5.2 after applying the fix mentioned in
> 
> https://github.com/zmanda/amanda/issues/185
> 
> Installing the packages over the packages coming from the Debian
> repositories seems a bit tricky:
> 
> the new packages use the user "amandabackup", so far it was "backup"
> 
> the path to amandad seems to change as well
> 
> I assume I can edit packaging/deb/rules to adjust that.
> 
> Unsure if that is a good thing to do.
>

The Debian packages from Zmanda follow the official documentation, the
Packages from Debian, aka now maintained by me, follow Debian
guidelines.  Upgrades between them is something that I do not try and
I do not expect good results.

There are patches to the build process and code to adapt the amanda
for the Debian guidelines.  I do my best to patch the documentation of
amanda on Debian, so there is no difference between what is
implemented and what is documented.


Kind regards
Jose M Calhariz

-- 
--
Não há fatos, só interpretações.
-- Friedrich Nietzsche


signature.asc
Description: PGP signature

Re: New Amanda Community release 3.5.2 Has Arrived!

[Stefan G. Weichinger]

Am 02.08.22 um 10:06 schrieb Stefan G. Weichinger:

Am 02.08.22 um 09:44 schrieb gene heskett:

On 8/2/22 01:40, Winston Sorfleet wrote:

Much appreciated José, count me in as a beta tester.



Me too, but its been a while and this is a fairly fresh bullseye 
install, and autogen

complains mightily, and quickly.

gene@coyote:~/src/amanda-tag-community-3.5.2$ ./autogen
See DEVELOPING for instructions on updating:
  * gettext macros
  * gnulib
  * libtool files
..creating file lists
..aclocal
config/amanda/libs.m4:160: warning: macro 'AM_PATH_GLIB_2_0' not found 
in library

...aclocal patches
..autoconf
configure:46532: error: possibly undefined macro: AM_PATH_GLIB_2_0
   If this token and others are legitimate, please use 
m4_pattern_allow.

   See the Autoconf documentation.
configure:46533: error: possibly undefined macro: AC_MSG_ERROR
autoconf failed

And the fix is?

build-essential., debhejper and friends are installed.


As far as I learned from Chris Hassell, the new packaging scripts should 
build packages for Debian with:


./packaging/deb/buildpkg

I am trying that for the branch "tag-community-3.5.2" right now in a 
Debian-11.4-VM.


There is quite a list of needed packages to install, Chris told me:

gcc g++ binutils gettext libtool autoconf automake bison flex swig 
libglib2.0-dev libjson-glib-1.0 libjson-glib-dev libssl-dev 
libcurl4-openssl-dev libncurses5-dev libreadline-dev perl-base 
perl-modules libcpanplus-perl libio-socket-ssl-perl libswitch-perl 
bsd-mailx mtx procps smbclient dump gnuplot-nox xinetd


and some extra:

xsltproc build-essential debhelper fakeroot dpkg-dev dh-make-perl git 
make gawk grep tar passwd


pressing SEND now, my build is still running


I was able to build packages for 3.5.2 after applying the fix mentioned in

https://github.com/zmanda/amanda/issues/185

Installing the packages over the packages coming from the Debian 
repositories seems a bit tricky:


the new packages use the user "amandabackup", so far it was "backup"

the path to amandad seems to change as well

I assume I can edit packaging/deb/rules to adjust that.

Unsure if that is a good thing to do.

Re: New Amanda Community release 3.5.2 Has Arrived!

[Stefan G. Weichinger]

Am 02.08.22 um 10:06 schrieb Stefan G. Weichinger:


pressing SEND now, my build is still running


hitting https://github.com/zmanda/amanda/issues/184

Re: New Amanda Community release 3.5.2 Has Arrived!

[Stefan G. Weichinger]

Am 02.08.22 um 09:44 schrieb gene heskett:

On 8/2/22 01:40, Winston Sorfleet wrote:

Much appreciated José, count me in as a beta tester.



Me too, but its been a while and this is a fairly fresh bullseye 
install, and autogen

complains mightily, and quickly.

gene@coyote:~/src/amanda-tag-community-3.5.2$ ./autogen
See DEVELOPING for instructions on updating:
  * gettext macros
  * gnulib
  * libtool files
..creating file lists
..aclocal
config/amanda/libs.m4:160: warning: macro 'AM_PATH_GLIB_2_0' not found 
in library

...aclocal patches
..autoconf
configure:46532: error: possibly undefined macro: AM_PATH_GLIB_2_0
   If this token and others are legitimate, please use 
m4_pattern_allow.

   See the Autoconf documentation.
configure:46533: error: possibly undefined macro: AC_MSG_ERROR
autoconf failed

And the fix is?

build-essential., debhejper and friends are installed.


As far as I learned from Chris Hassell, the new packaging scripts should 
build packages for Debian with:


./packaging/deb/buildpkg

I am trying that for the branch "tag-community-3.5.2" right now in a 
Debian-11.4-VM.


There is quite a list of needed packages to install, Chris told me:

gcc g++ binutils gettext libtool autoconf automake bison flex swig 
libglib2.0-dev libjson-glib-1.0 libjson-glib-dev libssl-dev 
libcurl4-openssl-dev libncurses5-dev libreadline-dev perl-base 
perl-modules libcpanplus-perl libio-socket-ssl-perl libswitch-perl 
bsd-mailx mtx procps smbclient dump gnuplot-nox xinetd


and some extra:

xsltproc build-essential debhelper fakeroot dpkg-dev dh-make-perl git 
make gawk grep tar passwd


pressing SEND now, my build is still running

Re: New Amanda Community release 3.5.2 Has Arrived!

[Stefan G. Weichinger]

Am 29.07.22 um 04:11 schrieb Pavan Raj:

Hello Everyone,

We at Zmanda are pleased to announce the 3.5.2 release of Amanda Community.

URL: http://www.amanda.org/download.php 
<http://www.amanda.org/download.php>


https://www.zmanda.com/downloads/

lists packages for Debian-9.9 (for example)

That isn't very helpful when Debian is at 11.4 currently.

Please provide usable packages for current distributions, not everyone 
wants to build software from source code.

Re: New Amanda Community release 3.5.2 Has Arrived!

[gene heskett]

On 8/2/22 01:40, Winston Sorfleet wrote:

Much appreciated José, count me in as a beta tester.



Me too, but its been a while and this is a fairly fresh bullseye 
install, and autogen

complains mightily, and quickly.

gene@coyote:~/src/amanda-tag-community-3.5.2$ ./autogen
See DEVELOPING for instructions on updating:
 * gettext macros
 * gnulib
 * libtool files
..creating file lists
..aclocal
config/amanda/libs.m4:160: warning: macro 'AM_PATH_GLIB_2_0' not found 
in library

...aclocal patches
..autoconf
configure:46532: error: possibly undefined macro: AM_PATH_GLIB_2_0
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
configure:46533: error: possibly undefined macro: AC_MSG_ERROR
autoconf failed

And the fix is?

build-essential., debhejper and friends are installed.


On 2022-08-02 1:27 a.m., Jose M Calhariz wrote:

On Mon, Aug 01, 2022 at 06:50:15PM +0100, Jose M Calhariz wrote:

On Mon, Aug 01, 2022 at 10:55:40AM +0200, Stefan G. Weichinger wrote:

Am 29.07.22 um 04:11 schrieb Pavan Raj:

Hello Everyone,

We at Zmanda are pleased to announce the 3.5.2 release of Amanda
Community.

Nice to hear ...

anyone touched that yet?

Looking forward to that release packaged for Debian (most of my
amanda-servers run Debian Linux).

Give me sometime to prepare non oficial Debian source packages for
Debian 11 and 10, so you can easily build for your servers. This time
I would like some reports of success with 3.5.2 before upload an
official package to Debian unstable.

I have problems with the autotools to compile amanda 3.5.2 for a
pre-offcial package for Debian, with alot of warnings about deprecated
macros.  I will work on this.




On gentoo I am afraid I have to try to come up with an ebuild 
myself for now

(even the 3.6 beta doesn't come with an ebuild yet).






Kind regards
Jose M Calhariz


Kind regards
Jose M Calhariz




.



Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Re: New Amanda Community release 3.5.2 Has Arrived!

[Winston Sorfleet]

Much appreciated José, count me in as a beta tester.

On 2022-08-02 1:27 a.m., Jose M Calhariz wrote:

On Mon, Aug 01, 2022 at 06:50:15PM +0100, Jose M Calhariz wrote:

On Mon, Aug 01, 2022 at 10:55:40AM +0200, Stefan G. Weichinger wrote:

Am 29.07.22 um 04:11 schrieb Pavan Raj:

Hello Everyone,

We at Zmanda are pleased to announce the 3.5.2 release of Amanda
Community.

Nice to hear ...

anyone touched that yet?

Looking forward to that release packaged for Debian (most of my
amanda-servers run Debian Linux).

Give me sometime to prepare non oficial Debian source packages for
Debian 11 and 10, so you can easily build for your servers.  This time
I would like some reports of success with 3.5.2 before upload an
official package to Debian unstable.

I have problems with the autotools to compile amanda 3.5.2 for a
pre-offcial package for Debian, with alot of warnings about deprecated
macros.  I will work on this.





On gentoo I am afraid I have to try to come up with an ebuild myself for now
(even the 3.6 beta doesn't come with an ebuild yet).






Kind regards
Jose M Calhariz


Kind regards
Jose M Calhariz

Re: New Amanda Community release 3.5.2 Has Arrived!

[Jose M Calhariz]

On Mon, Aug 01, 2022 at 06:50:15PM +0100, Jose M Calhariz wrote:
> On Mon, Aug 01, 2022 at 10:55:40AM +0200, Stefan G. Weichinger wrote:
> > Am 29.07.22 um 04:11 schrieb Pavan Raj:
> > > Hello Everyone,
> > > 
> > > We at Zmanda are pleased to announce the 3.5.2 release of Amanda
> > > Community.
> > 
> > Nice to hear ...
> > 
> > anyone touched that yet?
> > 
> > Looking forward to that release packaged for Debian (most of my
> > amanda-servers run Debian Linux).
> 
> Give me sometime to prepare non oficial Debian source packages for
> Debian 11 and 10, so you can easily build for your servers.  This time
> I would like some reports of success with 3.5.2 before upload an
> official package to Debian unstable.

I have problems with the autotools to compile amanda 3.5.2 for a
pre-offcial package for Debian, with alot of warnings about deprecated
macros.  I will work on this.

> 
> 
> 
> > 
> > On gentoo I am afraid I have to try to come up with an ebuild myself for now
> > (even the 3.6 beta doesn't come with an ebuild yet).
> > 
> > 
> > 
> > 
> 
> 
> Kind regards
> Jose M Calhariz
> 

Kind regards
Jose M Calhariz



-- 
--
Não há fatos, só interpretações.
-- Friedrich Nietzsche


signature.asc
Description: PGP signature

Re: New Amanda Community release 3.5.2 Has Arrived!

[Jose M Calhariz]

On Mon, Aug 01, 2022 at 10:55:40AM +0200, Stefan G. Weichinger wrote:
> Am 29.07.22 um 04:11 schrieb Pavan Raj:
> > Hello Everyone,
> > 
> > We at Zmanda are pleased to announce the 3.5.2 release of Amanda
> > Community.
> 
> Nice to hear ...
> 
> anyone touched that yet?
> 
> Looking forward to that release packaged for Debian (most of my
> amanda-servers run Debian Linux).

Give me sometime to prepare non oficial Debian source packages for
Debian 11 and 10, so you can easily build for your servers.  This time
I would like some reports of success with 3.5.2 before upload an
official package to Debian unstable.



> 
> On gentoo I am afraid I have to try to come up with an ebuild myself for now
> (even the 3.6 beta doesn't come with an ebuild yet).
> 
> 
> 
> 


Kind regards
Jose M Calhariz

-- 
--
O que sabemos é uma gota, o que ignoramos é um oceano.
-- Isaac Newton


signature.asc
Description: PGP signature

Re: New Amanda Community release 3.5.2 Has Arrived!

[Stefan G. Weichinger]

Am 29.07.22 um 04:11 schrieb Pavan Raj:

Hello Everyone,

We at Zmanda are pleased to announce the 3.5.2 release of Amanda
Community.


Nice to hear ...

anyone touched that yet?

Looking forward to that release packaged for Debian (most of my 
amanda-servers run Debian Linux).


On gentoo I am afraid I have to try to come up with an ebuild myself for 
now (even the 3.6 beta doesn't come with an ebuild yet).

New Amanda Community release 3.5.2 Has Arrived!

[Pavan Raj]

Hello Everyone,

We at Zmanda are pleased to announce the 3.5.2 release of Amanda Community.
URL: http://www.amanda.org/download.php

What's New
Experience enhanced tape handling capabilities with the new Amanda.
The 3.5.2 version of Amanda will prevent unintentional deletions of data on 
tapes. Whether you want to implement a 3-2-1 backup rule or do a simple 
physical media backup, hands-down, tape media will become your reliable storage 
medium under all circumstances.

If you have any other questions, reply to this email or write to us at 
cont...@zmanda.com<mailto:cont...@zmanda.com>.
Open Source. Open Formats. Open APIs.

--
Thanks & Regards,
V J N Pavan Raj | Director, Corporate Development | BETSOL |  
pavan@betsol.com<mailto:pavan@betsol.com> | (M) 1.720.448.7099 | (O) 
1.720.506.5534 |Check my availability (Calendar):  
HTML<https://calendly.com/pavanrajv>
[w88EDKKwH3E8wBJRU5ErkJggg==]

Confidentiality Notice | The information transmitted by this email is intended 
only for the person or entity to which it is addressed. This email may contain 
proprietary, business-confidential and/or privileged material. If you are not 
the intended recipient of this message, be aware that any use, review, 
re-transmission, distribution, reproduction or any action taken in reliance 
upon this message is strictly prohibited. If you received this in error, please 
contact the sender and delete the material from all computers.

Re: amanda backup hanging consistently

[Orion Poplawski]

On 6/17/22 04:25, Jose M Calhariz wrote:

Hi,


If you run tar by hand on the DLE does it finish?  After how much time?


Thanks for the suggestion.  That made me notice that it was bogging down 
dealing with a *very* deep directory that had been created by a buggy 
process going into infinite recursion.  Removing that appears to have 
fixed the dump.


Still seems like there is an issue with amanda not cleaning up properly 
from the timeout condition though.




On Wed, Jun 15, 2022 at 09:50:11AM -0600, Orion Poplawski wrote:

On 6/15/22 09:38, Orion Poplawski wrote:

Recently the backup of a particular DLE has started hanging consistently.  I
don't see any recent changes on the server except possibly a change from
kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
problem didn't start until June 6th.

The tar command is stuck trying to write out the name of the directory to 
amgtar:

root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
--verbose --verbose --block-number --file - --directory /export/backup/rufous
--no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
--verbose --verbose --block-number --file - --directory /export/backup/rufous
--no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .

# strace -f -s 500 -p 11321
strace: Process 11321 attached
write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59

# strace -f -s 500 -p 11432
strace: Process 11432 attached
write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59

amgtar is stuck writing output to amandad:

# strace -s 200 -p 11427
strace: Process 11427 attached
write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
2022-05-23 17:31
./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096


amgtar debug has:

Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 156
Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
/bin/tar
Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
/var/lib/amanda/gnutar-lists
Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : ONE-FILE-SYSTEM no
Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE no
Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
bytes written: [0-9][0-9]*
Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
Directory is new$
Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
Directory has been renamed
Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could not
open conf file
Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL ^Elapsed 
time:
Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL ^Throughput
Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
directory is on a different filesystem; not dumped
Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
ignored$
Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File .*
shrunk by [0-9][0-9]* bytes, padding with zeros
Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-amgtar   : NORMAL : Cannot
add file .*: No such file or directory$
Tue Jun 14 23:47:14.111407572 2022: pid 11427: ??-amgtar   : NORMAL : Error
exit delayed from previous errors
Tue Jun 14 23:47:14.111417962 2022: pid 11427: ??-amgtar   : ERROR amgtar: error
Tue Jun 14 23:47:14.114473250 2022: pid 11427: ??-amgtar   : Spawning
"/bin/tar /bin/tar -x --no-check-device -f -" in pipeline
Tue Jun 14 23:47:14.124455374 2022: pid 11431: ??-amgtar   : Executing:
/bin/tar '--version'
Tue Jun 14 23:47:14.126144343 20

Re: amanda backup hanging consistently

[Jose M Calhariz]

Hi,


If you run tar by hand on the DLE does it finish?  After how much time?

Kind regards
Jose M Calhariz


On Wed, Jun 15, 2022 at 09:50:11AM -0600, Orion Poplawski wrote:
> On 6/15/22 09:38, Orion Poplawski wrote:
> > Recently the backup of a particular DLE has started hanging consistently.  I
> > don't see any recent changes on the server except possibly a change from
> > kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
> > problem didn't start until June 6th.
> > 
> > The tar command is stuck trying to write out the name of the directory to 
> > amgtar:
> > 
> > root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
> > --verbose --verbose --block-number --file - --directory 
> > /export/backup/rufous
> > --no-check-device --listed-incremental
> > /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> > --ignore-failed-read --totals --exclude-from
> > /var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
> > root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
> > --verbose --verbose --block-number --file - --directory 
> > /export/backup/rufous
> > --no-check-device --listed-incremental
> > /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> > --ignore-failed-read --totals --exclude-from
> > /var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .
> > 
> > # strace -f -s 500 -p 11321
> > strace: Process 11321 attached
> > write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> > 
> > # strace -f -s 500 -p 11432
> > strace: Process 11432 attached
> > write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> > 
> > amgtar is stuck writing output to amandad:
> > 
> > # strace -s 200 -p 11427
> > strace: Process 11427 attached
> > write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
> > 2022-05-23 17:31
> > ./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
> > orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096
> > 
> > 
> > amgtar debug has:
> > 
> > Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid > > 0
> > euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
> > Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
> > Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 
> > 156
> > Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid > > 0
> > euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
> > Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
> > /bin/tar
> > Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
> > /var/lib/amanda/gnutar-lists
> > Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : 
> > ONE-FILE-SYSTEM no
> > Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
> > Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
> > Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE 
> > no
> > Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
> > Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
> > Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
> > Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
> > Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
> > bytes written: [0-9][0-9]*
> > Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
> > Directory is new$
> > Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
> > Directory has been renamed
> > Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could 
> > not
> > open conf file
> > Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL 
> > ^Elapsed time:
> > Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL 
> > ^Throughput
> > Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
> > directory is on a different filesystem; not dumped
> > Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
> > ignored$
> > Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File 
> > .*
> > shrunk by [0-9][0-9]* bytes, padding with zeros
> > Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-

Re: amanda backup hanging consistently

[Orion Poplawski]

On 6/15/22 09:38, Orion Poplawski wrote:
> Recently the backup of a particular DLE has started hanging consistently.  I
> don't see any recent changes on the server except possibly a change from
> kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
> problem didn't start until June 6th.
> 
> The tar command is stuck trying to write out the name of the directory to 
> amgtar:
> 
> root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
> --verbose --verbose --block-number --file - --directory /export/backup/rufous
> --no-check-device --listed-incremental
> /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> --ignore-failed-read --totals --exclude-from
> /var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
> root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
> --verbose --verbose --block-number --file - --directory /export/backup/rufous
> --no-check-device --listed-incremental
> /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> --ignore-failed-read --totals --exclude-from
> /var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .
> 
> # strace -f -s 500 -p 11321
> strace: Process 11321 attached
> write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> 
> # strace -f -s 500 -p 11432
> strace: Process 11432 attached
> write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> 
> amgtar is stuck writing output to amandad:
> 
> # strace -s 200 -p 11427
> strace: Process 11427 attached
> write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
> 2022-05-23 17:31
> ./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
> orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096
> 
> 
> amgtar debug has:
> 
> Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
> euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
> Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
> Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 156
> Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
> euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
> Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
> /bin/tar
> Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
> /var/lib/amanda/gnutar-lists
> Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : ONE-FILE-SYSTEM 
> no
> Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
> Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
> Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE no
> Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
> Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
> Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
> Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
> Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
> bytes written: [0-9][0-9]*
> Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
> Directory is new$
> Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
> Directory has been renamed
> Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could not
> open conf file
> Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL ^Elapsed 
> time:
> Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL 
> ^Throughput
> Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
> directory is on a different filesystem; not dumped
> Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
> ignored$
> Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File .*
> shrunk by [0-9][0-9]* bytes, padding with zeros
> Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-amgtar   : NORMAL : Cannot
> add file .*: No such file or directory$
> Tue Jun 14 23:47:14.111407572 2022: pid 11427: ??-amgtar   : NORMAL : Error
> exit delayed from previous errors
> Tue Jun 14 23:47:14.111417962 2022: pid 11427: ??-amgtar   : ERROR amgtar: 
> error
> Tue Jun 14 23:47:14.114473250 2022: pid 11427: ??-amgtar   : Spawning
> "/bin/tar /bin/tar -x --no-check-device -f -" in pipeline
> Tue Jun 14 23:47:14.124455374 2022: pid 11431: ??-amgtar   : Executing:
> /bin/tar '--version'
> Tue Jun 14 23:47:14.126144343 2022: pid 11427: ??-amgtar   : Spawning
> "/usr/bin/tar /usr/bin/tar --create --ve