Hmmm.
I think the clue here may be that you are using udp on the server and
tcp on the client? Clearly the server is attempting to contact the
client, but the client is not listening.
What does your LaunchDaemon script say? In particular, the ipv4
section, is the SockType key set to stream? If so then that means that
your client is listening only for TCP. You should be able to confirm
that by checking netstat:
% netstat -na | less
The lines reported on my MBP is related to amanda are:
tcp6 0 0 *.10080 *.*
LISTEN
tcp4 0 0 *.10080 *.*
LISTEN
Meaning that I'm listening on TCP port 10080, both ipv4 and ipv6
(though I don't use ipv6, we can ignore that).
If your netstat produces a similar result then that may point to udp
vs. tcp.
For that matter, if netstat isn't showing 10080 then that would tend
to indicate that the launchd script isn't running properly.
If all else fails, try using tcpdump on the client to watch the server
attempting to connect and troubleshoot from there.
Cheers,
Bruce.
On Jul 20, 2008, at 12:58 AM, Nouveaux Territoires wrote:
Le 19 juil. 08 à 22:30, Bruce Thompson a écrit :
I'm running Amanda 2.5.2p1 on Fedora 9 (server) and three MacBook
Pros (client) (10.4.X and 10.5.X) without difficulty.
A few quick questions that might point in the right direction:
1. What version of amanda are you running on the Macs?
The version is 2.5.1p3 (like the amanda sever).
2. What config options did you use?
./configure --with-user=amandabackup --with-group=admin --with-
config=saroumane --without-server --prefix=/usr/local/amanda --with-
amandahosts --with-portrange=50000,50014 --with-bsdtcp-security
3. What user is running the amanda client on the Macs?
amandabackup 14105 0.1 0.0 75356 580 ?? Rs 9:43AM
0:00.06 (launchproxy)
4. What is the contents of .amandahosts in that user's home directory
# machine utilisateur
backup amandabackup amdump
and backup is (in the /etc/hosts) :
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
192.168.50.20 backup backup.nouveauxterritoires.fr
5. What is in /tmp/amanda and do the contents of those files point
show any errors?
on the client, there are not logs in the /tmp/amada/
On the server, there are logs in the /tmp/amamda/server/saroumane
(the name of the computer's client) :
amcheck: debug 1 pid 9472 ruid 33 euid 0: start at Sat Jul 19
14:51:39 2008
amcheck: debug 1 pid 9472 ruid 33 euid 33: rename at Sat Jul 19
14:51:39 2008
security_getdriver(name=bsdtcp) returns 0x2aaaab121ac0
security_handleinit(handle=0x61f710, driver=0x2aaaab121ac0 (BSDTCP))
security_streaminit(stream=0x620290, driver=0x2aaaab121ac0 (BSDTCP))
amcheck-clients: time 0.005: connect_port: Skip port 512: Owned by
exec.
amcheck-clients: time 0.005: connect_port: Skip port 513: Owned by
login.
amcheck-clients: time 0.006: connect_port: Skip port 514: Owned by
shell.
amcheck-clients: time 0.006: connect_port: Skip port 515: Owned by
printer.
amcheck-clients: time 0.006: connect_port: Skip port 516: Owned by
videotex.
amcheck-clients: time 0.012: connect_port: Try port 517:
Available -
changer_query: changer return was 6 1
changer_query: searchable = 0
changer_find: looking for NULL changer is searchable = 0
amcheck-clients: time 3.009: connected to 192.168.50.22.10080
amcheck-clients: our side is 0.0.0.0.517
amcheck-clients: try_socksize: send buffer size is 65536
amcheck-clients: try_socksize: receive buffer size is 65536
security_seterror(handle=0x61f710, driver=0x2aaaab121ac0 (BSDTCP)
error=timeout waiting for ACK)
security_close(handle=0x61f710, driver=0x2aaaab121ac0 (BSDTCP))
security_stream_close(0x620290)
amcheck: pid 9472 finish time Sat Jul 19 14:52:12 2008
On the amanda server, my /etc/xinetd.d/amanda configured like this :
service amanda
{
only_from = localhost 82.235.225.240 127.0.0.1 intranet
supervision globtrans saroumane
socket_type = dgram
protocol = udp
wait = yes
# user = $USER
# group = $GROUP
user = amanda
group = disk
groups = yes
# server = $AMANDAD_PATH/amandad
server = /usr/local/amanda/libexec/amandad
server_args = -auth=bsd amdump amindexd amidxtaped
disable = no
}
The protocol used is 'udp'
and on my cMac OSX client is (in the configure options) -auth=bsdtcp
This configuration can be a problem ?
cheers
Julien
Cheers,
Bruce.
On Jul 19, 2008, at 12:09 PM, Nouveaux Territoires wrote:
Yes, i followed the instructions of this page.
The amanda client is apprently ok (with netstat).
But the amcheck command fail already !!
Le 19 juil. 08 à 17:03, Dustin J. Mitchell a écrit :
Good to hear you're building on a Mac!
Have you set up the necessary launchd script on the mac? There's
information about it at
http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes/Installing_Amanda_on_Mac_OS_X
Dustin
--
Storage Software Engineer
http://www.zmanda.com
!DSPAM:3,4882f190228678691415529!