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 -auth=bsdtcp amdump amdumpd\n"
According to one wiki document,
http://wiki.zmanda.com/index.php/Selfcheck_request_failed
this suggests a failure in bsdtcp authentication.
BTW the string "/usr/sbin/amandad -auth=bsdtcp amdump amdumpd"
matches the "ExecStart=" value in the systemd service file
"/usr/lib/systemd/system/amanda@.service".
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 backed up fine
> except the server itself.
>
> amcheck <config> -c <server> gives an error:
> tcpm_recv_token: Invalid size.
>
> The amcheck debug file ends with reading a string
> from a socket and saying:
>
> amcheck-clients: tcpm_recv_token: invalid size "Executing:
> /usr/sbin/amandad \
> -auth=bsdtcp amdump amdumpd\n"
> amcheck-clients: security_stream_seterr(0x7f6be589fac0, tcpm_recv_token: \
> invalid size: "Executing: /usr/sbin/amandad \
> -auth=bsdtcp amdump amdumpd\n")
>
> The amandad debug file contains these lines:
>
> amandad: security_stream_seterr(0x7fcfccf15e00, write error to: \
> Bad file descriptor)
> amandad: security_seterror(handle=0x7fcfccf14f00, driver=0x7fcfcac0f7e0 \
> (BSDTCP) error=write error to: Bad file descriptor)
>
> The problem is neither firewall nor selinux
> related as I've turned both off and still see
> the same error.
>
> Ideas?
>
> Jon
> --
> Jon H. LaBadie j...@jgcomp.com
> 11226 South Shore Rd. (703) 787-0688 (H)
> Reston, VA 20190 (703) 935-6720 (C)
>>> End of included message <<<
--
Jon H. LaBadie j...@jgcomp.com
11226 South Shore Rd. (703) 787-0688 (H)
Reston, VA 20190 (703) 935-6720 (C)
