AW: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server
Hi! We have some more server with (for example) german tar and there are no Problems with the backup. Amanda is installed in English -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Paul Bijnens Gesendet: Freitag, 4. November 2005 11:26 An: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > Hi! > > Thats all in sendsize: > > sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 > 2005 > sendsize: version 2.4.3 > sendsize[5132]: time 0.007: waiting for any estimate child > sendsize[5134]: time 0.007: calculating for amname '/pst', dirname '/pst', > spindle -1 > sendsize[5134]: time 0.007: getting size via gnutar for /pst level 0 > sendsize[5134]: time 0.034: spawning /usr/lib/amanda/runtar in pipeline > sendsize[5134]: argument list: /bin/tar --create --file /dev/null > --directory /pst --one-file-system --listed-incremental > /var/lib/amanda/gnutar-lists/pst_ps > t_0.new --sparse --ignore-failed-read --totals --exclude-from > /tmp/amanda/sendsize._pst.20051104023002.exclude . > sendsize[5134]: time 2938.236: Total bytes written: 86986362880 (81GB, > 28MB/s) > sendsize[5134]: time 2938.237: . > sendsize[5134]: estimate time for /pst level 0: 2938.203 > sendsize[5134]: estimate size for /pst level 0: 84947620 KB > sendsize[5134]: time 2938.237: waiting for /bin/tar "/pst" child > sendsize[5134]: time 2938.237: after /bin/tar "/pst" wait > sendsize[5134]: time 2938.238: done with amname '/pst', dirname '/pst', > spindle -1 > sendsize[5132]: time 2938.238: child 5134 terminated normally > sendsize: time 2938.238: pid 5132 finish time Fri Nov 4 03:19:00 2005 This sendsize is completely normal. The previous one you sent, did have the error about not finding the size line. But that size line is there in this run! Notice the line "Total bytes written: ..." > [EMAIL PROTECTED] gnutar-lists]# /bin/tar --create --file /dev/null > --directory /pst --one-file-system --listed-incremental > /var/lib/amanda/gnutar-lists/pst_pst_0.new --sparse --ignore-failed-read > --totals . > > After +1 hour > > Gesamtzahl geschriebener Bytes: 86991011840 (81GB, 27MB/s) (English: Total > number of written bytes ) Seems you have some mixed English-German environment. Amanda specifically looks for the English string, and does not recognize the german words. Could it be that some amdump runs somehow use the german environment? > > Seems to work but why not directly with amanda?! I cannot conclude that from the evidence you give here: the sendsize is perfect. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server
Sebastian Kösters wrote: Hi! Thats all in sendsize: sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 2005 sendsize: version 2.4.3 sendsize[5132]: time 0.007: waiting for any estimate child sendsize[5134]: time 0.007: calculating for amname '/pst', dirname '/pst', spindle -1 sendsize[5134]: time 0.007: getting size via gnutar for /pst level 0 sendsize[5134]: time 0.034: spawning /usr/lib/amanda/runtar in pipeline sendsize[5134]: argument list: /bin/tar --create --file /dev/null --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_ps t_0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._pst.20051104023002.exclude . sendsize[5134]: time 2938.236: Total bytes written: 86986362880 (81GB, 28MB/s) sendsize[5134]: time 2938.237: . sendsize[5134]: estimate time for /pst level 0: 2938.203 sendsize[5134]: estimate size for /pst level 0: 84947620 KB sendsize[5134]: time 2938.237: waiting for /bin/tar "/pst" child sendsize[5134]: time 2938.237: after /bin/tar "/pst" wait sendsize[5134]: time 2938.238: done with amname '/pst', dirname '/pst', spindle -1 sendsize[5132]: time 2938.238: child 5134 terminated normally sendsize: time 2938.238: pid 5132 finish time Fri Nov 4 03:19:00 2005 This sendsize is completely normal. The previous one you sent, did have the error about not finding the size line. But that size line is there in this run! Notice the line "Total bytes written: ..." [EMAIL PROTECTED] gnutar-lists]# /bin/tar --create --file /dev/null --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_pst_0.new --sparse --ignore-failed-read --totals . After +1 hour Gesamtzahl geschriebener Bytes: 86991011840 (81GB, 27MB/s) (English: Total number of written bytes ) Seems you have some mixed English-German environment. Amanda specifically looks for the English string, and does not recognize the german words. Could it be that some amdump runs somehow use the german environment? Seems to work but why not directly with amanda?! I cannot conclude that from the evidence you give here: the sendsize is perfect. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
AW: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server
Like i said i started amdumup with etimeout = 4000but now ist running since 8:36 now it is 10:53. And it is even running I dont understand. On the client thera are the following process from amanda: 8243 ?S 0:00 /usr/lib/amanda/sendbackup 8245 ?S 52:15 /usr/bin/gzip --fast 8246 ?S 1:19 /usr/lib/amanda/sendbackup 8247 ?S 0:00 sh -c /bin/tar -tf - 2>/dev/null | sed -e 's/^\.//' 8248 ?S 0:49 /bin/tar -tf - 8249 ?S 0:00 sed -e s/^\.// 8250 ?R 2:30 gtar --create --file - --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_pst_0.new --sparse -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Alexander Jolk Gesendet: Freitag, 4. November 2005 09:54 An: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > Thats all in sendsize: > > sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 > 2005 > sendsize: version 2.4.3 > sendsize[5132]: time 0.007: waiting for any estimate child > sendsize[5134]: time 0.007: calculating for amname '/pst', dirname '/pst', > spindle -1 > sendsize[5134]: time 0.007: getting size via gnutar for /pst level 0 > sendsize[5134]: time 0.034: spawning /usr/lib/amanda/runtar in pipeline > sendsize[5134]: argument list: /bin/tar --create --file /dev/null > --directory /pst --one-file-system --listed-incremental > /var/lib/amanda/gnutar-lists/pst_ps > t_0.new --sparse --ignore-failed-read --totals --exclude-from > /tmp/amanda/sendsize._pst.20051104023002.exclude . > sendsize[5134]: time 2938.236: Total bytes written: 86986362880 (81GB, > 28MB/s) > sendsize[5134]: time 2938.237: . > sendsize[5134]: estimate time for /pst level 0: 2938.203 > sendsize[5134]: estimate size for /pst level 0: 84947620 KB > sendsize[5134]: time 2938.237: waiting for /bin/tar "/pst" child > sendsize[5134]: time 2938.237: after /bin/tar "/pst" wait > sendsize[5134]: time 2938.238: done with amname '/pst', dirname '/pst', > spindle -1 > sendsize[5132]: time 2938.238: child 5134 terminated normally > sendsize: time 2938.238: pid 5132 finish time Fri Nov 4 03:19:00 2005 [...] > Seems to work but why not directly with amanda?! Remind me, did you change etimeout? Your sendsize debug file seems normal to me, and in fact we see that the estimate size is correctly identified. Could you show the corresponding amandad debug file please? Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
AW: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server
The last try from which i posted the output was by hand. Now i`am trying again with Amanda (Timeout 4000) -Ursprüngliche Nachricht- Von: Alexander Jolk [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 4. November 2005 09:54 An: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > Thats all in sendsize: > > sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 > 2005 > sendsize: version 2.4.3 > sendsize[5132]: time 0.007: waiting for any estimate child > sendsize[5134]: time 0.007: calculating for amname '/pst', dirname '/pst', > spindle -1 > sendsize[5134]: time 0.007: getting size via gnutar for /pst level 0 > sendsize[5134]: time 0.034: spawning /usr/lib/amanda/runtar in pipeline > sendsize[5134]: argument list: /bin/tar --create --file /dev/null > --directory /pst --one-file-system --listed-incremental > /var/lib/amanda/gnutar-lists/pst_ps > t_0.new --sparse --ignore-failed-read --totals --exclude-from > /tmp/amanda/sendsize._pst.20051104023002.exclude . > sendsize[5134]: time 2938.236: Total bytes written: 86986362880 (81GB, > 28MB/s) > sendsize[5134]: time 2938.237: . > sendsize[5134]: estimate time for /pst level 0: 2938.203 > sendsize[5134]: estimate size for /pst level 0: 84947620 KB > sendsize[5134]: time 2938.237: waiting for /bin/tar "/pst" child > sendsize[5134]: time 2938.237: after /bin/tar "/pst" wait > sendsize[5134]: time 2938.238: done with amname '/pst', dirname '/pst', > spindle -1 > sendsize[5132]: time 2938.238: child 5134 terminated normally > sendsize: time 2938.238: pid 5132 finish time Fri Nov 4 03:19:00 2005 [...] > Seems to work but why not directly with amanda?! Remind me, did you change etimeout? Your sendsize debug file seems normal to me, and in fact we see that the estimate size is correctly identified. Could you show the corresponding amandad debug file please? Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server
Sebastian Kösters wrote: Thats all in sendsize: sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 2005 sendsize: version 2.4.3 sendsize[5132]: time 0.007: waiting for any estimate child sendsize[5134]: time 0.007: calculating for amname '/pst', dirname '/pst', spindle -1 sendsize[5134]: time 0.007: getting size via gnutar for /pst level 0 sendsize[5134]: time 0.034: spawning /usr/lib/amanda/runtar in pipeline sendsize[5134]: argument list: /bin/tar --create --file /dev/null --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_ps t_0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._pst.20051104023002.exclude . sendsize[5134]: time 2938.236: Total bytes written: 86986362880 (81GB, 28MB/s) sendsize[5134]: time 2938.237: . sendsize[5134]: estimate time for /pst level 0: 2938.203 sendsize[5134]: estimate size for /pst level 0: 84947620 KB sendsize[5134]: time 2938.237: waiting for /bin/tar "/pst" child sendsize[5134]: time 2938.237: after /bin/tar "/pst" wait sendsize[5134]: time 2938.238: done with amname '/pst', dirname '/pst', spindle -1 sendsize[5132]: time 2938.238: child 5134 terminated normally sendsize: time 2938.238: pid 5132 finish time Fri Nov 4 03:19:00 2005 [...] Seems to work but why not directly with amanda?! Remind me, did you change etimeout? Your sendsize debug file seems normal to me, and in fact we see that the estimate size is correctly identified. Could you show the corresponding amandad debug file please? Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server
Hi! Thats all in sendsize: sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 2005 sendsize: version 2.4.3 sendsize[5132]: time 0.007: waiting for any estimate child sendsize[5134]: time 0.007: calculating for amname '/pst', dirname '/pst', spindle -1 sendsize[5134]: time 0.007: getting size via gnutar for /pst level 0 sendsize[5134]: time 0.034: spawning /usr/lib/amanda/runtar in pipeline sendsize[5134]: argument list: /bin/tar --create --file /dev/null --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_ps t_0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._pst.20051104023002.exclude . sendsize[5134]: time 2938.236: Total bytes written: 86986362880 (81GB, 28MB/s) sendsize[5134]: time 2938.237: . sendsize[5134]: estimate time for /pst level 0: 2938.203 sendsize[5134]: estimate size for /pst level 0: 84947620 KB sendsize[5134]: time 2938.237: waiting for /bin/tar "/pst" child sendsize[5134]: time 2938.237: after /bin/tar "/pst" wait sendsize[5134]: time 2938.238: done with amname '/pst', dirname '/pst', spindle -1 sendsize[5132]: time 2938.238: child 5134 terminated normally sendsize: time 2938.238: pid 5132 finish time Fri Nov 4 03:19:00 2005 Outputs: /opt [EMAIL PROTECTED] amanda]# /bin/tar --create --file /dev/null --directory /opt --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_opt_0.new --sparse --ignore-failed-read --totals . Gesamtzahl geschriebener Bytes: 798720 (780kB, ?B/s) (English: Total number of written bytes ) /pst [EMAIL PROTECTED] gnutar-lists]# /bin/tar --create --file /dev/null --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_pst_0.new --sparse --ignore-failed-read --totals . After +1 hour Gesamtzahl geschriebener Bytes: 86991011840 (81GB, 27MB/s) (English: Total number of written bytes ) Seems to work but why not directly with amanda?! -Ursprüngliche Nachricht- Von: Alexander Jolk [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 3. November 2005 15:20 An: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > I found this in /tmp/amanda on the client [...] > sendsize[25487]: time 1519.255: . Did you cut something here? That would have been what was interesting. > sendsize[25487]: estimate time for /pst level 0: 1519.252 Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
Re: AW: AW: AW: AW: AW: AW: Estimate timeout from server
Sebastian Kösters wrote: I found this in /tmp/amanda on the client [...] sendsize[25487]: time 1519.255: . Did you cut something here? That would have been what was interesting. sendsize[25487]: estimate time for /pst level 0: 1519.252 Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server
Sebastian Kösters wrote: I tried it by hand with /opt and it worked. -rw-r--r--1 root root 256 3. Nov 14:52 pst_opt_0.new tar (GNU tar) 1.13.25 i dont know why it has a Problem with /pst?! Ok its big (80GB) but not to big i think. You have failed to understand that we don't care about that listed-incremental file .new; what we are looking for is what tar gives on its stdout at the end of its run. Could you report the exact output of the tar command, both when running on /pst and on /opt? We know from your before debug files that it takes almost half an hour on /pst. Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server
I tried it by hand with /opt and it worked. -rw-r--r--1 root root 256 3. Nov 14:52 pst_opt_0.new tar (GNU tar) 1.13.25 i dont know why it has a Problem with /pst?! Ok its big (80GB) but not to big i think. -Ursprüngliche Nachricht- Von: Paul Bijnens [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 3. November 2005 14:46 An: Sebastian Kösters Betreff: Re: AW: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > I found this in /tmp/amanda on the client > ... > sendsize[25487]: argument list: /bin/tar --create --file /dev/null > --directory /pst --one-file-system --listed-incremental > /var/lib/amanda/gnutar-lists/pst_p > st_0.new --sparse --ignore-failed-read --totals . > sendsize[25485]: time 0.023: waiting for any estimate child > sendsize[25487]: time 1519.255: . > sendsize[25487]: estimate time for /pst level 0: 1519.252 > sendsize[25487]: no size line match in /bin/tar output for "/pst" > sendsize[25487]: . > sendsize[25487]: estimate size for /pst level 0: -1 KB > sendsize[25487]: time 1519.255: waiting for /bin/tar "/pst" child > sendsize[25487]: time 1519.256: after /bin/tar "/pst" wait > sendsize[25485]: time 1519.256: child 25487 terminated with signal 13 > sendsize: time 1519.257: pid 25485 finish time Thu Nov 3 14:25:44 2005 > > > whats that: no size line match in /bin/tar output for "/pst" Amanda looks in the tar output for a line like: Total bytes written: 33955840 (32MB, 938MB/s) But it does not find one. > > and that: size for /pst level 0: -1 KB ?? The -1 is means it failed. Does the tar command works for another directory instead of /pst ? e.g. /var/log -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: AW: AW: AW: AW: AW: Estimate timeout from server
On Thu, Nov 03, 2005 at 02:38:04PM +0100, Sebastian Kösters enlightened us: > I found this in /tmp/amanda on the client > > sendsize: debug 1 pid 25485 ruid 33 euid 33: start at Thu Nov 3 14:00:25 > 2005 > sendsize: version 2.4.3 > sendsize[25487]: time 0.002: calculating for amname '/pst', dirname '/pst', > spindle -1 > sendsize[25487]: time 0.002: getting size via gnutar for /pst level 0 > sendsize[25487]: time 0.003: spawning /usr/lib/amanda/runtar in pipeline > sendsize[25487]: argument list: /bin/tar --create --file /dev/null > --directory /pst --one-file-system --listed-incremental > /var/lib/amanda/gnutar-lists/pst_p > st_0.new --sparse --ignore-failed-read --totals . > sendsize[25485]: time 0.023: waiting for any estimate child > sendsize[25487]: time 1519.255: . > sendsize[25487]: estimate time for /pst level 0: 1519.252 > sendsize[25487]: no size line match in /bin/tar output for "/pst" > sendsize[25487]: . > sendsize[25487]: estimate size for /pst level 0: -1 KB > sendsize[25487]: time 1519.255: waiting for /bin/tar "/pst" child > sendsize[25487]: time 1519.256: after /bin/tar "/pst" wait > sendsize[25485]: time 1519.256: child 25487 terminated with signal 13 > sendsize: time 1519.257: pid 25485 finish time Thu Nov 3 14:25:44 2005 > > > whats that: no size line match in /bin/tar output for "/pst" > > and that: size for /pst level 0: -1 KB ?? > What version of tar is this? -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
AW: AW: AW: AW: AW: AW: Estimate timeout from server
I found this in /tmp/amanda on the client sendsize: debug 1 pid 25485 ruid 33 euid 33: start at Thu Nov 3 14:00:25 2005 sendsize: version 2.4.3 sendsize[25487]: time 0.002: calculating for amname '/pst', dirname '/pst', spindle -1 sendsize[25487]: time 0.002: getting size via gnutar for /pst level 0 sendsize[25487]: time 0.003: spawning /usr/lib/amanda/runtar in pipeline sendsize[25487]: argument list: /bin/tar --create --file /dev/null --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_p st_0.new --sparse --ignore-failed-read --totals . sendsize[25485]: time 0.023: waiting for any estimate child sendsize[25487]: time 1519.255: . sendsize[25487]: estimate time for /pst level 0: 1519.252 sendsize[25487]: no size line match in /bin/tar output for "/pst" sendsize[25487]: . sendsize[25487]: estimate size for /pst level 0: -1 KB sendsize[25487]: time 1519.255: waiting for /bin/tar "/pst" child sendsize[25487]: time 1519.256: after /bin/tar "/pst" wait sendsize[25485]: time 1519.256: child 25487 terminated with signal 13 sendsize: time 1519.257: pid 25485 finish time Thu Nov 3 14:25:44 2005 whats that: no size line match in /bin/tar output for "/pst" and that: size for /pst level 0: -1 KB ?? -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Sebastian Kösters Gesendet: Donnerstag, 3. November 2005 14:33 An: 'Alexander Jolk' Cc: amanda-users@amanda.org Betreff: AW: AW: AW: AW: AW: AW: Estimate timeout from server You are right. When i try it by hand nothing happens. It runs and runs and runs and the file stays at 0kb. I found no error messages. I also changed the persmissions of the amanda files / directorys to 777. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Alexander Jolk Gesendet: Donnerstag, 3. November 2005 14:21 An: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: >>On the client amanda starts the following command: >> >>/bin/tar --create --file /dev/null --directory /pst --one-file-system >>--listed-incremental /var/lib/amanda/gnutar-lists/pst_pst_0.new > > When run it by hand i get this error (translated from german to english) > > /bin/tar: No empty Archive created. You forgot the last dot `.' on the command line as given in the debug file. Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
AW: AW: AW: AW: AW: AW: Estimate timeout from server
You are right. When i try it by hand nothing happens. It runs and runs and runs and the file stays at 0kb. I found no error messages. I also changed the persmissions of the amanda files / directorys to 777. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Alexander Jolk Gesendet: Donnerstag, 3. November 2005 14:21 An: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: >>On the client amanda starts the following command: >> >>/bin/tar --create --file /dev/null --directory /pst --one-file-system >>--listed-incremental /var/lib/amanda/gnutar-lists/pst_pst_0.new > > When run it by hand i get this error (translated from german to english) > > /bin/tar: No empty Archive created. You forgot the last dot `.' on the command line as given in the debug file. Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
Re: AW: AW: AW: AW: AW: Estimate timeout from server
Sebastian Kösters wrote: On the client amanda starts the following command: /bin/tar --create --file /dev/null --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_pst_0.new When run it by hand i get this error (translated from german to english) /bin/tar: No empty Archive created. You forgot the last dot `.' on the command line as given in the debug file. Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
AW: AW: AW: AW: AW: Estimate timeout from server
When run it by hand i get this error (translated from german to english) /bin/tar: No empty Archive created. Everything is like on the other Mashines. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Alexander Jolk Gesendet: Donnerstag, 3. November 2005 09:58 An: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > It does not work. Which means? Do you get an error message? Please cite it. What do the relevant log files say? You showed us yesterday that the estimate phase took almost an hour on this machine, have you waited for that time? > On the client amanda starts the following command: > > /bin/tar --create --file /dev/null --directory /pst --one-file-system > --listed-incremental /var/lib/amanda/gnutar-lists/pst_pst_0.new What happens if you run that command by hand? (And wait until completion, obviously.) Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
Re: AW: AW: AW: AW: Estimate timeout from server
Sebastian Kösters wrote: It does not work. Which means? Do you get an error message? Please cite it. What do the relevant log files say? You showed us yesterday that the estimate phase took almost an hour on this machine, have you waited for that time? On the client amanda starts the following command: /bin/tar --create --file /dev/null --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_pst_0.new What happens if you run that command by hand? (And wait until completion, obviously.) Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
AW: AW: AW: AW: Estimate timeout from server
It does not work. On the client amanda starts the following command: /bin/tar --create --file /dev/null --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_pst_0.new But pst_pst_0.new has always 0kb. And amcheck always told me that everything is ok?! -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Stefan G. Weichinger Gesendet: Mittwoch, 2. November 2005 22:01 An: amanda-users@amanda.org Betreff: Re: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > My report looks like this: > > NOTES: > planner: tapecycle (1) <= runspercycle (10) Please get that sorted out, I assume that this is not what you want, although it has nothing to do with your timeouts. > > Thats all. I tested with a seperate config. Have you increased etimeout already, as Alexander suggested? Stefan.
AW: AW: AW: AW: Estimate timeout from server
I am testing right now with a timeout = 5000s. The Partition i want to backup has 80GB. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Stefan G. Weichinger Gesendet: Mittwoch, 2. November 2005 22:01 An: amanda-users@amanda.org Betreff: Re: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > My report looks like this: > > NOTES: > planner: tapecycle (1) <= runspercycle (10) Please get that sorted out, I assume that this is not what you want, although it has nothing to do with your timeouts. > > Thats all. I tested with a seperate config. Have you increased etimeout already, as Alexander suggested? Stefan.
Re: AW: AW: AW: Estimate timeout from server
Sebastian Kösters wrote: > My report looks like this: > > NOTES: > planner: tapecycle (1) <= runspercycle (10) Please get that sorted out, I assume that this is not what you want, although it has nothing to do with your timeouts. > > Thats all. I tested with a seperate config. Have you increased etimeout already, as Alexander suggested? Stefan.
AW: AW: AW: Estimate timeout from server
My report looks like this:
These dumps were to tape DailySet150.
The next tape Amanda expects to use is: DailySet150.
FAILURE AND STRANGE DUMP SUMMARY:
pst/pst lev 0 FAILED [Estimate timeout from pst]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:15
Run Time (hrs:min) 0:15
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
Label Time Size %Nb
DailySet150 0:00 0.00.0 0
NOTES:
planner: tapecycle (1) <= runspercycle (10)
planner: Adding new disk pst:/pst.
driver: WARNING: got empty schedule from planner
taper: tape DailySet150 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
pst /pst0 FAILED ---
(brought to you by Amanda version 2.4.4p4)
Thats all. I tested with a seperate config.
-Ursprüngliche Nachricht-
Von: Alexander Jolk [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 2. November 2005 13:36
An: Sebastian Kösters
Cc: amanda-users@amanda.org
Betreff: Re: AW: AW: Estimate timeout from server
Sebastian Kösters wrote:
> It failes only doing amdump config
Would you happen to have a relevant error message to show from your
amdump report?
> Amandad on client
[...]
> amandad: time 0.000: got packet:
>
> Amanda 2.4 REQ HANDLE 000-E0426409 SEQ 1130912894
> SECURITY USER amanda
> SERVICE sendsize
> OPTIONS features=feff9ffe0f;maxdumps=1;hostname=pst;
> GNUTAR /pst 0 1970:1:1:0:0:0 -1 OPTIONS |;bsd-auth;compress-fast;index;
[...]
> amandad: time 3428.573: sending REP packet:
>
> Amanda 2.4 REP HANDLE 000-E0426409 SEQ 1130912894
> OPTIONS features=feff9f00;
> /pst 0 SIZE 84404220
>
>
> amandad: time 3438.570: dgram_recv: timeout after 10 seconds
> amandad: time 3438.570: waiting for ack: timeout, retrying
Sounds like a simple estimate timeout to me, 3500s for one partition is
quite long. Bump up your etimeout in amanda.conf to something like
5000s and see whether that works. Or try to find out why estimate on
the pst:/pst takes so long, and do something about that. You might for
instance split it up in smaller chunks. Or switch to server side
estimates which are instant.
You should have got a clear message in amdump's report though, saying
`estimate timeout', which is english for `estimate timeout'.
Alex
--
Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED]
Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
Re: AW: AW: Estimate timeout from server
Sebastian Kösters wrote: It failes only doing amdump config Would you happen to have a relevant error message to show from your amdump report? Amandad on client [...] amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 000-E0426409 SEQ 1130912894 SECURITY USER amanda SERVICE sendsize OPTIONS features=feff9ffe0f;maxdumps=1;hostname=pst; GNUTAR /pst 0 1970:1:1:0:0:0 -1 OPTIONS |;bsd-auth;compress-fast;index; [...] amandad: time 3428.573: sending REP packet: Amanda 2.4 REP HANDLE 000-E0426409 SEQ 1130912894 OPTIONS features=feff9f00; /pst 0 SIZE 84404220 amandad: time 3438.570: dgram_recv: timeout after 10 seconds amandad: time 3438.570: waiting for ack: timeout, retrying Sounds like a simple estimate timeout to me, 3500s for one partition is quite long. Bump up your etimeout in amanda.conf to something like 5000s and see whether that works. Or try to find out why estimate on the pst:/pst takes so long, and do something about that. You might for instance split it up in smaller chunks. Or switch to server side estimates which are instant. You should have got a clear message in amdump's report though, saying `estimate timeout', which is english for `estimate timeout'. Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
AW: AW: Estimate timeout from server
Amanda Tape Server Host Check - amcheck-server: slot 6: date 20051026 label DailySet106 (exact label match) NOTE: skipping tape-writable test Tape DailySet106 label ok Server check took 0.187 seconds Amanda Backup Client Hosts Check Client check: 28 hosts checked in 10.532 seconds, 0 problems found (brought to you by Amanda 2.4.4p4) It failes only doing amdump config Amandad on client amandad: debug 1 pid 29466 ruid 33 euid 33: start at Wed Nov 2 07:28:11 2005 amandad: version 2.4.3 amandad: build: VERSION="Amanda-2.4.3" amandad:BUILT_DATE="Thu Feb 13 11:14:37 EST 2003" amandad:BUILT_MACH="Linux stripples.devel.redhat.com 2.4.20-2.41smp #1 SMP Sun Feb 9 09:47:42 EST 2003 i686 i686 i386 GNU/Linux" amandad:CC="gcc" amandad:CONFIGURE_COMMAND="'./configure' '--host=i386-redhat-linux' '--build=i386-redhat-linux' '--target=i386-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libd ir=/usr/lib' '--libexecdir=/usr/lib/amanda' '--localstatedir=/var/lib' '--sharedstatedir=/usr/com' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--e nable-shared' '--with-index-server=localhost' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-smbclient=/usr/bin/smbclient' '--with-amandahosts' '--with-user=amanda' '--with-group=disk' '--with-gnutar=/bin/tar'" amandad: paths: bindir="/usr/bin" sbindir="/usr/sbin" amandad:libexecdir="/usr/lib/amanda" mandir="/usr/share/man" amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" amandad:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/" amandad:RDEV_PREFIX="/dev/r" DUMP="/sbin/dump" amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient" amandad:GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip" amandad:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" amandad:listed_incr_dir="/var/lib/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="localhost" amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 000-E0426409 SEQ 1130912894 SECURITY USER amanda SERVICE sendsize OPTIONS features=feff9ffe0f;maxdumps=1;hostname=pst; GNUTAR /pst 0 1970:1:1:0:0:0 -1 OPTIONS |;bsd-auth;compress-fast;index; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 000-E0426409 SEQ 1130912894 amandad: time 0.001: bsd security: remote host raid-backup user amanda local user amanda amandad: time 0.002: amandahosts security check passed amandad: time 0.002: running service "/usr/lib/amanda/sendsize" amandad: time 299.936: got packet: Amanda 2.4 REQ HANDLE 000-E0426409 SEQ 1130912894 SECURITY USER amanda SERVICE sendsize OPTIONS features=feff9ffe0f;maxdumps=1;hostname=pst; GNUTAR /pst 0 1970:1:1:0:0:0 -1 OPTIONS |;bsd-auth;compress-fast;index; amandad: time 299.936: received dup P_REQ packet, ACKing it amandad: time 299.937: sending ack: Amanda 2.4 ACK HANDLE 000-E0426409 SEQ 1130912894 amandad: time 599.873: got packet: Amanda 2.4 REQ HANDLE 000-E0426409 SEQ 1130912894 SECURITY USER amanda SERVICE sendsize OPTIONS features=feff9ffe0f;maxdumps=1;hostname=pst; GNUTAR /pst 0 1970:1:1:0:0:0 -1 OPTIONS |;bsd-auth;compress-fast;index; amandad: time 599.873: received dup P_REQ packet, ACKing it amandad: time 599.873: sending ack: Amanda 2.4 ACK HANDLE 000-E0426409 SEQ 1130912894 amandad: time 3428.573: sending REP packet: Amanda 2.4 REP HANDLE 000-E0426409 SEQ 1130912894 OPTIONS features=feff9f00; /pst 0 SIZE 84404220 amandad: time 3438.570: dgram_recv: timeout after 10 seconds amandad: time 3438.570: waiting for ack: timeout, retrying amandad: time 3448.570: dgram_recv: timeout after 10 seconds amandad: time 3448.570: waiting for ack: timeout, retrying amandad: time 3458.570: dgram_recv: timeout after 10 seconds amandad: time 3458.570: waiting for ack: timeout, retrying amandad: time 3468.570: dgram_recv: timeout after 10 seconds amandad: time 3468.570: waiting for ack: timeout, retrying amandad: time 3478.570: dgram_recv: timeout after 10 seconds amandad: time 3478.570: waiting for ack: timeout, giving up! amandad: time 3478.570: pid 29466 finish time Wed Nov 2 08:26:10 2005 sendsize on client sendsize: debug 1 pid 29467 ruid 33 euid 33: start at Wed Nov 2 07:28:11 2005 sendsize: version 2.4.3 sendsize[29469]: time 0.004: cal
