Re: amanda 2.6.1 - configuration problem ?
Jean-Louis Martineau schrieb: > Hi Stefan, > > Try the attached patch. errm, using binary osol-packages there as mentioned. will have to prepare compile-environment to try that. maybe faster for you to generate a new opensolaris-server-pkg? ;) thanks, Stefan
Re: amanda 2.6.1 - configuration problem ?
Hi Stefan,
Try the attached patch.
Jean-Louis
Stefan G. Weichinger wrote:
Greets,
as I start to explore the wonders of opensolaris I have a testbox
running OpenSolaris 2008.11. I installed the amanda-packages from zmanda
and set up amanda 2.6.1 to give zfs-snapshots a try.
Things work fine when I use a DLE like this:
sun.oops.intern home /export/home zfs-snapshot
Let's call it the "one-line syntax".
When I use the "multi-line syntax":
sun.oops.intern r_storage /export/storage {
zfs-snapshot
} 5
the defined script is not included.
(( sidenote: I wanted to use that syntax to enable tape_splitsize for
the particular DLE, my example here does not contain that line as it
should work like this as well ))
--->
## relevant parts in amanda.conf
define script-tool script_zfs_snapshot {
comment "zfs-snapshot"
plugin "amzfs-snapshot"
execute-where client
execute-on pre-dle-amcheck, post-dle-amcheck, pre-dle-estimate,
post-dle-estimate, pre-dle-backup, post-dle-backup
property "DF-PATH" "/usr/sbin/df"
property "ZFS-PATH" "/usr/sbin/zfs"
}
define application-tool app_amgtar {
comment "amgtar"
plugin "amgtar"
property "ATIME-PRESERVE" "no"
property "GNUTAR-PATH" "/usr/bin/gtar"
}
define dumptype zfs-snapshot {
program "APPLICATION"
application "app_amgtar"
script "script_zfs_snapshot"
auth "bsdtcp"
}
## output of "amadmin daily ..."
s...@sun:~$ amadmin daily disklist sun r_storage | grep script
s...@sun:~$ amadmin daily disklist sun /home | grep script
script "script_zfs_snapshot"
Only the one-liner triggers the usage of the script.
This is also traceable by "zfs list -t snapshot" while amdump is
running: there is no snapshot created etc.
The one-line syntax works as expected, creating the snapshot etc
--
I assume that this is not wanted behavior, at least it seems to hurt the
rule of "least surprise" ...
Stefan
Index: common-src/conffile.c
===
--- common-src/conffile.c (revision 15137)
+++ common-src/conffile.c (working copy)
@@ -5708,7 +5708,7 @@
valdst->v.pp_scriptlist = NULL;
if (valsrc->v.pp_scriptlist) {
g_slist_foreach(valsrc->v.pp_scriptlist, ©_pp_scriptlist,
-valdst->v.pp_scriptlist);
+&valdst->v.pp_scriptlist);
}
break;
@@ -5747,9 +5747,9 @@
gpointer user_data_p)
{
pp_script_t *pp_script = data_p;
-pp_scriptlist_t pp_scriptlist = user_data_p;
+pp_scriptlist_t *pp_scriptlist = user_data_p;
-pp_scriptlist = g_slist_append(pp_scriptlist, pp_script);
+*pp_scriptlist = g_slist_append(*pp_scriptlist, pp_script);
}
static void
amanda 2.6.1 - configuration problem ?
Greets,
as I start to explore the wonders of opensolaris I have a testbox
running OpenSolaris 2008.11. I installed the amanda-packages from zmanda
and set up amanda 2.6.1 to give zfs-snapshots a try.
Things work fine when I use a DLE like this:
sun.oops.intern home /export/home zfs-snapshot
Let's call it the "one-line syntax".
When I use the "multi-line syntax":
sun.oops.intern r_storage /export/storage {
zfs-snapshot
} 5
the defined script is not included.
(( sidenote: I wanted to use that syntax to enable tape_splitsize for
the particular DLE, my example here does not contain that line as it
should work like this as well ))
--->
## relevant parts in amanda.conf
define script-tool script_zfs_snapshot {
comment "zfs-snapshot"
plugin "amzfs-snapshot"
execute-where client
execute-on pre-dle-amcheck, post-dle-amcheck, pre-dle-estimate,
post-dle-estimate, pre-dle-backup, post-dle-backup
property "DF-PATH" "/usr/sbin/df"
property "ZFS-PATH" "/usr/sbin/zfs"
}
define application-tool app_amgtar {
comment "amgtar"
plugin "amgtar"
property "ATIME-PRESERVE" "no"
property "GNUTAR-PATH" "/usr/bin/gtar"
}
define dumptype zfs-snapshot {
program "APPLICATION"
application "app_amgtar"
script "script_zfs_snapshot"
auth "bsdtcp"
}
## output of "amadmin daily ..."
s...@sun:~$ amadmin daily disklist sun r_storage | grep script
s...@sun:~$ amadmin daily disklist sun /home | grep script
script "script_zfs_snapshot"
Only the one-liner triggers the usage of the script.
This is also traceable by "zfs list -t snapshot" while amdump is
running: there is no snapshot created etc.
The one-line syntax works as expected, creating the snapshot etc
--
I assume that this is not wanted behavior, at least it seems to hurt the
rule of "least surprise" ...
Stefan
Configuration Problem.
Hi, I am getting this error, “Holding disk /var/tmp: 47624432 KB disk space available, that's plenty ERROR: /dev/rst0: rewinding tape: Inappropriate ioctl for device (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run Server check took 30.019 seconds Amanda Backup Client Hosts Check ERROR: 127.0.0.1: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Client check: 1 host checked in 0.005 seconds, 1 problem found” Please send me the complete configuration guide for Amanda 2.4.2.p1 its compile in Redhat 8. Thanks. Rehan Anwer.
Re: Configuration Problem.
On Tuesday 05 August 2003 07:17, rehanann wrote: >Hi, > I am getting this error, >"Holding disk /var/tmp: 47624432 KB disk space available, that's > plenty ERROR: /dev/rst0: rewinding tape: Inappropriate ioctl for > device (expecting a new tape) >NOTE: skipping tape-writable test >NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist >NOTE: it will be created on the next run >Server check took 30.019 seconds > >Amanda Backup Client Hosts Check > >ERROR: 127.0.0.1: [access as amanda not allowed from > [EMAIL PROTECTED] amandahostsauth failed >Client check: 1 host checked in 0.005 seconds, 1 problem found" > >Please send me the complete configuration guide for Amanda 2.4.2.p1 > its compile in Redhat 8. > >Thanks. >Rehan Anwer. I'll let Jay give the definitive answer here, but generally speaking, the use of 'localhost' is a no-no. You should use the FQDN of that machine so there is absolutely no ambiguity in access rights. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.27% 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.
Re: configuration problem
Have you run the program amlabel ? It will create the amada labels at the head of the tape so that amanda will accept them. Jerry Stretch Industry Inet - Original Message - From: "Dovli" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 07, 2002 8:10 AM Subject: configuration problem > Hello > > I have installed amanda on a Linux server that has a Seagate STT8000A > tape device but I could not manage to get amanda to use my tape device. > Here's the output of amcheck: > Amanda Tape Server Host Check > - > Holding disk /dumps/amanda: 20584876 KB disk space available, that's plenty > ERROR: /dev/ht0: not an amanda tape >(expecting a new tape) > > The tape device is functional otherwise, > What did I do wrong? > Thank you very much for your support. > Dovli >
Re: configuration problem
On Fri, 7 Jun 2002 at 4:10pm, Dovli wrote > I have installed amanda on a Linux server that has a Seagate STT8000A > tape device but I could not manage to get amanda to use my tape device. > Here's the output of amcheck: > Amanda Tape Server Host Check > - > Holding disk /dumps/amanda: 20584876 KB disk space available, that's plenty > ERROR: /dev/ht0: not an amanda tape >(expecting a new tape) > > The tape device is functional otherwise, > What did I do wrong? > Thank you very much for your support. 1) You need to use the non-rewinding tape device -- /dev/nht0 2) You need to label your tapes before amanda can use them -- 'man amlabel' -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
configuration problem
Hello I have installed amanda on a Linux server that has a Seagate STT8000A tape device but I could not manage to get amanda to use my tape device. Here's the output of amcheck: Amanda Tape Server Host Check - Holding disk /dumps/amanda: 20584876 KB disk space available, that's plenty ERROR: /dev/ht0: not an amanda tape (expecting a new tape) The tape device is functional otherwise, What did I do wrong? Thank you very much for your support. Dovli Here is my configuration file: ## !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! ### ### ### ### This file is not meant to be installed "as is", and in fact, it ### ### WILL NOT WORK! You must go through it and make changes appropriate ### ### to your own situation. See the documentation in this file, in the ### ### "man amanda" man page, in the "docs" directory and at the Amanda### ### web page (www.amanda.org). ### ### ### ### !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! ### # # amanda.conf - sample Amanda configuration file. This started off life as # the actual config file in use at CS.UMD.EDU. # # If your configuration is called, say, "csd", then this file normally goes # in /usr/local/etc/amanda/csd/amanda.conf. # org "Matrix"# your organization name for reports mailto "[EMAIL PROTECTED]" # space separated list of operators at your site dumpuser "backup" # the user to run dumps under inparallel 4# maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 25 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle ### ### ### # WARNING: don't use `inf' for tapecycle, it's broken! ### ### ### bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300# 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 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host tapebufs 20 # A positive integer telling taper how many 32k buffers to allocate. # WARNING! If this is set too high, taper will not be able to allocate # the memory and will die. The default is 20 (640k). # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. # Some tape changers require tapedev to be defined; others will use # their own tape device selection mechanism. Some use a separate tape # changer device (changerdev), others will simply ignore this # parameter. Some rely on a configuration file (changerfile) to # obtain more information about tape devices, number of slots, etc; # others just need to store some data in files, whose names will start # with changerfile. For more information about individual tape # changers, read docs/TAPE.CHANGERS. # At most one changerfile entry must be defined; select the most # appropriate one for your configuration. If you select man-changer, # keep the first one; if you decide not to use a tape changer, you may # comment them all out. runtapes 1 # number of tapes to be used in a single run of amdump #tpchanger "chg-manual" # the tape-changer glue script tapedev "/dev/ht0" # the no-rewind tape device to be used #rawtapedev "/dev/ht0" # the raw device to be used (ftape only) #changerfile "/usr/adm/amanda/DailySet1/changer" #changerfile "/usr/adm/amanda/DailySet1/changer-status" #changerfile "/usr/local/etc/amanda/DailySet1/changer.conf" #changerdev "/dev/null" tapetype STT8000A
Re: Configuration Problem
Robert Vetter wrote: [...] > Now I want to backup some directorys from other machines, which run > FreeBSD. I have installed the client there, and did all the required > modifications of system files. amandad seems to work fine. It runs as > user operator. I also created the ~operator/.amandahosts file which > consist os this line: > > devel3.pss.local backup > > Now when I run the amcheck program on the server I get this error > message: > > ERROR: office.pss.local: [access as operator not allowed from > [EMAIL PROTECTED]] open of //.amandahosts failed You'll need to make sure that "operator"'s home directory is where you think it is. On FreeBSD, it seems to be "/" by default, and that is where amandad is looking for the file. You'll also want to make sure that the permissions on the file are correct. The following works for me: > ls -l /.amandahosts -r 1 operator operator 27 Aug 6 21:46 /.amandahosts I'm guessing that in your case, "/.amandahosts" either does not exist or is owned by root. If you would rather put that file somewhere else, you'll need to change the operator user's home directory. -Ben -- Benjamin LewisThank goodness modern convenience is a Database Analyst/Programmer thing of the remote future. Purdue University Computing Center -- Pogo, by Walt Kelly [EMAIL PROTECTED]
Configuration Problem
Hello, I'm trying to install AMANDA in our company network. I've already installed the server on a Debian Linux machine and everthing seems to work fine there - I am able to make backups of the local directorys there The server runs as user backup there. Now I want to backup some directorys from other machines, which run FreeBSD. I have installed the client there, and did all the required modifications of system files. amandad seems to work fine. It runs as user operator. I also created the ~operator/.amandahosts file which consist os this line: devel3.pss.localbackup Now when I run the amcheck program on the server I get this error message: ERROR: office.pss.local: [access as operator not allowed from [EMAIL PROTECTED]] open of //.amandahosts failed I don't know what is wrong here. I checked the FAQ list, but didn't find a solution. Can someone give me some hints? Thanks a lot Robert Vetter
Re: Configuration Problem
"John R. Jackson" wrote: > > >The .amandohosts file is owned by user root ... > > It should probably be owned by "operator", and should be mode 0400 > or 0600. It should not be group/world readable. > > >is located in /root > >directory and readably by all users. ... > > What are the permissions on /root? I seem to recall people having > problems with that in the past. > > >this directory is also the > >homedirectory for the user operator. > > You sure about that? Note this message: > > fopen of //.amandahosts failed: No such file or directory > > That's not the path you think it should be. Hi John, Now it works! The problem was that /root was _not_ the home directory fot the user operator! Thanks a lot Robert
Re: Configuration Problem
>The .amandohosts file is owned by user root ... It should probably be owned by "operator", and should be mode 0400 or 0600. It should not be group/world readable. >is located in /root >directory and readably by all users. ... What are the permissions on /root? I seem to recall people having problems with that in the past. >this directory is also the >homedirectory for the user operator. You sure about that? Note this message: fopen of //.amandahosts failed: No such file or directory That's not the path you think it should be. Amanda creates that name by sticking "/.amandahosts" on the end of the home directory (as reported by getpwuid) of whoever it is running as. If you look at the first line of the amandad*debug file it will tell you the UID. Based on the message, whatever user that maps to (which should be "operator", but don't assume that since things are obviously not working right someplace along the line) appears to have a home directory of "/". >Robert John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Configuration Problem
"John R. Jackson" wrote: > > >... [amandad] runs as > >user operator. I also created the ~operator/.amandahosts file ... > >... > >ERROR: office.pss.local: [access as operator not allowed from > >[EMAIL PROTECTED]] open of //.amandahosts failed > > That says amandad, running as "operator", could not open "/.amandahosts". > A better reason is probably in /tmp/amanda/amandad*debug on the client > (I'm not sure why we don't log it in the error message). > > Who owns that file? What are the permissions? Hello John & Jason, Thanks for your help. The .amandohosts file is owned by user root, is located in /root directory and readably by all users. this directory is also the homedirectory for the user operator. The /tmp/amanda directory and all files in it are owned by user operator and only this user has access to it (rwx--). in the amandad.debug file I faund following: Amanda 2.4 REQ HANDLE 001-083D0508 SEQ 997275472 SECURITY USER backup SERVICE selfcheck OPTIONS ; DUMP ad0s1f 0 OPTIONS |;bsd-auth;compress-fast; sending ack: Amanda 2.4 ACK HANDLE 001-083D0508 SEQ 997275472 bsd security: remote host devel3.pss.local user backup local user operator fopen of //.amandahosts failed: No such file or directory amandad: sending REP packet: Amanda 2.4 REP HANDLE 001-083D0508 SEQ 997275472 ERROR [access as operator not allowed from [EMAIL PROTECTED]] open of //.amandahosts failed Robert
Re: Configuration Problem
"John R. Jackson" wrote: > > >... [amandad] runs as > >user operator. I also created the ~operator/.amandahosts file ... > >... > >ERROR: office.pss.local: [access as operator not allowed from > >[EMAIL PROTECTED]] open of //.amandahosts failed > > That says amandad, running as "operator", could not open "/.amandahosts". > A better reason is probably in /tmp/amanda/amandad*debug on the client > (I'm not sure why we don't log it in the error message). > > Who owns that file? What are the permissions? Hello John & Jason, Thanks for your help. The .amandohosts file is owned by user root, is located in /root directory and readably by all users. this directory is also the homedirectory for the user operator. The /tmp/amanda directory and all files in it are owned by user operator and only this user has access to it (rwx--). in the amandad.debug file I faund following: Amanda 2.4 REQ HANDLE 001-083D0508 SEQ 997275472 SECURITY USER backup SERVICE selfcheck OPTIONS ; DUMP ad0s1f 0 OPTIONS |;bsd-auth;compress-fast; sending ack: Amanda 2.4 ACK HANDLE 001-083D0508 SEQ 997275472 bsd security: remote host devel3.pss.local user backup local user operator fopen of //.amandahosts failed: No such file or directory amandad: sending REP packet: Amanda 2.4 REP HANDLE 001-083D0508 SEQ 997275472 ERROR [access as operator not allowed from [EMAIL PROTECTED]] open of //.amandahosts failed Robert
Re: Configuration Problem
>... [amandad] runs as >user operator. I also created the ~operator/.amandahosts file ... >... >ERROR: office.pss.local: [access as operator not allowed from >[EMAIL PROTECTED]] open of //.amandahosts failed That says amandad, running as "operator", could not open "/.amandahosts". A better reason is probably in /tmp/amanda/amandad*debug on the client (I'm not sure why we don't log it in the error message). Who owns that file? What are the permissions? >Robert Vetter John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: [Amanda-users] Configuration Problem
On Wed, Aug 08, 2001 at 12:32:28PM +0200, Robert Vetter wrote: > Hello, > > I'm trying to install AMANDA in our company network. I've already > installed the server on a Debian Linux machine and everthing seems to > work fine there - I am able to make backups of the local directorys > there The server runs as user backup there. > Now I want to backup some directorys from other machines, which run > FreeBSD. I have installed the client there, and did all the required > modifications of system files. amandad seems to work fine. It runs as > user operator. I also created the ~operator/.amandahosts file which > consist os this line: > > devel3.pss.local backup ^ you said you run as operator, put that here not backup. > > Now when I run the amcheck program on the server I get this error > message: > > ERROR: office.pss.local: [access as operator not allowed from > [EMAIL PROTECTED]] open of //.amandahosts failed > > I don't know what is wrong here. I checked the FAQ list, but didn't find > a solution. > Can someone give me some hints? > > Thanks a lot > > Robert Vetter > ___ > Amanda-users mailing list > [EMAIL PROTECTED] > http://mail.topic.com.au/cgi-bin/mailman/listinfo/amanda-users -- Jason Thomas Phone: +61 2 6257 7111 System Administrator - UID 0 Fax:+61 2 6257 7311 tSA Consulting Group Pty. Ltd. Mobile: 0418 29 66 81 1 Hall Street Lyneham ACT 2602 http://www.topic.com.au/ PGP signature
