On Fri, Dec 16, 2016 at 08:48:12AM -0500, Jean-Louis Martineau wrote:
> Can you run 'amcheck -c DS1 cyber' on the server (mums.jgcomp.com)?
> 

Yes, that works fine.  Backups are working also.

Note Jean-Louis, my DLEs use hostnames rather than FQDNs.
So "amcheck -c DS1 cyber.jgcomp.com" fails with:

  Argument 'cyber.jgcomp.com' matches neither a host nor a disk.

Jon
> Jean-Louis
> 
> On 15/12/16 10:23 PM, Jon LaBadie wrote:
> > I have finally gotten amdump_client "trying" to work.
> > Had to modify the systemd [email protected] unit file.
> > 
> > Of the three amdump_client commands, list works, check
> > fails (below), and dump shows not errors but ends quickly.
> > 
> > The server is CentOS 7.2, Amanda 3.3.3 and the client is
> > Fedora 24, Amanda 3.3.9.
> > 
> > Here is a run:
> > 
> >    $ amdump_client --config DS1 check
> >    config: DS1
> >    CHECKING
> > 
> >    Amanda Backup Client Hosts Check
> >    --------------------------------
> >    WARNING: cyber: selfcheck request failed: Permission denied
> >    Client check: 1 host checked in 13.365 seconds.  1 problem found.
> > 
> >    (brought to you by Amanda 3.3.3)
> >    The check is finished
> > 
> > The two debug files created on the client are:
> > 
> > amdump_client
> >    pid 3354 ruid 33 euid 33 version 3.3.9: start at Thu Dec 15 17:43:08 2016
> >    Arguments: --config DS1 check
> >    pid 3354 ruid 33 euid 33 version 3.3.9: rename at Thu Dec 15 17:43:08 
> > 2016
> >    cmd: /usr/sbin/amservice -f /dev/null -s mums.jgcomp.com bsdtcp amdumpd
> >    send: CONFIG DS1
> >    send: CHECK
> >    send: END
> >    ru_utime   : 0
> >    ru_stime   : 0
> >    ru_maxrss  : 19296
> >    ru_ixrss   : 0
> >    ru_idrss   : 0
> >    ru_isrss   : 0
> >    ru_minflt  : 2849
> >    ru_majflt  : 0
> >    ru_nswap   : 0
> >    ru_inblock : 0
> >    ru_oublock : 16
> >    ru_msgsnd  : 0
> >    ru_msgrcv  : 0
> >    ru_nsignals: 0
> >    ru_nvcsw   : 5
> >    ru_nivcsw  : 3
> >    pid 3354 finish time Thu Dec 15 17:43:22 2016
> > 
> > amservice
> >    pid 3355 ruid 0 euid 33 version 3.3.9: start at Thu Dec 15 17:43:08 2016
> >    security_getdriver(name=bsdtcp) returns 0x7fd09fa77820
> >    security_handleinit(handle=0x55ebae217980, driver=0x7fd09fa77820 
> > (BSDTCP))
> >    security_streaminit(stream=0x55ebae21e090, driver=0x7fd09fa77820 
> > (BSDTCP))
> >    connect_port: Skip port 512: owned by exec.
> >      [ 57 Skip port lines snipped ]
> >    connect_port: Skip port 570: owned by meter.
> >    make_socket opening socket with family 2
> >    connect_port: Try  port 571: available - Success
> >    connected to 205.166.177.17:10080
> >    our side is 0.0.0.0:571
> >    try_socksize: send buffer size is 65536
> >    try_socksize: receive buffer size is 65536
> >    tcpm_send_token: data is still flowing
> >    REP: CONNECT CTL 499999
> > 
> >    REP:
> > 
> >    security_streaminit(stream=0x55ebae2260f0, driver=0x7fd09fa77820 
> > (BSDTCP))
> >    security_close(handle=0x55ebae217980, driver=0x7fd09fa77820 (BSDTCP))
> >    security_stream_close(0x55ebae21e090)
> >    failed to write to stdout: Resource temporarily unavailable
> >    stream_read_callback: data is still flowing
> >    failed to write to stdout: Resource temporarily unavailable
> >    failed to write to stdout: Resource temporarily unavailable
> >    failed to write to stdout: Resource temporarily unavailable
> >    security_stream_close(0x55ebae2260f0)
> >    ru_utime   : 0
> >    ru_stime   : 0
> >    ru_maxrss  : 12208
> >    ru_ixrss   : 0
> >    ru_idrss   : 0
> >    ru_isrss   : 0
> >    ru_minflt  : 556
> >    ru_majflt  : 0
> >    ru_nswap   : 0
> >    ru_inblock : 0
> >    ru_oublock : 24
> >    ru_msgsnd  : 0
> >    ru_msgrcv  : 0
> >    ru_nsignals: 0
> >    ru_nvcsw   : 12
> >    ru_nivcsw  : 5
> >    pid 3355 finish time Thu Dec 15 17:43:22 2016
> > 
> > Suggestions of where to look next appreciated.
> > 
> > Jon
>>> End of included message <<<

-- 
Jon H. LaBadie                 [email protected]
 11226 South Shore Rd.          (703) 787-0688 (H)
 Reston, VA  20190              (703) 935-6720 (C)

Reply via email to