Re: big update killed 1 host

2017-02-03 Thread Jean-Louis Martineau
Ask the amanda and systemd package maintainer for centos. Since your problem is to backup the amanda server,you can try to use the "local" auth. Jean-Louis On 02/02/17 04:04 PM, Jon LaBadie wrote: > On Sun, Jan 29, 2017 at 10:45:37PM -0500, Jon LaBadie wrote: >> I added updates to my CentOS

Re: big update killed 1 host

2017-02-02 Thread Jon LaBadie
On Sun, Jan 29, 2017 at 10:45:37PM -0500, Jon LaBadie wrote: > I added updates to my CentOS Amanda server that > changed the OS release from 7.2 to 7.3. Amanda > version remained at 3.3.3. Before update, all > clients including the server were working fine. > > After the update, all clients

Re: big update killed 1 host

2017-01-30 Thread Jon LaBadie
On Mon, Jan 30, 2017 at 02:07:46PM -0500, Jean-Louis Martineau wrote: > Jon, > > Why systemd print the ExecStart on the socket? it's a systemd bug or a > misconfiguration. > > Jean-Louis > I don't know that "systemd" is printing the string. I simply said the string matches what is in the

Re: big update killed 1 host

2017-01-30 Thread Stefan G. Weichinger
Am 2017-01-30 um 20:07 schrieb Jean-Louis Martineau: > Jon, > > Why systemd print the ExecStart on the socket? it's a systemd bug or a > misconfiguration. correct, it should be in amanda@.service -> (on gentoo linux): # cat /usr/lib64/systemd/system/amanda@.service [Unit] Description=Amanda

Re: big update killed 1 host

2017-01-30 Thread Jean-Louis Martineau
Jon, Why systemd print the ExecStart on the socket? it's a systemd bug or a misconfiguration. Jean-Louis On 30/01/17 12:38 AM, Jon LaBadie wrote: > Follow-up, > > amrecover gives the same error whether run from the server/client > or from another client. > > On the server/client I also ran: >

Re: big update killed 1 host

2017-01-30 Thread Stefan G. Weichinger
Am 2017-01-30 um 06:38 schrieb Jon LaBadie: > Follow-up, > > amrecover gives the same error whether run from the server/client > or from another client. > > On the server/client I also ran: > > $ amservice mums.jgcomp.com bsdtcp noop < /dev/null > Request failed: tcpm_recv_token: invalid

Re: big update killed 1 host

2017-01-29 Thread Jon LaBadie
Follow-up, amrecover gives the same error whether run from the server/client or from another client. On the server/client I also ran: $ amservice mums.jgcomp.com bsdtcp noop < /dev/null Request failed: tcpm_recv_token: invalid size: "Executing: \ /usr/sbin/amandad