Greetings;
I think I have it almost configured, amcheck reports one error as
follows:
manda@coyote:/GenesAmandaHelper-0.61$ /usr/sbin/amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /usr/dumps: 1533056 MB disk space available, using 1532556
MB
slot 1: cont
> But, changing user to amanda is not yet completed, after changing the
> amanda file in /etc/xinetd.d to user=amanda and restarting xinetd, I get this
> at the end of an amcheck:
> WARNING: coyote: selfcheck request failed: tcpm_recv_token: invalid
> size: "amandad: must be executed as the \"ba
On Monday 13 May 2019 12:53:22 pm Chris Hassell wrote:
> > But, changing user to amanda is not yet completed, after changing
> > the amanda file in /etc/xinetd.d to user=amanda and restarting
> > xinetd, I get this at the end of an amcheck:
> >
> > WARNING: coyote: selfcheck request failed: tcpm_r
AFAIK amanda always ran as "backup" under Debian, which caused some unexpected
side effects fir the home directory.
On May 13, 2019 2:05:36 PM EDT, Gene Heskett wrote:
>On Monday 13 May 2019 12:53:22 pm Chris Hassell wrote:
>
>> > But, changing user to amanda is not yet completed, after changing
On Mon, May 13, 2019 at 16:53:22 +, Chris Hassell wrote:
> Where was this built? Was it the default-from-debian? I may pull
> that apart to see how they decided it should be built by default.
Yes, I have been wanting to suggest that as you work on cleaning up the
Amanda-provided Debian packa
I can build and install. Hurrah!
I have a script that builds a runtime environment for amanda, including
building some vtapes. When I run that, all seems to run well, until I
go to build my vtape slots with amlabel. then I get a loop of:
--
21
Can't
On Mon, May 13, 2019 at 12:42:33 -0400, Gene Heskett wrote:
> Amanda Backup Client Hosts Check
>
> WARNING: coyote: selfcheck request failed: Connection refused <--
> Client check: 5 hosts checked in 10.010 seconds. 1 problem found.
>
> (brought to you by Aman
On Monday 13 May 2019 03:04:23 pm Winston Sorfleet wrote:
> AFAIK amanda always ran as "backup" under Debian, which caused some
> unexpected side effects fir the home directory.
>
Can you elaborate? I have never ran the distro version on the server,
this machine, but I have run the distro client
On Mon, May 13, 2019 at 18:37:15 -0400, Gene Heskett wrote:
> All the backups are user 34, with /var/backups as home dirs, and /bin/sh
> as login
Right. If you are running the official Debian package, that's the user
you care about.
> And there is NOT a /var/backup directory that actually exi
On Mon, May 13, 2019 at 14:36:09 -0600, Charles Curley wrote:
> The short of it is that JSON.pm is not in my @INC. It has been
> installed, at /usr/local/share/perl/5.24.1/Amanda/Report/. But that
> does not appear to be in my @INC array.
In my installation (Amanda 1:3.5.1-4~WIP+4 built for Ubuntu
(Sorry, I just noticed the separate thread on the topic of Debian
package building.)
On Sun, May 12, 2019 at 12:36:55 -0600, Charles Curley wrote:
> I now get
>
> --
> dh_fixperms -v >> /home/charles/amanda/build/debian/dpkg.log 2>&1
> # fix perms m
On Mon, May 13, 2019 at 16:18:36 -0400, Nathan Stratton Treadway wrote:
> Anyway, the place to look for Debian-specific changes would be in the
> Salsa repository:
> https://salsa.debian.org/debian/amanda/debian
Also, it may be useful to look at the buildd logs (e.g. to search for
"./configure"
12 matches
Mail list logo
