amcheck/amdump error on zfs ng-zone root
amanda 3.1.2, solaris x86 server, solaris x86 client, client != server client successfully backing up. We moved a zpool from another machine and imported several non-global zones onto the client. Underlying mount points seem to be protection 700, we now see the following error from amcheck. ERROR: mailserv: Script 'amzfs-snapshot' command 'POST-DLE-AMCHECK' exited with status 1: see /tmp/amanda/client/curie/selfcheck.20130215114153.debug Client check: 1 host checked in 9.278 seconds. 32 problems found. amdump produces its own errors, but the file systems system actually seem to be backing up just fine. The success of the backups would be amanda's runtar which is suid root. The failure, at least accourding to the message above, would be amanda attempting to run # df, withoug sufficient access. - Me? I think the restrictive permissions on the mount points are not good protection, if you, if you've taken over the global zone you've taken over the non-global zones. Restricting the mount point permissions will not contain a breach in a non-global zone, that is not where the access lives. Probably not an argument I have the energy to make with the other admin. May need to ACL the mount points to allow amanda access (just because the errors make the amanda output files very ugly and are really false negatives, as far as overall success are concerned. Is there an in-Amanda solution? I'll post my work-around to the list, once I've gotten around to working on this and have it tested. thanks, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: amdump error
Lei Zhong wrote: Hi all, I got a weird amdump error. It passed amcheck. I was using dump type always-full specified in disklist. FAIL planner [hostname] /u02/backup 20050729 0 [disk /u02/backup, all estimate failed] It looks like it could estimate how much data was to be backed up, and so it choked. You could try using the "server" estimate plan. It's wildly inaccurate the first run, but after that it's fine. :) Graeme
amdump error
Hi all, I got a weird amdump error. It passed amcheck. I was using dump type always-full specified in disklist. FAIL planner [hostname] /u02/backup 20050729 0 [disk /u02/backup, all estimate failed] FINISH planner date 20050729 time 1.144 WARNING driver WARNING: got empty schedule from planner Thanks, Lei
Re: amdump error
On Fri, 25 Jan 2002 at 8:48am, Davidson, Brian wrote > amcheck reports no errors so that seems ok, but when amdump runs I get a > core dump on taper and the following error report to amanda: > > > FAILURE AND STRANGE DUMP SUMMARY: > taper: FATAL syncpipe_get: r: unexpected EOF > > Any ideas where to look to fix the problem? > First, what OS and version of amanda? What backup program are you using? Check in /tmp/amanda/sendbackup*debug as well as in the log files (amdump.N and log.$DATE.N). Also check your system logs for anything strange. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
amdump error
amcheck reports no errors so that seems ok, but when amdump runs I get a core dump on taper and the following error report to amanda: FAILURE AND STRANGE DUMP SUMMARY: taper: FATAL syncpipe_get: r: unexpected EOF Any ideas where to look to fix the problem? Brian Davidson DynCorp Treasury Integration Group 11710 Plaza America Dr. Reston, VA 20190 703-261-4694 [EMAIL PROTECTED]
Re: amdump error
Hello,
First thing this morning:
The problem repeated itself. I even copied the configuration to a test configuration
and amdump ran just fine.
1500:
I just ran amdump by hand and got a good backup while at a doctor's office. I had
changed one thing: I commented out of my disk list all
entries with the following dumptype used:
define dumptype nocomp-root-incr {
nocomp-root
comment "incremental only"
skip-full
}
Is there anything obviously wrong about this?
2335:
Wait! the cron job just failed! Yikes!
> Is there any chance the run from the night before hasn't finished?
There are no leftover processes, and amcleanup run as my amanda user shows nothing to
recover from
[streak : bv-amanda]$ amcleanup Daily
amcleanup: no unprocessed logfile to clean up.
Scanning /amanda1...
lost+found: skipping cruft directory, perhaps you should delete it.
[streak : bv-amanda]$
I am running amanda version 2.4.2p1 on both server and all clients. The server is a
redhat linux 7.0 machine running a distclean compile of
kernel 2.2.19 (not redhat's version). I have not patched amanda with anything (yet),
but the fstab issues I mentioned in a previous post,
do not exist here. (that is, I have removed the "label" scheme used in redhat 7.0's
/etc/fstab).
I am running linux's version of dump, although that's irrelevant here.
>
> Was the machine possibly rebooted while the previous run was still
> going and amcleanup was not run during the boot sequence?
It was rebooted several times during the day (the day after the first failure), but no
amanda sequences were being run at the time. I have
also updated my rc.local with the following script exerpt:
echo "cleaning up any amanda dumps left in the lurch..."
for i in `ls /usr/local/etc/amanda |grep -v "^lbl"`
do
echo $i
su -l bv-amanda -c "/usr/local/sbin/amcleanup ${i}"
done
> If the above ideas don't help, you could add a couple of lines to the
> script right before it exits:
>
> ls -l $errfile $logdir/log 1>&2
> ps -fu AMANDA 1>&2
Here's the ouput, but it just worked when I ran amdump by hand as my amanda user. the
cron entry is in my amanda user's crontab...
start jason's debug
ls: /var/amanda/DailySet1/amdump: No such file or directory
ls: /var/amanda/DailySet1/log: No such file or directory
UIDPID PPID C STIME TTY TIME CMD
1160021886 21885 0 Apr30 pts/000:00:00 -bash
11600 2050 2049 0 11:36 pts/300:00:00 -bash
11600 2805 2050 0 11:46 pts/300:00:00 sh /usr/local/sbin/amdump Daily
11600 2810 2805 0 11:46 pts/300:00:00 ps -fu bv-amanda
I guess I will see what happens tonight...
--jason
--
~~~
Jason Brooks ~ (503) 641-3440 x1861
Direct ~ (503) 924-1861
System / Network Administrator
Wind River Systems
8905 SW Nimbus ~ Suite 255
Beaverton, Or 97008
Re: amdump error
>I am trying to see why my cron job "amdump Daily" is sometimes failing >with the message: > > "amdump: amdump or amflush is already running, or you must run > amcleanup" Is there any chance the run from the night before hasn't finished? Was the machine possibly rebooted while the previous run was still going and amcleanup was not run during the boot sequence? What version of Amanda are you using? Amcleanup had some problems at one point. >Well, $errfile corresponds to "/var/amanda/DailySet1/amdump" and >$logdir/log corresponds to "/var/amanda/DailySet1/log". Neither one of >these files exist, so why is amdump balking at this point? One or the other obviously existed at the time amdump ran or the test would not have triggered. If the above ideas don't help, you could add a couple of lines to the script right before it exits: ls -l $errfile $logdir/log 1>&2 ps -fu AMANDA 1>&2 This will tell you while file exists and when it was last modified. Make sure the arguments to ps are right for your OS, but the idea is to display any processes still running for the Amanda user (change AMANDA to match your config). >--jason John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amdump error
Hello, I am trying to post my messages atomically: one topic at a time. Please let me know if this is not correct... I am trying to see why my cron job "amdump Daily" is sometimes failing with the message: "amdump: amdump or amflush is already running, or you must run amcleanup" This configuration has functioned before. Cron is executing as my amanda user, and all permissions (I believe) are correct. Running "amcleanup Daily" produces "amcleanup: no unprocessed logfile to clean up." I looked in the amdump script to find the line "amdump or amflush is already running": if test -f $errfile || test -f $logdir/log; then echo "amdump: amdump or amflush is already running, or you must run amcleanup" >&2 exit 1 fi Well, $errfile corresponds to "/var/amanda/DailySet1/amdump" and $logdir/log corresponds to "/var/amanda/DailySet1/log". Neither one of these files exist, so why is amdump balking at this point? --jason -- ~~~ Jason Brooks ~ (503) 641-3440 x1861 Direct ~ (503) 924-1861 System / Network Administrator Wind River Systems 8905 SW Nimbus ~ Suite 255 Beaverton, Or 97008
RESULT! - (was Newbie help please with amdump error message)
Hi - especially Chris Marble and John Jackson... What a wonderful thing sleep is... Based on various suggestions, I forced amanda to use GNUTAR. Running amcheck again, it complained about a non-existant directory (gnutar-lists) which I created amdump worked! Thanks Chris / John for responding so quickly and so many times. Dirk
Newbie help please with amdump error message
Hi I've just installed amanda for the first time. A test amdump gives me the following report... FAILURE AND STRANGE DUMP SUMMARY: localhost/etc lev 0 FAILED [disk /etc offline on localhost?] Any light-shining would be appreciated thanks Dirk
Re: Newbie help please with amdump error message
>I've just installed amanda for the first time. A test amdump gives me the foll >owing report... > >FAILURE AND STRANGE DUMP SUMMARY: > localhost/etc lev 0 FAILED [disk /etc offline on localhost?] First, I suggest using the real host name rather than "localhost". You'll be much happier keeping things apart later. Did you run amcheck? Did it have anything to say? Are you using dump or GNU tar? Many versions of dump will not deal with subdirectories of a file system. If that's what you want to do, you may have to use GNU tar. >Dirk John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Newbie help please with amdump error message
>The 'program' listed was DUMP so I added > >program 'GNUTAR' to my disklist ... >amadmin now says GNUTAR but the same error comes up in the report. Huh? Amdump still complains about /etc? Is amcheck still happy? What's in /tmp/amanda/sendsize*debug on the client? What version of GNU tar do you have? If it's 1.12, you need to apply the Amanda patches from the web page. If it's 1.13, you should be at 1.13.19 -- almost anything earlier has problems. >Dirk John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Newbie help please with amdump error message
Following another suggestion I had a few minutes ago, I ran
amadmin Daily disklist
The 'program' listed was DUMP so I added
program 'GNUTAR' to my disklist to give
xxx/etc{
nocomp-user
program "GNUTAR"
}
amadmin now says GNUTAR but the same error comes up in the report.
> My error, that doesn't tell you. I think Amanda defaults to dump if it can
> find it. On many systems dump can only work on filesystems but that's not
> true with the linux dump. What version of dump are you running?
> /sbin/dump --version
> will give an error message and the dump version. 0.4b21 is the latest and
> best. If you're running an older one I suggest getting the latest from
> www.sourceforge.net.
>
0.4b19 so I'll get the latest version
> Try specifying a partition to back up in your disklist file. /tmp should be quick
> if it exists.
back to work...
thanks
Dirk
Re: Newbie help please with amdump error message
Sorry about the etiquette.. I was expecting to converse via the mailing list but got a number of direct responses. nocomp-user program is set to DUMP Dirk - Original Message - From: "John R. Jackson" > In the future, you might want to respond to the whole list. They're used > to it :-). If I (or anyone else who tries to help) gets busy, it may > take longer to get a response. It also lets everyone know how resolution > of the problem is progressing. > > >> First, I suggest using the real host name rather than "localhost". > >> You'll be much happier keeping things apart later. > > > >I've tried that as well, got the same report. > > I didn't mean to imply this would fix the problem. It was a general > Amanda usage suggestion. > > >> Are you using dump or GNU tar? ... > > > >Not sure... I built amanda with all the defaults (RH7 and amanda 2.4.2p1). > >Is there an easy way to tell? > > What dumptype did you use in your disklist? > > If you run "amadmin disklist ", what is "program" > set to? > > >Dirk > > JJ >
Re: amdump error: lev 0 FAILED [/usr/bin/tar returned 1]
>I am trying to find why tar is failing. ... What's in /tmp/amanda/sendbackup*debug on the client? Are you getting FAILED or STRANGE messages logged in the E-mail? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amdump error: lev 0 FAILED [/usr/bin/tar returned 1]
Alert: This only occurs when I try and dump a root partition. Seems to
work fine on others.
On Fri, 3 Nov 2000, Eric Wadsworth wrote:
> I am trying to find why tar is failing. Here is information, if anyone has
> ideas:
>
> 'amadmin DailySet1 version' shows where GNUTAR is set:
> GNUTAR="/usr/bin/tar"
>
> I verified, and yes, tar is there.
>
> These are in the amanda.conf file:
>
> define dumptype global {
> comment "Global definitions"
> index yes
> }
>
> define dumptype root-tar {
> global
> program "GNUTAR"
> comment "root partitions dumped with tar"
> compress none
> index
> exclude list "/usr/local/etc/amanda/exclude.gtar"
> priority low
> }
>
> There is only one line in the disklist file:
>
> this.system.consys.com /dev/da0s1a root-tar
>
> this.system is the amanda host (has the tape drive). This partition is the
> root partition on the computer.
>
> There is no such file /usr/local/etc/amanda/exclude.gtar as specified in
> the definition of root-tar (See above), but I tried a dump with that line
> commented out, same result.
>
> Thanks in advance for any ideas! --- Eric
>
>
amdump error: lev 0 FAILED [/usr/bin/tar returned 1]
I am trying to find why tar is failing. Here is information, if anyone has
ideas:
'amadmin DailySet1 version' shows where GNUTAR is set:
GNUTAR="/usr/bin/tar"
I verified, and yes, tar is there.
These are in the amanda.conf file:
define dumptype global {
comment "Global definitions"
index yes
}
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index
exclude list "/usr/local/etc/amanda/exclude.gtar"
priority low
}
There is only one line in the disklist file:
this.system.consys.com /dev/da0s1a root-tar
this.system is the amanda host (has the tape drive). This partition is the
root partition on the computer.
There is no such file /usr/local/etc/amanda/exclude.gtar as specified in
the definition of root-tar (See above), but I tried a dump with that line
commented out, same result.
Thanks in advance for any ideas! --- Eric
