Re: amanda client packaging and ambind (amrecover error on client)

[Orion Poplawski]

On 12/23/21 02:01, David Simpson wrote:
Hit this exact problem in Almalinux 8.5 with a couple of test machines 
(rpm from default repo/appstream):


https://utcc.utoronto.ca/~cks/space/blog/linux/Ubuntu1804AmandaProblem 



ambind is not included in client packages for 3.5.1, therefore the 
client will error trying to launch amrecover  – is this across the board 
for all distros/packages?


The solution as above is then to install the amanda-server package.



(doesn’t seem to be the case for Zmanda community RHEL7 rpm - 
amanda-backup_client.x86_64    3.5.1-1.rhel7)



David



File a bug against RHEL8 and point them to bug #1710147.  This was fixed 
long ago in Fedora.


https://bugzilla.redhat.com/show_bug.cgi?id=1710147

--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of NWRA Technical Systems  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: amanda client packaging and ambind (amrecover error on client)

[David Simpson]

Good that Debian is packaging properly.. perhaps limited to Centos and 
associated clones... and perhaps Ubuntu may also still be issue

Consistent packaging is indeed the way forward.

Will consider putting in a stanza to sort this out in the ansible code, on Alma 
hosts...

thanks
David

-
David Simpson - Senior Systems Engineer
ARCCA, Redwood Building,
King Edward VII Avenue,
Cardiff, CF10 3NB   
    

David Simpson - peiriannydd uwch systemau
ARCCA, Adeilad Redwood,
King Edward VII Avenue,
Caerdydd, CF10 3NB

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Charles Curley
Sent: 23 December 2021 16:35
To: amanda-users 
Subject: Re: amanda client packaging and ambind (amrecover error on client)

External email to Cardiff University - Take care when replying/opening 
attachments or links.
Nid ebost mewnol o Brifysgol Caerdydd yw hwn - Cymerwch ofal wrth ateb/agor 
atodiadau neu ddolenni.



On Thu, 23 Dec 2021 09:07:42 -0700
Charles Curley  wrote:

> No.
>
> root@hawk:~# apt-file search ambind | grep /ambind$
> amanda-common: /usr/lib/amanda/ambind
> root@hawk:~#

I should have specified: This is on Debian 11 (Bullseye). It was also the case 
on Debian 10 (Buster) and likely earlier.

--
Does anybody read signatures any more?

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcharlescurley.com%2F&data=04%7C01%7Csimpsond4%40cardiff.ac.uk%7Ccc0a7136b6f7444c62d908d9c6324ae7%7Cbdb74b3095684856bdbf06759778fcbc%7C1%7C0%7C637758742005135291%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=%2FWaVWyBsApvgy1T72ZR3hXeqFxJ2QckGqBOQ8tiP7ck%3D&reserved=0
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcharlescurley.com%2Fblog%2F&data=04%7C01%7Csimpsond4%40cardiff.ac.uk%7Ccc0a7136b6f7444c62d908d9c6324ae7%7Cbdb74b3095684856bdbf06759778fcbc%7C1%7C0%7C637758742005135291%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=i3mmH0IhbyBwa1m2lq1qleeq6ABgyhtePdPiX86qP6s%3D&reserved=0

Re: amanda client packaging and ambind (amrecover error on client)

[Charles Curley]

On Thu, 23 Dec 2021 09:07:42 -0700
Charles Curley  wrote:

> No.
> 
> root@hawk:~# apt-file search ambind | grep /ambind$
> amanda-common: /usr/lib/amanda/ambind
> root@hawk:~# 

I should have specified: This is on Debian 11 (Bullseye). It was also
the case on Debian 10 (Buster) and likely earlier.

-- 
Does anybody read signatures any more?

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

Re: amanda client packaging and ambind (amrecover error on client)

[Charles Curley]

On Thu, 23 Dec 2021 09:01:24 +
David Simpson  wrote:

> ambind is not included in client packages for 3.5.1, therefore the
> client will error trying to launch amrecover  - is this across the
> board for all distros/packages?

No.

root@hawk:~# apt-file search ambind | grep /ambind$
amanda-common: /usr/lib/amanda/ambind
root@hawk:~# 

Long term, the solution is to package Amanda properly.

-- 
Does anybody read signatures any more?

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

amanda client packaging and ambind (amrecover error on client)

[David Simpson]

Hit this exact problem in Almalinux 8.5 with a couple of test machines (rpm 
from default repo/appstream):

https://utcc.utoronto.ca/~cks/space/blog/linux/Ubuntu1804AmandaProblem

ambind is not included in client packages for 3.5.1, therefore the client will 
error trying to launch amrecover  - is this across the board for all 
distros/packages?

The solution as above is then to install the amanda-server package.



(doesn't seem to be the case for Zmanda community RHEL7 rpm - 
amanda-backup_client.x86_643.5.1-1.rhel7)

David


-
David Simpson - Senior Systems Engineer
ARCCA, Redwood Building,
King Edward VII Avenue,
Cardiff, CF10 3NB

David Simpson - peiriannydd uwch systemau
ARCCA, Adeilad Redwood,
King Edward VII Avenue,
Caerdydd, CF10 3NB

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Stefan G. Weichinger]

Am 18.07.19 um 13:49 schrieb Stefan G. Weichinger:
> Am 18.07.19 um 13:45 schrieb Stefan G. Weichinger:
>> Am 18.07.19 um 10:44 schrieb Diego Zuccato:
>>> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>>>
 Add the same pattern near line 757:
 return if $line =~ /^Unable to initialize messaging context/;
>>> Tks! Applied. Hope it gets included in next update!
>>>
>>
>> https://github.com/zmanda/amanda/pull/111
> 
> hm, sorry, should have rebased that ... or so.
> 

Does someone have patches in place for this ACCESS_DENIED issue
mentioned here:

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

I am currently unsure when it is safe to ignore these messages.

And I have amsamba-DLEs with dozens of these messages.

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Stefan G. Weichinger]

Am 18.07.19 um 13:45 schrieb Stefan G. Weichinger:
> Am 18.07.19 um 10:44 schrieb Diego Zuccato:
>> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>>
>>> Add the same pattern near line 757:
>>> return if $line =~ /^Unable to initialize messaging context/;
>> Tks! Applied. Hope it gets included in next update!
>>
> 
> https://github.com/zmanda/amanda/pull/111

hm, sorry, should have rebased that ... or so.

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Stefan G. Weichinger]

Am 18.07.19 um 10:44 schrieb Diego Zuccato:
> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
> 
>> Add the same pattern near line 757:
>> return if $line =~ /^Unable to initialize messaging context/;
> Tks! Applied. Hope it gets included in next update!
> 

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

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Diego Zuccato]

Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:

> Add the same pattern near line 757:
> return if $line =~ /^Unable to initialize messaging context/;
Tks! Applied. Hope it gets included in next update!

-- 
Diego Zuccato
Servizi Informatici
Dip. di Fisica e Astronomia (DIFA) - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
mail: diego.zucc...@unibo.it

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Stefan G. Weichinger]

Am 17.07.19 um 19:04 schrieb Jean-Louis Martineau:
> Add the same pattern near line 757:
> return if $line =~ /^Unable to initialize messaging context/;

Oh, Jean-Louis, nice to read you!

thanks for the missing line, yes, now my first test dump is free of that
error.

Do we have a PR somewhere for this, should I file one?

Thanks, regards, Stefan

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Jean-Louis Martineau]

Add the same pattern near line 757:
   return if $line =~ /^Unable to initialize messaging context/;

From: owner-amanda-us...@amanda.org  on behalf 
of Stefan G. Weichinger 
Sent: July 17, 2019 12:52 PM
To: Diego Zuccato; AMANDA users
Subject: Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: 
Application 'amsamba': exited with status 1

Am 16.07.19 um 10:07 schrieb Stefan G. Weichinger:
> Am 16.07.19 um 09:14 schrieb Diego Zuccato:
>> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
>>
>>> I never figured out the correct patch ;-)
>>> Pls show your change, I want to give it another try.
>> Here it is.
>> -8<--
>> # diff -u amsamba.ori amsamba
>> --- amsamba.ori  2019-07-16 09:09:28.430585521 +0200
>> +++ amsamba  2019-07-10 11:02:13.352987193 +0200
>> @@ -462,6 +462,7 @@
>>  debug("stderr: " . $_);
>>  next if /^Domain=/;
>>  next if /^WARNING/g;
>> +next if /^Unable to initialize messaging context/g;
>>  # message if samba server is configured with 'security = share'
>>  next if /Server not using user level security and no password 
>> supplied./;
>>  $self->print_to_server("smbclient: $_",
>> @@ -554,6 +555,7 @@
>>  next if /^Domain=/;
>>  next if /dumped \d+ files and directories/;
>>  next if /^WARNING/g;
>> +next if /^Unable to initialize messaging context/g;
>>  # message if samba server is configured with 'security = share'
>>  next if /Server not using user level security and no password 
>> supplied./;
>>  debug("stderr: $_");
>> -8<--
>
> thanks, applied, check tmrw (after amdump over night)

I still get these messages (double-checked: yes, it's the server with
the patch applied)


/-- pre01svdeb02 ntcs-pgmdata lev 1 STRANGE
  sendbackup: info BACKUP=APPLICATION
  sendbackup: info APPLICATION=amsamba
  sendbackup: info RECOVER_CMD=/bin/gzip -dc
|/usr/lib/amanda/application/amsamba restore [./file-to-restore]+
  sendbackup: info COMPRESS_SUFFIX=.gz
  sendbackup: info end
  ? smbclient: Unable to initialize messaging context
  sendbackup: size 52576.4208984375
  sendbackup: native-CRC eb374f92:55162880
  sendbackup: client-CRC bb9be9c1:8157700
  sendbackup: end
  \


This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Stefan G. Weichinger]

Am 16.07.19 um 10:07 schrieb Stefan G. Weichinger:
> Am 16.07.19 um 09:14 schrieb Diego Zuccato:
>> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
>>
>>> I never figured out the correct patch ;-)
>>> Pls show your change, I want to give it another try.
>> Here it is.
>> -8<--
>> # diff -u amsamba.ori amsamba
>> --- amsamba.ori  2019-07-16 09:09:28.430585521 +0200
>> +++ amsamba  2019-07-10 11:02:13.352987193 +0200
>> @@ -462,6 +462,7 @@
>>  debug("stderr: " . $_);
>>  next if /^Domain=/;
>>  next if /^WARNING/g;
>> +next if /^Unable to initialize messaging context/g;
>>  # message if samba server is configured with 'security = share'
>>  next if /Server not using user level security and no password 
>> supplied./;
>>  $self->print_to_server("smbclient: $_",
>> @@ -554,6 +555,7 @@
>>  next if /^Domain=/;
>>  next if /dumped \d+ files and directories/;
>>  next if /^WARNING/g;
>> +next if /^Unable to initialize messaging context/g;
>>  # message if samba server is configured with 'security = share'
>>  next if /Server not using user level security and no password 
>> supplied./;
>>  debug("stderr: $_");
>> -8<--
> 
> thanks, applied, check tmrw (after amdump over night)

I still get these messages (double-checked: yes, it's the server with
the patch applied)


/-- pre01svdeb02 ntcs-pgmdata lev 1 STRANGE
  sendbackup: info BACKUP=APPLICATION
  sendbackup: info APPLICATION=amsamba
  sendbackup: info RECOVER_CMD=/bin/gzip -dc
|/usr/lib/amanda/application/amsamba restore [./file-to-restore]+
  sendbackup: info COMPRESS_SUFFIX=.gz
  sendbackup: info end
  ? smbclient: Unable to initialize messaging context
  sendbackup: size 52576.4208984375
  sendbackup: native-CRC eb374f92:55162880
  sendbackup: client-CRC bb9be9c1:8157700
  sendbackup: end
  \

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Stefan G. Weichinger]

Am 16.07.19 um 09:14 schrieb Diego Zuccato:
> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
> 
>> I never figured out the correct patch ;-)
>> Pls show your change, I want to give it another try.
> Here it is.
> -8<--
> # diff -u amsamba.ori amsamba
> --- amsamba.ori   2019-07-16 09:09:28.430585521 +0200
> +++ amsamba   2019-07-10 11:02:13.352987193 +0200
> @@ -462,6 +462,7 @@
>   debug("stderr: " . $_);
>   next if /^Domain=/;
>   next if /^WARNING/g;
> + next if /^Unable to initialize messaging context/g;
>   # message if samba server is configured with 'security = share'
>   next if /Server not using user level security and no password 
> supplied./;
>   $self->print_to_server("smbclient: $_",
> @@ -554,6 +555,7 @@
>   next if /^Domain=/;
>   next if /dumped \d+ files and directories/;
>   next if /^WARNING/g;
> + next if /^Unable to initialize messaging context/g;
>   # message if samba server is configured with 'security = share'
>   next if /Server not using user level security and no password 
> supplied./;
>   debug("stderr: $_");
> -8<--

thanks, applied, check tmrw (after amdump over night)

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Diego Zuccato]

Il 12/07/19 15:23, Diego Zuccato ha scritto:

> define dumptype win {
> auth "local"
> #estimate client
> #compress server custom
> #server-custom-compress "/usr/bin/pigz"
> program "APPLICATION"
> application {
>   plugin "amsamba"
>   property "AMANDAPASS" "/etc/amanda/daily/pass"
> }
> }
> (note the commented lines), I get a different error:
> FAILURE DUMP SUMMARY:
>   localhost //192.168.48.41/port lev 0  FAILED [data timeout]
>   localhost //192.168.48.41/port lev 0  FAILED [Got empty header]
>   localhost //192.168.48.41/port lev 0  FAILED [data timeout]
>   localhost //192.168.48.41/port lev 0  FAILED [Got empty header]
I finally managed to find the issue: seems newer amsamba does not like
local auth!
When changed to bsdtcp, it all started working again.

I'd prefer using local, but if bsdtcp is needed I'll use it :)

-- 
Diego Zuccato
Servizi Informatici
Dip. di Fisica e Astronomia (DIFA) - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
mail: diego.zucc...@unibo.it

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Diego Zuccato]

Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:

> I never figured out the correct patch ;-)
> Pls show your change, I want to give it another try.
Here it is.
-8<--
# diff -u amsamba.ori amsamba
--- amsamba.ori 2019-07-16 09:09:28.430585521 +0200
+++ amsamba 2019-07-10 11:02:13.352987193 +0200
@@ -462,6 +462,7 @@
debug("stderr: " . $_);
next if /^Domain=/;
next if /^WARNING/g;
+   next if /^Unable to initialize messaging context/g;
# message if samba server is configured with 'security = share'
next if /Server not using user level security and no password 
supplied./;
$self->print_to_server("smbclient: $_",
@@ -554,6 +555,7 @@
next if /^Domain=/;
next if /dumped \d+ files and directories/;
next if /^WARNING/g;
+   next if /^Unable to initialize messaging context/g;
# message if samba server is configured with 'security = share'
next if /Server not using user level security and no password 
supplied./;
debug("stderr: $_");
-8<--

But backups are still marked "strange". Seems it's not enough to ignore
it in amsamba... Maybe someone else can find the right fix...

-- 
Diego Zuccato
Servizi Informatici
Dip. di Fisica e Astronomia (DIFA) - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
mail: diego.zucc...@unibo.it

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Stefan G. Weichinger]

Am 10.07.19 um 14:17 schrieb Diego Zuccato:

> Too bad the patch given here:
> http://www.backupcentral.com/forum/14/292396/smbclient_usage_fails_with__unable_to_initialize_messaging_context_
> is not in packaged version (3.5.1) yet.
> 
> Adding the two lines, in my case, fixes the amcheck issue.

I never figured out the correct patch ;-)

Pls show your change, I want to give it another try.

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Diego Zuccato]

Il 10/07/19 14:23, Diego Zuccato ha scritto:

>> Too bad amdump fails after quite a long time with:
>> FAILED [data timeout]
>> FAILED [Error accepting incoming connection: Connection timed out]
>> Which incoming connection is it referring to???
I tried trplacing tcpd (default dep of Debian package) with xinetd but
the error remains the same.

If I change slightly the config for that dumptype to
define dumptype win {
auth "local"
#estimate client
#compress server custom
#server-custom-compress "/usr/bin/pigz"
program "APPLICATION"
application {
plugin "amsamba"
property "AMANDAPASS" "/etc/amanda/daily/pass"
}
}
(note the commented lines), I get a different error:
FAILURE DUMP SUMMARY:
  localhost //192.168.48.41/port lev 0  FAILED [data timeout]
  localhost //192.168.48.41/port lev 0  FAILED [Got empty header]
  localhost //192.168.48.41/port lev 0  FAILED [data timeout]
  localhost //192.168.48.41/port lev 0  FAILED [Got empty header]

I also see two gzip processes instead of just one:
30897 backup 20   0  2540  1496  1216 S  0.0  0.0  0:00.08 /bin/gzip
--fast
30900 backup 20   0  2540   756   692 S  0.0  0.0  0:00.00 /bin/gzip
--best
30902 backup 20   0 48472 31732 13740 S  0.0  0.4  0:00.28
/usr/bin/perl /usr/lib/amanda/application/amsamba backup --message line
--config daily --host localhost --disk //192.168.48.41/port --device
//192.168.48.41/port --level 0 --index line --record --amandapass
/etc/amanda/daily/pass
30905 backup 20   0 72244 17492 14916 S  0.0  0.2  0:00.14
/usr/bin/smbclient //192.168.48.41/portinerie -d 0 -U Backup -E -W MGMT
-c tarmode full reset hidden system quiet; tar c -
30906 backup 20   0  5612  1040   896 S  0.0  0.0  0:00.00 /bin/tar
-tf -
And when pigz is configured I still see a gzip process...

> Any hint?
Please help!

-- 
Diego Zuccato
Servizi Informatici
Dip. di Fisica e Astronomia (DIFA) - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
mail: diego.zucc...@unibo.it

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Diego Zuccato]

Il 10/07/19 14:17, Diego Zuccato ha scritto:

> Too bad amdump fails after quite a long time with:
> FAILED [data timeout]
> FAILED [Error accepting incoming connection: Connection timed out]
> 
> Which incoming connection is it referring to???
Forgot to say that:
1) if I place the wrong password in the pass file, it fails immediatly
2) launching smbclient from command line works:
# sudo -u backup smbclient //192.168.48.41/port -d 0 -U Backup -E -W
MGMT -c ls\;quit
Unable to initialize messaging context
Enter MGMT\Backup's password:
  .   D0  Wed Jun 12 08:17:51 2019
  ..  D0  Wed Jun 12 08:17:51 2019
[...files and folders...]

314572543 blocks of size 4096. 48702724 blocks available

Any hint?
Tks.

-- 
Diego Zuccato
Servizi Informatici
Dip. di Fisica e Astronomia (DIFA) - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
mail: diego.zucc...@unibo.it

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Diego Zuccato]

Il 09/07/19 18:22, Tobias Koeck ha scritto:

> It seems to break only 'amcheck a2g-2' right now. The 'amdump' command
> seems to be dumping and writing it anway so it doesn't seem that super
> urgent.
I just upgraded to Debian 10, too, to check if that would fix my issues
with amsamba.
Too bad the patch given here:
http://www.backupcentral.com/forum/14/292396/smbclient_usage_fails_with__unable_to_initialize_messaging_context_
is not in packaged version (3.5.1) yet.

Adding the two lines, in my case, fixes the amcheck issue.

Too bad amdump fails after quite a long time with:
FAILED [data timeout]
FAILED [Error accepting incoming connection: Connection timed out]

Which incoming connection is it referring to???

-- 
Diego Zuccato
Servizi Informatici
Dip. di Fisica e Astronomia (DIFA) - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
mail: diego.zucc...@unibo.it

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Charles Curley]

On Mon, 8 Jul 2019 17:51:44 +0200
Tobias Koeck  wrote:

> Hi,
>
> since I have upgraded to Debian 10 I get strange amsamba errors.
>
> Any ideas why?

I'm no expert on Samba. However, while upgrading from Debian stretch
(9.x) to buster (10.0), I saw the following notices which may be
relevant here:

1)

--

samba (2:4.6.5+dfsg-5) unstable; urgency=medium

The samba service has been removed. Use the individual services instead:

* nmbd
* smbd
* samba-ad-dc

 -- Mathieu Parent   Tue, 18 Jul 2017 22:52:05 +0200

--

2)

--

If your computer gets IP address information from a DHCP server on the
network, the DHCP server may also provide information about WINS
servers ("NetBIOS name servers") present on the network.  This
requires a change to your smb.conf file so that DHCP-provided WINS
settings will automatically be read from /var/lib/samba/dhcp.conf.

The dhcp-client package must be installed to take advantage of this
feature.  Modify smb.conf to use WINS settings from DHCP?

--



-- 
"When we talk of civilization, we are too apt to limit the meaning of
the word to its mere embellishments, such as arts and sciences; but
the true distinction between it and barbarism is, that the one
presents a state of society under the protection of just and
well-administered law, and the other is left to the chance government
of brute force."
- The Rev. James White, Eighteen Christian Centuries, 1889
Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB
https://charlescurley.com

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Tobias Koeck]

Hi Jose,

thank's for responding.

It seems to break only 'amcheck a2g-2' right now. The 'amdump' command 
seems to be dumping and writing it anway so it doesn't seem that super 
urgent.


Still amcheck won't work for Windows network shares so no way to know if 
it works before you tried amdump. :-)


I have put a bug report to the smbclient package, too.

Greetings
Tobias

On 7/9/19 4:56 PM, Jose M Calhariz wrote:

Hi,

I do not have a setup for testing amsamba, but I will do my the best
next week.  I am going to DebConf19 and should have time to look into
it.

Kind regards
Jose M Calhariz

On Mon, Jul 08, 2019 at 05:51:44PM +0200, Tobias Koeck wrote:

Hi,

since I have upgraded to Debian 10 I get strange amsamba errors.

Any ideas why?
---

for amcheck a2g-2 I'll get for the samba checks

HOST localhost ERROR: smbclient: Unable to initialize messaging context
HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited
with status 1

The Amsamba* file shows the following output

on Jul 08 12:01:25.509075732 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: pid 2464 ruid 34 euid 34 version 3.5.1: start at Mon Jul  8
12:01:25 2019
Mon Jul 08 12:01:25.510363259 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: Arguments: selfcheck
Mon Jul 08 12:01:25.574864631 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: pid 2464 ruid 34 euid 34 version 3.5.1: rename at Mon Jul  8
12:01:25 2019
Mon Jul 08 12:01:25.574918101 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: application: Amsamba
Mon Jul 08 12:01:25.574971869 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: warning: Use of uninitialized value $regex_match in pattern
match (m//) at /usr/lib/amanda/application/amsamba line 92.
Mon Jul 08 12:01:25.575022213 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: Arguments: selfcheck --message line --config a2g-2 --host
localhost --disk //192.168.0.250/ftp --device //192.168.0.250/ftp
--index line --record --amandapass /etc/amandapass
Mon Jul 08 12:01:25.575041181 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: command: selfcheck
Mon Jul 08 12:01:25.575069629 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: disk //192.168.0.250/ftp
Mon Jul 08 12:01:25.575083965 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: amsamba version 3.5.1
Mon Jul 08 12:01:25.614619170 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: amsamba smbclient-version 4.9.5-Debian
Mon Jul 08 12:01:25.614697420 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: /usr/bin/smbclient
Mon Jul 08 12:01:25.614786687 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: amandapass: /etc/amandapass
Mon Jul 08 12:01:25.616603666 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: password_wtr 4
Mon Jul 08 12:01:25.616620367 2019: pid 2466: thd-0x55b9ce332000:
Amsamba: password_rdr 3
Mon Jul 08 12:01:25.616742029 2019: pid 2466: thd-0x55b9ce332000:
Amsamba: warning: close() on unopened filehandle 1 at
/usr/lib/amanda/application/amsamba line 428.
Mon Jul 08 12:01:25.616817693 2019: pid 2466: thd-0x55b9ce332000:
Amsamba: warning: close() on unopened filehandle 2 at
/usr/lib/amanda/application/amsamba line 429.
Mon Jul 08 12:01:25.616890194 2019: pid 2466: thd-0x55b9ce332000:
Amsamba: execute: /usr/bin/smbclient /usr/bin/smbclient
//192.168.0.250/ftp -U backup -E -c quit
Mon Jul 08 12:01:25.647162371 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: stderr: WARNING: The "syslog" option is deprecated
Mon Jul 08 12:01:25.647300656 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: stderr: Unable to initialize messaging context
Mon Jul 08 12:01:25.647333909 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: smbclient: Unable to initialize messaging context
Mon Jul 08 12:01:25.647416879 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: stderr: WARNING: The "syslog" option is deprecated
Mon Jul 08 12:01:25.703629806 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_utime   : 0
Mon Jul 08 12:01:25.703651035 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_stime   : 0
Mon Jul 08 12:01:25.703658632 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_maxrss  : 32104
Mon Jul 08 12:01:25.703665341 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_ixrss   : 0
Mon Jul 08 12:01:25.703671709 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_idrss   : 0
Mon Jul 08 12:01:25.703677904 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_isrss   : 0
Mon Jul 08 12:01:25.703684089 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_minflt  : 5399
Mon Jul 08 12:01:25.703690386 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_majflt  : 0
Mon Jul 08 12:01:25.703696679 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_nswap   : 0
Mon Jul 08 12:01:25.703702963 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_inblock : 256
Mon Jul 08 12:01:25.703709143 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_oublock : 16
Mon Jul 08 12:01:25.703715213 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_msgsnd  : 0
Mon Jul 08 12:01:25.703721198 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_msgrcv  : 0
Mon Jul 08 12:01:25.703727193 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_nsignals: 0
Mon Jul 0

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Jose M Calhariz]

Hi,

I do not have a setup for testing amsamba, but I will do my the best
next week.  I am going to DebConf19 and should have time to look into
it.

Kind regards
Jose M Calhariz

On Mon, Jul 08, 2019 at 05:51:44PM +0200, Tobias Koeck wrote:
> Hi,
> 
> since I have upgraded to Debian 10 I get strange amsamba errors.
> 
> Any ideas why?
> ---
> 
> for amcheck a2g-2 I'll get for the samba checks
> 
> HOST localhost ERROR: smbclient: Unable to initialize messaging context
> HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited
> with status 1
> 
> The Amsamba* file shows the following output
> 
> on Jul 08 12:01:25.509075732 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: pid 2464 ruid 34 euid 34 version 3.5.1: start at Mon Jul  8
> 12:01:25 2019
> Mon Jul 08 12:01:25.510363259 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: Arguments: selfcheck
> Mon Jul 08 12:01:25.574864631 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: pid 2464 ruid 34 euid 34 version 3.5.1: rename at Mon Jul  8
> 12:01:25 2019
> Mon Jul 08 12:01:25.574918101 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: application: Amsamba
> Mon Jul 08 12:01:25.574971869 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: warning: Use of uninitialized value $regex_match in pattern
> match (m//) at /usr/lib/amanda/application/amsamba line 92.
> Mon Jul 08 12:01:25.575022213 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: Arguments: selfcheck --message line --config a2g-2 --host
> localhost --disk //192.168.0.250/ftp --device //192.168.0.250/ftp
> --index line --record --amandapass /etc/amandapass
> Mon Jul 08 12:01:25.575041181 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: command: selfcheck
> Mon Jul 08 12:01:25.575069629 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: disk //192.168.0.250/ftp
> Mon Jul 08 12:01:25.575083965 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: amsamba version 3.5.1
> Mon Jul 08 12:01:25.614619170 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: amsamba smbclient-version 4.9.5-Debian
> Mon Jul 08 12:01:25.614697420 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: /usr/bin/smbclient
> Mon Jul 08 12:01:25.614786687 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: amandapass: /etc/amandapass
> Mon Jul 08 12:01:25.616603666 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: password_wtr 4
> Mon Jul 08 12:01:25.616620367 2019: pid 2466: thd-0x55b9ce332000:
> Amsamba: password_rdr 3
> Mon Jul 08 12:01:25.616742029 2019: pid 2466: thd-0x55b9ce332000:
> Amsamba: warning: close() on unopened filehandle 1 at
> /usr/lib/amanda/application/amsamba line 428.
> Mon Jul 08 12:01:25.616817693 2019: pid 2466: thd-0x55b9ce332000:
> Amsamba: warning: close() on unopened filehandle 2 at
> /usr/lib/amanda/application/amsamba line 429.
> Mon Jul 08 12:01:25.616890194 2019: pid 2466: thd-0x55b9ce332000:
> Amsamba: execute: /usr/bin/smbclient /usr/bin/smbclient
> //192.168.0.250/ftp -U backup -E -c quit
> Mon Jul 08 12:01:25.647162371 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: stderr: WARNING: The "syslog" option is deprecated
> Mon Jul 08 12:01:25.647300656 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: stderr: Unable to initialize messaging context
> Mon Jul 08 12:01:25.647333909 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: smbclient: Unable to initialize messaging context
> Mon Jul 08 12:01:25.647416879 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: stderr: WARNING: The "syslog" option is deprecated
> Mon Jul 08 12:01:25.703629806 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_utime   : 0
> Mon Jul 08 12:01:25.703651035 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_stime   : 0
> Mon Jul 08 12:01:25.703658632 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_maxrss  : 32104
> Mon Jul 08 12:01:25.703665341 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_ixrss   : 0
> Mon Jul 08 12:01:25.703671709 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_idrss   : 0
> Mon Jul 08 12:01:25.703677904 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_isrss   : 0
> Mon Jul 08 12:01:25.703684089 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_minflt  : 5399
> Mon Jul 08 12:01:25.703690386 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_majflt  : 0
> Mon Jul 08 12:01:25.703696679 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_nswap   : 0
> Mon Jul 08 12:01:25.703702963 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_inblock : 256
> Mon Jul 08 12:01:25.703709143 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_oublock : 16
> Mon Jul 08 12:01:25.703715213 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_msgsnd  : 0
> Mon Jul 08 12:01:25.703721198 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_msgrcv  : 0
> Mon Jul 08 12:01:25.703727193 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_nsignals: 0
> Mon Jul 08 12:01:25.703733198 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_nvcsw   : 11
> Mon Jul 08 12:01:25.703739145 2019: pid 2464: thd-0x55b9ce332000:
> Amsamba: ru_nivcsw  : 31
> Mon Jul 08 12:01:25.703904507 2019: pid 2464: thd-0x5

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Nathan Stratton Treadway]

On Mon, Jul 08, 2019 at 17:51:44 +0200, Tobias Koeck wrote:
> Hi,
> 
> since I have upgraded to Debian 10 I get strange amsamba errors.
> 
> Any ideas why?
[...]
> Mon Jul 08 12:01:25.616890194 2019: pid 2466: thd-0x55b9ce332000: Amsamba: 
> execute: /usr/bin/smbclient /usr/bin/smbclient  //192.168.0.250/ftp -U backup 
> -E -c quit
> Mon Jul 08 12:01:25.647162371 2019: pid 2464: thd-0x55b9ce332000: Amsamba: 
> stderr: WARNING: The "syslog" option is deprecated
> Mon Jul 08 12:01:25.647300656 2019: pid 2464: thd-0x55b9ce332000: Amsamba: 
> stderr: Unable to initialize messaging context
> Mon Jul 08 12:01:25.647333909 2019: pid 2464: thd-0x55b9ce332000: Amsamba: 
> smbclient: Unable to initialize messaging context

I don't have any ideas for this particular error, but if no one else has
any better suggestions, my next step would be to try running smbclient
commands manually from the command line (i.e.  "smbclient
//192.168.0.250/ftp -U backup -E -c quit" and similar commands) to see
if you get the same messages.  If so, that would indicate the issue is
within the Debian 10 samba package and related configuration files
directly; if not you would know it's something more specific to the
context in which Amsamba is kicking off the smbclient executable...

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

amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

[Tobias Koeck]

Hi,

since I have upgraded to Debian 10 I get strange amsamba errors.

Any ideas why?
---

for amcheck a2g-2 I'll get for the samba checks

HOST localhost ERROR: smbclient: Unable to initialize messaging context
HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited
with status 1

The Amsamba* file shows the following output

on Jul 08 12:01:25.509075732 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: pid 2464 ruid 34 euid 34 version 3.5.1: start at Mon Jul  8
12:01:25 2019
Mon Jul 08 12:01:25.510363259 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: Arguments: selfcheck
Mon Jul 08 12:01:25.574864631 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: pid 2464 ruid 34 euid 34 version 3.5.1: rename at Mon Jul  8
12:01:25 2019
Mon Jul 08 12:01:25.574918101 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: application: Amsamba
Mon Jul 08 12:01:25.574971869 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: warning: Use of uninitialized value $regex_match in pattern
match (m//) at /usr/lib/amanda/application/amsamba line 92.
Mon Jul 08 12:01:25.575022213 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: Arguments: selfcheck --message line --config a2g-2 --host
localhost --disk //192.168.0.250/ftp --device //192.168.0.250/ftp
--index line --record --amandapass /etc/amandapass
Mon Jul 08 12:01:25.575041181 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: command: selfcheck
Mon Jul 08 12:01:25.575069629 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: disk //192.168.0.250/ftp
Mon Jul 08 12:01:25.575083965 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: amsamba version 3.5.1
Mon Jul 08 12:01:25.614619170 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: amsamba smbclient-version 4.9.5-Debian
Mon Jul 08 12:01:25.614697420 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: /usr/bin/smbclient
Mon Jul 08 12:01:25.614786687 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: amandapass: /etc/amandapass
Mon Jul 08 12:01:25.616603666 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: password_wtr 4
Mon Jul 08 12:01:25.616620367 2019: pid 2466: thd-0x55b9ce332000:
Amsamba: password_rdr 3
Mon Jul 08 12:01:25.616742029 2019: pid 2466: thd-0x55b9ce332000:
Amsamba: warning: close() on unopened filehandle 1 at
/usr/lib/amanda/application/amsamba line 428.
Mon Jul 08 12:01:25.616817693 2019: pid 2466: thd-0x55b9ce332000:
Amsamba: warning: close() on unopened filehandle 2 at
/usr/lib/amanda/application/amsamba line 429.
Mon Jul 08 12:01:25.616890194 2019: pid 2466: thd-0x55b9ce332000:
Amsamba: execute: /usr/bin/smbclient /usr/bin/smbclient
//192.168.0.250/ftp -U backup -E -c quit
Mon Jul 08 12:01:25.647162371 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: stderr: WARNING: The "syslog" option is deprecated
Mon Jul 08 12:01:25.647300656 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: stderr: Unable to initialize messaging context
Mon Jul 08 12:01:25.647333909 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: smbclient: Unable to initialize messaging context
Mon Jul 08 12:01:25.647416879 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: stderr: WARNING: The "syslog" option is deprecated
Mon Jul 08 12:01:25.703629806 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_utime   : 0
Mon Jul 08 12:01:25.703651035 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_stime   : 0
Mon Jul 08 12:01:25.703658632 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_maxrss  : 32104
Mon Jul 08 12:01:25.703665341 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_ixrss   : 0
Mon Jul 08 12:01:25.703671709 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_idrss   : 0
Mon Jul 08 12:01:25.703677904 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_isrss   : 0
Mon Jul 08 12:01:25.703684089 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_minflt  : 5399
Mon Jul 08 12:01:25.703690386 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_majflt  : 0
Mon Jul 08 12:01:25.703696679 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_nswap   : 0
Mon Jul 08 12:01:25.703702963 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_inblock : 256
Mon Jul 08 12:01:25.703709143 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_oublock : 16
Mon Jul 08 12:01:25.703715213 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_msgsnd  : 0
Mon Jul 08 12:01:25.703721198 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_msgrcv  : 0
Mon Jul 08 12:01:25.703727193 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_nsignals: 0
Mon Jul 08 12:01:25.703733198 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_nvcsw   : 11
Mon Jul 08 12:01:25.703739145 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: ru_nivcsw  : 31
Mon Jul 08 12:01:25.703904507 2019: pid 2464: thd-0x55b9ce332000:
Amsamba: pid 2464 finish time Mon Jul  8 12:01:25 2019
:

Greetings
Tobias

Re: restored amanda client errors out

[Gene Heskett]

On Sunday 23 June 2019 10:49:17 Nathan Stratton Treadway wrote:

> On Sun, Jun 23, 2019 at 02:37:46 -0400, Gene Heskett wrote:
> > And at 2:30 the next morning I can report that it worked with no
> > complaints.
>
> Great.  And is it the case that amcheck is now happy for the DLEs on
> picnc which it previously gave the "Could not access /media/pi/
> [...] Permission denied" errors messages?
>
Yes, narry a whimper, Natham, thank you.
>   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



Copyright 2019 by Maurice E. Heskett
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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: restored amanda client errors out

[Nathan Stratton Treadway]

On Sun, Jun 23, 2019 at 02:37:46 -0400, Gene Heskett wrote:
> And at 2:30 the next morning I can report that it worked with no 
> complaints.

Great.  And is it the case that amcheck is now happy for the DLEs on
picnc which it previously gave the "Could not access /media/pi/
[...] Permission denied" errors messages?

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: restored amanda client errors out

[Gene Heskett]

On Saturday 22 June 2019 11:32:57 Gene Heskett wrote:

> On Saturday 22 June 2019 11:10:28 Nathan Stratton Treadway wrote:
> > On Sat, Jun 22, 2019 at 09:42:42 -0400, Gene Heskett wrote:
> > > Fails amcheck with
> > > amanda@coyote:/root$ /usr/local/sbin/amcheck Daily
> > > '/usr/local/etc/amanda/Daily/amanda.conf', line 487: application
> > > name expected: 0 12 '/usr/local/etc/amanda/Daily/amanda.conf',
> > > line 487: end of line is expected
> >
> > [...]
> >
> > > #program "GNUTAR"
> > > auth "bsdtcp"
> > >   allow-split true
> > > program "APPLICATION"
> > > application = "app_amgtar"  <--line 487
> >
> > There shouldn't be any "=" character on this line.
>
> Duh. ... amcheck works normally.  We'll see how it runs tonight.
>
And at 2:30 the next morning I can report that it worked with no 
complaints.

Thank you Nathan
>
> > 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
>
> Cheers, Gene Heskett



Copyright 2019 by Maurice E. Heskett
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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: restored amanda client errors out

[Gene Heskett]

On Saturday 22 June 2019 11:10:28 Nathan Stratton Treadway wrote:

> On Sat, Jun 22, 2019 at 09:42:42 -0400, Gene Heskett wrote:
> > Fails amcheck with
> > amanda@coyote:/root$ /usr/local/sbin/amcheck Daily
> > '/usr/local/etc/amanda/Daily/amanda.conf', line 487: application
> > name expected: 0 12 '/usr/local/etc/amanda/Daily/amanda.conf', line
> > 487: end of line is expected
>
> [...]
>
> > #program "GNUTAR"
> > auth "bsdtcp"
> > allow-split true
> > program "APPLICATION"
> > application = "app_amgtar"  <--line 487
>
> There shouldn't be any "=" character on this line.
>
Duh. ... amcheck works normally.  We'll see how it runs tonight.

Thank you Nathan
>   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


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: restored amanda client errors out

[Nathan Stratton Treadway]

On Sat, Jun 22, 2019 at 09:42:42 -0400, Gene Heskett wrote:
> Fails amcheck with
> amanda@coyote:/root$ /usr/local/sbin/amcheck Daily
> '/usr/local/etc/amanda/Daily/amanda.conf', line 487: application name 
> expected: 0 12
> '/usr/local/etc/amanda/Daily/amanda.conf', line 487: end of line is expected
[...]
> #program "GNUTAR"
> auth "bsdtcp"
>   allow-split true
> program "APPLICATION"
> application = "app_amgtar"  <--line 487

There shouldn't be any "=" character on this line.

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: restored amanda client errors out

[Gene Heskett]

On Friday 21 June 2019 22:14:20 Nathan Stratton Treadway wrote:

> On Fri, Jun 21, 2019 at 20:26:26 -0400, Gene Heskett wrote:
> > You may have brought something to my attention, I know for a fact
> > that the amanda.conf on this server machine is using amgtar.
> >
> > define application-tool app_amgtar {
> >  comment "amgtar"
> >  plugin  "amgtar"
>
> [...]
>
> > later in that file however,
> >
> > define dumptype dt_amgtar {
> > program "APPLICATION"
> > application "app_amgtar"
> > index yes
> > }
> >
> > define dumptype global {
> > comment "Global definitions"
> > # This is quite useful for setting global parameters, so you
> > don't have
> > # to type them everywhere.  All dumptype definitions in this
> > sample file
> > # do include these definitions, either directly or indirectly.
> > # There's nothing special about the name `global'; if you create
> > any # dumptype that does not contain the word `global' or the name
> > of any # other dumptype that contains it, these definitions won't
> > apply. # Note that these definitions may be overridden in other #
> > dumptypes, if the redefinitions appear *after* the `global' #
> > dumptype name.
> > # You may want to use this for globally enabling or disabling
> > # indexing, recording, etc.  Some examples:
> > index yes
> > program "GNUTAR"
> >auth "bsdtcp"
> >allow-split true
> >
> >
> > But as can be seen, the global dumptype never got changed, it still
> > says GNUTAR!!  What is the proper syntax?  I'll change it before the
> > run tonight.
> >
> > But at the same time I don't know what the "canned at another farm"
> > clients are running. ATM I up to my butt in something else, but I
> > will see about it over the weekend.
>
> If you want to keep the changes as minimal as possible, you might just
> want to change the disklist entries for that client machine to use
> "dt_amgtar" instead of "global" -- that will leave the other DLEs
> unchanged.
>
> In long run if you want to change the global default you would just
> edit the global dumptype definition to replace
>   program "GNUTAR"
> with
>   program "APPLICATION"
>   application "app_amgtar"
>
> (given that the application "app_amgtar" already exists in your .conf
> file).
>
Fails amcheck with
amanda@coyote:/root$ /usr/local/sbin/amcheck Daily
'/usr/local/etc/amanda/Daily/amanda.conf', line 487: application name expected: 
0 12
'/usr/local/etc/amanda/Daily/amanda.conf', line 487: end of line is expected

at line 217 in amanda.conf:
define application-tool app_amgtar {
 comment "amgtar"
 plugin  "amgtar"
 #property "GNUTAR-PATH" "/path/to/gtar"
 #property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir"
 #default from gnutar_list_dir setting in amanda-client.conf
 property "ONE-FILE-SYSTEM" "yes"  #use '--one-file-system' option
 #property "SPARSE" "yes"   #use '--sparse' option
 #property "ATIME-PRESERVE" "yes"   #use '--atime-preserve=system' option
 property "CHECK-DEVICE" "no"   #use '--no-check-device' if set to "no"
 property "IGNORE" ": socket ignored$"
# property append "IGNORE" ": Directory is new$"
# property append "IGNORE" ": Directory has been renamed"
 property append "IGNORE" "file changed as we read it$"
}

Then at line 463:
define dumptype dt_amgtar {
program "APPLICATION"
application "app_amgtar"
index yes
}

And:
define dumptype global {
comment "Global definitions"
# This is quite useful for setting global parameters, so you don't have
# to type them everywhere.  All dumptype definitions in this sample file
# do include these definitions, either directly or indirectly.
# There's nothing special about the name `global'; if you create any
# dumptype that does not contain the word `global' or the name of any
# other dumptype that contains it, these definitions won't apply.
# Note that these definitions may be overridden in other
# dumptypes, if the redefinitions appear *after* the `global'
# dumptype name.
# You may want to use this for globally enabling or disabling
# indexing, recording, etc.  Some examples:
index yes
#program "GNUTAR"
auth "bsdtcp"
allow-split true
program "APPLICATION"
application = "app_amgtar"  <--line 487

# record no
#   splitsize   2000m
##   split_diskbuffer   "/dumps"
#   fallback_splitsize  64m

#   estimate calcsize
}
# end of "global"

Clearly, one of these is superfoulous(sp?) <_damnit I wish we had a spellchecker
with a real dictionary.

This amanda.conf has never been replaced, just edited as time & tech went by,
so I expect it does contain errors. Point them out please.

Thanks Nathan

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)
If we desire respect for the law, we must first make the law resp

Re: restored amanda client errors out

[Nathan Stratton Treadway]

On Fri, Jun 21, 2019 at 20:26:26 -0400, Gene Heskett wrote:

> You may have brought something to my attention, I know for a fact that 
> the amanda.conf on this server machine is using amgtar.
> 
> define application-tool app_amgtar {
>  comment "amgtar"
>  plugin  "amgtar"
[...]
> 
> later in that file however,
> 
> define dumptype dt_amgtar {
> program "APPLICATION"
> application "app_amgtar"
> index yes
> }
> 
> define dumptype global {
> comment "Global definitions"
> # This is quite useful for setting global parameters, so you don't 
> have
> # to type them everywhere.  All dumptype definitions in this sample 
> file
> # do include these definitions, either directly or indirectly.
> # There's nothing special about the name `global'; if you create any
> # dumptype that does not contain the word `global' or the name of any
> # other dumptype that contains it, these definitions won't apply.
> # Note that these definitions may be overridden in other
> # dumptypes, if the redefinitions appear *after* the `global'
> # dumptype name.
> # You may want to use this for globally enabling or disabling
> # indexing, recording, etc.  Some examples:
> index yes
> program "GNUTAR"
>auth "bsdtcp"
>allow-split true

> 
> But as can be seen, the global dumptype never got changed, it still says 
> GNUTAR!!  What is the proper syntax?  I'll change it before the run 
> tonight.  
>  
> 
> But at the same time I don't know what the "canned at another farm" 
> clients are running. ATM I up to my butt in something else, but I will 
> see about it over the weekend.

If you want to keep the changes as minimal as possible, you might just
want to change the disklist entries for that client machine to use
"dt_amgtar" instead of "global" -- that will leave the other DLEs
unchanged.

In long run if you want to change the global default you would just edit
the global dumptype definition to replace
  program "GNUTAR"
with
  program "APPLICATION"
  application "app_amgtar"

(given that the application "app_amgtar" already exists in your .conf
file).


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: restored amanda client errors out

[Gene Heskett]

On Friday 21 June 2019 16:07:02 Nathan Stratton Treadway wrote:

> On Fri, Jun 21, 2019 at 14:49:47 -0400, Gene Heskett wrote:
> > On Friday 21 June 2019 12:23:33 Nathan Stratton Treadway wrote:
> > > Have you tried using the amgtar application rather than GNUTAR
> > > anywhere?  With v3.5 on the server and Stretch on this client, you
>
> [...]
>
> > Been using its since around 2.4 IIRC.  Long long time anyway.
>
> Hmmm, that's strange.  In the Amanda Mail Report snippet you quoted in
> your original message, the sendbackup messages section for "picnc /"
> includes the line:
>   sendbackup: info BACKUP=/bin/tar
> , which is consistent with what I see for clients in my environment
> which are still using GNUTAR... while the newer clients using amgtar
> report these lines instead:
>   sendbackup: info BACKUP=APPLICATION
>   sendbackup: info APPLICATION=amgtar
>
> So... double check your "picnc" disklist entries and the associated
> dumptype definitions?
>
>   Nathan
>
You may have brought something to my attention, I know for a fact that 
the amanda.conf on this server machine is using amgtar.

define application-tool app_amgtar {
 comment "amgtar"
 plugin  "amgtar"
 #property "GNUTAR-PATH" "/path/to/gtar"
 #property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir"
 #default from gnutar_list_dir setting in amanda-client.conf
 property "ONE-FILE-SYSTEM" "yes"  #use '--one-file-system' option
 #property "SPARSE" "yes"   #use '--sparse' option
 #property "ATIME-PRESERVE" "yes"   #use '--atime-preserve=system' 
option
 property "CHECK-DEVICE" "no"   #use '--no-check-device' if set 
to "no"
 property "IGNORE" ": socket ignored$"
# property append "IGNORE" ": Directory is new$"
# property append "IGNORE" ": Directory has been renamed"
 property append "IGNORE" "file changed as we read it$"
}

later in that file however,

define dumptype dt_amgtar {
program "APPLICATION"
application "app_amgtar"
index yes
}

define dumptype global {
comment "Global definitions"
# This is quite useful for setting global parameters, so you don't 
have
# to type them everywhere.  All dumptype definitions in this sample 
file
# do include these definitions, either directly or indirectly.
# There's nothing special about the name `global'; if you create any
# dumptype that does not contain the word `global' or the name of any
# other dumptype that contains it, these definitions won't apply.
# Note that these definitions may be overridden in other
# dumptypes, if the redefinitions appear *after* the `global'
# dumptype name.
# You may want to use this for globally enabling or disabling
# indexing, recording, etc.  Some examples:
index yes
program "GNUTAR"
auth "bsdtcp"
allow-split true
:   #   program "APPLICATION"
# record no
#   splitsize   2000m
##   split_diskbuffer   "/dumps"
#   fallback_splitsize  64m

#   estimate calcsize
}

But as can be seen, the global dumptype never got changed, it still says 
GNUTAR!!  What is the proper syntax?  I'll change it before the run 
tonight.
   

But at the same time I don't know what the "canned at another farm" 
clients are running. ATM I up to my butt in something else, but I will 
see about it over the weekend.
> --
>-- 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


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: restored amanda client errors out

[Nathan Stratton Treadway]

On Fri, Jun 21, 2019 at 14:49:47 -0400, Gene Heskett wrote:
> On Friday 21 June 2019 12:23:33 Nathan Stratton Treadway wrote:
> > Have you tried using the amgtar application rather than GNUTAR
> > anywhere?  With v3.5 on the server and Stretch on this client, you
[...]
> Been using its since around 2.4 IIRC.  Long long time anyway.


Hmmm, that's strange.  In the Amanda Mail Report snippet you quoted in
your original message, the sendbackup messages section for "picnc /"
includes the line:
  sendbackup: info BACKUP=/bin/tar  
 
, which is consistent with what I see for clients in my environment
which are still using GNUTAR... while the newer clients using amgtar
report these lines instead:
  sendbackup: info BACKUP=APPLICATION   
 
  sendbackup: info APPLICATION=amgtar   
 

So... double check your "picnc" disklist entries and the associated
dumptype definitions?

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: restored amanda client errors out

[Gene Heskett]

On Friday 21 June 2019 12:23:33 Nathan Stratton Treadway wrote:

> On Fri, Jun 21, 2019 at 10:37:59 -0400, Gene Heskett wrote:
> > On Friday 21 June 2019 10:27:37 C. Scheeder wrote:
> > > Hi,
> > > As far as i recal this is an expected behavior for this version of
> > > amanda.
> > >
> > > short explanation:
> > >
> > > amcheck does all work as normal user, so if the user hasn't access
> > > to the full tree up to the root dir it will complain it can't
> > > access these dirs.
> > >
> > > amdump does the backups with elevated rights, so it can access
> > > these dirs without a problem.
> > >
> > > That isn't nice but i have learned to live with it
> >
> > Arrrgh, spit. But it is also the only explanation that makes any
> > sense, so I guess I'll have to do likewise.
>
> Gene, these DLEs are using GNUTAR dumptypes, right?

No, not in at least a decade, Nathan. I think, but haven't tried it, that 
my estimate phase might be too real.

> Have you tried using the amgtar application rather than GNUTAR
> anywhere?  With v3.5 on the server and Stretch on this client, you
> should be all set to switch.  I haven't actually tested your scenario
> myself, but I'm fairly certain that amgtar's design allows it to avoid
> this particular permission problem, so you might find this a good
> reason to make the switch to amgtar at this point

Been using its since around 2.4 IIRC.  Long long time anyway.

>   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


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: restored amanda client errors out

[Nathan Stratton Treadway]

On Fri, Jun 21, 2019 at 10:37:59 -0400, Gene Heskett wrote:
> On Friday 21 June 2019 10:27:37 C. Scheeder wrote:
> 
> > Hi,
> > As far as i recal this is an expected behavior for this version of
> > amanda.
> >
> > short explanation:
> >
> > amcheck does all work as normal user, so if the user hasn't access to
> > the full tree up to the root dir it will complain it can't access
> > these dirs.
> >
> > amdump does the backups with elevated rights, so it can access these
> > dirs without a problem.
> >
> > That isn't nice but i have learned to live with it
> 
> Arrrgh, spit. But it is also the only explanation that makes any sense, 
> so I guess I'll have to do likewise.

Gene, these DLEs are using GNUTAR dumptypes, right?

Have you tried using the amgtar application rather than GNUTAR
anywhere?  With v3.5 on the server and Stretch on this client, you
should be all set to switch.  I haven't actually tested your scenario
myself, but I'm fairly certain that amgtar's design allows it to avoid
this particular permission problem, so you might find this a good reason
to make the switch to amgtar at this point

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: restored amanda client errors out

[Gene Heskett]

On Friday 21 June 2019 10:27:37 C. Scheeder wrote:

> Hi,
> As far as i recal this is an expected behavior for this version of
> amanda.
>
> short explanation:
>
> amcheck does all work as normal user, so if the user hasn't access to
> the full tree up to the root dir it will complain it can't access
> these dirs.
>
> amdump does the backups with elevated rights, so it can access these
> dirs without a problem.
>
> That isn't nice but i have learned to live with it

Arrrgh, spit. But it is also the only explanation that makes any sense, 
so I guess I'll have to do likewise.

Thanks for such a quick answer Christoph.
>
> Cu Christoph
>
> Am 21.06.19 um 16:00 schrieb Gene Heskett:
> > I sent this yesterday around noon, but it never came back.  I've
> > also appended additional info at the bottom.
> >
> > resent msg=
> >
> > I just installed the stretch version of amanda common and amanda
> > client, with should have restored one of my machines to a full
> > backup status.
> >
> > Unforch, it didn't, and this situtation existed on the previous
> > jessie install, where a pi scatters its stuff over a larg e number
> > of mount points all attached to /, so basically nothing has actually
> > changed.
> >
> > But here is the emailed report from last nights run:
> > STRANGE DUMP DETAILS:
> >/-- picnc / lev 0 STRANGE
> >sendbackup: start [picnc:/ level 0]
> >sendbackup: info BACKUP=/bin/tar
> >sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
> >sendbackup: info end
> >? /bin/tar: ./dev: directory is on a different filesystem; not
> > dumped ? /bin/tar: ./proc: directory is on a different filesystem;
> > not dumped ? /bin/tar: ./run: directory is on a different
> > filesystem; not dumped ? /bin/tar: ./sys: directory is on a
> > different filesystem; not dumped ? /bin/tar: ./media/pi/backuppi:
> > directory is on a different filesystem; not dumped
> >? /bin/tar: ./media/pi/bootpi: directory is on a different
> > filesystem; not dumped
> >? /bin/tar: ./media/pi/workpi1: directory is on a different
> > filesystem; not dumped
> >? /bin/tar: ./media/pi/workpi120: directory is on a different
> > filesystem; not dumped
> >
> >| /bin/tar: ./tmp/.X11-unix/X0: socket ignored
> >| /bin/tar: ./tmp/ssh-5i6ERjqwMXjX/agent.705: socket ignored
> >| /bin/tar: ./tmp/ssh-VqldgesfylC3/agent.611: socket ignored
> >| Total bytes written: 8424396800 (7.9GiB, 5.2MiB/s)
> >
> >sendbackup: size 8226950
> >sendbackup: end
> >\
> > ==
> > then in the actual report:
> > ==
> > picnc   /   080343685  45.9 25:48 
> > 5314.9 0:25 150937.9
> > picnc   /boot   1  36  29  79.8  0:05 
> > 7168.4 0:00 295570.0
> >
> > That level 0 should have been around 7 or 8GB. The 1st 4 shoulda
> > been in the excludes file and I can fix that easy nuff, as should
> > the last 3. But it looks as if I'll have to make disklist entries
> > for the pair of ssd's plugged into /media.
> >
> > But thats  not legal either: amcheck says:
> > ERROR: picnc: Could not access /media/pi/workpi120
> > (/media/pi/workpi120): Permission denied
> > ERROR: picnc: Could not access /media/pi/bootpi (/media/pi/bootpi):
> > Permission denied
> > ERROR: picnc: Could not access /media/pi/backuppi
> > (/media/pi/backuppi): Permission denied
> > ERROR: picnc: Could not access /media/pi/workpi1
> > (/media/pi/workpi1): Permission denied
> >
> > /media is owned by root:root, but everything beyond that is pi:pi
> > who is 1st
> > user on picnc.coyote.den
> >
> > What changed to cause this sudden fussiness? Better yet, how do I
> > fix this?
> > =end resent
> >
> > There seems to a marked disagreement between amanda and amanda.
> >
> > After it has logged the no perms errors above, then at the end of
> > the body of that same message (and this is after I had added those 4
> > locations as separate LDE's, I see this in the same run report:
> > picnc   /media/pi/backuppi  0   0   0   --   0:01   
> >  8.9 0:00 0.0
> > picnc   /media/pi/bootpi0   0   0   --   0:00   
> > 72.9 0:00 0.0
> > picnc   /media/pi/workpi1   02603 817  31.4  5:45 
> > 7734.3 0:08 104628.4
> > picnc   /media/pi/workpi120 0   0   0   --   0:01   
> >  8.3 0:00 0.0
> >
> > Which looks perfectly normal since there is not in fact anything on
> > 3 of those partitions/directories, its two separate SSD's,  on usb
> > adaptors plugged into that pi-3b.
> >
> >
> > Twould be nice if stories matched.  Helpful even.
> >
> > Cheers, Gene Heskett


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

Re: restored amanda client errors out

[C. Scheeder]

Hi,
As far as i recal this is an expected behavior for this version of amanda.

short explanation:

amcheck does all work as normal user, so if the user hasn't access to 
the full tree up to the root dir it will complain it can't access these 
dirs.


amdump does the backups with elevated rights, so it can access these 
dirs without a problem.


That isn't nice but i have learned to live with it

Cu Christoph

Am 21.06.19 um 16:00 schrieb Gene Heskett:

I sent this yesterday around noon, but it never came back.  I've also
appended additional info at the bottom.

resent msg=

I just installed the stretch version of amanda common and amanda client,
with should have restored one of my machines to a full
backup status.

Unforch, it didn't, and this situtation existed on the previous jessie
install, where a pi scatters its stuff over a larg e number
of mount points all attached to /, so basically nothing has actually
changed.

But here is the emailed report from last nights run:
STRANGE DUMP DETAILS:
   /-- picnc / lev 0 STRANGE
   sendbackup: start [picnc:/ level 0]
   sendbackup: info BACKUP=/bin/tar
   sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
   sendbackup: info end
   ? /bin/tar: ./dev: directory is on a different filesystem; not dumped
   ? /bin/tar: ./proc: directory is on a different filesystem; not dumped
   ? /bin/tar: ./run: directory is on a different filesystem; not dumped
   ? /bin/tar: ./sys: directory is on a different filesystem; not dumped
   ? /bin/tar: ./media/pi/backuppi: directory is on a different
filesystem; not dumped
   ? /bin/tar: ./media/pi/bootpi: directory is on a different filesystem;
not dumped
   ? /bin/tar: ./media/pi/workpi1: directory is on a different filesystem;
not dumped
   ? /bin/tar: ./media/pi/workpi120: directory is on a different
filesystem; not dumped
   | /bin/tar: ./tmp/.X11-unix/X0: socket ignored
   | /bin/tar: ./tmp/ssh-5i6ERjqwMXjX/agent.705: socket ignored
   | /bin/tar: ./tmp/ssh-VqldgesfylC3/agent.611: socket ignored
   | Total bytes written: 8424396800 (7.9GiB, 5.2MiB/s)
   sendbackup: size 8226950
   sendbackup: end
   \
==
then in the actual report:
==
picnc   /   080343685  45.9 25:48  5314.9
0:25 150937.9
picnc   /boot   1  36  29  79.8  0:05  7168.4
0:00 295570.0

That level 0 should have been around 7 or 8GB. The 1st 4 shoulda been
in the excludes file and I can fix that easy nuff, as should the last 3.
But it looks as if I'll have to make disklist entries for the pair of
ssd's plugged into /media.

But thats  not legal either: amcheck says:
ERROR: picnc: Could not access /media/pi/workpi120 (/media/pi/workpi120):
Permission denied
ERROR: picnc: Could not access /media/pi/bootpi (/media/pi/bootpi):
Permission denied
ERROR: picnc: Could not access /media/pi/backuppi (/media/pi/backuppi):
Permission denied
ERROR: picnc: Could not access /media/pi/workpi1 (/media/pi/workpi1):
Permission denied

/media is owned by root:root, but everything beyond that is pi:pi who is
1st
user on picnc.coyote.den

What changed to cause this sudden fussiness? Better yet, how do I fix
this?
=end resent

There seems to a marked disagreement between amanda and amanda.

After it has logged the no perms errors above, then at the end of the
body of that same message (and this is after I had added those 4
locations as separate LDE's, I see this in the same run report:
picnc   /media/pi/backuppi  0   0   0   --   0:01 8.9
0:00 0.0
picnc   /media/pi/bootpi0   0   0   --   0:0072.9
0:00 0.0
picnc   /media/pi/workpi1   02603 817  31.4  5:45  7734.3
0:08 104628.4
picnc   /media/pi/workpi120 0   0   0   --   0:01 8.3
0:00 0.0

Which looks perfectly normal since there is not in fact anything on 3 of
those partitions/directories, its two separate SSD's,  on usb adaptors
plugged into that pi-3b.


Twould be nice if stories matched.  Helpful even.
   
Cheers, Gene Heskett

restored amanda client errors out

[Gene Heskett]

I sent this yesterday around noon, but it never came back.  I've also 
appended additional info at the bottom.

resent msg= 

I just installed the stretch version of amanda common and amanda client, 
with should have restored one of my machines to a full 
backup status.

Unforch, it didn't, and this situtation existed on the previous jessie 
install, where a pi scatters its stuff over a larg e number 
of mount points all attached to /, so basically nothing has actually 
changed. 

But here is the emailed report from last nights run:
STRANGE DUMP DETAILS:
  /-- picnc / lev 0 STRANGE
  sendbackup: start [picnc:/ level 0]
  sendbackup: info BACKUP=/bin/tar
  sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
  sendbackup: info end
  ? /bin/tar: ./dev: directory is on a different filesystem; not dumped
  ? /bin/tar: ./proc: directory is on a different filesystem; not dumped
  ? /bin/tar: ./run: directory is on a different filesystem; not dumped
  ? /bin/tar: ./sys: directory is on a different filesystem; not dumped
  ? /bin/tar: ./media/pi/backuppi: directory is on a different 
filesystem; not dumped
  ? /bin/tar: ./media/pi/bootpi: directory is on a different filesystem; 
not dumped
  ? /bin/tar: ./media/pi/workpi1: directory is on a different filesystem; 
not dumped
  ? /bin/tar: ./media/pi/workpi120: directory is on a different 
filesystem; not dumped
  | /bin/tar: ./tmp/.X11-unix/X0: socket ignored
  | /bin/tar: ./tmp/ssh-5i6ERjqwMXjX/agent.705: socket ignored
  | /bin/tar: ./tmp/ssh-VqldgesfylC3/agent.611: socket ignored
  | Total bytes written: 8424396800 (7.9GiB, 5.2MiB/s)
  sendbackup: size 8226950
  sendbackup: end
  \
==
then in the actual report:
==
picnc   /   080343685  45.9 25:48  5314.9  
0:25 150937.9
picnc   /boot   1  36  29  79.8  0:05  7168.4  
0:00 295570.0

That level 0 should have been around 7 or 8GB. The 1st 4 shoulda been 
in the excludes file and I can fix that easy nuff, as should the last 3.
But it looks as if I'll have to make disklist entries for the pair of 
ssd's plugged into /media.

But thats  not legal either: amcheck says:
ERROR: picnc: Could not access /media/pi/workpi120 (/media/pi/workpi120): 
Permission denied
ERROR: picnc: Could not access /media/pi/bootpi (/media/pi/bootpi): 
Permission denied
ERROR: picnc: Could not access /media/pi/backuppi (/media/pi/backuppi): 
Permission denied
ERROR: picnc: Could not access /media/pi/workpi1 (/media/pi/workpi1): 
Permission denied

/media is owned by root:root, but everything beyond that is pi:pi who is 
1st 
user on picnc.coyote.den

What changed to cause this sudden fussiness? Better yet, how do I fix 
this?
=end resent

There seems to a marked disagreement between amanda and amanda.

After it has logged the no perms errors above, then at the end of the 
body of that same message (and this is after I had added those 4 
locations as separate LDE's, I see this in the same run report:
picnc   /media/pi/backuppi  0   0   0   --   0:01 8.9  
0:00 0.0
picnc   /media/pi/bootpi0   0   0   --   0:0072.9  
0:00 0.0
picnc   /media/pi/workpi1   02603 817  31.4  5:45  7734.3  
0:08 104628.4
picnc   /media/pi/workpi120 0   0   0   --   0:01 8.3  
0:00 0.0

Which looks perfectly normal since there is not in fact anything on 3 of 
those partitions/directories, its two separate SSD's,  on usb adaptors 
plugged into that pi-3b.


Twould be nice if stories matched.  Helpful even.
  
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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

restored amanda client errors out

[Gene Heskett]

I just installed the sttetch version of amanda common and amanda client, with 
should have restored one of my machines to a full 
backup status.

Unforch, it didn't, and this situtation existed on the previous jessie install, 
where a pi scatters its stuff over a larg e number 
of mount points all attached to /, so basically nothing has actually changed. 

But here is the emailed report from last nights run:
STRANGE DUMP DETAILS:
  /-- picnc / lev 0 STRANGE
  sendbackup: start [picnc:/ level 0]
  sendbackup: info BACKUP=/bin/tar
  sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
  sendbackup: info end
  ? /bin/tar: ./dev: directory is on a different filesystem; not dumped
  ? /bin/tar: ./proc: directory is on a different filesystem; not dumped
  ? /bin/tar: ./run: directory is on a different filesystem; not dumped
  ? /bin/tar: ./sys: directory is on a different filesystem; not dumped
  ? /bin/tar: ./media/pi/backuppi: directory is on a different filesystem; not 
dumped
  ? /bin/tar: ./media/pi/bootpi: directory is on a different filesystem; not 
dumped
  ? /bin/tar: ./media/pi/workpi1: directory is on a different filesystem; not 
dumped
  ? /bin/tar: ./media/pi/workpi120: directory is on a different filesystem; not 
dumped
  | /bin/tar: ./tmp/.X11-unix/X0: socket ignored
  | /bin/tar: ./tmp/ssh-5i6ERjqwMXjX/agent.705: socket ignored
  | /bin/tar: ./tmp/ssh-VqldgesfylC3/agent.611: socket ignored
  | Total bytes written: 8424396800 (7.9GiB, 5.2MiB/s)
  sendbackup: size 8226950
  sendbackup: end
  \
==
then in the actual report:
==
picnc   /   080343685  45.9 25:48  5314.9  0:25 
150937.9
picnc   /boot   1  36  29  79.8  0:05  7168.4  0:00 
295570.0

That level 0 should have been around 7 or 8GB. The 1st 4 shoulda been 
in the excludes file and I can fix that easy nuff, as should the last 3.
But it looks as if I'll have to make disklist entries for the pair of 
ssd's plugged into /media.

But thats  not legal either: amcheck says:
ERROR: picnc: Could not access /media/pi/workpi120 (/media/pi/workpi120): 
Permission denied
ERROR: picnc: Could not access /media/pi/bootpi (/media/pi/bootpi): Permission 
denied
ERROR: picnc: Could not access /media/pi/backuppi (/media/pi/backuppi): 
Permission denied
ERROR: picnc: Could not access /media/pi/workpi1 (/media/pi/workpi1): 
Permission denied

/media is owned by root:root, but everything beyond that is pi:pi who is 1st 
user on picnc.coyote.den

What changed to cause this sudden fussiness? Better yet, how do I fix this?

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

Re: amanda client on leap 15 system, ie systemd

[Jason L Tibbitts III]

> "BC" == Cuttler, Brian R (HEALTH)  writes:

BC> Can anyone provide the files I need, give hints on what I'm doing
BC> wrong or help in some other way?

I don't believe Amanda upstream ships systemd unit files, so you would
need to provide them yourself.  Perhaps look at the files Fedora ships,
which can be seen at
https://src.fedoraproject.org/rpms/amanda/tree/master

Look for the various service and socket files.  amanda.socket and
amanda@.service are the main ones, providing socket activation for the
regular non-kerberized daemon over TCP.  There are other unit files for
using kerberos and running over UDP.

You may of course need to edit the user, group and any paths as
appropriate.

 - J<
 

amanda client on leap 15 system, ie systemd

[Cuttler, Brian R (HEALTH)]

Hi, installing current version of amanda client on leap 15 system using system.

My understanding, and I have read some of what has been written to the amanda 
groups, is that rather than /etc/xinetd.d we need amanda.socket and 
amanda.service files, and while I have seen some discussion of them, there is 
some subtlety that I have clearly missed.

Can anyone provide the files I need, give hints on what I'm doing wrong or help 
in some other way?

Thank you,

Brian


Brian Cuttler
Network and System Administrator, ITG - Information Technology Group
Wadsworth Center, NYS Department of Health
Biggs Lab, Empire State Plaza, Albany, NY 12201
(518) 486-1697 | brian.cutt...@health.ny.gov

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 05.03.19 um 18:54 schrieb Stefan G. Weichinger:
> Am 04.03.19 um 12:35 schrieb Stefan G. Weichinger:
> 
>> amanda-client host runs docker.service
>>
>> amdump starts, estimates ok, dump proceeds ... hangs at ~99%
>>
>> If I stop docker.service, amdump finishes OK.
> 
> Addon: if I stop the portainer container, amdump works OK ...
> 
> Solved that with 2 cronjobs now, would be cooler with some
> pre/post-hook, right?

can the script-api hooks simply call a "systemctl stop some.service" or
do the scripts have to be perl-scripts with specific properties?

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 04.03.19 um 12:35 schrieb Stefan G. Weichinger:

> amanda-client host runs docker.service
> 
> amdump starts, estimates ok, dump proceeds ... hangs at ~99%
> 
> If I stop docker.service, amdump finishes OK.

Addon: if I stop the portainer container, amdump works OK ...

Solved that with 2 cronjobs now, would be cooler with some
pre/post-hook, right?

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 26.02.19 um 16:44 schrieb Charles Curley:
> On Tue, 26 Feb 2019 13:56:35 +0100
> "Stefan G. Weichinger"  wrote:
> 
>> Do I understand correctly:
>>
>> with "auth ssh" amanda only uses ssh for auth and transport of data?
>>
>> So port 22 per default?
> 
> Correct, unless you specify otherwise.

I still see this behavior:

amanda-client host runs docker.service

amdump starts, estimates ok, dump proceeds ... hangs at ~99%

If I stop docker.service, amdump finishes OK.

All with ssh-auth enabled ... so where is the blocking? I assume I have
to do debug logs ...

Re: amanda client on updated debian-9.8

[Jose M Calhariz]

Hi,


On Wed, Feb 27, 2019 at 08:13:17AM +0100, Stefan G. Weichinger wrote:
> Am 26.02.19 um 16:26 schrieb Jose M Calhariz:
> > 
> > My plan is for Debian 11, current is 9, to make ssh authentication
> > the default.  I will not disable bsd authentication, only harder to
> > setup.
> > 
> > In attach is the Readme.Debian that I have created.
> 
> thanks
> 
> What I wonder and what IMO is not explicitly clear from the docs:
> 
> does the client have to be able to login into backupuser@server as
> well?

Only when you want to run amrecover on the client.  Because of the
security issues I have it disabled 99,9% of the time.

> 
> And additionally I still wonder what docker does that makes amdump
> hang at 99,99%
> 

Kind regards
Jose M Calhariz


-- 
--
Se vives de acordo com as leis da natureza, nunca seras
pobre; se vives de acordo com as opinioes alheias, nunca
seras rico.
--  Seneca


signature.asc
Description: PGP signature

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 26.02.19 um 16:26 schrieb Jose M Calhariz:
> 
> My plan is for Debian 11, current is 9, to make ssh authentication
> the default.  I will not disable bsd authentication, only harder to
> setup.
> 
> In attach is the Readme.Debian that I have created.

thanks

What I wonder and what IMO is not explicitly clear from the docs:

does the client have to be able to login into backupuser@server as well?

And additionally I still wonder what docker does that makes amdump
hang at 99,99%

Re: amanda client on updated debian-9.8

[Charles Curley]

On Tue, 26 Feb 2019 13:56:35 +0100
"Stefan G. Weichinger"  wrote:

> Do I understand correctly:
> 
> with "auth ssh" amanda only uses ssh for auth and transport of data?
> 
> So port 22 per default?

Correct, unless you specify otherwise.

-- 
"When we talk of civilization, we are too apt to limit the meaning of
the word to its mere embellishments, such as arts and sciences; but
the true distinction between it and barbarism is, that the one
presents a state of society under the protection of just and
well-administered law, and the other is left to the chance government
of brute force."
- The Rev. James White, Eighteen Christian Centuries, 1889
Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB
https://charlescurley.com

Re: amanda client on updated debian-9.8

[Jose M Calhariz]

My plan is for Debian 11, current is 9, to make ssh authentication the
default.  I will not disable bsd authentication, only harder to setup.

In attach is the Readme.Debian that I have created.

Kind regards
Jose M Calhariz

On Mon, Feb 25, 2019 at 07:48:03AM +0100, Stefan G. Weichinger wrote:
> Am 25.02.19 um 00:08 schrieb Jose M Calhariz:
> > On Thu, Feb 21, 2019 at 04:50:25PM +0100, Stefan G. Weichinger
> > wrote:
> >> 
> >> does anyone see estimates fail on a updated Debian 9.8 amanda
> >> client server?
> >> 
> >> update: seems that my new docker daemon on the client closes the 
> >> iptables for amanda
> >> 
> >> does anyone have a snippet for me?
> >> 
> >> I read 
> >> https://wiki.zmanda.com/index.php/How_To:Set_Up_iptables_for_Amanda
> >> and loaded that module without success so far.
> >> 
> >> connection is coming in, estimate starts, but results seem not
> >> get back to the tape server
> >> 
> >> 
> > 
> > I would start using ssh authentication instead of old bsd.  Is what
> > I use in my setups and most probably would work with your docker
> > daemon.
> > 
> > I have written documentation on how to setup it and would like
> > beta tester to read it.
> 
> good suggestion, thanks! Will try that asap.
> 
> And sure, show us the howto
> 
> 
> 
> 

-- 
--
Se vives de acordo com as leis da natureza, nunca seras
pobre; se vives de acordo com as opinioes alheias, nunca
seras rico.
--  Seneca
Notes on making amanda-client work on a Debian system

To get indexing (or specifically amrecover) to work right two things need
to be done:

1. If you're using tcpd, make sure to edit the server's /etc/hosts.allow and 
   allow all client machines into the daemon amandad

2. Edit the server(s) ~backup/.amandahosts and add an entry like:
   "   root"

As always: for more complex setups consult the manpages and available
documentation in /usr/share/doc/amanda-common ;-) 

- - - - -

To make a client work using SSH transport do:

  Copy the contents of id_rsa_amanda.pub from backup@amanda-server into 
~backup/.ssh/authorized_keys

mkdir -p ~backup/.ssh
echo -n 
'from="XXX.XXX.XXX.XXX",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,command="/usr/lib/amanda/amandad
 -auth=ssh amdump" ' >> ~backup/.ssh/authorized_keys
cat id_rsa_amanda.pub >> ~backup/.ssh/authorized_keys

  Edit the autorized_keys to replace XXX.XXX.XXX.XXX with the IP of
  the backup server.

  Change the shell of the backup account to /bin/bash.

chsh -s /bin/bash backup

  Test in the server that "amcheck $CONF -c $CLIENT" works



 -- Jose M Calhariz , Fri, 14 Jul 2017 11:53:08 +0100


signature.asc
Description: PGP signature

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 25.02.19 um 20:15 schrieb Stefan G. Weichinger:

>> dump runs but hangs at 99,99% ... oh my.
> 
> I get data timeout for that one test DLE.
> 
> And I assume it will be the same for the other DLEs tonight.
> 
> I now stopped docker .. reran amdump, and it is through successfully
> within minutes.
> 
> So there still seems to be some conflict.

We will stop docker while amdump for now.

Do I understand correctly:

with "auth ssh" amanda only uses ssh for auth and transport of data?

So port 22 per default?

I'd be happy to resolve this.

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 25.02.19 um 19:11 schrieb Stefan G. Weichinger:
> Am 25.02.19 um 17:51 schrieb Stefan G. Weichinger:
> 
>>> another client dumps fine via ssh already
>>>
>>> do all clients have to have ssh-access to the server as well?
>>
>> estimate calcsize does not work with ssh for me
>>
>> estimate server ... starts dumping after the estimate.
> 
> dump runs but hangs at 99,99% ... oh my.

I get data timeout for that one test DLE.

And I assume it will be the same for the other DLEs tonight.

I now stopped docker .. reran amdump, and it is through successfully
within minutes.

So there still seems to be some conflict.

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 25.02.19 um 17:51 schrieb Stefan G. Weichinger:

>> another client dumps fine via ssh already
>>
>> do all clients have to have ssh-access to the server as well?
> 
> estimate calcsize does not work with ssh for me
> 
> estimate server ... starts dumping after the estimate.

dump runs but hangs at 99,99% ... oh my.

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 25.02.19 um 17:09 schrieb Stefan G. Weichinger:
> Am 25.02.19 um 16:36 schrieb Charles Curley:
>> On Mon, 25 Feb 2019 08:12:21 +0100
>> "Stefan G. Weichinger"  wrote:
>>
>>> on my way. amcheck ok, amdump not. seems to still run via inetd.
>>>
>>> I assume I should disable inetd on the client ... does not help so
>>> far. Digging further ;-)
>>
>> Once you shift over to ssh, you no longer need inetd for Amanda. You
>> may need it for other things, though.
> 
> disabled inetd
> 
> amcheck works
> 
> amdump not yet
> 
> seems as if the estimates aren't getting reported back
> 
> another client dumps fine via ssh already
> 
> do all clients have to have ssh-access to the server as well?

estimate calcsize does not work with ssh for me

estimate server ... starts dumping after the estimate.

nice

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 25.02.19 um 16:36 schrieb Charles Curley:
> On Mon, 25 Feb 2019 08:12:21 +0100
> "Stefan G. Weichinger"  wrote:
> 
>> on my way. amcheck ok, amdump not. seems to still run via inetd.
>>
>> I assume I should disable inetd on the client ... does not help so
>> far. Digging further ;-)
> 
> Once you shift over to ssh, you no longer need inetd for Amanda. You
> may need it for other things, though.

disabled inetd

amcheck works

amdump not yet

seems as if the estimates aren't getting reported back

another client dumps fine via ssh already

do all clients have to have ssh-access to the server as well?

Re: amanda client on updated debian-9.8

[Charles Curley]

On Mon, 25 Feb 2019 08:12:21 +0100
"Stefan G. Weichinger"  wrote:

> on my way. amcheck ok, amdump not. seems to still run via inetd.
> 
> I assume I should disable inetd on the client ... does not help so
> far. Digging further ;-)

Once you shift over to ssh, you no longer need inetd for Amanda. You
may need it for other things, though.

-- 
"When we talk of civilization, we are too apt to limit the meaning of
the word to its mere embellishments, such as arts and sciences; but
the true distinction between it and barbarism is, that the one
presents a state of society under the protection of just and
well-administered law, and the other is left to the chance government
of brute force."
- The Rev. James White, Eighteen Christian Centuries, 1889
Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB
https://charlescurley.com

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 25.02.19 um 07:48 schrieb Stefan G. Weichinger:
> Am 25.02.19 um 00:08 schrieb Jose M Calhariz:
>> On Thu, Feb 21, 2019 at 04:50:25PM +0100, Stefan G. Weichinger
>> wrote:
>>>
>>> does anyone see estimates fail on a updated Debian 9.8 amanda
>>> client server?
>>>
>>> update: seems that my new docker daemon on the client closes the 
>>> iptables for amanda
>>>
>>> does anyone have a snippet for me?
>>>
>>> I read 
>>> https://wiki.zmanda.com/index.php/How_To:Set_Up_iptables_for_Amanda
>>> and loaded that module without success so far.
>>>
>>> connection is coming in, estimate starts, but results seem not
>>> get back to the tape server
>>>
>>>
>>
>> I would start using ssh authentication instead of old bsd.  Is what
>> I use in my setups and most probably would work with your docker
>> daemon.
>>
>> I have written documentation on how to setup it and would like
>> beta tester to read it.
> 
> good suggestion, thanks! Will try that asap.

on my way. amcheck ok, amdump not. seems to still run via inetd.

I assume I should disable inetd on the client ... does not help so far.
Digging further ;-)

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 25.02.19 um 00:08 schrieb Jose M Calhariz:
> On Thu, Feb 21, 2019 at 04:50:25PM +0100, Stefan G. Weichinger
> wrote:
>> 
>> does anyone see estimates fail on a updated Debian 9.8 amanda
>> client server?
>> 
>> update: seems that my new docker daemon on the client closes the 
>> iptables for amanda
>> 
>> does anyone have a snippet for me?
>> 
>> I read 
>> https://wiki.zmanda.com/index.php/How_To:Set_Up_iptables_for_Amanda
>> and loaded that module without success so far.
>> 
>> connection is coming in, estimate starts, but results seem not
>> get back to the tape server
>> 
>> 
> 
> I would start using ssh authentication instead of old bsd.  Is what
> I use in my setups and most probably would work with your docker
> daemon.
> 
> I have written documentation on how to setup it and would like
> beta tester to read it.

good suggestion, thanks! Will try that asap.

And sure, show us the howto

Re: amanda client on updated debian-9.8

[Winston Sorfleet]

I'll second Josés comment on the retirement of bsd (on a set of debian
machines).  I can't remember the specifics, but I see from my RCS
comments on the disklist config, that I had to deliberately discontinue
using bsd/bsdtcp some time ago.

On 24/02/2019 6:08 p.m., Jose M Calhariz wrote:
> On Thu, Feb 21, 2019 at 04:50:25PM +0100, Stefan G. Weichinger wrote:
>> does anyone see estimates fail on a updated Debian 9.8 amanda client server?
>>
>> update: seems that my new docker daemon on the client closes the
>> iptables for amanda
>>
>> does anyone have a snippet for me?
>>
>> I read
>> https://wiki.zmanda.com/index.php/How_To:Set_Up_iptables_for_Amanda and
>> loaded that module without success so far.
>>
>> connection is coming in, estimate starts, but results seem not get back
>> to the tape server
>>
>>
> I would start using ssh authentication instead of old bsd.  Is what I
> use in my setups and most probably would work with your docker daemon.
>
> I have written documentation on how to setup it and would like beta
> tester to read it. 
>
> Kind regards
> Jose M Calhariz
>




signature.asc
Description: OpenPGP digital signature

Re: amanda client on updated debian-9.8

[Jose M Calhariz]

On Thu, Feb 21, 2019 at 04:50:25PM +0100, Stefan G. Weichinger wrote:
> 
> does anyone see estimates fail on a updated Debian 9.8 amanda client server?
> 
> update: seems that my new docker daemon on the client closes the
> iptables for amanda
> 
> does anyone have a snippet for me?
> 
> I read
> https://wiki.zmanda.com/index.php/How_To:Set_Up_iptables_for_Amanda and
> loaded that module without success so far.
> 
> connection is coming in, estimate starts, but results seem not get back
> to the tape server
> 
> 

I would start using ssh authentication instead of old bsd.  Is what I
use in my setups and most probably would work with your docker daemon.

I have written documentation on how to setup it and would like beta
tester to read it. 

Kind regards
Jose M Calhariz

-- 
--
Se vives de acordo com as leis da natureza, nunca seras
pobre; se vives de acordo com as opinioes alheias, nunca
seras rico.
--  Seneca


signature.asc
Description: PGP signature

Re: amanda client on updated debian-9.8

[Stefan G. Weichinger]

Am 21.02.19 um 16:50 schrieb Stefan G. Weichinger:
> 
> does anyone see estimates fail on a updated Debian 9.8 amanda client server?
> 
> update: seems that my new docker daemon on the client closes the
> iptables for amanda
> 
> does anyone have a snippet for me?

as soon as I stop docker (runs with "--iptables=false already), backup works

amanda client on updated debian-9.8

[Stefan G. Weichinger]

does anyone see estimates fail on a updated Debian 9.8 amanda client server?

update: seems that my new docker daemon on the client closes the
iptables for amanda

does anyone have a snippet for me?

I read
https://wiki.zmanda.com/index.php/How_To:Set_Up_iptables_for_Amanda and
loaded that module without success so far.

connection is coming in, estimate starts, but results seem not get back
to the tape server

updated amanda client

[Cuttler, Brian R (HEALTH)]

We did a server update, which replaced old libraries, so we did an update to 
the Amanda install.

After updating (possibly incorrectly) the security.conf, we still have a 
getpeername error.

Not sure how to fix this, not seeing anything directly related in the archives.

Any help would be appreciated.

Thank you,
Brian



[root@netd /tmp/amanda/amandad]# more amandad.20180417104331.debug

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: pid 57255 ruid 210 euid 210 
version 3.3.9: start at Tue Apr 17 10:43:31 2018

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: 
security_getdriver(name=BSDTCP) returns 0x280d61a8

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: version 3.3.9

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: build: 
VERSION="Amanda-3.3.9"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:BUILT_DATE="Sun 
Apr 8 11:38:59 UTC 2018" BUILT_MACH=""

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:BUILT_REV="6535" 
BUILT_BRANCH="tags" CC="cc"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: paths: 
bindir="/usr/local/bin" sbindir="/usr/local/sbin"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
libexecdir="/usr/local/libexec/amanda"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
amlibexecdir="/usr/local/libexec/amanda"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
mandir="/usr/local/man" AMANDA_TMPDIR="/tmp/amanda"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
AMANDA_DBGDIR="/tmp/amanda"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
RDEV_PREFIX="/dev/r" DUMP="/sbin/dump"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
RESTORE="/sbin/restore" VDUMP=UNDEF VRESTORE=UNDEF

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:XFSDUMP=UNDEF 
XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
SAMBA_CLIENT="/usr/bin/smbclient"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
GNUTAR="/usr/local/bin/gtar" COMPRESS_PATH="/usr/bin/gzip"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
UNCOMPRESS_PATH="/usr/bin/gzip"  LPRCMD=UNDEF  MAILER=UNDEF

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
listed_incr_dir="/usr/local/var/amanda/gnutar-lists"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: defs:  
DEFAULT_SERVER="111i386-quarterly-job-16"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
DEFAULT_CONFIG="DailySet1"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
DEFAULT_TAPE_SERVER="111i386-quarterly-job-16"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
DEFAULT_TAPE_DEVICE="" NEED_STRSTR AMFLOCK_POSIX

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:AMFLOCK_FLOCK 
AMFLOCK_LOCKF AMFLOCK_LNLOCK AMANDA_DEBUG_DAYS=4

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:BSD_SECURITY 
USE_AMANDAHOSTS CLIENT_LOGIN="amanda"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:CHECK_USERID 
HAVE_GZIP COMPRESS_SUFFIX=".gz"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
COMPRESS_FAST_OPT="--fast" COMPRESS_BEST_OPT="--best"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
UNCOMPRESS_OPT="-dc"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:CONFIGURE_ARGS=" 
'--libexecdir=/usr/local/libexec/amanda' '--without-amlibexecdir' 
'--with-amandahosts' '--with-fqdn' '--with-dump-honor-nodump' 
'--disable-glibtest' '--with-user=amanda' '--with-group=amanda' 
'--with-bsdtcp-security' '--with-bsdudp-security' '--with-ssh-security' 
'--disable-installperms' 
'--with-security-file=/usr/local/etc/amanda/security.conf' 
'--with-gnutar-listdir=/usr/local/var/amanda/gnutar-lists' 
'--with-gnutar=/usr/local/bin/gtar' '--without-server' 
'--with-amandates=/usr/local/var/amanda/amandates' '--prefix=/usr/local' 
'--localstatedir=/var' '--mandir=/usr/local/man' '--disable-silent-rules' 
'--infodir=/usr/local/info/' '--build=i386-portbld-freebsd11.1' 
'build_alias=i386-portbld-freebsd11.1' 'CC=cc' 'CFLAGS=-O2 -pipe  
-fstack-protector -fno-strict-aliasing' 'LDFLAGS=  -fstack-protector' 'LIBS=' 
'CPPFLAGS=' 'CPP=cpp' 'PERL=/usr/local/bin/perl-amanda' 'PKG_CONFIG=pkgconf'"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: getpeername returned: Socket 
is not connected

Re: Ubuntu 16.04 amanda-client package

[Charles Curley]

On Fri, 14 Apr 2017 15:41:32 -0400
Chris Hoogendyk  wrote:

> I didn't.

Ah, thanks for clarifying.

And thanks for the writeup.

-- 

The right of the people to be secure in their persons, houses, papers,
and effects, against unreasonable searches and seizures, shall not be
violated, and no Warrants shall issue, but upon probable cause,
supported by Oath or affirmation, and particularly describing the
place to be searched, and the persons or things to be seized.
-- U.S. Const. Amendment IV

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

Re: Ubuntu 16.04 amanda-client package

[Chris Hoogendyk]

I didn't.

I have the server's public key on the client.

When I ssh'd from the client to the server, I only got the known_hosts and then terminated the 
connection. In retrospect, I'm not sure I even needed that. I should try setting aside known_hosts 
on the client and see if amcheck on the server still works. In any case, I never fully ssh in as 
amanda or as backup. I don't even remember the password for amanda. I set it to something outrageous 
and then promptly forgot it. I log in as myself and use sudo to get to amanda if needed.


For amrecover, I typically run it on the server and then move things to the 
client, if needed.


On 4/14/17 3:27 PM, Charles Curley wrote:

On Fri, 14 Apr 2017 14:37:17 -0400
Chris Hoogendyk  wrote:


I think that's it. Relatively simple once you get it. Hope I didn't
miss documenting any steps.

Looks good. I like locking down the keys to a specific executable.

I don't see where you generated the client's keys, or copied its public
key to the server. Those steps should be between steps 4 and 5 on the
client.

And if you want to run amrecover on the client, you will need to
copy user backup's public key from the client to the server.




--
---

Chris Hoogendyk

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



---

Erdös 4

Re: Ubuntu 16.04 amanda-client package

[Charles Curley]

On Fri, 14 Apr 2017 14:37:17 -0400
Chris Hoogendyk  wrote:

> I think that's it. Relatively simple once you get it. Hope I didn't
> miss documenting any steps.

Looks good. I like locking down the keys to a specific executable.

I don't see where you generated the client's keys, or copied its public
key to the server. Those steps should be between steps 4 and 5 on the
client.

And if you want to run amrecover on the client, you will need to
copy user backup's public key from the client to the server.


-- 

The right of the people to be secure in their persons, houses, papers,
and effects, against unreasonable searches and seizures, shall not be
violated, and no Warrants shall issue, but upon probable cause,
supported by Oath or affirmation, and particularly describing the
place to be searched, and the persons or things to be seized.
-- U.S. Const. Amendment IV

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

Re: Ubuntu 16.04 amanda-client package

[Chris Hoogendyk]

amandad-path in the dumptype was the last requirement. amcheck works now. That was what was blocking 
the ssh connection, because the authorized_key was locked down to only allow the one command and no 
other:


from="wahoo.server.isb.nsm,172.30.144.37",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,command="/usr/lib/amanda/amandad 
-auth=ssh amdump" ssh-rsa . . . . (the key)


Thank you, Jean-Louis! Also, Charles Curley.

It turns out that it is necessary to have a valid shell for ssh-auth. I tried changing it back to 
nologin after amcheck worked, and the result was that amcheck failed, indicating "This account is 
currently not available."


Steps required to get the amanda client (with the Debian/Ubuntu 16.04 amanda 3.3.6 pkg) running, 
assuming I'm using ssh-auth and have a server with amanda built from source with user and group amanda:

==

Start on the client (this is after having done the `aptitude install 
amanda-client`),

1. Change backup user's shell from /usr/sbin/nologin to /bin/bash in 
/etc/passwd.

2. Change ownership of backup user's home directory from root:root to backup:backup (assume root 
will still manage its cron jobs that backup other stuff into /var/backups).


3. `sudo su - backup`

4. `mkdir .ssh`

5. `ssh amanda.server`  <-- to set up known_hosts entry

6. `cd .ssh`  and then `vi authorized_keys`  and put in the correct public key entry for the amanda 
server.



On the server (where amanda is already set up and working for itself and other 
clients),

1. `sudo su - amanda`

2. `ssh amanda.client`   <-- to set up known_hosts entry for the new client

3. `vi daily/disklist` and set up disklist entries for client, e.g.

   kilgore.server.isb.nsm  /home{
comp-user-tar
client-username "backup"
amandad-path "/usr/lib/amanda/amandad"
} 001server-rm

where the client-username and amandad-path are specified because they differ on the client 
build of amanda compared to the server build. Of course, those could also have been entered in a 
specific dumptype in amanda.conf and then that dumptype could have been used here. That would be the 
easier route if there were lots of DLEs on this client.


4. `amcheck daily` to see that everything works.


Along the way, look at log files and debug files at /tmp/amanda/server/daily/  on the server (I 
start with `ls -lt | head` so that I get the most recent) and /var/log/auth.log on the client.


I think that's it. Relatively simple once you get it. Hope I didn't miss 
documenting any steps.



On 4/14/17 1:39 PM, Jean-Louis Martineau wrote:

On 14/04/17 01:33 PM, Chris Hoogendyk wrote:
> Close to working, but not quite.
>
> Here is the line from
> /tmp/amanda/server/daily/amcheck.20170414130845.debug on the server:
>
> Fri Apr 14 13:08:45 2017: thd-0x2383200: amcheck-clients: exec:
> /usr/bin/ssh -x -o BatchMode=yes -o PreferredAuthentications=publickey
> -l backup -i /usr/local/etc/amanda/.ssh/id_rsa_daily_config
> kilgore.server.isb.nsm /usr/local/libexec/amanda/amandad -auth=ssh
>
> The key is that it is asking to execute
> /usr/local/libexec/amanda/amandad on the client, but amandad is at
> /usr/lib/amanda/amandad. I had changed that in the authorized_keys
> file on the client, but where is the server getting that in the first
> place? How do I change it for this client, short of setting up that
> directory with a symlink? And, would a symlink even work? Or would the
> security checks disallow a symlink?

Set the amandad-path in the dumptype.

>
> At the moment, I'm getting "Permission denied (publickey,password)."
> during amcheck.

Something is not correctly set for ssh, check ssh and sshd logs files.
Run the ssh command from the command line

Jean-Louis
>
>
> On 4/14/17 12:07 PM, Jean-Louis Martineau wrote:
>> Chris,
>>
>> The home directory is not important, but you must put the .amandahosts
>> and .ssh there.
>>
>> In the dle, you must set client-username and probably amandad-path (but
>> it is better to set it in the client .ssh/authorized_keys for security.
>>
>> According to
>> 
https://unix.stackexchange.com/questions/184031/can-a-command-be-executed-over-ssh-with-a-nologin-user,

>>
>> the nologin shell should not be a problem.
>> But you can set it to valid shell if you want to connect to the client
>>
>> Try to ssh the client from the server to accept the server keys
>> (known_hosts),a valid might be required here, I'm not sure.
>> Then run amcheck.
>>
>> Jean-Louis
>>
>> On 14/04/17 11:46 AM, Chris Hoogendyk wrote:
>> > Thank you, Jean-Louis,
>> >
>> > It's not so much a question of what doesn't work 

Re: Ubuntu 16.04 amanda-client package

[Jean-Louis Martineau]

On 14/04/17 01:33 PM, Chris Hoogendyk wrote:

Close to working, but not quite.

Here is the line from 
/tmp/amanda/server/daily/amcheck.20170414130845.debug on the server:


Fri Apr 14 13:08:45 2017: thd-0x2383200: amcheck-clients: exec: 
/usr/bin/ssh -x -o BatchMode=yes -o PreferredAuthentications=publickey 
-l backup -i /usr/local/etc/amanda/.ssh/id_rsa_daily_config 
kilgore.server.isb.nsm /usr/local/libexec/amanda/amandad -auth=ssh


The key is that it is asking to execute 
/usr/local/libexec/amanda/amandad on the client, but amandad is at 
/usr/lib/amanda/amandad. I had changed that in the authorized_keys 
file on the client, but where is the server getting that in the first 
place? How do I change it for this client, short of setting up that 
directory with a symlink? And, would a symlink even work? Or would the 
security checks disallow a symlink?


Set the amandad-path in the dumptype.



At the moment, I'm getting "Permission denied (publickey,password)." 
during amcheck.


Something is not correctly set for ssh, check ssh and sshd logs files.
Run the ssh command from the command line

Jean-Louis



On 4/14/17 12:07 PM, Jean-Louis Martineau wrote:

Chris,

The home directory is not important, but you must put the .amandahosts
and .ssh there.

In the dle, you must set client-username and probably amandad-path (but
it is better to set it in the client .ssh/authorized_keys for security.

According to
https://unix.stackexchange.com/questions/184031/can-a-command-be-executed-over-ssh-with-a-nologin-user, 


the nologin shell should not be a problem.
But you can set it to valid shell if you want to connect to the client

Try to ssh the client from the server to accept the server keys
(known_hosts),a valid might be required here, I'm not sure.
Then run amcheck.

Jean-Louis

On 14/04/17 11:46 AM, Chris Hoogendyk wrote:
> Thank you, Jean-Louis,
>
> It's not so much a question of what doesn't work as it is of where to
> start.
>
> There doesn't seem to be any documentation of how the Debian/Ubuntu
> package was built or what steps should be required to implement a 
client.

>
> Typically, when I build Amanda on a client, I build it with ssh-auth
> and user and group amanda. After the client is built and installed, I
> manually ssh back and forth to set up the known_hosts, transfer the
> public key to the new client, set up .amandahosts, and maybe a couple
> of other steps. Then I edit the disklist and add entries for the new
> client, run amcheck, and work out any remaining glitches, but usually
> it just works at this point.
>
> With the Debian/Ubuntu 3.3.6 package on Ubuntu 16.04, as I tried to
> figure out what had been done, I started out by running `dpkg-query -L
> amanda-client`. Since there was no amanda user or amandbackup user
> installed, I began looking at user backup. But its home directory,
> /var/backups, seemed weird, and its shell was /usr/sbin/nologin. So
> then what? Is it assumed that I will manually edit known_hosts and so
> on? And will the ssh-auth connection work when the client user has a
> shell of /usr/sbin/nologin? Or should I change that shell to something
> that works? And then just start hacking through with my normal
> procedures, but with a special dumptype that incorporates
> client-username "backup"?
>
> I'd prefer to do it as intended rather than hacking. One would presume
> that should be smoother, assuming the intended setup is known
> (documented).
>
>
> On 4/14/17 8:29 AM, Jean-Louis Martineau wrote:
>> Chris,
>>
>> We could help if you tell us what doesn't work.
>>
>> Jean-Louis
>>
>> On 13/04/17 03:53 PM, Chris Hoogendyk wrote:
>> > I have a group of amanda servers and clients that are all Ubuntu 
14.04

>> > with amanda 3.3.6 installed from source with ssh config and user
>> amanda.
>> >
>> > Now I'm trying to set up a new client that is Ubuntu 16.04. I 
saw that

>> > the aptitude had amanda 3.3.6, common, server, and client packages.
>> > So, I thought, hey, that will make things easy.
>> >
>> > Not.
>> >
>> > So, it seems they built the package with user backup, home 
directory

>> > /var/backups, and shell /usr/sbin/nologin. There doesn't seem to be
>> > any readme or install or configure instructions anywhere explaining
>> > how it has been built and how it has to be set up to function. I 
had

>> > assumed it would be largely ready to go, with instructions on what
>> > configuration remained to be done.
>> >
>> > I also haven't been able to find much of anything through google.
>> >
>> > Does anyone have any guidance on this? Or should I just rip it 
out an

Re: Ubuntu 16.04 amanda-client package

[Chris Hoogendyk]

Close to working, but not quite.

Here is the line from /tmp/amanda/server/daily/amcheck.20170414130845.debug on 
the server:

Fri Apr 14 13:08:45 2017: thd-0x2383200: amcheck-clients: exec: /usr/bin/ssh -x -o BatchMode=yes -o 
PreferredAuthentications=publickey -l backup -i /usr/local/etc/amanda/.ssh/id_rsa_daily_config 
kilgore.server.isb.nsm /usr/local/libexec/amanda/amandad -auth=ssh


The key is that it is asking to execute /usr/local/libexec/amanda/amandad on the client, but amandad 
is at /usr/lib/amanda/amandad. I had changed that in the authorized_keys file on the client, but 
where is the server getting that in the first place? How do I change it for this client, short of 
setting up that directory with a symlink? And, would a symlink even work? Or would the security 
checks disallow a symlink?


At the moment, I'm getting "Permission denied (publickey,password)." during 
amcheck.


On 4/14/17 12:07 PM, Jean-Louis Martineau wrote:

Chris,

The home directory is not important, but you must put the .amandahosts
and .ssh there.

In the dle, you must set client-username and probably amandad-path (but
it is better to set it in the client .ssh/authorized_keys for security.

According to
https://unix.stackexchange.com/questions/184031/can-a-command-be-executed-over-ssh-with-a-nologin-user,
the nologin shell should not be a problem.
But you can set it to valid shell if you want to connect to the client

Try to ssh the client from the server to accept the server keys
(known_hosts),a valid might be required here, I'm not sure.
Then run amcheck.

Jean-Louis

On 14/04/17 11:46 AM, Chris Hoogendyk wrote:
> Thank you, Jean-Louis,
>
> It's not so much a question of what doesn't work as it is of where to
> start.
>
> There doesn't seem to be any documentation of how the Debian/Ubuntu
> package was built or what steps should be required to implement a client.
>
> Typically, when I build Amanda on a client, I build it with ssh-auth
> and user and group amanda. After the client is built and installed, I
> manually ssh back and forth to set up the known_hosts, transfer the
> public key to the new client, set up .amandahosts, and maybe a couple
> of other steps. Then I edit the disklist and add entries for the new
> client, run amcheck, and work out any remaining glitches, but usually
> it just works at this point.
>
> With the Debian/Ubuntu 3.3.6 package on Ubuntu 16.04, as I tried to
> figure out what had been done, I started out by running `dpkg-query -L
> amanda-client`. Since there was no amanda user or amandbackup user
> installed, I began looking at user backup. But its home directory,
> /var/backups, seemed weird, and its shell was /usr/sbin/nologin. So
> then what? Is it assumed that I will manually edit known_hosts and so
> on? And will the ssh-auth connection work when the client user has a
> shell of /usr/sbin/nologin? Or should I change that shell to something
> that works? And then just start hacking through with my normal
> procedures, but with a special dumptype that incorporates
> client-username "backup"?
>
> I'd prefer to do it as intended rather than hacking. One would presume
> that should be smoother, assuming the intended setup is known
> (documented).
>
>
> On 4/14/17 8:29 AM, Jean-Louis Martineau wrote:
>> Chris,
>>
>> We could help if you tell us what doesn't work.
>>
>> Jean-Louis
>>
>> On 13/04/17 03:53 PM, Chris Hoogendyk wrote:
>> > I have a group of amanda servers and clients that are all Ubuntu 14.04
>> > with amanda 3.3.6 installed from source with ssh config and user
>> amanda.
>> >
>> > Now I'm trying to set up a new client that is Ubuntu 16.04. I saw that
>> > the aptitude had amanda 3.3.6, common, server, and client packages.
>> > So, I thought, hey, that will make things easy.
>> >
>> > Not.
>> >
>> > So, it seems they built the package with user backup, home directory
>> > /var/backups, and shell /usr/sbin/nologin. There doesn't seem to be
>> > any readme or install or configure instructions anywhere explaining
>> > how it has been built and how it has to be set up to function. I had
>> > assumed it would be largely ready to go, with instructions on what
>> > configuration remained to be done.
>> >
>> > I also haven't been able to find much of anything through google.
>> >
>> > Does anyone have any guidance on this? Or should I just rip it out and
>> > build from source? Amanda is one of the few things that I have
>> > continued to build from source since I switched from Solaris to Ubuntu
>> > several years ago. All the other major packages get patches and
&

Re: Ubuntu 16.04 amanda-client package

[Charles Curley]

On Fri, 14 Apr 2017 12:07:03 -0400
Jean-Louis Martineau  wrote:

> According to 
> https://unix.stackexchange.com/questions/184031/can-a-command-be-executed-over-ssh-with-a-nologin-user,
> the nologin shell should not be a problem.
> But you can set it to valid shell if you want to connect to the client
> 
> Try to ssh the client from the server to accept the server keys 
> (known_hosts),a valid might be required here, I'm not sure.

My experience has been, yes, you must ssh into the machine manually the
first time you make a connection. Amanda will choke if you don't. So
you have to give the user a suitable shell such as bash.

I have not experimented with setting the shell back to nologin
afterwards.

> Then run amcheck.



-- 

The right of the people to be secure in their persons, houses, papers,
and effects, against unreasonable searches and seizures, shall not be
violated, and no Warrants shall issue, but upon probable cause,
supported by Oath or affirmation, and particularly describing the
place to be searched, and the persons or things to be seized.
-- U.S. Const. Amendment IV

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

Re: Ubuntu 16.04 amanda-client package

[Charles Curley]

On Fri, 14 Apr 2017 11:46:46 -0400
Chris Hoogendyk  wrote:

> With the Debian/Ubuntu 3.3.6 package on Ubuntu 16.04, as I tried to
> figure out what had been done, I started out by running `dpkg-query
> -L amanda-client`. Since there was no amanda user or amandbackup user
> installed, I began looking at user backup. But its home
> directory, /var/backups, seemed weird, and its shell
> was /usr/sbin/nologin. So then what? Is it assumed that I will
> manually edit known_hosts and so on? And will the ssh-auth connection
> work when the client user has a shell of /usr/sbin/nologin? Or should
> I change that shell to something that works? And then just start
> hacking through with my normal procedures, but with a special
> dumptype that incorporates client-username "backup"?

I run amanda packages on debian, and they seem to have the same
characteristics as those for Ubuntu. I currently run all version
1:3.4.3-1. So, what I end up with is a mixture of the two models. On
the new machine, I:

Change the shell for the backup user to bash:

sed -i~ -e 
's/backup:x:34:34:backup:\/var\/backups:\/usr\/sbin\/nologin/backup:x:34:34:backup:\/var\/backups:\/bin\/bash/'
 /etc/passwd

Let the backup user create files, like ~/.ssh and .bash_history.

chown backup /var/backups

Only then do I do the key setup for SSH. I do it as user 'backup' so
that backup owns all the relevant files.

Since I run all debian, all my clients and servers run amanda as user
'backup'. So I don't have the user name problem you have. I guess you
can address that in the relevant ~/.ssh/config or in amanda's
configuration.

-- 

The right of the people to be secure in their persons, houses, papers,
and effects, against unreasonable searches and seizures, shall not be
violated, and no Warrants shall issue, but upon probable cause,
supported by Oath or affirmation, and particularly describing the
place to be searched, and the persons or things to be seized.
-- U.S. Const. Amendment IV

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

Re: Ubuntu 16.04 amanda-client package

[Jean-Louis Martineau]

Chris,

The home directory is not important,  but you must put the .amandahosts 
and .ssh there.


In the dle, you must set client-username and probably amandad-path (but 
it is better to set it in the client .ssh/authorized_keys for security.


According to 
https://unix.stackexchange.com/questions/184031/can-a-command-be-executed-over-ssh-with-a-nologin-user,

the nologin shell should not be a problem.
But you can set it to valid shell if you want to connect to the client

Try to ssh the client from the server to accept the server keys 
(known_hosts),a valid might be required here, I'm not sure.

Then run amcheck.

Jean-Louis

On 14/04/17 11:46 AM, Chris Hoogendyk wrote:

Thank you, Jean-Louis,

It's not so much a question of what doesn't work as it is of where to 
start.


There doesn't seem to be any documentation of how the Debian/Ubuntu 
package was built or what steps should be required to implement a client.


Typically, when I build Amanda on a client, I build it with ssh-auth 
and user and group amanda. After the client is built and installed, I 
manually ssh back and forth to set up the known_hosts, transfer the 
public key to the new client, set up .amandahosts, and maybe a couple 
of other steps. Then I edit the disklist and add entries for the new 
client, run amcheck, and work out any remaining glitches, but usually 
it just works at this point.


With the Debian/Ubuntu 3.3.6 package on Ubuntu 16.04, as I tried to 
figure out what had been done, I started out by running `dpkg-query -L 
amanda-client`. Since there was no amanda user or amandbackup user 
installed, I began looking at user backup. But its home directory, 
/var/backups, seemed weird, and its shell was /usr/sbin/nologin. So 
then what? Is it assumed that I will manually edit known_hosts and so 
on? And will the ssh-auth connection work when the client user has a 
shell of /usr/sbin/nologin? Or should I change that shell to something 
that works? And then just start hacking through with my normal 
procedures, but with a special dumptype that incorporates 
client-username "backup"?


I'd prefer to do it as intended rather than hacking. One would presume 
that should be smoother, assuming the intended setup is known 
(documented).



On 4/14/17 8:29 AM, Jean-Louis Martineau wrote:

Chris,

We could help if you tell us what doesn't work.

Jean-Louis

On 13/04/17 03:53 PM, Chris Hoogendyk wrote:
> I have a group of amanda servers and clients that are all Ubuntu 14.04
> with amanda 3.3.6 installed from source with ssh config and user 
amanda.

>
> Now I'm trying to set up a new client that is Ubuntu 16.04. I saw that
> the aptitude had amanda 3.3.6, common, server, and client packages.
> So, I thought, hey, that will make things easy.
>
> Not.
>
> So, it seems they built the package with user backup, home directory
> /var/backups, and shell /usr/sbin/nologin. There doesn't seem to be
> any readme or install or configure instructions anywhere explaining
> how it has been built and how it has to be set up to function. I had
> assumed it would be largely ready to go, with instructions on what
> configuration remained to be done.
>
> I also haven't been able to find much of anything through google.
>
> Does anyone have any guidance on this? Or should I just rip it out and
> build from source? Amanda is one of the few things that I have
> continued to build from source since I switched from Solaris to Ubuntu
> several years ago. All the other major packages get patches and
> security updates fairly regularly, so it pays to stick with aptitude.
>
>


*Disclaimer*

This message is the property of *CARBONITE, INC.* 
<http://www.carbonite.com> and may contain confidential or privileged 
information.


If this message has been delivered to you by mistake, then do not 
copy or deliver this message to anyone. Instead, destroy it and 
notify me by reply e-mail.





This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail

Re: Ubuntu 16.04 amanda-client package

[Chris Hoogendyk]

Thank you, Jean-Louis,

It's not so much a question of what doesn't work as it is of where to start.

There doesn't seem to be any documentation of how the Debian/Ubuntu package was built or what steps 
should be required to implement a client.


Typically, when I build Amanda on a client, I build it with ssh-auth and user and group amanda. 
After the client is built and installed, I manually ssh back and forth to set up the known_hosts, 
transfer the public key to the new client, set up .amandahosts, and maybe a couple of other steps. 
Then I edit the disklist and add entries for the new client, run amcheck, and work out any remaining 
glitches, but usually it just works at this point.


With the Debian/Ubuntu 3.3.6 package on Ubuntu 16.04, as I tried to figure out what had been done, I 
started out by running `dpkg-query -L amanda-client`. Since there was no amanda user or amandbackup 
user installed, I began looking at user backup. But its home directory, /var/backups, seemed weird, 
and its shell was /usr/sbin/nologin. So then what? Is it assumed that I will manually edit 
known_hosts and so on? And will the ssh-auth connection work when the client user has a shell of 
/usr/sbin/nologin? Or should I change that shell to something that works? And then just start 
hacking through with my normal procedures, but with a special dumptype that incorporates 
client-username "backup"?


I'd prefer to do it as intended rather than hacking. One would presume that should be smoother, 
assuming the intended setup is known (documented).



On 4/14/17 8:29 AM, Jean-Louis Martineau wrote:

Chris,

We could help if you tell us what doesn't work.

Jean-Louis

On 13/04/17 03:53 PM, Chris Hoogendyk wrote:
> I have a group of amanda servers and clients that are all Ubuntu 14.04
> with amanda 3.3.6 installed from source with ssh config and user amanda.
>
> Now I'm trying to set up a new client that is Ubuntu 16.04. I saw that
> the aptitude had amanda 3.3.6, common, server, and client packages.
> So, I thought, hey, that will make things easy.
>
> Not.
>
> So, it seems they built the package with user backup, home directory
> /var/backups, and shell /usr/sbin/nologin. There doesn't seem to be
> any readme or install or configure instructions anywhere explaining
> how it has been built and how it has to be set up to function. I had
> assumed it would be largely ready to go, with instructions on what
> configuration remained to be done.
>
> I also haven't been able to find much of anything through google.
>
> Does anyone have any guidance on this? Or should I just rip it out and
> build from source? Amanda is one of the few things that I have
> continued to build from source since I switched from Solaris to Ubuntu
> several years ago. All the other major packages get patches and
> security updates fairly regularly, so it pays to stick with aptitude.
>
>


*Disclaimer*

This message is the property of *CARBONITE, INC.* <http://www.carbonite.com> and may contain 
confidential or privileged information.


If this message has been delivered to you by mistake, then do not copy or deliver this message to 
anyone. Instead, destroy it and notify me by reply e-mail.




--
---

Chris Hoogendyk

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



---

Erdös 4

Re: Ubuntu 16.04 amanda-client package

[Jean-Louis Martineau]

Chris,

We could help if you tell us what doesn't work.

Jean-Louis

On 13/04/17 03:53 PM, Chris Hoogendyk wrote:
I have a group of amanda servers and clients that are all Ubuntu 14.04 
with amanda 3.3.6 installed from source with ssh config and user amanda.


Now I'm trying to set up a new client that is Ubuntu 16.04. I saw that 
the aptitude had amanda 3.3.6, common, server, and client packages. 
So, I thought, hey, that will make things easy.


Not.

So, it seems they built the package with user backup, home directory 
/var/backups, and shell /usr/sbin/nologin. There doesn't seem to be 
any readme or install or configure instructions anywhere explaining 
how it has been built and how it has to be set up to function. I had 
assumed it would be largely ready to go, with instructions on what 
configuration remained to be done.


I also haven't been able to find much of anything through google.

Does anyone have any guidance on this? Or should I just rip it out and 
build from source? Amanda is one of the few things that I have 
continued to build from source since I switched from Solaris to Ubuntu 
several years ago. All the other major packages get patches and 
security updates fairly regularly, so it pays to stick with aptitude.




This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail

Re: Ubuntu 16.04 amanda-client package

[Jean-Louis Martineau]

On 13/04/17 07:38 PM, Charles Curley wrote:
> On Thu, 13 Apr 2017 22:42:06 +
> Debra S Baddorf  wrote:
>
>> Q to others:  does the client  have to have the same username and
>> locations as the server?

No, they do not need to be the same.

Jean-Louis
This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail

Re: Ubuntu 16.04 amanda-client package

[Chris Hoogendyk]

from the man page for amanda-auth, there is a client-usaername that can be defined in a dumptype. I 
haven't tried it yet, but . . .



On 4/13/17 7:38 PM, Charles Curley wrote:

On Thu, 13 Apr 2017 22:42:06 +
Debra S Baddorf  wrote:


Q to others:  does the client  have to have the same username and
locations as the server?

Yes.



--
---

Chris Hoogendyk

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



---

Erdös 4

Re: Ubuntu 16.04 amanda-client package

[Charles Curley]

On Thu, 13 Apr 2017 22:42:06 +
Debra S Baddorf  wrote:

> Q to others:  does the client  have to have the same username and
> locations as the server?

Yes.

-- 

The right of the people to be secure in their persons, houses, papers,
and effects, against unreasonable searches and seizures, shall not be
violated, and no Warrants shall issue, but upon probable cause,
supported by Oath or affirmation, and particularly describing the
place to be searched, and the persons or things to be seized.
-- U.S. Const. Amendment IV

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

Re: Ubuntu 16.04 amanda-client package

[Debra S Baddorf]

Q to others:  does the client  have to have the same username and locations as 
the server?

A  to you:  for my own peace of mind and ease of finding things,  I personally 
would rebuild it from scratch.   But I only know about RedHat.  Then again,  
you are already used to building from scratch,  so ….

Deb Baddorf


> On Apr 13, 2017, at 2:53 PM, Chris Hoogendyk  wrote:
> 
> I have a group of amanda servers and clients that are all Ubuntu 14.04 with 
> amanda 3.3.6 installed from source with ssh config and user amanda.
> 
> Now I'm trying to set up a new client that is Ubuntu 16.04. I saw that the 
> aptitude had amanda 3.3.6, common, server, and client packages. So, I 
> thought, hey, that will make things easy.
> 
> Not.
> 
> So, it seems they built the package with user backup, home directory 
> /var/backups, and shell /usr/sbin/nologin. There doesn't seem to be any 
> readme or install or configure instructions anywhere explaining how it has 
> been built and how it has to be set up to function. I had assumed it would be 
> largely ready to go, with instructions on what configuration remained to be 
> done.
> 
> I also haven't been able to find much of anything through google.
> 
> Does anyone have any guidance on this? Or should I just rip it out and build 
> from source? Amanda is one of the few things that I have continued to build 
> from source since I switched from Solaris to Ubuntu several years ago. All 
> the other major packages get patches and security updates fairly regularly, 
> so it pays to stick with aptitude.
> 
> 
> -- 
> ---
> 
> Chris Hoogendyk
> 
> -
>   O__   Systems Administrator
>  c/ /'_ --- Biology & Geosciences Departments
> (*) \(*) -- 315 Morrill Science Center
> ~~ - University of Massachusetts, Amherst
> 
> 
> 
> ---
> 
> Erdös 4
> 

Ubuntu 16.04 amanda-client package

[Chris Hoogendyk]

I have a group of amanda servers and clients that are all Ubuntu 14.04 with amanda 3.3.6 installed 
from source with ssh config and user amanda.


Now I'm trying to set up a new client that is Ubuntu 16.04. I saw that the aptitude had amanda 
3.3.6, common, server, and client packages. So, I thought, hey, that will make things easy.


Not.

So, it seems they built the package with user backup, home directory /var/backups, and shell 
/usr/sbin/nologin. There doesn't seem to be any readme or install or configure instructions anywhere 
explaining how it has been built and how it has to be set up to function. I had assumed it would be 
largely ready to go, with instructions on what configuration remained to be done.


I also haven't been able to find much of anything through google.

Does anyone have any guidance on this? Or should I just rip it out and build from source? Amanda is 
one of the few things that I have continued to build from source since I switched from Solaris to 
Ubuntu several years ago. All the other major packages get patches and security updates fairly 
regularly, so it pays to stick with aptitude.



--
---

Chris Hoogendyk

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



---

Erdös 4

Re: Amanda client weirdnesses on MacOSX

[Jon LaBadie]

On Fri, Sep 11, 2015 at 09:12:46AM -0400, Robert Heller wrote:
> I am using the Amanda 2.5.0p2 client on a MacOSX (matching a Amanda 2.5.0p2 
> server on a CentOS 5.11 system) and have it set up to use GnuTAR for backup 
> on 
> the Mac (a MacMini).  This works OK, but there are some weirdnesses:
> 
> The incremental backups (level > 0) are just about as large as the level 0 
> backups.  Why is this?  Is there something I could/should do special?
> 
Not knowing Macs, my comments are based on UNIX/Linux and the assumption
that Macs are similar in ways that count :)

A file's metadata, stored in the file's inode, includes three time
stamps: "atime" (data access or read), "mtime" (data modification or
write), and "ctime" (metadata change).  ctime is modified by access,
write, or other metadata changes eg. ownership or permission changes. 

GnuTAR incrementals are mostly (?entirely?) based on ctime changes.

Look for something that scans the contents of all files each day.
Maybe content indexer's, anti-virus, or ???  These might change
atime and thus ctime.

Linux and UNIX have filesystem mount options (eg noatime) that
limit atime changes to only when other inode changes are needed.
See if your Mac supports similar options and if they are being
used.

BTW, Linux's "ls(1)" command normally shows mtime with the -l options.
You can see the other times by adding the "c" (ctime) or "u" (atime)
options, i.e. "ls -lu".  If you find a lot of files have the same
atime or ctime you know when a command may have scanned everything.

Jon
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)

Amanda client weirdnesses on MacOSX

[Robert Heller]

I am using the Amanda 2.5.0p2 client on a MacOSX (matching a Amanda 2.5.0p2 
server on a CentOS 5.11 system) and have it set up to use GnuTAR for backup on 
the Mac (a MacMini).  This works OK, but there are some weirdnesses:

The incremental backups (level > 0) are just about as large as the level 0 
backups.  Why is this?  Is there something I could/should do special?

I built the Amanda 2.5.0p2 client from source on the Mac.  It has GnuTAR 1.17 
installed:

frodo.deepsoft.com% gnutar --version
tar (GNU tar) 1.17
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Modified to support extended attributes.
Written by John Gilmore and Jay Fenlason.

The MacOSX version is (I think 10.6 or 10.7):
frodo.deepsoft.com% uname -a
Darwin frodo.deepsoft.com 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 
16:26:45 PDT 2012; root:xnu-1699.32.7~1/RELEASE_I386 i386

The disklist section looks like this:

# Frodo
 
frodo / comp-user-span-tar 4   
frodo /Applications comp-user-span-tar 4   
frodo /Library  comp-user-span-tar 4   
frodo /System   comp-user-span-tar 4   
frodo /Userscomp-user-span-tar 4   

(The mac has one actual file system, but I am breaking it up (using excludes) 
to reduce the sizes of the backups -- I don't have enough holding disk space 
for the whole thing at one go.)

The dump types look like this:

define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index
#   exclude list "/etc/amanda/exclude.gtar"
exclude list ".amanda.excludes"
priority low
}

define dumptype comp-user-span-tar {
root-tar
tape_splitsize 1432 Mb
comment "Non-root partitions on reasonably fast machines, incrmentals only"
compress client fast
priority medium
}

And frodo:/.amanda.excludes contains:

frodo.deepsoft.com% cat /.amanda.excludes
./Applications
./Library
./System
./Users
./.dbfseventsd
./opt/local/var/macports/software/
./private/tmp/

 



-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

Re: [Amanda-users] Help in installing Amanda Client in FreeBSD 8.0/9.0

[Olivier Nicole]

Jose,

> Im new to Amanda. I have installed Amanda Server on a CentOS but on
> trying to install it on the FreeBSD clients I have I am experiencing
> hitches. Any help you can accord will be highly appreciated.

I am not sure what are your problem sin installing amanda client on
FreeBSD.

Go to /usr/ports/misc/amanda-client
make
make install

That should do it.

Else you ned to be specific on the type of propblems you are facing.

Best regards,

Olivier

Re: How to accept Source-High-Ports on an Amanda Client

[Jean-Louis Martineau]

On 02/26/2012 04:51 AM, Thomas Marko wrote:

Anyway, how can I achieve, that Amanda accepts such translated connections 
(xlated to high ports)?

You can't.

You can try the bsdtcp auth, maybe your firewall do it correctly for TCP 
connection.

You can use the ssh auth, it doesn't use a privileged port.

Jean-Louis

How to accept Source-High-Ports on an Amanda Client

[Thomas Marko]

Hi!

I have an Amanda Server running behind a Check Point Firewall (R75.20). 
Connections to the Internet are natted behind the firewall's external IP 
address thus the source port as well as the source ip address is translated.
 
The Amanda client (3.2.1) runs on a machine directly connected to the Internet 
(no NAT).

When checking the next backup with amcheck, I get the following error message:

ERROR: NAK : host : port 27271 not secure

There is a kernel parameter for Check Point firewall, affecting the behavior 
for NAT of UDP privileged source ports. As default, Check Point (should) 
translate(s) the source port to a privileged port if the original source port 
was a privileged port:

fwx_udp_hide_high: When not "0", a UDP connection from this (low) port will be 
hidden behind high port (1+) instead of low ports (600-1023).

As this parameter is default 0 (as well as on my firewall), the connection 
should be natted as described above, but it isn't. The source port is always a 
high port >1.

Anyway, how can I achieve, that Amanda accepts such translated connections 
(xlated to high ports)?

Thank you!

Regards,
Thomas

Amanda client on Solaris 8 (SPARC)

[Neil Carter]

Greetings:

This is another information gathering effort...

I've got one old server that needs to be backed up with the remainder of my
servers. The issue is that it's running Solaris 8 (SPARC) for an OS and,
no, that can't be changed.

Based upon research:

-- the current 3.3.0, which the remainder of my system is built on, won't
work on Solaris 8 due to package requirements, etc.

-- I can only go back so far, 2.4?, to get a client that will work with the
3.3.0 server.

If any of this is incorrect, please reply.

So, what can anyone tell me about which version of the client will compile
on Solaris 8 and work with the 3.3.0 server?

Thanks!

Neil

Re: MAC Amanda client backup

[Pieter Bowman]

>> ...
>>I did installed 2.5.0p2 client with same options that mentioned above
>> wiki page. Then I started the launch daeomns for bsdudp, For some reason I
>> am seeinng follwing error in logs on
>> 
>>com.apple.launchd[1] org.amanda.amandad.basdudp getpwnam("amandabackup")
>> failed
>>com.apple.launchd[1] org.amanda.amandad.bsdudp  Exited with exit code 1.
>> 
>> 
>> Any inputs how to fix this.
>> ...

You need to create the user amandabackup.  You can do that via System
Preferences->Accounts.

Pieter

Re: MAC Amanda client backup

[Brian Cuttler]

Ravikiran,

I'm sorry, the /tmp/amanda/server/* files will of course be
on your linux amanda server, rather than your MAC amanda client.

If you can find the logs for the server side of the connection,
please see if they tell you anything useful.

On the client side, double check the .amandahosts file in the
amanda user's login directory, check that your equiv of xinetd
is running, check for any type of firewall or IP filter on the
client, for for that matter, any intermediate firewall that 
may exist between your client and server.



On Wed, Jul 06, 2011 at 02:41:46PM -0700, ravikiran velineni wrote:
> On Wed, Jul 6, 2011 at 1:45 PM, Pieter Bowman  wrote:
> 
> >
> > >> ...
> > >> > > I have downloded the tar file and built myself. i didnt find any
> > >> > > xinetd.files, I created one directory by myself xinetd.d and created
> > file
> > >> > > for amanda
> > >>
> > >> ... does your OS use a different mechanism for this ?
> > >> Solaris uses /etc/inetd.conf, I thought MAC used xinetd services
> > >> but if you aren't finding an /etc/xinet.d directory
> > >>
> > >> Is there such a service installed on your particular machine ?
> > >> Could that package have been removed or not been installed ?
> > >>
> > >> there is something odd here that we haven't quite gotten to yet
> > >> ...
> >
> > You may be able to find all your MacOS X questions answered here:
> >
> >
> > http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes/Installing_Amanda_on_Mac_OS_X
> >
> > Specifically look at the section about LaunchDaemons.
> >
> > Pieter
> >
> 
>I did installed seeing that page, even after launchind the daemons using
> that. no luck then I tried xineted,  My amanda server version is 2.5.0p2 and
> amanda client on mc os x is 2.6.1p2. Does this matters ?
> 
> 
> 
> -- 
> Cheers !
> "Don't ever let somebody tell you, you can't do something"
> Ravikiran .Velineni
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: MAC Amanda client backup

[Pieter Bowman]

>> ...
>> > > I have downloded the tar file and built myself. i didnt find any
>> > > xinetd.files, I created one directory by myself xinetd.d and created file
>> > > for amanda
>> 
>> ... does your OS use a different mechanism for this ?
>> Solaris uses /etc/inetd.conf, I thought MAC used xinetd services
>> but if you aren't finding an /etc/xinet.d directory
>> 
>> Is there such a service installed on your particular machine ?
>> Could that package have been removed or not been installed ?
>> 
>> there is something odd here that we haven't quite gotten to yet
>> ...

You may be able to find all your MacOS X questions answered here:

http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes/Installing_Amanda_on_Mac_OS_X

Specifically look at the section about LaunchDaemons.

Pieter

Re: MAC Amanda client backup

[Brian Cuttler]

Ravikiran,

On Wed, Jul 06, 2011 at 12:54:44PM -0700, ravikiran velineni wrote:
> > > There is no  error file, when I ran amcheck i am getting the
> > following
> > > error:   Selfcheck failed: timeout waiting for ACK
> >
> > That is very unusual, are you certain that neither the server
> > nor the client system has any files under /tmp/amanda ?
> >
> > Yes I checked one more time i didnt find any file on server and client in
> /tmp directory.

Normally you find a structure like, /tmp/amanda/server and
/tmp/amanda/client, each with *.debug files.

Are there any files being written to /var/log/* or whereever
else your OS may put log files ?

> > I have downloded the tar file and built myself. i didnt find any
> > xinetd.files, I created one directory by myself xinetd.d and created file
> > for amanda

... does your OS use a different mechanism for this ?
Solaris uses /etc/inetd.conf, I thought MAC used xinetd services
but if you aren't finding an /etc/xinet.d directory

Is there such a service installed on your particular machine ?
Could that package have been removed or not been installed ?

there is something odd here that we haven't quite gotten to yet

>   service amanda
>  {
>   socket_type = dgram
>   protocol  = udp
>   wait=  yes
>   user   = amanda
>   group  = disk
>   group = root
>   server  = /usr/local/libexec/amanda/amandad
>   groups  = yes
>   disable = no
> }
> 
> when I try to start this I get permission denied error ? I am running as
> root.
> 
> >
> > > >I didnt install xtar ,  I followed the documentation from this page
> > and
> > > installed.
> > >
> > >
> > >
> > http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes/Installing_Amanda_on_Mac_OS_X
> > >
> > >
> > >   I am running 2.6. client with 2.5.0p2 does it matters ?
> > >
> > >
> > >  Cheers,
> > > Ravi.
> > ---
> >   Brian R Cuttler brian.cutt...@wadsworth.org
> >   Computer Systems Support(v) 518 486-1697
> >   Wadsworth Center(f) 518 473-6384
> >   NYS Department of HealthHelp Desk 518 473-0773
> >
> >
> >
> > IMPORTANT NOTICE: This e-mail and any attachments may contain
> > confidential or sensitive information which is, or may be, legally
> > privileged or otherwise protected by law from further disclosure.  It
> > is intended only for the addressee.  If you received this in error or
> > from someone who was not authorized to send it to you, please do not
> > distribute, copy or use it or any attachments.  Please notify the
> > sender immediately by reply e-mail and delete this from your
> > system. Thank you for your cooperation.
> >
> >
> >
> 
> 
> -- 
> Cheers !
> "Don't ever let somebody tell you, you can't do something"
> Ravikiran .Velineni
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: Amanda client backup

[Brian Cuttler]

Ravikiran,

You may want to do a group reply, see if anyone in the amanda
users list other than myself has any input.


On Wed, Jul 06, 2011 at 10:42:26AM -0700, ravikiran velineni wrote:
> On Wed, Jul 6, 2011 at 8:50 AM, Brian Cuttler  wrote:
> > We are backing up MacOS from Solaris, shouldn't be too different.
> >
> > Do you have any error messages or log files you can share ?
> >
> 
> There is no  error file, when I ran amcheck i am getting the following
> error:   Selfcheck failed: timeout waiting for ACK

That is very unusual, are you certain that neither the server
nor the client system has any files under /tmp/amanda ?

You built amanda ? Downloaded a prebuild package ?
Updated xinet.d files ?


> >I didnt install xtar ,  I followed the documentation from this page and
> installed.
> 
> 
> http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes/Installing_Amanda_on_Mac_OS_X
> 
> 
>   I am running 2.6. client with 2.5.0p2 does it matters ?
> 
> 
>  Cheers,
> Ravi.
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: Amanda client backup

[Brian Cuttler]

Ravikiran,

We are backing up MacOS from Solaris, shouldn't be too different.

Do you have any error messages or log files you can share ?

Did # amcheck run ok but # amdump fail ?

Did you install xtar on the client, since gtar will not pick
up all of the information that is secreted in the client's
file system ?



On Tue, Jul 05, 2011 at 11:59:05PM -0500, ravikiran velineni wrote:
> Hi Brian,
> 
> I am using trying to backup mac os x 10.6 server using amanda backup. I am
> running amanda server on liunx box. My server version is 2.5.1p2 and client
> is 2.6. I was able to install every thing fine and ran launchd opened the
> bsdudp ports, but when server tries to connect it is not able to connect
> properly.  Do you have any idea ?
> 
> 
> -- 
> Cheers !
> "Don't ever let somebody tell you, you can't do something"
> Ravikiran .Velineni
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: setting up Amanda client on ubuntu 8.04

[Chris Hoogendyk]

OK, I got it ironed out. Fairly simple.

I spent some time installing and configuring xinetd for Amanda; but, in 
the end, I don't think I needed it. I'm using auth=ssh, and in looking 
for the right configuration for that, I came across a statement from one 
of the amanda developers saying auth=ssh doesn't use inetd or xinetd. 
Makes sense. That would explain amcheck giving error messages that 
seemed to come from amanda on the client even before I had installed and 
configured xinetd. I haven't gone the step of removing that 
configuration and seeing if things still work, but I will.


The actual error that caused all the errors I was seeing from amcheck 
was the inability of the loader to find the libamandad libraries. I had 
built from source, and it didn't make sense to me that it didn't work. 
However `ldd -v /usr/local/libexec/amandad` said it couldn't find them. 
Then I found some postings on help.ubuntu.com relating to installing 
other software that said you would have to do `sudo ldconfig 
/usr/local/lib` in order to configure the loader with the latest 
additions to /usr/local/lib. I did that, and then ldd worked and amcheck 
from the server moved on.


Then I just had to create /usr/local/var/amanda/gnutar-lists/ with 
ownership by amanda:amanda.


After that, I got successful backups of the ubuntu client last night.

Now I have to move on to several other ubuntu servers hanging off a 
Solaris Amanda backup server in another building. Should be easy now, 
having a clean example with detailed notes.



---

Chris Hoogendyk

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




--- 


Erdös 4





Chris Hoogendyk wrote:
I'm feelling like a real newbie here. I'm finally getting around to 
working on some ubuntu servers. I did not install or configure ubuntu, 
but I do have an admin account and the cooperation of the person who 
did install them.


My Amanda server is Solaris 9 on SPARC, and all the backups I've done 
thus far have been with Solaris tools, fssnap, ufsdump, etc. This is 
my first attempt at ubuntu. I have Amanda 2.5.1p3 on the server. I 
checked aptget and found that the ubuntu package was 2.5.1p1. So, 
rather than take that or jump to 2.6.x, I just transferred my source 
over from the Amanda server and built it. I used --with-user=amanda 
--with-group=amanda --without-server --without-ipv6 
--with-ssh-security. Everything went smoothly. I followed a similar 
procedure to what I've done setting up other Solaris clients, setting 
up .amandahosts entries, opening /etc/hosts.allow, touch 
/etc/amandates, ssh back and forth to get known_hosts, and copy 
authorized_keys. I saw that /etc/services already had entries for amanda.


Then I set up my entries in amanda.conf and the disklist and ran an 
`amcheck daily`.


Watching auth.log on the ubuntu client, I see it accepting the key for 
amanda. However, nothing is ever noted in /tmp/amanda.


On the server, I get


mormyrid:/usr/local/etc/amanda/daily:amanda$ amcheck daily
Amanda Tape Server Host Check
-
Holding disk /var/spool/amanda/disk2: 133419362 KB disk space 
available, using 122933602 KB
Holding disk /var/spool/amanda/disk1: 136905679 KB disk space 
available, using 126419919 KB

slot 14: read label `bio-daily-027', date `20091217224501'
NOTE: skipping tape-writable test
Tape bio-daily-027 label ok
NOTE: host info dir 
/usr/local/etc/amanda/daily/curinfo/morrill-auth.bio.mor.nsm does not 
exist

NOTE: it will be created on the next run.
NOTE: index dir 
/usr/local/etc/amanda/daily/index/morrill-auth.bio.mor.nsm does not exist

NOTE: it will be created on the next run.
Server check took 29.425 seconds
/usr/local/libexec/amandad: error while loading shared libraries: 
libamandad-2.5.1p3.so: cannot open shared object file: No such file or 
directory


* Authorized Use Only *


Amanda Backup Client Hosts Check

WARNING: morrill-auth.bio.mor.nsm: selfcheck request failed: EOF on 
read from morrill-auth.bio.mor.nsm

Client check: 6 hosts checked in 12.117 seconds, 1 problem found

(brought to you by Amanda 2.5.1p3)



If I remove the entries for morrill-auth from the disklist, I get rid 
of all those errors



mormyrid:/usr/local/etc/amanda/daily:amanda$ amcheck daily
Amanda Tape Server Host Check
-
Holding disk /var/spool/amanda/disk2: 133419362 KB disk space 
available, using 122933602 KB
Holding disk /var/spool/amanda/disk1: 136905679 KB disk space 
available, using 126419919 KB

slot 14: read label `bio-daily-027', date `20091217224501'
NOTE: skipping tape-writable test
Tape bio-daily-027 label ok
Server check took 31.242 seconds

* Authorized Use Only *


Amanda Backup Client Hosts Check

Client check: 5 hosts checked in 2.073 seconds, 0 problems fo

setting up Amanda client on ubuntu 8.04

[Chris Hoogendyk]

I'm feelling like a real newbie here. I'm finally getting around to 
working on some ubuntu servers. I did not install or configure ubuntu, 
but I do have an admin account and the cooperation of the person who did 
install them.


My Amanda server is Solaris 9 on SPARC, and all the backups I've done 
thus far have been with Solaris tools, fssnap, ufsdump, etc. This is my 
first attempt at ubuntu. I have Amanda 2.5.1p3 on the server. I checked 
aptget and found that the ubuntu package was 2.5.1p1. So, rather than 
take that or jump to 2.6.x, I just transferred my source over from the 
Amanda server and built it. I used --with-user=amanda 
--with-group=amanda --without-server --without-ipv6 --with-ssh-security. 
Everything went smoothly. I followed a similar procedure to what I've 
done setting up other Solaris clients, setting up .amandahosts entries, 
opening /etc/hosts.allow, touch /etc/amandates, ssh back and forth to 
get known_hosts, and copy authorized_keys. I saw that /etc/services 
already had entries for amanda.


Then I set up my entries in amanda.conf and the disklist and ran an 
`amcheck daily`.


Watching auth.log on the ubuntu client, I see it accepting the key for 
amanda. However, nothing is ever noted in /tmp/amanda.


On the server, I get


mormyrid:/usr/local/etc/amanda/daily:amanda$ amcheck daily
Amanda Tape Server Host Check
-
Holding disk /var/spool/amanda/disk2: 133419362 KB disk space available, 
using 122933602 KB
Holding disk /var/spool/amanda/disk1: 136905679 KB disk space available, 
using 126419919 KB

slot 14: read label `bio-daily-027', date `20091217224501'
NOTE: skipping tape-writable test
Tape bio-daily-027 label ok
NOTE: host info dir 
/usr/local/etc/amanda/daily/curinfo/morrill-auth.bio.mor.nsm does not exist

NOTE: it will be created on the next run.
NOTE: index dir 
/usr/local/etc/amanda/daily/index/morrill-auth.bio.mor.nsm does not exist

NOTE: it will be created on the next run.
Server check took 29.425 seconds
/usr/local/libexec/amandad: error while loading shared libraries: 
libamandad-2.5.1p3.so: cannot open shared object file: No such file or 
directory


* Authorized Use Only *


Amanda Backup Client Hosts Check

WARNING: morrill-auth.bio.mor.nsm: selfcheck request failed: EOF on read 
from morrill-auth.bio.mor.nsm

Client check: 6 hosts checked in 12.117 seconds, 1 problem found

(brought to you by Amanda 2.5.1p3)



If I remove the entries for morrill-auth from the disklist, I get rid of 
all those errors



mormyrid:/usr/local/etc/amanda/daily:amanda$ amcheck daily
Amanda Tape Server Host Check
-
Holding disk /var/spool/amanda/disk2: 133419362 KB disk space available, 
using 122933602 KB
Holding disk /var/spool/amanda/disk1: 136905679 KB disk space available, 
using 126419919 KB

slot 14: read label `bio-daily-027', date `20091217224501'
NOTE: skipping tape-writable test
Tape bio-daily-027 label ok
Server check took 31.242 seconds

* Authorized Use Only *


Amanda Backup Client Hosts Check

Client check: 5 hosts checked in 2.073 seconds, 0 problems found

(brought to you by Amanda 2.5.1p3)



I'm seeing a couple of things here. One is that the shared object file 
error appears when I try to use the linux gnutar dump type. The other is 
that I'm getting an EOF back from morrill-auth. Am I going to need to 
recompile Amanda on my server to get some feature that wasn't included 
when I originally set it up? I'm using wrappers for ufsdump. But it 
shouldn't be asking for anything on the server, it should be calling the 
ubuntu server and asking it to do its thing.


I also noticed that xinetd is not installed on the ubuntu server. Since 
I'm unfamiliar with either ubuntu or xinetd, I'm puzzled why it wasn't 
installed by default if it is needed to launch the services that are in 
/etc/services by default.


Sorry if this seems a bit scattered. I'm way late getting out of here today.

TIA


--
---

Chris Hoogendyk

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




--- 


Erdös 4

Re: Dumpdates for Amanda client?

[stan]

On Wed, Dec 30, 2009 at 12:19:13PM -0600, Dr 440 wrote:
> 
> 
>I'm using zmanda client 2.6.1, and I am trying to find the windows 
> equivalent of unix's dumpdates file so I can debug a server issue. 
> 
>Does such an equivalent file/mechanism exist on the zmanda windows client? 
> I see there is also a zwc-mysql application running as a service that works 
> with zmanda. Is there any way to retrieve the data from there?

Boy, I would think any stnadard query tool that could connect to MySQL
would work. But I am no Windows expert. We just started using this client,
and have found the logfile generated by the client to be a useful debging
tool. alos, maybe that will help.

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Dumpdates for Amanda client?

[Dr 440]

   I'm using zmanda client 2.6.1, and I am trying to find the windows 
equivalent of unix's dumpdates file so I can debug a server issue. 

   Does such an equivalent file/mechanism exist on the zmanda windows client? I 
see there is also a zwc-mysql application running as a service that works with 
zmanda. Is there any way to retrieve the data from there?

Re: amanda client issue, dumps failing

[Brian Cuttler]

On Wed, Aug 12, 2009 at 02:31:17PM -0400, Jean-Louis Martineau wrote:
> Brian,
> 
> gtar read the complete directory hierarchy before sending data, it can 
> take a long time if you have a lot of files.

Ok, will keep an eye. Looking at the sendfile log we are down
to at least ./spool/imap/user/gling, but if its only headers
at this point we could be in for a long run.

Snapshots... move to ZFS, let amanda halt the mail system while
it performs the snapshot (which is very fast on ZFS) and then
result mail... So, step 1, update mailserv to Solaris 10, 2)
convert the file system 3)...all without having good backups
to start.

Apreciate your helping us out of yet another situation we
created ourselves.

> Jean-Louis
> 
> Brian Cuttler wrote:
> >cool thanks.
> >
> >its working, but its crawling.
> >
> >20 minutes and little actual data moved. Which I realized
> >is not an amanda issue.
> >
> >mailserv:/usr1 0 82499m dumping0m (  0.00%) (13:52:17)
> >
> >
> >On Wed, Aug 12, 2009 at 01:38:21PM -0400, Jean-Louis Martineau wrote:
> >  
> >>Brian,
> >>
> >>Try "estimate calcsize" or "estimate server"
> >>
> >>Jean-Louis
> >>
> >>Brian Cuttler wrote:
> >>
> >>>Amanda users,
> >>>
> >>>For the issue below, we have see several hundred thousand emails
> >>>move through the system system each day. UFSdump is failing because
> >>>it seems too many files come and go, queries to "continue" but can't
> >>>get a reply (I don't know of a way anyway).
> >>>
> >>>We tried to switch the problem DLE to gtar - but the estimate phase
> >>>seems to take hours to run. I haven't set etimeout high enough to get
> >>>a estimate yet, and this will push actual dumps back by hours.
> >>>
> >>>Is there a workaround I can employ, either to get quicker estimates
> >>>(ok to assume level 0 is the usage of the partition) or get ufsdump
> >>>to work ?
> >>>
> >>>I've recommended we do something to quiess the system, but our mail god
> >>>hasn't seemed to take any interested in that suggestion. Nor do we 
> >>>currently have a mechanism to snapshot or replicate (rsync, break a
> >>>mirror, etc) the partition.
> >>>
> >>>   thanks,
> >>>
> >>>   Brian
> >>>
> >>>- Forwarded message from Brian Cuttler  -
> >>>
> >>>Date: Tue, 11 Aug 2009 11:37:35 -0400
> >>>From: Brian Cuttler 
> >>>To: daver , amanda-users@amanda.org,
> >>>   Chris Knight 
> >>>Cc: Ivan Auger 
> >>>Subject: Re: amanda probelm
> >>>In-Reply-To: <4a818aa0.5070...@wadsworth.org>
> >>>User-Agent: Mutt/1.4.1i
> >>>
> >>>
> >>>Reviewing the issue.
> >>>
> >>>Server, Solaris 10x86, Amanda 2.6.1 (with patches)
> >>>Client, Solaris 9, Amanda  2.4.4
> >>>
> >>>The problem performing level 0 dumps is that there are a large
> >>>number of files in flux -- its the mailhost system -- so ufsdump
> >>>eventually asks for help, to continue or quit.
> >>>
> >>>There is no help in non-interactive mode, and I don't know if there
> >>>is a mechanism to get amanda to respond to ufsdump's query. So the
> >>>level 0 of /usr1 usually fails.
> >>>
> >>>Warnings - Dave's suggestion, that the history of the error be more
> >>>explicite is a good one. Can # amdump report last successful level 0,
> >>>ie due date, if current level zero fails ? Put it in the notes 
> >>>section or something ?
> >>>
> >>>Non-solutions - a snapshot of an open file is an open file. All things
> >>>being equal, you will get as many open files in a snapshot as in a
> >>>live system. This will not resolve the problem.
> >>>
> >>>Work arounds
> >>>   1) quiess the mail server for a period of time, force a level 0
> >>>  of /usr1 during that interval.
> >>>
> >>>   2) Quiess mail delivery long enough to snapshot/rsync or break
> >>>  a mirror. Backup the placid copy.
> >>>
> >>>   3) Q: will a TAR of the DLE get a backup when ufsdump can not ?
> >>>
> >>>   4) "Its not really a problem."
> >>>  By and large each individual message will be backed up "most"
> >>>  of the time, each message is its own file and if its not on
> >>>  the level 0 its on almost all of the level 1 and 2 dumps.
> >>>  What we will lose are the index files, which would probably
> >>>  require a rebuild after a restore anyway, so that are not
> >>>  that important to get only tape.
> >>>
> >>>
> >>>On Tue, Aug 11, 2009 at 11:13:36AM -0400, daver wrote:
> >>> 
> >>>  
> brian checking over all the overdue files systems on curie, I find only 
> mailserv:/usr1 is truly overdue
> 
> As you mentioned., this may be due to the system being too active.  
> there are NO warnings, in this regard, with the exception of a "Can't 
> switch to degraded mode for unknown reason" in amdump
> 
> as we just about never read these amanda files and use the email 
> generated by the system to notify us of problems, this would seem to be 
> a significant problem with Amanda.  I agree that the developers should

Re: amanda client issue, dumps failing

[Chris Hoogendyk]

yes, /var/mail does tend to be a problem. My mail.log can get to a 
quarter million lines a day, but that's not the same as getting that 
number of messages. Typically, my level 1 backups aren't much different 
from the level 0, because basically everything changes every day. I get 
by with fssnap. That isn't the same as quiescing the system, but it 
reduces exposure to issues to the time it takes to do the snapshot. The 
thing is, with an active mail system you need a place for the backing 
store that is nearly as large as the mail partition, because things are 
going to change while you are backing up, so they will have to get copied.


If your mail admin isn't cooperative, ask your mail admin, or your mail 
admin's boss, whether they care about having backups. Ask them if it is 
alright not to have a backup. You could even ask them if there are any 
legal requirements relating to discovery, etc. (NYS Dept. of Health? 
I'll bet there are!) That might get you in deeper than you want, but 
hey, it should get some attention.


For details on how I do it (on Solaris 9), see 
http://wiki.zmanda.com/index.php/Backup_client#Chris_Hoogendyk.27s_Example.


If they would allow it, you could set up a sudo entry for the amanda 
user to stop sendmail, take a snapshot, and start sendmail again (or 
whatever mail software you are using). It would be sort of like what I 
have for stopping xntpd to snapshot the root partition, but you would 
special case it for the /var/mail partition. Presumably, they have the 
/etc/init.d/sendmail or similar script properly set up so that you won't 
be in danger of screwing things up. Presumably, they would work with you 
to get it going.



---

Chris Hoogendyk

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




--- 


Erdös 4




Brian Cuttler wrote:

Amanda users,

For the issue below, we have see several hundred thousand emails
move through the system system each day. UFSdump is failing because
it seems too many files come and go, queries to "continue" but can't
get a reply (I don't know of a way anyway).

We tried to switch the problem DLE to gtar - but the estimate phase
seems to take hours to run. I haven't set etimeout high enough to get
a estimate yet, and this will push actual dumps back by hours.

Is there a workaround I can employ, either to get quicker estimates
(ok to assume level 0 is the usage of the partition) or get ufsdump
to work ?

I've recommended we do something to quiess the system, but our mail god
hasn't seemed to take any interested in that suggestion. Nor do we 
currently have a mechanism to snapshot or replicate (rsync, break a

mirror, etc) the partition.

thanks,

Brian

- Forwarded message from Brian Cuttler  -

Date: Tue, 11 Aug 2009 11:37:35 -0400
From: Brian Cuttler 
To: daver , amanda-users@amanda.org,
Chris Knight 
Cc: Ivan Auger 
Subject: Re: amanda probelm
In-Reply-To: <4a818aa0.5070...@wadsworth.org>
User-Agent: Mutt/1.4.1i


Reviewing the issue.

Server, Solaris 10x86, Amanda 2.6.1 (with patches)
Client, Solaris 9, Amanda  2.4.4

The problem performing level 0 dumps is that there are a large
number of files in flux -- its the mailhost system -- so ufsdump
eventually asks for help, to continue or quit.

There is no help in non-interactive mode, and I don't know if there
is a mechanism to get amanda to respond to ufsdump's query. So the
level 0 of /usr1 usually fails.

Warnings - Dave's suggestion, that the history of the error be more
explicite is a good one. Can # amdump report last successful level 0,
ie due date, if current level zero fails ? Put it in the notes 
section or something ?


Non-solutions - a snapshot of an open file is an open file. All things
being equal, you will get as many open files in a snapshot as in a
live system. This will not resolve the problem.

Work arounds
1) quiess the mail server for a period of time, force a level 0
   of /usr1 during that interval.

2) Quiess mail delivery long enough to snapshot/rsync or break
   a mirror. Backup the placid copy.

3) Q: will a TAR of the DLE get a backup when ufsdump can not ?

4) "Its not really a problem."
   By and large each individual message will be backed up "most"
   of the time, each message is its own file and if its not on
   the level 0 its on almost all of the level 1 and 2 dumps.
   What we will lose are the index files, which would probably
   require a rebuild after a restore anyway, so that are not
   that important to get only tape.


On Tue, Aug 11, 2009 at 11:13:36AM -0400, daver wrote:
  
brian checking over all the overdue files systems on curie, I find only 
mailserv:/usr1 is truly overdue


As you mentioned., this may be due to the system being too active

amanda client issue, dumps failing

[Brian Cuttler]

Amanda users,

For the issue below, we have see several hundred thousand emails
move through the system system each day. UFSdump is failing because
it seems too many files come and go, queries to "continue" but can't
get a reply (I don't know of a way anyway).

We tried to switch the problem DLE to gtar - but the estimate phase
seems to take hours to run. I haven't set etimeout high enough to get
a estimate yet, and this will push actual dumps back by hours.

Is there a workaround I can employ, either to get quicker estimates
(ok to assume level 0 is the usage of the partition) or get ufsdump
to work ?

I've recommended we do something to quiess the system, but our mail god
hasn't seemed to take any interested in that suggestion. Nor do we 
currently have a mechanism to snapshot or replicate (rsync, break a
mirror, etc) the partition.

thanks,

Brian

- Forwarded message from Brian Cuttler  -

Date: Tue, 11 Aug 2009 11:37:35 -0400
From: Brian Cuttler 
To: daver , amanda-users@amanda.org,
Chris Knight 
Cc: Ivan Auger 
Subject: Re: amanda probelm
In-Reply-To: <4a818aa0.5070...@wadsworth.org>
User-Agent: Mutt/1.4.1i


Reviewing the issue.

Server, Solaris 10x86, Amanda 2.6.1 (with patches)
Client, Solaris 9, Amanda  2.4.4

The problem performing level 0 dumps is that there are a large
number of files in flux -- its the mailhost system -- so ufsdump
eventually asks for help, to continue or quit.

There is no help in non-interactive mode, and I don't know if there
is a mechanism to get amanda to respond to ufsdump's query. So the
level 0 of /usr1 usually fails.

Warnings - Dave's suggestion, that the history of the error be more
explicite is a good one. Can # amdump report last successful level 0,
ie due date, if current level zero fails ? Put it in the notes 
section or something ?

Non-solutions - a snapshot of an open file is an open file. All things
being equal, you will get as many open files in a snapshot as in a
live system. This will not resolve the problem.

Work arounds
1) quiess the mail server for a period of time, force a level 0
   of /usr1 during that interval.

2) Quiess mail delivery long enough to snapshot/rsync or break
   a mirror. Backup the placid copy.

3) Q: will a TAR of the DLE get a backup when ufsdump can not ?

4) "Its not really a problem."
   By and large each individual message will be backed up "most"
   of the time, each message is its own file and if its not on
   the level 0 its on almost all of the level 1 and 2 dumps.
   What we will lose are the index files, which would probably
   require a rebuild after a restore anyway, so that are not
   that important to get only tape.


On Tue, Aug 11, 2009 at 11:13:36AM -0400, daver wrote:
> brian checking over all the overdue files systems on curie, I find only 
> mailserv:/usr1 is truly overdue
> 
> As you mentioned., this may be due to the system being too active.  
> there are NO warnings, in this regard, with the exception of a "Can't 
> switch to degraded mode for unknown reason" in amdump
> 
> as we just about never read these amanda files and use the email 
> generated by the system to notify us of problems, this would seem to be 
> a significant problem with Amanda.  I agree that the developers should 
> be contacted in this regard.
> 
> as to getting /usr1 backed up. if amanda can't do it, perhaps we need to 
> consider an alternative. like tar
> 
> 
> 
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773


- End forwarded message -
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: amanda client package without amdump

[Andreas Kuntzagk]

Hi,

I wrongly had the idea that the client initiates the backup. (Upto now 
my only client has been the server itself) Now I see that it's the 
server starting the backup so having amdump in the Serverpackage makes 
sense.


Now I only have to figure out some communication issues between server 
and client.


Will get back with more questions ;-)

thanks, Andreas


On Wed, 2009-07-15 at 10:02 +0200, Andreas Kuntzagk wrote:

Hi,

I installed amanda-backup-client_2.6.1p1-1_amd64.deb on a Ubuntu Server 
8.04. Now I see that there is no amdump in it. Shouldn't that be part of 
the client? Or do I need to install the server-package?


amdump is in the amanda-server package.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 8.04.2
Release:8.04
Codename:   hardy

$ dpkg -S /usr/sbin/amdump
amanda-server: /usr/sbin/amdump

Thanks,

Re: amanda client package without amdump

[Mark Fisher]

On Wed, 2009-07-15 at 10:02 +0200, Andreas Kuntzagk wrote:
> Hi,
> 
> I installed amanda-backup-client_2.6.1p1-1_amd64.deb on a Ubuntu Server 
> 8.04. Now I see that there is no amdump in it. Shouldn't that be part of 
> the client? Or do I need to install the server-package?

amdump is in the amanda-server package.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 8.04.2
Release:8.04
Codename:   hardy

$ dpkg -S /usr/sbin/amdump
amanda-server: /usr/sbin/amdump

Thanks,

-- 
Mark Fisher

http://www.nativ-systems.com/  CONSULTING  ·  TECHNOLOGY  · OUTSOURCING
Nativ Systems Ltd. 23 - 25 Eastcastle Street, W1W 8DF
phone:  +44 (0)20 7580 9488 fax:+44 (0)20 7580 9489
Company Reg No.: 6071152 Company VAT No.: 889 1875 42
Registered in England and Wales

amanda client package without amdump

[Andreas Kuntzagk]

Hi,

I installed amanda-backup-client_2.6.1p1-1_amd64.deb on a Ubuntu Server 
8.04. Now I see that there is no amdump in it. Shouldn't that be part of 
the client? Or do I need to install the server-package?


regards, Andreas

[Amanda-users] amrecover and amanda-client conf file

[shantanu uab]

I have followed Amanda 15 minute guide, 
http://www.zmanda.com/quick-backup-setup.html  and Amanda quick start   guide, 
http://wiki.zmanda.com/index.php/Quick_start for the installation. I have 
following doubts regarding amanda client configuration file options. 
What is the config name option in it? If I specify my config option say 
labtops, then Amanda looks for the config file in the /etc/amanda/labtops 
directory. 

Does Amanda load /etc/amanda/amanda-client.conf file everytime we give command 
amrecover (with or without config name option on command line)?

Can we leave config name blank on command line as well as in the 
/etc/amanda/amanda-client.conf file? If not, do we need to create this config 
directory and another config file for every configuration? How are we supposed 
to use /etc/amanda/amanda-client.conf file and the conf file specific to 
particular configuration?

Can index server and tape server options have different values? or Do they 
point to same host (amanda server)? And is index server related to the index 
option in Amanda server conf file? 

huh... :?

--
Thanks,
Shantanu Pavgi.

+--
|This was sent by shantanu@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--