Re: amcheckdump(8) failure and other issues
Jukka Salmi -- amanda-users (2013-05-13 22:37:12 +0200): Hello I'm currently updating Amanda on some NetBSD/amd64 5.2_STABLE systems from 2.5.2p1 to 3.3.1; Amanda has been built from pkgsrc. So far the Amanda server and one Amanda client have been updated. The first thing I tried after the update was to check the latest backup (created by the old Amanda), but this failed: $ amcheckdump Daily /dev/null You will need the following volume: DAILY07 Press enter when ready Validating image foo.salmi.ch:/usr dumped 20130512032500 level 1 amcheckdump: Can't locate object method new via package Amanda::Xfer::Source::Recovery (perhaps you forgot to load Amanda::Xfer::Source::Recovery?) at /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Recovery/Clerk.pm line 551. I haven't run amdump(8) yet, thus e.g. $logdir/amdump.$n is still from an Amanda 2.5.2p1 run. Could this be the reason for the failure and I should just run amdump(8)? In the meantime I created a test configuration and ran amdump(8). However, this particular problem still exists. More specifically, now I get foo.salmi.ch:/0 44979k failed: process terminated while waiting for dumping foo.salmi.ch:/etc 1 4k failed: killed while writing to tape (7:45:12) bar.salmi.ch:/0 22788k failed: process terminated while waiting for dumping bar.salmi.ch:/etc 1 5k dump done (7:45:12), process terminated while waiting for writing to tape (bar is the Amanda server) The taper logfile reveals: [...] Amanda::Changer::compat initialized with script /usr/pkg/libexec/amanda/chg-disk, temporary directory /etc/pkg/amanda/Test Amanda::Taper::Scan::traditional stage 1: search for oldest reusable volume Amanda::Taper::Scan::traditional no oldest reusable volume Amanda::Taper::Scan::traditional stage 2: scan for any reusable volume Amanda::Changer::compat: invoking /usr/pkg/libexec/amanda/chg-disk with -info Amanda::Changer::compat: Got response '8 8 1' with exit status 0 Amanda::Changer::compat: invoking /usr/pkg/libexec/amanda/chg-disk with -slot current Amanda::Changer::compat: Got response '8 file:/var/amanda/vtapes/Test' with exit status 0 Slot 8 with label TEST08 is usable Amanda::Taper::Scan::traditional result: 'TEST08' on file:/var/amanda/vtapes/Test slot 8, mode 2 Amanda::Taper::Scribe preparing to write, part size 0, using LEOM (falling back to holding disk as cache) (splitter) (LEOM supported) critical (fatal): Can't locate object method new via package Amanda::Xfer::Dest::Taper::Splitter (perhaps you forgot to load Amanda::Xfer::Dest::Taper::Splitter?) at /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Taper/Scribe.pm line 731. Hmm, looks similar to the problem mentioned above... Any hints? Another potential issue I noticed is with amstatus(8): [...] It seems that this problem was caused by reading an amdump output file created by 2.5.2p1 amdump with 3.3.1 amdump; amstatus(8) now seems to work fine. TIA cheers, Jukka -- This email fills a much-needed gap in the archives.
Re: amcheckdump(8) failure and other issues
On 05/14/2013 02:22 AM, Jukka Salmi wrote: critical (fatal): Can't locate object method new via package Amanda::Xfer::Dest::Taper::Splitter (perhaps you forgot to load Amanda::Xfer::Dest::Taper::Splitter?) at /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Taper/Scribe.pm line 731. Hmm, looks similar to the problem mentioned above... Any hints? It looks like your installation is not complete, or you have multiple version installed? Do you have the following file: /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/XferServer.pm What's the output of the following command: grep AMANDA_COMPONENTS /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Constants.pm Another potential issue I noticed is with amstatus(8): [...] It seems that this problem was caused by reading an amdump output file created by 2.5.2p1 amdump with 3.3.1 amdump; amstatus(8) now seems to work fine. This is normal, amstatus can only read amdump.* from it own version. Jean-Louis
Re: amcheckdump(8) failure and other issues
Hello Jukka Salmi -- amanda-users (2013-05-14 08:22:16 +0200): Jukka Salmi -- amanda-users (2013-05-13 22:37:12 +0200): Hello I'm currently updating Amanda on some NetBSD/amd64 5.2_STABLE systems from 2.5.2p1 to 3.3.1; Amanda has been built from pkgsrc. So far the Amanda server and one Amanda client have been updated. The first thing I tried after the update was to check the latest backup (created by the old Amanda), but this failed: $ amcheckdump Daily /dev/null You will need the following volume: DAILY07 Press enter when ready Validating image foo.salmi.ch:/usr dumped 20130512032500 level 1 amcheckdump: Can't locate object method new via package Amanda::Xfer::Source::Recovery (perhaps you forgot to load Amanda::Xfer::Source::Recovery?) at /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Recovery/Clerk.pm line 551. I haven't run amdump(8) yet, thus e.g. $logdir/amdump.$n is still from an Amanda 2.5.2p1 run. Could this be the reason for the failure and I should just run amdump(8)? In the meantime I created a test configuration and ran amdump(8). However, this particular problem still exists. The first attached patch seems to fix this problem. Note that I don't really understand Perl... More specifically, now I get foo.salmi.ch:/0 44979k failed: process terminated while waiting for dumping foo.salmi.ch:/etc 1 4k failed: killed while writing to tape (7:45:12) bar.salmi.ch:/0 22788k failed: process terminated while waiting for dumping bar.salmi.ch:/etc 1 5k dump done (7:45:12), process terminated while waiting for writing to tape (bar is the Amanda server) The taper logfile reveals: [...] Amanda::Changer::compat initialized with script /usr/pkg/libexec/amanda/chg-disk, temporary directory /etc/pkg/amanda/Test Amanda::Taper::Scan::traditional stage 1: search for oldest reusable volume Amanda::Taper::Scan::traditional no oldest reusable volume Amanda::Taper::Scan::traditional stage 2: scan for any reusable volume Amanda::Changer::compat: invoking /usr/pkg/libexec/amanda/chg-disk with -info Amanda::Changer::compat: Got response '8 8 1' with exit status 0 Amanda::Changer::compat: invoking /usr/pkg/libexec/amanda/chg-disk with -slot current Amanda::Changer::compat: Got response '8 file:/var/amanda/vtapes/Test' with exit status 0 Slot 8 with label TEST08 is usable Amanda::Taper::Scan::traditional result: 'TEST08' on file:/var/amanda/vtapes/Test slot 8, mode 2 Amanda::Taper::Scribe preparing to write, part size 0, using LEOM (falling back to holding disk as cache) (splitter) (LEOM supported) critical (fatal): Can't locate object method new via package Amanda::Xfer::Dest::Taper::Splitter (perhaps you forgot to load Amanda::Xfer::Dest::Taper::Splitter?) at /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Taper/Scribe.pm line 731. The second attached patch seems to fix this problem. However, with those two patches applied amdump(8) succeeds. Manual verification shows that the dumps are ok, but amcheckdump(8) fails: $ amcheckdump Test /dev/null You will need the following volume: TEST01 Press enter when ready Validating image foo.salmi.ch:/ dumped 20130514144326 level 1 Reading volume TEST01 file 1 filter stderr: Level 1 dump of / on foo.salmi.ch:/dev/rraid0a filter stderr: Label: none filter stderr: gzip: (stdin): trailing garbage ignored Validation errors: /usr/bin/gzip exited with status 1 Validating image bar.salmi.ch:/ dumped 20130514144326 level 1 Reading volume TEST01 file 2 filter stderr: Level 1 dump of / on bar.salmi.ch:/dev/rxbd0a filter stderr: Label: none filter stderr: gzip: (stdin): trailing garbage ignored Validation errors: /usr/bin/gzip exited with status 1 Validating image foo.salmi.ch:/etc dumped 20130514144326 level 0 Reading volume TEST01 file 3 filter stderr: gzip: (stdin): trailing garbage ignored Validation errors: /usr/bin/gzip exited with status 1 Validating image bar.salmi.ch:/etc dumped 20130514144326 level 0 Reading volume TEST01 file 4 filter stderr: gzip: (stdin): trailing garbage ignored Validation errors: /usr/bin/gzip exited with status 1 Some images failed to be correclty validated. Full debug output of such an amcheckdump(8) run is available [1]here. BTW, while the header of dump files created using GNUTAR is ok, the header of files created using DUMP tells me: dd if=tape bs=32k skip=1 | [...] | /sbin/restore -xpGf - ... At least NetBSD's restore(8) has no -p and no -G option. Cheers, Jukka [1] http://salmi.ch/~jukka/Amanda/amcheckdump.20130514140608.debug -- This email fills a much-needed gap in the archives. --- Amanda/Recovery/Clerk.pm.orig 2013-05-13 11:03:18.0 +0200 +++ Amanda/Recovery/Clerk.pm2013-05-14 13:15:17.0 +0200 @@ -23,6 +23,7 @@ use warnings; use Carp; use Amanda::Xfer qw( :constants ); +use Amanda::XferServer; use Amanda::Device qw( :constants ); use Amanda::Header; use
Re: amcheckdump(8) failure and other issues
Hello Sorry, I only noticed your email after I sent my previous one... Jean-Louis Martineau -- amanda-users (2013-05-14 10:39:15 -0400): On 05/14/2013 02:22 AM, Jukka Salmi wrote: critical (fatal): Can't locate object method new via package Amanda::Xfer::Dest::Taper::Splitter (perhaps you forgot to load Amanda::Xfer::Dest::Taper::Splitter?) at /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Taper/Scribe.pm line 731. Hmm, looks similar to the problem mentioned above... Any hints? It looks like your installation is not complete, or you have multiple version installed? No, only Amanda 3.3.1 is installed from pkgsrc: $ pkg_info -a | grep ^amanda amanda-common-3.3.1nb2 Common libraries and binaries for Amanda amanda-server-3.3.1nb1 Server part of Amanda, a network backup system amanda-client-3.3.1nb1 Client part of Amanda, a network backup system Do you have the following file: /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/XferServer.pm Yes: $ ls -l /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/XferServer.pm -rw-r--r-- 1 root wheel 4174 May 13 11:03 /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/XferServer.pm What's the output of the following command: grep AMANDA_COMPONENTS /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Constants.pm $ grep AMANDA_COMPONENTS /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Constants.pm $AMANDA_COMPONENTS = ndmp; Cheers, Jukka -- This email fills a much-needed gap in the archives.
Re: amcheckdump(8) failure and other issues
On 05/14/2013 12:01 PM, Jukka Salmi wrote: $ grep AMANDA_COMPONENTS /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Constants.pm $AMANDA_COMPONENTS = ndmp; That's the problem, it should be like: $AMANDA_COMPONENTS = server restore client amrecover ndmp Xfer.pm load XferServer only if server is included in $AMANDA_COMPONENTS. Jean-Louis
Re: amcheckdump(8) failure and other issues
Jean-Louis Martineau -- amanda-users (2013-05-14 12:21:28 -0400): On 05/14/2013 12:01 PM, Jukka Salmi wrote: $ grep AMANDA_COMPONENTS /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Constants.pm $AMANDA_COMPONENTS = ndmp; That's the problem, it should be like: $AMANDA_COMPONENTS = server restore client amrecover ndmp Xfer.pm load XferServer only if server is included in $AMANDA_COMPONENTS. Ok, thanks. In this case it seems to me that the Amanda pkgsrc packages need to be fixed. Thanks for your help! Cheers, Jukka -- This email fills a much-needed gap in the archives.
Re: amcheckdump(8) failure and other issues
Jean-Louis Martineau -- amanda-users (2013-05-14 12:21:28 -0400): On 05/14/2013 12:01 PM, Jukka Salmi wrote: $ grep AMANDA_COMPONENTS /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Constants.pm $AMANDA_COMPONENTS = ndmp; That's the problem, it should be like: $AMANDA_COMPONENTS = server restore client amrecover ndmp Xfer.pm load XferServer only if server is included in $AMANDA_COMPONENTS. Ok, I adjusted Constants.pm to list all components in AMANDA_COMPONENTS (and reverted my changes to the other Perl modules). Now amdump(8) succeeds, but amcheckdump(8) still fails: $ amcheckdump Test /dev/null You will need the following volume: TEST03 Press enter when ready Validating image pi.salmi.ch:/ dumped 20130514213725 level 1 Reading volume TEST03 file 1 filter stderr: Level 1 dump of / on pi.salmi.ch:/dev/rraid0a filter stderr: Label: none Validation errors: /usr/bin/gzip exited with status 1 Validating image tau.salmi.ch:/ dumped 20130514213725 level 1 Reading volume TEST03 file 2 filter stderr: gzip: error writing to output: Broken pipe filter stderr: Level 1 dump of / on tau.salmi.ch:/dev/rxbd0a filter stderr: Label: none Validation errors: /usr/bin/gzip exited with status 1 Validating image pi.salmi.ch:/etc dumped 20130514213725 level 0 Reading volume TEST03 file 3 filter stderr: gzip: error writing to output: Broken pipe Validation errors: /usr/bin/gzip exited with status 1 Validating image tau.salmi.ch:/etc dumped 20130514213725 level 0 Reading volume TEST03 file 4 filter stderr: gzip: (stdin): trailing garbage ignored filter stderr: gzip: (stdin): trailing garbage ignored Validation errors: /usr/bin/gzip exited with status 1 Some images failed to be correclty validated. (full debug output available [1]here) BTW, with Amanda 2.5.2p1, amverify(8) used to work fine. Any hint about what could cause this problem? TIA cheers, Jukka [1] http://salmi.ch/~jukka/Amanda/amcheckdump.20130514213840.debug -- This email fills a much-needed gap in the archives.
amcheckdump(8) failure and other issues
Hello I'm currently updating Amanda on some NetBSD/amd64 5.2_STABLE systems from 2.5.2p1 to 3.3.1; Amanda has been built from pkgsrc. So far the Amanda server and one Amanda client have been updated. The first thing I tried after the update was to check the latest backup (created by the old Amanda), but this failed: $ amcheckdump Daily /dev/null You will need the following volume: DAILY07 Press enter when ready Validating image foo.salmi.ch:/usr dumped 20130512032500 level 1 amcheckdump: Can't locate object method new via package Amanda::Xfer::Source::Recovery (perhaps you forgot to load Amanda::Xfer::Source::Recovery?) at /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Recovery/Clerk.pm line 551. I haven't run amdump(8) yet, thus e.g. $logdir/amdump.$n is still from an Amanda 2.5.2p1 run. Could this be the reason for the failure and I should just run amdump(8)? Another potential issue I noticed is with amstatus(8): $ amstatus Daily ** (process:13775): WARNING **: Use of uninitialized value $gdatestamp in hash element at /usr/pkg/sbin/amstatus line 450, AMDUMP line 82. ** (process:13775): WARNING **: Use of uninitialized value $gdatestamp in hash element at /usr/pkg/sbin/amstatus line 451, AMDUMP line 82. ** (process:13775): WARNING **: Use of uninitialized value $datestamp in concatenation (.) or string at /usr/pkg/sbin/amstatus line 1428, AMDUMP line 106. ** (process:13775): WARNING **: Use of uninitialized value $datestamp in hash element at /usr/pkg/sbin/amstatus line 1429, AMDUMP line 106. ** (process:13775): WARNING **: Use of uninitialized value $datestamp in concatenation (.) or string at /usr/pkg/sbin/amstatus line 1428, AMDUMP line 107. [...] Using /var/amanda/Daily/amdump.1 From Sun May 12 03:25:00 CEST 2013 bar.salmi.ch:/ 0 14166k dump done (3:27:58), process terminated while waiting for writing to tape bar.salmi.ch:/ 0no estimate bar.salmi.ch:/etc0 1748k dump done (3:27:29), process terminated while waiting for writing to tape bar.salmi.ch:/etc0no estimate bar.salmi.ch:/usr0 3k dump done (3:27:22), process terminated while waiting for writing to tape bar.salmi.ch:/usr1no estimate bar.salmi.ch:/var0 72858k dump done (3:32:11), process terminated while waiting for writing to tape bar.salmi.ch:/var0no estimate [...] The rest of the amstatus(8) output looks ok. Are those Perl warnings and the process terminated [...] messages to be expected because amdump(8) has not been run since Amanda was updated, or is this a serious issue which should be fixed before running amdump(8)? TIA cheers, Jukka -- This email fills a much-needed gap in the archives.
