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

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

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

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

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

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

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

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 client packaging and ambind (amrecover error on client)

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

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

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

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

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

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

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! >

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

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

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

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

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

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

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

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

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

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

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"

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

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

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

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.

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

Re: restored amanda client errors out

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

Re: restored amanda client errors out

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

Re: restored amanda client errors out

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 > > >

Re: restored amanda client errors out

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

Re: restored amanda client errors out

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

Re: restored amanda client errors out

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

Re: restored amanda client errors out

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" [...] > >

Re: restored amanda client errors out

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

Re: restored amanda client errors out

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

Re: restored amanda client errors out

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

Re: restored amanda client errors out

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

Re: restored amanda client errors out

gt; 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 > >

Re: restored amanda client errors out

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

restored amanda client errors out

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

restored amanda client errors out

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

Re: amanda client on leap 15 system, ie systemd

> "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

amanda client on leap 15 system, ie systemd

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

Re: amanda client on updated debian-9.8

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, amdum

Re: amanda client on updated debian-9.8

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 ... Sol

Re: amanda client on updated debian-9.8

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

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

Re: amanda client on updated debian-9.8

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

Re: amanda client on updated debian-9.8

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

Re: amanda client on updated debian-9.8

: > 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? > >> > >>

Re: amanda client on updated debian-9.8

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

Re: amanda client on updated debian-9.8

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

Re: amanda client on updated debian-9.8

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

Re: amanda client on updated debian-9.8

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

Re: amanda client on updated debian-9.8

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

Re: amanda client on updated debian-9.8

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.

Re: amanda client on updated debian-9.8

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

Re: amanda client on updated debian-9.8

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 o

Re: amanda client on updated debian-9.8

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

Re: amanda client on updated debian-9.8

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 snippe

Re: amanda client on updated debian-9.8

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 a

amanda client on updated debian-9.8

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

updated amanda client

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

Re: Ubuntu 16.04 amanda-client package

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

Re: Ubuntu 16.04 amanda-client package

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

Re: Ubuntu 16.04 amanda-client package

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

Re: Ubuntu 16.04 amanda-client package

ult 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

Re: Ubuntu 16.04 amanda-client package

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. S

Re: Ubuntu 16.04 amanda-client package

int. > > 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 direct

Re: Ubuntu 16.04 amanda-client package

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

Re: Ubuntu 16.04 amanda-client package

On Fri, 14 Apr 2017 11:46:46 -0400 Chris Hoogendyk <hoogen...@bio.umass.edu> 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 a

Re: Ubuntu 16.04 amanda-client package

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

Re: Ubuntu 16.04 amanda-client package

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

Re: Ubuntu 16.04 amanda-client package

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

Re: Ubuntu 16.04 amanda-client package

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

Re: Ubuntu 16.04 amanda-client package

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

Re: Ubuntu 16.04 amanda-client package

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

Re: Ubuntu 16.04 amanda-client package

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,

Ubuntu 16.04 amanda-client package

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

Re: Amanda client weirdnesses on MacOSX

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:

Amanda client weirdnesses on MacOSX

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

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

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

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

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

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

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

Amanda client on Solaris 8 (SPARC)

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

Re: MAC Amanda client backup

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

Re: MAC Amanda client backup

... 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

Re: Amanda client backup

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

Re: Amanda client backup

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 br...@wadsworth.org wrote: We are backing up MacOS from

Re: MAC Amanda client backup

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

Re: MAC Amanda client backup

... 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

Re: setting up Amanda client on ubuntu 8.04

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

setting up Amanda client on ubuntu 8.04

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

Dumpdates for Amanda client?

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

Re: Dumpdates for Amanda client?

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

amanda client issue, dumps failing

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

Re: amanda client issue, dumps failing

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

Re: amanda client issue, dumps failing

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,

amanda client package without amdump

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

Re: amanda client package without amdump

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

Re: amanda client package without amdump

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

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

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

  1   2   3   4   >