amanda service on client seems to trasition to maintenance on amcheck from server

[solamanda]

amanda service on client seems to trasition to maintenance on amcheck from server

On, Solaris 10 x86, I, downloaded amanda via pkg-get

server:
# uname -a
SunOS server 5.10 Generic_118855-33 i86pc i386 i86pc
# cat /etc/release
Solaris 10 11/06 s10x_u3wos_10 X86
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 14 November 2006
#



$ amlabel weekly weekly001
rewinding, reading label, not an amanda tape
rewinding, writing label weekly001, checking label, done.
$ amcheck weekly
Amanda Tape Server Host Check
-----------------------------
Holding disk /amandadisk: 13870244 disk space available, that's plenty
NOTE: skipping tape-writable test
Tape weekly001 label ok
NOTE: info dir /usr/local/etc/amanda/CIS/curinfo: does not exist
NOTE: it will be created on the next run
NOTE: index dir /usr/local/etc/amanda/CIS/index: does not exist
Server check took 0.005 seconds

Amanda Backup Client Hosts Check
--------------------------------
WARNING: client.myamandasetup.com: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.036 seconds, 1 problem found

(brought to you by Amanda 2.4.4p4)
$

On server:
$ cat ~/.amandahosts
client.myamandasetup.com amanda
client amanda
$

On client:
# uname -a
SunOS client 5.10 Generic_137138-09 i86pc i386 i86pc
#

# cat /etc/release
Solaris 10 10/08 s10x_u6wos_07b X86
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 27 October 2008
#

$ ls -al
total 18
drwxr-xr-x 2 amanda sys 512 Jan 13 10:40 .
drwxr-xr-x 6 root bin 512 Jan 8 16:54 ..
-rw-r--r-- 1 amanda sys 40 Jan 13 11:22 .amandahosts

$ cat .aman*
server amanda
server.myamandasetup.com amanda
$


snoop on client:

72 0.08710 server -> client UDP D=10080 S=682 LEN=125
73 0.00009 client -> server ICMP Destination unreachable (UDP port 10080 unreachable)


Something interesting, A_PC_On_The_lan is a pc on the lan......why does snoop show this traffic...there's no amanda config on that pc....

598 0.13226 server -> A_PC_ON_The_lan TELNET R port=1583 \r\nAmanda Backup Clie
599 0.16638 A_PC_ON_The_lan -> server TELNET C port=1583
600 0.00015 server -> A_PC_ON_The_lan TELNET R port=1583 \r\n(brought to you by

Coming back to the issues of backing the client onto the server:

On client, before amcheck weekly is, on server run:
# svcs -a | grep amanda
online 14:30:07 svc:/network/amanda/udp:default

After running, on server, amcheck weekly, client shows:
# svcs -a | grep amanda
maintenance 14:33:54 svc:/network/amanda/udp:default



On client:
# grep amanda /etc/inetd.conf
amanda dgram udp wait amanda /opt/csw/libexec/amandad amandad

# grep amanda /etc/services
amanda 10080/udp


On server:
# svcs -a | grep amanda
online 15:06:51 svc:/network/amanda/udp:default
#
# grep amanda /etc/inetd.conf
amanda dgram udp wait amanda /opt/csw/libexec/amandad amandad
# grep amanda /etc/services
amanda 10080/udp # Amanda

[pyeatman]

Can the service on the client then be easily restarted with, say

# svcadm clear svc:/network/amanda/udp:default
# svcadm restart svc:/network/amanda/udp:default

Do system and possibly Amanda logs on the client offer any more detail?

Paul

[solamanda]

yes the service is restarted that way....

what is the log location?

[pyeatman]

Amanda logs are in /var/log/amanda. Of course, Solaris system messages are in /var/adm/messages.