R: Hostname lookup failed
Someone have deleted the PTR record of this server. Now i have added it, and amanda works perfectly. I thought that was a dns problem, but i was convinced that amanda uses only forward lookup zone. Thanks to all for help. Giovanni p.s. Sorry again for bad english.
Re: problems with index creation
Le samedi 02 juillet 2005 à 13:31 -0400, Jon LaBadie a écrit : On Sat, Jul 02, 2005 at 06:17:11PM +0200, Eric DOUTRELEAU wrote: Hi with changing index to index yes it didn't solved my problem. and the output if the commands give me the same output. the only thing that i can see about the hosts that failed is that they a lot of partition to backup. one has 20 and the othr 36 Selon Jon LaBadie [EMAIL PROTECTED]: On Fri, Jul 01, 2005 at 05:36:18PM +0200, ERic Doutreleau wrote: Indeed i have index yes for almost type except some that are realted to my problems. i will test that that night thanks for your answer Le vendredi 01 juillet 2005 à 07:25 -0400, Jon LaBadie a écrit : On Fri, Jul 01, 2005 at 11:48:38AM +0200, Eric Doutreleau wrote: i have a problem with index creation. i have out the word index on my dumptype but the index created are always empty. Just to confirm, do you have just the word index, or is it index yes? Should be the latter. Do you specify spindle numbers for those DLEs to prevent all 20 and 36 from trying to be backed up at the same time? yes i did the backup are running fine it s only the index the problem I seem to recall some problem with udp packet size and large number of DLEs. well it was what i was thinking of i will search the archive for that.
Re: problems with index creation
On Tuesday 05 July 2005 05:15, Eric Doutreleau wrote: [...] On Fri, Jul 01, 2005 at 05:36:18PM +0200, ERic Doutreleau wrote: Indeed i have index yes for almost type except some that are realted to my problems. i will test that that night thanks for your answer Le vendredi 01 juillet 2005 à 07:25 -0400, Jon LaBadie a écrit : On Fri, Jul 01, 2005 at 11:48:38AM +0200, Eric Doutreleau wrote: i have a problem with index creation. i have out the word index on my dumptype but the index created are always empty. Just to confirm, do you have just the word index, or is it index yes? Should be the latter. This is correct, it should be index yes in the config. WRT spindle numbers, they should correspond to the drives per box. So you can use 1 for the 1st driv, 2 for the 2nd drive etc, per box. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: planner segfault, FreeBSD 4.11
Hello I can confirm this problem. It looks like a bug with 2.95.4 gcc --version 2.95.4 System: 4.10-RELEASE-p3 I've installed gcc 3.4 and recompiled amanda 2.4.5 with it. It works now. Amanda 2.4.5 works with FreebSD 5.4 so I chose gcc 3.4. Perhaps it works with other 3.x gcc too Regards, Thomas Am Mittwoch, den 08.06.2005, 22:11 +0200 schrieb Per olof Ljungmark: I was wrong, Amanda *was* built with gmake 3.80. I have rebuilt the system, recompiled Amanda as well but got same error. I will need to go back to 2.4.4 apparently. It's not gmake that is important, but gcc (and gcc 3.80 does not exist AFAIK). What does gcc --version say? [candyman] /opt/amanda# /usr/bin/gcc --version 2.95.4 [candyman] /opt/amanda# /usr/local/bin/gmake --version GNU Make 3.80 Problem already reported in fact: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/81104 Per olof -- * Thomas Vogt UNIX System Administrator - SolNet AS9044 - PGP-3239B720 * * Phone: sip:[EMAIL PROTECTED] / sip:[EMAIL PROTECTED] * signature.asc Description: This is a digitally signed message part
exclude list optional not working?
I've just added exclude lists as per the examples in the online documentation, with the following configuration: exclude list optional .amanda.excludes However, amcheck now complains on every item in the disklist for a *single* host, that it [Can't open exclude file '/filepath' : Permission denied]. I thought optional was supposed to prevent this from being an error condition? And, even stranger, it doesn't seem to generate any similar errors on any of the other client systems, just a single one. Any ideas? -- Graeme Humphries ([EMAIL PROTECTED]) Linux Administrator VCom Inc. (306) 955-7075 ext 485 My views and comments do not necessarily reflect the views of my employer.
chg-zd-mtx always cleans?
Here's another little oddity I've been noticing: when using the chg-zd-mtx changer script, even though I've set autoclean to 0 and cleanslot to 7, when I do an amtape update it *always* loads and runs the cleaning tape, and does a cleaning cycle. This, in turn, screws up the update. Is this supposed to happen? Am I missing a piece of configuration for that changer script? :) -- Graeme Humphries ([EMAIL PROTECTED]) Linux Administrator VCom Inc. (306) 955-7075 ext 485 My views and comments do not necessarily reflect the views of my employer.
Re: exclude list optional not working?
Graeme Humphries wrote: I've just added exclude lists as per the examples in the online documentation, with the following configuration: exclude list optional .amanda.excludes However, amcheck now complains on every item in the disklist for a *single* host, that it [Can't open exclude file '/filepath' : Permission denied]. I thought optional was supposed to prevent this from being an error condition? And, even stranger, it doesn't seem to generate any similar errors on any of the other client systems, just a single one. Any ideas? As you have read the docs, this file should be specified relative to the DLE on the client. I'd suggest setting exclude list optional ./.amanda.excludes instead and check that this file is accessible by the AMANDA-user. The optional means that the existence of the file is optional, not its accessibility due to wrong permissions if existing. If it exists, it has to be accessible. -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
Re: exclude list optional not working?
--On Tuesday, July 05, 2005 09:51:36 -0600 Graeme Humphries [EMAIL PROTECTED] wrote: I've just added exclude lists as per the examples in the online documentation, with the following configuration: exclude list optional .amanda.excludes However, amcheck now complains on every item in the disklist for a *single* host, that it [Can't open exclude file '/filepath' : Permission denied]. I thought optional was supposed to prevent this from being an error condition? And, even stranger, it doesn't seem to generate any similar errors on any of the other client systems, just a single one. Any ideas? amcheck runs as your Amanda user and may not have permissions to the directory where your exclude file lives. amdump is suid root so it will be able to access the file. I consider it a bug but others consider it a feature (fewer suid programs). 'optional' just means it's ok to not be there, but 'permission denied' is an error and Amanda reports it as such. Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: exclude list optional not working?
On Tue, 2005-07-05 at 11:41 -0500, Frank Smith wrote: amcheck runs as your Amanda user and may not have permissions to the directory where your exclude file lives. I *thought* I had amanda running as root on the client, but I may be wrong. It doesn't complain that it can't access any of those shares, which only root should be able to have full access to. 'optional' just means it's ok to not be there, but 'permission denied' is an error and Amanda reports it as such. That's not what the online man page seems to say: If optional is specified for exclude list, then amcheck will not complain if the file doesn't exist or is not readable. The file is not readable (permission denied entering the directory that contains is). Maybe it only checks for permission problems on the exact file, and not on containing directories? Graeme
Re: exclude list optional not working?
On Tue, 2005-07-05 at 18:07 +0200, Stefan G. Weichinger wrote: As you have read the docs, this file should be specified relative to the DLE on the client. Yep. I want it to, like shown in the docs, just look for a .amanda.excludes file in the root of every share I'm backing up. I'd suggest setting exclude list optional ./.amanda.excludes Hmmm, would that really make a difference? Given a disklist entry like /files/share, wouldn't that just cause it to look for /files/share/./.amanda.excludes? The optional means that the existence of the file is optional, not its accessibility due to wrong permissions if existing. If it exists, it has to be accessible. But the file *doesn't* exist in any of these directories yet. I just added the config change, I haven't actually created the file anywhere yet. Graeme
Re: chg-zd-mtx always cleans?
On Tue, 2005-07-05 at 12:55 -0400, Jon LaBadie wrote: Do your slot numbers, first slot to last slot include the slot with the cleaning tape? Yeah, I had a typo in my changer config file that was breaking this. Once I fixed that, it worked fine. :P If like my DDS3 changer, amanda may not be running the cleaning tape; but instead just loading it. On my changer loading a cleaning tape automatically runs it. Yeah, I think that's exactly what was happening.
Re: chg-zd-mtx always cleans?
On Tue, Jul 05, 2005 at 09:56:52AM -0600, Graeme Humphries wrote: Here's another little oddity I've been noticing: when using the chg-zd-mtx changer script, even though I've set autoclean to 0 and cleanslot to 7, when I do an amtape update it *always* loads and runs the cleaning tape, and does a cleaning cycle. This, in turn, screws up the update. Is this supposed to happen? Am I missing a piece of configuration for that changer script? :) Do your slot numbers, first slot to last slot include the slot with the cleaning tape? If like my DDS3 changer, amanda may not be running the cleaning tape; but instead just loading it. On my changer loading a cleaning tape automatically runs it. Again on mine, that causes the magazine to be ejected at the end of the cleaning run. I ended up not having a cleaning tape in the magazine at all. Load it manually when I want to clean. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: exclude list optional not working?
--On Tuesday, July 05, 2005 10:47:59 -0600 Graeme Humphries [EMAIL PROTECTED] wrote: On Tue, 2005-07-05 at 11:41 -0500, Frank Smith wrote: amcheck runs as your Amanda user and may not have permissions to the directory where your exclude file lives. I *thought* I had amanda running as root on the client, but I may be wrong. It doesn't complain that it can't access any of those shares, which only root should be able to have full access to. You really shouldn't be running Amanda as root, but as a separate user. When you run 'make install' as root it installs the executables that need root access suid root. Then when your backups run it can access everything necessary. 'optional' just means it's ok to not be there, but 'permission denied' is an error and Amanda reports it as such. That's not what the online man page seems to say: If optional is specified for exclude list, then amcheck will not complain if the file doesn't exist or is not readable. The file is not readable (permission denied entering the directory that contains is). Maybe it only checks for permission problems on the exact file, and not on containing directories? In my experience the error occurs if Amanda can't access the directory to see if the file is there. Perhaps the docs need to be rephrased. The error is harmless, runtar can access the exclude file (as root) and will do what you want (assuming your file is correct). Frank Graeme -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: exclude list optional not working?
On Tue, 2005-07-05 at 12:07 -0500, Frank Smith wrote: You really shouldn't be running Amanda as root, but as a separate user. When you run 'make install' as root it installs the executables that need root access suid root. Then when your backups run it can access everything necessary. I've installed via Debian (Ubuntu) package, and the reason I need to run as root is because on our fileserver, giving access to the amanda user in the unix permissions isn't feasible. You can thank Samba and Windows clients that decide to automatically overwrite ACLs for that. ;P In my experience the error occurs if Amanda can't access the directory to see if the file is there. Perhaps the docs need to be rephrased. The error is harmless, runtar can access the exclude file (as root) and will do what you want (assuming your file is correct). I'd rather just have any permission related error ignored if the optional keyword is used. Is there a situation where we *would* want it to hard error out on an optional exclude list if it can't get into the directory the exclude list is supposed to be in? Graeme
Re: driver: WARNING: got empty schedule from planner
below is the error message from the amdump.X. My OS is solaris 8. thanks for your help. m5413.drsite.univision.com $ cat amdump.1 amdump: start at Tue Jul 5 13:21:10 EDT 2005 amdump: datestamp 20050705 planner: pid 5866 executable /usr/local/libexec/planner version 2.4.4p4 planner: build: VERSION=Amanda-2.4.4p4 planner:BUILT_DATE=Wed Jun 15 14:10:32 EDT 2005 planner:BUILT_MACH=SunOS m5413.drsite.univision.com 5.8 Generic_117350-14 sun4u sparc SUNW,Sun-Fire-V240 planner:CC=gcc planner:CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=uol' planner: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin planner:libexecdir=/usr/local/libexec mandir=/usr/local/man planner:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda planner:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/dsk/ planner:RDEV_PREFIX=/dev/rdsk/ DUMP=/usr/sbin/ufsdump planner:RESTORE=/usr/sbin/ufsrestore VDUMP=UNDEF VRESTORE=UNDEF driver: pid 5865 executable /usr/local/libexec/driver version 2.4.4p4 driver: tape size 103809024 driver: send-cmd time 0.003 to taper: START-TAPER 20050705 planner:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF planner:SAMBA_CLIENT=UNDEF GNUTAR=UNDEF planner:COMPRESS_PATH=/usr/bin/gzip planner:UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=UNDEF planner:MAILER=/usr/bin/mailx planner:listed_incr_dir=/usr/local/var/amanda/gnutar-lists planner: defs: DEFAULT_SERVER=m5413.drsite.univision.com planner:DEFAULT_CONFIG=DailySet1 planner:DEFAULT_TAPE_SERVER=m5413.drsite.univision.com planner:DEFAULT_TAPE_DEVICE=/dev/rmt/0bn HAVE_MMAP HAVE_SYSVSHM planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE planner:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS planner:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP planner: taper COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast : pid planner: 5867 COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc executable taper version 2.4.4p4 planner: time 0.023: dgram_bind: socket bound to 0.0.0.0.624 READING CONF FILES... taper: page size is 8192 taper: buffer size is 32768 taper: buffer[00] at fef0 taper: buffer[01] at fef08000 taper: buffer[02plannerdriver: started ] at : time dumper0fef10.025 pid : startup took 5868taper0.025 : buffer[ secs 03driver: started SETTING UP FOR ESTIMATES... ] at dumper1plannerfef18000 pid : time 58690.041taper : setting up estimates for : buffer[driver: started m5413.drsite.univision.com04dumper2:] at pid /dumpsfef25870 dumperdumper m5413.drsite.univision.com: dgram_bind: socket bound to : dgram_bind: socket bound to taperdumper:0.0.0.00.0.0.0: buffer[: dgram_bind: socket bound to /dumps.626.628050.0.0.0 overdue ] at .62712970driver: started dumperdumperfef28000 daydumper3: pid : pid dumpers pid 58685870taper: pid for level 0 5871 executable executable : buffer[5869setup_estimate: dumper0dumper206 executable m5413.drsite.univision.com version version ] at dumper1:2.4.4p42.4.4p4fef3 version /dumps, using port , using port 2.4.4p4: command 626 628 taper, using port 0dumper: buffer[627 , options:: dgram_bind: socket bound to 07 last_level 0.0.0.0] at -1fef38000.629 next_level0 -taper12970: buffer[ level_days 080 ] at getting estimates fef40 (0 ) taper-1 (dumper: buffer[-: pid 091) -5871] at 1 executable fef48000 (-1dumper3 ) version taper2.4.4p4: buffer[planner, using port 10: time 629 ] at 0.065fef5: setting up estimates took 0.023taper secs : buffer[ GETTING ESTIMATES... 11] at fef58000 taper: buffer[12] at fef6 taper: buffer[13] at fef68000 taper: buffer[14] at fef7 taper: buffer[15] at fef78000 taper: buffer[16] at fef8 taper: buffer[17] at fef88000 taper: buffer[18] at fef9 taper: buffer[19] at fef98000 taper: buffer structures at fefa for 240 bytes changer: opening pipe to: /usr/local/libexec/chg-zd-mtx -info changer: got exit: 2 str: none cannot determine first slot taper: could not get changer info: cannot determine first slot planner: time 2.124: got result for host m5413.drsite.univision.com disk /dumps: 0 - -1K, -1 - -1K, -1 - -1K planner: time 2.124: getting estimates took 2.053 secs FAILED QUEUE: 0: m5413.drsite.univision.com /dumps DONE QUEUE: empty ANALYZING ESTIMATES... planner: FAILED m5413.drsite.univision.com /dumps 20050705 0 [disk /dumps, all estimate failed] INITIAL SCHEDULE (size 64): DELAYING DUMPS IF NEEDED, total_size 64, tape length 103809024 mark 0 delay: Total size now 64. PROMOTING DUMPS IF NEEDED, total_lev0 0, balanced_size 0... planner: time 2.139: analysis took 0.015 secs GENERATING SCHEDULE: ENDFLUSH driver: adding holding disk 0 dir /cust/home/amanda/dumps size 2048000 reserving 2048000 out of 2048000 for degraded-mode dumps driver: flush size 0 driver: start time 2.141 inparallel 4 bandwidth 2000 diskspace 2048000 dir OBSOLETE datestamp 20050705 driver
Re: driver: WARNING: got empty schedule from planner
khalid maqsudi wrote: below is the error message from the amdump.X. My OS is solaris 8. thanks for your help. [...] changer: opening pipe to: /usr/local/libexec/chg-zd-mtx -info changer: got exit: 2 str: none cannot determine first slot taper: could not get changer info: cannot determine first slot You should debug your chg-zd-mtx-setup ... -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
Re: exclude list optional not working?
On Tue, Jul 05, 2005 at 11:19:09AM -0600, Graeme Humphries wrote: In my experience the error occurs if Amanda can't access the directory to see if the file is there. Perhaps the docs need to be rephrased. I'd rather just have any permission related error ignored if the optional keyword is used. Is there a situation where we *would* want it to hard error out on an optional exclude list if it can't get into the directory the exclude list is supposed to be in? I'd have to peek at the docs/source to be certain of this, but I haven't done so. While runtar is setuid root, I don't think the pieces that set up the runtar command line are run setuid root. They still need normal amanda user access to the exclude file. If there were no exclude file, then the admin can reasonably feel that it is not contributing to the list of excluded file. Thus no error on setting optional is reasonable. But what about an existing exclude file without access permissions? If that was not an error, how would the admin know the exclude file was not contributing anything to the list of excluded files?? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: exclude list optional not working?
On Tue, 2005-07-05 at 16:50 -0500, Frank Smith wrote: You can do what I do, just ignore the errors from amcheck that you know are bogus. That's probably what I'll end up doing, but I know that for me it's generally bad practice, because it means that eventually I'll just stop paying attention to the warnings amcheck mails me, and I'll miss something important. ;)
Re: exclude list optional not working?
Title: Re: exclude list optional not working? On Tue, 2005-07-05 at 23:14 +0200, Paul Bijnens wrote: - or if the file is not readable: in that case amanda trusts the suid-root runtar executable so that gnutar can read the contents of the file, never mind the permissions. But Amanda does need to verify if the file is there or not, otherwise gnutar will complain about having handed a nonexisting file in the argument list. Ahhh, I see, it just passes off the file to tar if it can be verified as existing. In my case, it can't verify that the file exists or not, so it chokes. Interesting. I wonder how I'll work around that. :)
Re: exclude list optional not working?
Title: Re: exclude list optional not working? On Tue, 2005-07-05 at 15:34 -0400, Jon LaBadie wrote: If there were no exclude file, then the admin can reasonably feel that it is not contributing to the list of excluded file. Thus no error on setting optional is reasonable. But what about an existing exclude file without access permissions? If that was not an error, how would the admin know the exclude file was not contributing anything to the list of excluded files?? That's a good question, but I don't think it directly affects the issue. The way I'm looking at it is this: the docs claim that optional will ignore errors if it can't read the exclude list file. Regardless of whether or not this is a good design decision, if that's the intended functionality, it should work regardless of if the permission problems are on the file itself or on the enclosing directory (structure). Does that make sense? Graeme
Re: exclude list optional not working?
Graeme Humphries wrote: I'd rather just have any permission related error ignored if the optional keyword is used. Is there a situation where we *would* want it to hard error out on an optional exclude list if it can't get into the directory the exclude list is supposed to be in? Amanda will not complain - if the exclude file on the client is not there at all In this case amanda can construct a gtar argument list that does not contain the exclude list of a non-existing file. - or if the file is not readable: in that case amanda trusts the suid-root runtar executable so that gnutar can read the contents of the file, never mind the permissions. But Amanda does need to verify if the file is there or not, otherwise gnutar will complain about having handed a nonexisting file in the argument list. -- 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: exclude list optional not working?
On Tuesday 05 July 2005 12:47, Graeme Humphries wrote: On Tue, 2005-07-05 at 11:41 -0500, Frank Smith wrote: amcheck runs as your Amanda user and may not have permissions to the directory where your exclude file lives. I *thought* I had amanda running as root on the client, but I may be wrong. It doesn't complain that it can't access any of those shares, which only root should be able to have full access to. This is beginning to sound as if the install isn't quite right. 1) amanda MUST be built by the user who will run it, in most cases this would be the user 'amanda'. 2) The user amanda MUST be a member of a high ranking group such as 'disk', 'backup', or I've seen one case of 'sys'. 3) amanda MUST be installed by root after being built. 4) the user running amanda must be the one who built it. 5) only when all the above is followed, will all the exec permissions be correct. Amanda will do its own suid to root when it needs those perms. This fails if root built it. If you installed from an rpm, I've seen a couple of broken rpms, and generally speaking, probably well over 80% of us have built it from tarballs. I build every new snapshot of 2.4.5 thats put up within a day or so of its appearance, and run that one till the next one shows up or I get bit have to back up a version. Thats been a very un-common occurance... And finally, to amanda (and tar) there is a huge difference between an .amanda-excludes file and an ./.amanda-excludes file. It takes the leading ./ to anchor it to the current directory. The second . in front of the amanda-excludes file only serves to hide it from a normal directory listing. Now, you can have such a file as an .amanda-excludes, which contains a list of stuff in ./ style to skip, but in my experience with using it, a full path to the excludes file was needed, such as /amanda/.amanda-excludes. 'optional' just means it's ok to not be there, but 'permission denied' is an error and Amanda reports it as such. That's not what the online man page seems to say: If optional is specified for exclude list, then amcheck will not complain if the file doesn't exist or is not readable. The file is not readable (permission denied entering the directory that contains is). Maybe it only checks for permission problems on the exact file, and not on containing directories? Graeme And this says the install isn't quite up to specs, see above. Its also in the top 10 FAQ I believe. I HTH, Graeme. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: exclude list optional not working?
On Tuesday 05 July 2005 13:19, Graeme Humphries wrote: On Tue, 2005-07-05 at 12:07 -0500, Frank Smith wrote: You really shouldn't be running Amanda as root, but as a separate user. When you run 'make install' as root it installs the executables that need root access suid root. Then when your backups run it can access everything necessary. I've installed via Debian (Ubuntu) package, and the reason I need to run as root is because on our fileserver, giving access to the amanda user in the unix permissions isn't feasible. You can thank Samba and Windows clients that decide to automatically overwrite ACLs for that. ;P amanda cannot do an suid root if it was built as root, no way around it due to the failure of the suid command if its already owned by root. In my experience the error occurs if Amanda can't access the directory to see if the file is there. Perhaps the docs need to be rephrased. The error is harmless, runtar can access the exclude file (as root) and will do what you want (assuming your file is correct). I'd rather just have any permission related error ignored if the optional keyword is used. Is there a situation where we *would* want it to hard error out on an optional exclude list if it can't get into the directory the exclude list is supposed to be in? Graeme -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: chg-zd-mtx always cleans?
On Tuesday 05 July 2005 12:55, Jon LaBadie wrote: On Tue, Jul 05, 2005 at 09:56:52AM -0600, Graeme Humphries wrote: Here's another little oddity I've been noticing: when using the chg-zd-mtx changer script, even though I've set autoclean to 0 and cleanslot to 7, when I do an amtape update it *always* loads and runs the cleaning tape, and does a cleaning cycle. This, in turn, screws up the update. Is this supposed to happen? Am I missing a piece of configuration for that changer script? :) Do your slot numbers, first slot to last slot include the slot with the cleaning tape? If like my DDS3 changer, amanda may not be running the cleaning tape; but instead just loading it. On my changer loading a cleaning tape automatically runs it. Again on mine, that causes the magazine to be ejected at the end of the cleaning run. I ended up not having a cleaning tape in the magazine at all. Load it manually when I want to clean. There is also a numbering base difference Jon, some of amanda runs on base 0 numbers and some of it runs on base 1 numbers. If the magazine has room for 8 tapes, then in chg-scsi for instance, the slots are 0-7, and if you have a cleaning tape in the last slot then the first slot is still 0, but the last-slot becomes 6. You are still specing 7 usable slots and the cleaner tape then is in slot 7. How this works in the other changer scripts I don't know. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: exclude list optional not working?
--On Tuesday, July 05, 2005 15:20:15 -0600 Graeme Humphries [EMAIL PROTECTED] wrote: On Tue, 2005-07-05 at 23:14 +0200, Paul Bijnens wrote: - or if the file is not readable: in that case amanda trusts the suid-root runtar executable so that gnutar can read the contents of the file, never mind the permissions. But Amanda does need to verify if the file is there or not, otherwise gnutar will complain about having handed a nonexisting file in the argument list. Ahhh, I see, it just passes off the file to tar if it can be verified as existing. In my case, it can't verify that the file exists or not, so it chokes. Interesting. I wonder how I'll work around that. :) You can do what I do, just ignore the errors from amcheck that you know are bogus. Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
