Greetings all;
It appears this is working with one exception:
coyote /usr/movies lev 1 FAILED [too many dumper retry: "[request failed:
timeout waiting for REP]"]
I have had a dtimeout=1800 in there since forever. I do not believe this
is the real problem.
So it looks like a timeout error, in which case I should see some cpu load
during the time that an amstatus Daily says it is dumping that dle. But
there is no activity at all till the dump times out. The created file in
/dumps/dumpdate remains at zero length.
I have grepped for /usr/movies in /tmp/amanda-dbg/client/Daily and in
/tmp/amanda-dbg/server/Daily, and I find this in the last dumper* that
contains the string 'movies'
1226668289.475834: dumper: getcmd: PORT-DUMP 00-00045 54598 coyote
ffffffff9ffeffffffff3f /usr/movies NODEVICE 1 2008:11:12:6:31:53
amgtar X X X BSD
|" <auth>BSD</auth>\n <record>YES</record>\n <index>YES</index>\n
<exclude>\n <list>/GenesAmandaHelper-0.6/excludes</list>\n
</exclude>\n <backup-program>\n <plugin>amgtar</plugin>\n <property>\n
<name>CHECK-DEVICE</name>\n
<value>no</value>\n </property>\n </backup-program>\n"
1226668289.479651: dumper: make_socket opening socket with family 2
1226668289.479686: dumper: connect_port: Try port 1024: available - Success
1226668289.479783: dumper: connected to 127.0.0.1.54598
1226668289.479791: dumper: our side is 0.0.0.0.1024
1226668289.479798: dumper: try_socksize: send buffer size is 65536
1226668289.480504: dumper: send request:
----
SERVICE sendbackup
OPTIONS features=ffffffff9ffeffffffff3f;hostname=coyote;config=Daily;
<dle>
<program>APPLICATION</program>
<disk>/usr/movies</disk>
<level>1</level>
<auth>BSD</auth>
<record>YES</record>
<index>YES</index>
<exclude>
<list>/GenesAmandaHelper-0.6/excludes</list>
</exclude>
<backup-program>
<plugin>amgtar</plugin>
<property>
<name>CHECK-DEVICE</name>
<value>no</value>
</property>
</backup-program>
</dle>
----
1226668289.480513: dumper: security_getdriver(name=BSD) returns 0xb7eeaa80
1226668289.480523: dumper: security_handleinit(handle=0x96f8318,
driver=0xb7eeaa80 (BSD))
1226668289.480573: dumper: dgram_send_addr(addr=0x96f8338, dgram=0xb7ef2a04)
1226668289.480580: dumper: (sockaddr_in *)0x96f8338 = { 2, 10080, 192.168.71.3 }
1226668289.480585: dumper: dgram_send_addr: 0xb7ef2a04->socket = 4
1226668289.480857: dumper: dgram_recv(dgram=0xb7ef2a04, timeout=0,
fromaddr=0xb7f029f0)
1226668289.480868: dumper: (sockaddr_in *)0xb7f029f0 = { 2, 10080, 192.168.71.3
}
1226668349.540378: dumper: dgram_send_addr(addr=0x96f8338, dgram=0xb7ef2a04)
1226668349.540413: dumper: (sockaddr_in *)0x96f8338 = { 2, 10080, 192.168.71.3 }
1226668349.540420: dumper: dgram_send_addr: 0xb7ef2a04->socket = 4
1226668349.540704: dumper: dgram_recv(dgram=0xb7ef2a04, timeout=0,
fromaddr=0xb7f029f0)
1226668349.540715: dumper: (sockaddr_in *)0xb7f029f0 = { 2, 10080, 192.168.71.3
}
1226668409.600377: dumper: dgram_send_addr(addr=0x96f8338, dgram=0xb7ef2a04)
1226668409.600413: dumper: (sockaddr_in *)0x96f8338 = { 2, 10080, 192.168.71.3 }
1226668409.600596: dumper: dgram_send_addr: 0xb7ef2a04->socket = 4
1226668409.600901: dumper: dgram_recv(dgram=0xb7ef2a04, timeout=0,
fromaddr=0xb7f029f0)
1226668409.600912: dumper: (sockaddr_in *)0xb7f029f0 = { 2, 10080, 192.168.71.3
}
1226668469.660379: dumper: security_seterror(handle=0x96f8318,
driver=0xb7eeaa80 (BSD) error=timeout waiting for REP)
1226668469.660414: dumper: security_close(handle=0x96f8318, driver=0xb7eeaa80
(BSD))
1226668469.660462: dumper: putresult: 11 TRY-AGAIN
Which it does, one more time with what looks to be the same result.
So obviously that file isn't telling me the real problem. Where do I look
next? No firewall is running, and selinux isn't bitching.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
TOO BAD YOU CAN'T BUY a voodoo globe so that you could make the earth spin
real fast and freak everybody out.
-- Jack Handley, The New Mexican, 1988.
|
