On Mon April 7 2003 20:05, a blob of green gelatin wrote:
>Howdy,
>
>I've run into a problem that doesn't seem to show up anywhere in
> the amanda archives (which means its unique, which I doubt, or
> that I'm missing something really simple, which is more likely
> the case).
>
>I've installed amanda-2.4.4 on RedHat 7.2 and have been successful
> in being able to dump (or tar) to the holding disk, and then have
> the holding disk dump to tape (DLT 40Gb tapes). However, if I
> hit a partition/disk that's bigger than my holding disk, it will
> not dump to tape directly. I've closed down my configuration to
> just include a partition local to the server. If the holding
> disk is larger than the partition (for a level 0) then things are
> great. If my partition's too big for it, I'll get the
> following:
>
>---- Begin amdump.1 snippet -----
>
>DUMP tecopa.sf.apexion.com fffffeff9ffe0f /usr 20030407 8 0
> 1970:1:1:0:0:0 1136481 158
>--------
>driver: adding holding disk 0 dir /home/amanda/holdingdisk size
> 1024000 reserving 1024000 out of 1024000 for degraded-mode dumps
>driver: start time 2.034 inparallel 4 bandwidth 2000 diskspace
> 1024000 dir OBSOLETE datestamp 20030407 driver: drain-ends tapeq
> FIRST big-dumpers sssS
>changer: got exit: 0 str: 3 99 1
>changer_query: changer return was 99 1
>changer_query: searchable = 0
>changer_find: looking for dailies1 changer is searchable = 0
>changer: opening pipe to: /usr/local/libexec/chg-manual -slot
> current changer: got exit: 0 str: 3 /dev/nst0
>taper: slot 3: date 20030407 label dailies1 (exact label match)
>taper: read label `dailies1' date `20030407'
>taper: wrote label `dailies1' date `20030407'
>driver: result time 19.458 from taper: TAPER-OK
>driver: dumping tecopa.sf.apexion.com:/usr directly to tape
>driver: send-cmd time 19.459 to taper: PORT-WRITE 00-00001
>tecopa.sf.apexion.com fffffeff9ffe0f /usr 0 20030407
>taper: try_socksize: receive buffer size is 65536
>taper: stream_server: waiting for connection: 0.0.0.0.32810
>driver: result time 19.459 from taper: PORT 32810
>driver: send-cmd time 19.459 to dumper0: PORT-DUMP 01-00002 32810
>tecopa.sf.apexion.com fffffeff9ffe0f /usr NODEVICE 0
> 1970:1:1:0:0:0 DUMP
>
>|;auth=bsd;
>
>driver: state time 19.459 free kps: -5192 space: 1024000 taper:
> writing idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup:
> 86400 driver-idle: not-idle
>driver: interface-state time 19.459 if : free 600 if LE0: free 400
> if LOCAL: free -6192
>driver: hdisk-state time 19.459 hdisk 0: free 1024000 dumpers 0
>taper: stream_accept: timeout after 120 seconds
>dumper: stream_client: connect to 127.0.0.1.32810 failed:
> Connection timed out
Are you useing localhost as the client address? Please use its
FQDN, there are warnings about weird localhost problems aplenty in
the archives.
>driver: result time 208.459 from dumper0: FAILED 01-00002 [taper
> port open: Connection timed out]
>driver: result time 208.460 from taper: TAPE-ERROR 00-00001 [port
> connect timeout]
>dump of driver schedule before start degraded mode:
>--------
>--------
>dump of driver schedule after start degraded mode:
>--------
>--------
>driver: state time 208.461 free kps: 2000 space: 1024000 taper:
> DOWN idle-dumpers: 4 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400
> driver-idle: not-idle
>driver: interface-state time 208.461 if : free 600 if LE0: free
> 400 if LOCAL: free 1000
>driver: hdisk-state time 208.461 hdisk 0: free 1024000 dumpers 0
>
>--------- end of /var/amanda/dailies/amdump.1 snippet -------
>
>Can anyone shed some light as to why I'm seeing this bit:
>
>taper: stream_accept: timeout after 120 seconds
>dumper: stream_client: connect to 127.0.0.1.32810 failed:
> Connection timed out
Another localhost access...
>driver: result time 208.459 from dumper0: FAILED 01-00002 [taper
> port open: Connection timed out]
>driver: result time 208.460 from taper: TAPE-ERROR 00-00001 [port
> connect timeout]
>
>
>If I dump from the holding disk, there is no timeout and things
> 'tape' fine. I can also 'tape' partitions over the network to
> the amanda server as long as the partition's smaller than the
> holding disk. So this timeout message is real puzzling, and I'm
> not seeing anything on it in the amanda-users archives.
>
>Can anyone toss out some ideas?
>
>Thanks!
>
>Chris
>
>ps. Here's some info from my amanda.conf just in case:
>
>etimeout 1200 # number of seconds per filesystem for
> estimates. #etimeout -600 # total number of seconds for
> estimates. # a positive number will be multiplied by the number
> of filesystems on # each host; a negative number will be taken as
> an absolute total time-out.
># The default is 5 minutes per filesystem.
>
>dtimeout 3600 # number of idle seconds before a dump is
> aborted. ---
>runtapes 1 # number of tapes to be used in a single
> run of amdump
>tpchanger "chg-manual" # the tape-changer glue script
>tapedev "/dev/nst0" # the no-rewind tape device to be used
>#rawtapedev "/dev/null" # the raw device to be used (ftape only)
>rawtapedev "/dev/nst0" # the raw device to be used (ftape only)
>changerfile "/usr/local/etc/amanda/dailies/changer"
>#changerfile "/usr/local/etc/amanda/dailies/changer-status"
>#changerfile "/usr/local/etc/amanda/dailies/changer.conf"
>#changerdev "/dev/null"
>changerdev "/dev/nst0"
>
>maxdumpsize -1 # Maximum number of bytes the planner will
>schedule
> # for a run (default: runtapes *
> tape_length). tapetype DLT-80 # what kind of tape it is
> (see tapetypes below)
>
>----- end of amanda.conf snippet ----
>
>----
>
>Celestial navigation is based on the premise that the Earth is the
>center of the universe. The premise is wrong, but the navigation
>works. An incorrect model can be a useful tool.
> -- Kelvin Throop III
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.25% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
|
