Re: GNUTAR hanging
Hi Guys, I think i found out the culprit to this issue. The main problem of the GNUTAR to be in hanging state was due to the cancellation of the amdump process during its execution. This happenned when the amdump (running) process is being cancelled and were being rerun at a certain point of time. This thus causes the compression running on the client at that time to wait indefinitely and hanging in the memory space. This happenned to me and i have to manually kill it. By the way guys is there any solution to resume amanda backup if the internet connection was down for a moment? Regards, Anthony Jean-Louis Martineau-2 wrote: amanda version? tar version? Any other amanda process running? Send the complete debug files: sendbackup.*.debug and amandad.*.debug from the client dumper.*.debug from the server. anthonyh wrote: Hi guys, Any solution to the GNUTAR hanging issue yet? I'm having the same problem as the tar problem runs indefinitely for some time until i killed it. top - 10:31:19 up 5 days, 12:01, 1 user, load average: 1.11, 1.03, 1.01 Tasks: 44 total, 2 running, 41 sleeping, 0 stopped, 1 zombie Cpu(s): 30.6% us, 69.4% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si Mem:125064k total, 122244k used, 2820k free,77304k buffers Swap: 262072k total,0k used, 262072k free,14384k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 17812 root 25 0 1920 652 568 R 99.7 0.5 4732:18 tar 4546 root 16 0 2888 868 724 R 0.3 0.7 0:00.03 top 1 root 16 0 1952 460 392 S 0.0 0.4 0:01.09 init # ps aux |grep tar root 17812 99.5 0.5 1920 652 ?RMay01 4732:26 gtar --create -- file - --directory /boot --one-file-system --listed-incremental /usr/local/var/a manda/gnutar-lists/anthonyho.no-ip.org_boot_1.new --sparse --ignore-failed-read --totals . root 4548 0.0 0.4 4820 572 pts/1D10:31 0:00 grep tar Any workaround? Regards, Anthony -- View this message in context: http://www.nabble.com/GNUTAR-hanging-tf3473915.html#a10337314 Sent from the Amanda - Users mailing list archive at Nabble.com.
Dump error index tee cannot write
Hi Guys, I'm facing some error when running the dmp of my backup. The following is my sendbackup.debug log file. sendbackup: debug 1 pid 30943 ruid 514 euid 514: start at Fri May 4 14:59:15 2007 sendbackup: version 2.5.1p3 Reading conf file /usr/local/etc/amanda/amanda-client.conf. Reading conf file /usr/local/etc/amanda/DailySet1/amanda-client.conf. sendbackup: debug 1 pid 30943 ruid 514 euid 514: rename at Fri May 4 14:59:15 2007 sendbackup req: GNUTAR /boot 0 1970:1:1:0:0:0 OPTIONS |;auth=bsd;compress-fast;index; parsed request as: program `GNUTAR' disk `/boot' device `/boot' level 0 since 1970:1:1:0:0:0 options `|;auth=bsd;compress-fast;index;' sendbackup: start: mars.mydomain.com:/boot lev 0 sendbackup: time 0.003: spawning /bin/gzip in pipeline sendbackup: argument list: /bin/gzip --fast sendbackup-gnutar: time 0.005: pid 30945: /bin/gzip --fast sendbackup-gnutar: time 0.005: doing level 0 dump as listed-incremental to '/usr/local/var/amanda/gnutar-lists/mars.mydomain.com_boot_0.new' sendbackup-gnutar: time 0.005: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: time 0.007: spawning /usr/local/libexec/runtar in pipeline sendbackup: argument list: runtar DailySet1 gtar --create --file - --directory /boot --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/mars.mydomain.com_boot_0.new --sparse -- ignore-failed-read --totals . sendbackup-gnutar: time 0.024: /usr/local/libexec/runtar: pid 30948 sendbackup: time 0.024: started backup sendbackup: time 0.031: started index creator: /bin/tar -tf - 2/dev/null | sed -e 's/^\.//' sendbackup: time 30.290: 118: strange(?): sendbackup: time 30.290: index tee cannot write [Broken pipe] sendbackup: time 30.290: pid 30946 finish time Fri May 4 14:59:45 2007 sendbackup: time 30.290: 118: strange(?): gzip: stdout: Broken pipe sendbackup: time 30.291: 118: strange(?): sendbackup: index tee cannot write [Broken pipe] sendbackup: time 30.292: 118: strange(?): sed: Couldn't flush stdout: Broken pipe Any Ideas guys? Regards, Anthony -- View this message in context: http://www.nabble.com/Dump-error-index-tee-cannot-write-tf3691356.html#a10320367 Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: amrecover issue
Hi Guys,settape x:/backup/amanda/dumps/tape01 Thank You for replying this mail. Well actually i'm a bit confused with the way the amanda recovers the data. Is it true that the host in the command settape host:file:/backup/amanda/dumps/tape01 refers to the amanda tape server? Newbie here guys. Regards, Anthony Olivier Nicole wrote: Hi, Currently i'm having some issue with the amrecover. Whenever i tried to execute the amrecover it executed properly but till i started to extract the data it stated there Can't Talk to Tape Server I would try in two directions: 1) try to amrecover on the server itself, to some temporary directory 2) check the firewall on your server best regards, Olivier -- View this message in context: http://www.nabble.com/amrecover-issue-tf3669327.html#a10309363 Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: amrecover issue
Hi, Actually yeah, i got it messed up a bit. Well the following is the Redefined output. I'm not sure whether i did something wrong or have forgotten some confgurations but the following is what i've done. by the way guys is it the settape command is correct? settape sanback.mydomain.com:file:/backup/amanda/dumps/tape09 If i use this, the following is the error that had occur. # amrecover DailySet1 AMRECOVER Version 2.5.1p3. Contacting server on sanback.mydomain.com ... 220 sanback AMANDA index server (2.5.1p3) ready. Setting restore date to today (2007-05-04) 200 Working date set to 2007-05-04. 200 Config set to DailySet1. 501 Host sanback.mydomain.com is not in your disklist. Trying host sanback.mydomain.com ... 501 Host sanback.mydomain.com is not in your disklist. Trying host sanback ... 501 Host sanback is not in your disklist. Use the sethost command to choose a host to recover amrecover sethost anthonyh.mydomain.com 200 Dump host set to anthonyh.mydomain.com. amrecover listdisk 200- List of disk for host anthonyh.mydomain.com 201- /boot 200 List of disk for host anthonyh.mydomain.com amrecover setdisk /boot 200 Disk set to /boot. amrecover list amrecover ls 2007-05-03-20-10-13 lost+found/ 2007-05-03-20-10-13 grub/ 2007-05-03-20-10-13 . amrecover add grub/ Added dir /grub/ at date 2007-05-03-20-10-13 amrecover list TAPE DailySet1-09:3 LEVEL 2 DATE 2007-05-03-20-10-13 /grub amrecover listtape Invalid command: listtape amrecover listape Invalid command: listape amrecover list TAPE DailySet1-09:3 LEVEL 2 DATE 2007-05-03-20-10-13 /grub amrecover settape sanback.mydomain.com:file:/backup/amanda/dumps/tape09 Using tape file:/backup/amanda/dumps/tape09 from server sanback.mydomain.com. amrecover extract Extracting files using tape drive file:/backup/amanda/dumps/tape09 on host sanback.mydomain.com. The following tapes are needed: DailySet1-09 Restoring files into directory /root Continue [?/Y/n]? y Extracting files using tape drive file:/backup/amanda/dumps/tape09 on host sanback.mydomain.com. Load tape DailySet1-09 now Continue [?/Y/n/s/t]? y warning: GNUTAR program not available. amrecover couldn't exec: No such file or directory problem executing tar Extractor child exited with status 1 Any ideas guys? Newbie here... Regards, Anthony Paul Bijnens wrote: On 2007-04-30 14:05, anthonyh wrote: Hi Guys. This is my first post in this Forum. Currently i'm having some issue with the amrecover. Whenever i tried to execute the amrecover it executed properly but till i started to extract the data it stated there Can't Talk to Tape Server Well you edited the log to obfuscate the hostnames. Hoping you know what you did: # amrecover DailySet1 AMRECOVER Version 2.5.1p3. Contacting server on y.com ... 220 y.com AMANDA index server (2.5.1p3) ready. So, y.com is the amanda index-server Setting restore date to today (2007-04-30) 200 Working date set to 2007-04-30. 200 Config set to DailySet1. 501 Host y is not in your disklist. Trying host y.com ... And you are executing this command from y.com itself So client == server? 501 Host y.com is not in your disklist. Trying host y.com ... 501 Host y.com is not in your disklist. Use the sethost command to choose a host to recover amrecover sethost x.com And you want to restore something from a different host x.xom ? 200 Dump host set to x.com amrecover setdisk /home/abamon 200 Disk set to /home/abamon. amrecover list amrecover add * Added file /libexec.tar.gz Added file /.zshrc Added file /.viminfo Added dir /.ssh/ at date 2007-04-30-18-32-42 Added file /.mysql_history Added file /.bashrc Added file /.bash_profile Added file /.bash_logout Added file /.bash_history amrecover list TAPE DailySet1-001:1 LEVEL 0 DATE 2007-04-30-18-32-42 /.bash_history /.bash_logout /.bash_profile /.bashrc /.mysql_history /.ssh /.viminfo /.zshrc /libexec.tar.gz amrecover settape x:/backup/amanda/dumps/tape01 Using tape /backup/amanda/dumps/tape01 from server x.com And here Amanda somehow believes that x.com is the tapeserver? I would expect y.com instead here. Unless x.com is some tapeserver running amanda-server software too? amrecover extract Extracting files using tape drive /backup/amanda/dumps/tape01 on host x.com The following tapes are needed: DailySet1-001 Restoring files into directory /tmp/amanda/client/DailySet1 Continue [?/Y/n]? y Extracting files using tape drive /backup/amanda/dumps/tape01 on host x.com Load tape DailySet1-001 now Continue [?/Y/n/s/t]? y amrecover - can't talk to tape server That's what I expect, yes. But I'm not 100% sure because you obfuscated the hostnames -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email
Re: amrecover issue
Hi,
I'm abit confused in this part because as far as i know the amanda service
is using udp packet and the amindexd/amidxtaped are using tcp. can
everything be fitted into one context that primarily stating that its using
udp protocol?
/etc/xinit.d/amanda
service amanda
{
only_from = x.com y.com
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
server_args = -auth=bsd amdump amindexd amidxtaped
disable = no
}
Thank you guys. Newbie here ...
Regards,
Anthony
Jean-Louis Martineau-2 wrote:
Check amrecover and amandad debug files.
anthonyh wrote:
The following are some of my config files
/etc/xinit.d/amanda
service amanda
{
only_from = x.com y.com
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
server_args = -auth=bsd amdump amindexd
disable = no
}
You forgot amidxtaped
server_args = -auth=bsd amdump amindexd amidxtaped
You must also add an entry in .amandahosts
The following 2 services are not needed if all your client are 2.5.1.
/etc/xinit.d/amandaidx
service amandaidx
{
only_from = x.com y.com
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
server_args = -auth=bsd amdump amindexd
disable = no
}
service amidxtape
{
only_from = x.com y.com
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
server_args = -auth=bsd amdump amidxtaped
disable = no
}
Any good Solution Guys? Thanks!
Also you tape device /backup/amanda/dumps/tape01 is not correct,
it should be file:/backup/amanda/dumps/tape01
use: setape x.com:file:/backup/amanda/dumps/tape0
Jean-Louis
--
View this message in context:
http://www.nabble.com/amrecover-issue-tf3669327.html#a10309749
Sent from the Amanda - Users mailing list archive at Nabble.com.
amrecover issue
Hi Guys. This is my first post in this Forum. Currently i'm having some issue
with the amrecover. Whenever i tried to execute the amrecover it executed
properly but till i started to extract the data it stated there Can't Talk
to Tape Server
# amrecover DailySet1
AMRECOVER Version 2.5.1p3. Contacting server on y.com ...
220 y.com AMANDA index server (2.5.1p3) ready.
Setting restore date to today (2007-04-30)
200 Working date set to 2007-04-30.
200 Config set to DailySet1.
501 Host y is not in your disklist.
Trying host y.com ...
501 Host y.com is not in your disklist.
Trying host y.com ...
501 Host y.com is not in your disklist.
Use the sethost command to choose a host to recover
amrecover sethost x.com
200 Dump host set to x.com
amrecover setdisk /home/abamon
200 Disk set to /home/abamon.
amrecover list
amrecover add *
Added file /libexec.tar.gz
Added file /.zshrc
Added file /.viminfo
Added dir /.ssh/ at date 2007-04-30-18-32-42
Added file /.mysql_history
Added file /.bashrc
Added file /.bash_profile
Added file /.bash_logout
Added file /.bash_history
amrecover list
TAPE DailySet1-001:1 LEVEL 0 DATE 2007-04-30-18-32-42
/.bash_history
/.bash_logout
/.bash_profile
/.bashrc
/.mysql_history
/.ssh
/.viminfo
/.zshrc
/libexec.tar.gz
amrecover settape x:/backup/amanda/dumps/tape01
Using tape /backup/amanda/dumps/tape01 from server x.com
amrecover extract
Extracting files using tape drive /backup/amanda/dumps/tape01 on host x.com
The following tapes are needed: DailySet1-001
Restoring files into directory /tmp/amanda/client/DailySet1
Continue [?/Y/n]? y
Extracting files using tape drive /backup/amanda/dumps/tape01 on host x.com
Load tape DailySet1-001 now
Continue [?/Y/n/s/t]? y
amrecover - can't talk to tape server
the following is the debug file
amrecover.xxx.debug file
amrecover: debug 1 pid 2307 ruid 0 euid 0: start at Mon Apr 30 19:00:32 2007
Reading conf file /usr/local/etc/amanda/amanda-client.conf.
Reading conf file /usr/local/etc/amanda/DailySet1/amanda-client.conf.
amrecover: debug 1 pid 2307 ruid 0 euid 0: rename at Mon Apr 30 19:00:32
2007
security_getdriver(name=bsd) returns 0xa380e0
security_handleinit(handle=0x9af3a28, driver=0xa380e0 (BSD))
amrecover: bind_portrange2: Try port 709: Available - Success
amrecover: dgram_bind: socket bound to 0.0.0.0.709
amrecover: dgram_send_addr(addr=0xbff86bf0, dgram=0xa39024)
amrecover: (sockaddr_in *)0xbff86bf0 = { 2, 10080, 10.10.10.20 }
amrecover: dgram_send_addr: 0xa39024-socket = 3
amrecover: dgram_recv(dgram=0xa39024, timeout=0, fromaddr=0xa49010)
amrecover: (sockaddr_in *)0xa49010 = { 2, 10080, 10.10.10.20 }
amrecover: dgram_recv(dgram=0xa39024, timeout=0, fromaddr=0xa49010)
amrecover: (sockaddr_in *)0xa49010 = { 2, 10080, 10.10.10.20 }
amrecover: dgram_send_addr(addr=0xbff86920, dgram=0xa39024)
amrecover: (sockaddr_in *)0xbff86920 = { 2, 10080, 10.10.10.20 }
amrecover: dgram_send_addr: 0xa39024-socket = 3
security_streaminit(stream=0x9af51f8, driver=0xa380e0 (BSD))
amrecover: connect_port: Try port 5: Available -
amrecover: connected to 10.10.10.20.50036
amrecover: our side is 0.0.0.0.5
amrecover: try_socksize: send buffer size is 65536
amrecover: try_socksize: receive buffer size is 65536
security_close(handle=0x9af3a28, driver=0xa380e0 (BSD))
add_dir_list_item: Adding 2007-04-30-18-32-42 0 DailySet1-001:1 1
/.
add_dir_list_item: Adding 2007-04-30-18-32-42 0 DailySet1-001:1 1
/.bash_history
add_dir_list_item: Adding 2007-04-30-18-32-42 0 DailySet1-001:1 1
/.bash_logout
add_dir_list_item: Adding 2007-04-30-18-32-42 0 DailySet1-001:1 1
/.bash_profile
add_dir_list_item: Adding 2007-04-30-18-32-42 0 DailySet1-001:1 1
/.bashrc
add_dir_list_item: Adding 2007-04-30-18-32-42 0 DailySet1-001:1 1
/.mysql_history
add_dir_list_item: Adding 2007-04-30-18-32-42 0 DailySet1-001:1 1
/.ssh/
add_dir_list_item: Adding 2007-04-30-18-32-42 0 DailySet1-001:1 1
/.viminfo
add_dir_list_item: Adding 2007-04-30-18-32-42 0 DailySet1-001:1 1
/.zshrc
add_dir_list_item: Adding 2007-04-30-18-32-42 0 DailySet1-001:1 1
/libexec.tar.gz
add_glob (*) - ^[^/]*$
add_file: Looking for [^/]*[/]*$
add_file: Converted path=([^/.]|\.[^/]+|[^/.][^/]*)[/]*$ to
path_on_disk=/([^/.]|\.[^/]+|[^/.][^/]*)[/]*$
add_file: Pondering ditem-path=/libexec.tar.gz
add_file: (Successful) Added /libexec.tar.gz
add_file: Pondering ditem-path=/.zshrc
add_file: (Successful) Added /.zshrc
add_file: Pondering ditem-path=/.viminfo
add_file: (Successful) Added /.viminfo
add_file: Pondering ditem-path=/.ssh/
add_file: (Successful) Added dir /.ssh/ at date 2007-04-30-18-32-42
add_file: Pondering ditem-path=/.mysql_history
add_file: (Successful) Added /.mysql_history
add_file: Pondering ditem-path=/.bashrc
add_file: (Successful) Added /.bashrc
add_file: Pondering ditem-path=/.bash_profile
add_file: (Successful) Added /.bash_profile
add_file: Pondering ditem-path=/.bash_logout
add_file: (Successful) Added /.bash_logout
add_file: Pondering
