amrecover via ssh: client using amanda user instead of amandabackup
I'm attempting an amrecover on a Fedora 8 client (amanda-client-2.5.2p1-8.fc8), with a Fedora Core 6 tape-server (amanda-backup_server-2.5.1p3-1.fc6). I've done all the mucking around with ssh keys as described here: http://www.amanda.org/docs/howto-auth.html The error is: [EMAIL PROTECTED] ~]# amrecover daily Permission denied (publickey,gssapi-with-mic,password). AMRECOVER Version 2.5.2p1. Contacting server on tape-server ... [request failed: EOF on read from tape-server] [EMAIL PROTECTED] ~]# It looks like amrecover on the client is attempting to connect to the server as 'amanda' instead of 'amandabackup'. From the tape-server's /var/log/secure: Feb 22 22:42:43 tape-server sshd[4780]: input_userauth_request: invalid user amanda How do I tell amrecover to connect as amandabackup instead of amanda?
Re: Best Amanda Setup for Restores
On Friday 22 February 2008, Gordon J. Mills III wrote: > I am beginning to question my sanity here . I am using the amrecover > interface to recover it but it seems that it will first extract the entire > tar'd up dle to /tmp/Amanda before extracting the small folder that I > requested. Am I wrong about that? > If this is the case (and it seems to be what I have experienced) then my > problem is that the entire tar'd up dle will not fit on the partition which > contains /tmp/Amanda/. So to get at this particular folder for this restore > I need to change that default to another drive which does have enough free > space. > I'll let others answer the question of whether there is a way of changing this default, but I can recommend a simple solution -- make /tmp/amanda a link to a directory on some other disk that has enough space. -- -- Jeffrey Anderson| [EMAIL PROTECTED] Lawrence Berkeley National Laboratory | Office: 50A-5104E | Mailstop 50A-5101 Phone: 510 486-4208 | Fax: 510 486-6808
RE: Best Amanda Setup for Restores
I guess I am doing something wrong here. I would like to find out what it is. In /tmp/amanda, amrecover creates a file named server.domain.name._.20080114.0.0002048. That file is 55G when I delete it. I have to delete it because at that point the disk is full. This is a backup of the / folder and it is compressed. The folder that is selected for extraction is 4.3G. I have used the lcd command to select the folder where it want the restore to be put. The client and the server are the same machine in this scenario. The amrecover.*.debug file is 2.5M. I will send it to you if that will help. The amrecover session all goes fine. I run it. Select the disk, date, folder that I want, etc. run the extract. Where can I get the complete output of the session? Thanks, -Gordon -Original Message- From: Jean-Louis Martineau [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 3:32 PM To: [EMAIL PROTECTED] Cc: amanda-users@amanda.org Subject: Re: Best Amanda Setup for Restores amrecover only write to disk the files you asked for extraction. amrecover extract in the current directory when we executed amrecover (not on /tmp/Amanda), you can use the lcd command to change the cwd. Can you post the complete output of the amrecover session and the complete amrecover.*.debug file. Jean-Louis Gordon J. Mills III wrote: >> Is this simply a case of not realizing that 'amrestore' is generally used >> for complete dle restoration while 'amrecover' is used for individual >> file/directory recovery? >> > > I am beginning to question my sanity here . I am using the amrecover > interface to recover it but it seems that it will first extract the entire > tar'd up dle to /tmp/Amanda before extracting the small folder that I > requested. Am I wrong about that? > If this is the case (and it seems to be what I have experienced) then my > problem is that the entire tar'd up dle will not fit on the partition which > contains /tmp/Amanda/. So to get at this particular folder for this restore > I need to change that default to another drive which does have enough free > space. > > To further clarify, I am running Debian and using the packages in the debian > archive for Amanda. I am using vtapes also. > > Thanks for the help, > Gordon > > >
RE: Best Amanda Setup for Restores
>Let me assure, AFAIK Amanda does not do that. >How did you come to that conclusion? >What is the name of the file that is created in "/tmp/Amanda" (uppercase >A in the name???) The A is lowercase. My mail client put the uppercase. The file is server.domain.name._.20080114.0.0002048. It is 55G when I am forced to delete it because the disk is full. Scratching head now. -Gordon > If this is the case (and it seems to be what I have experienced) then my > problem is that the entire tar'd up dle will not fit on the partition which > contains /tmp/Amanda/. So to get at this particular folder for this restore > I need to change that default to another drive which does have enough free > space. > > To further clarify, I am running Debian and using the packages in the debian > archive for Amanda. I am using vtapes also. -- Paul Bijnens, xplanation Technology ServicesTel +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: Best Amanda Setup for Restores
amrecover only write to disk the files you asked for extraction. amrecover extract in the current directory when we executed amrecover (not on /tmp/Amanda), you can use the lcd command to change the cwd. Can you post the complete output of the amrecover session and the complete amrecover.*.debug file. Jean-Louis Gordon J. Mills III wrote: Is this simply a case of not realizing that 'amrestore' is generally used for complete dle restoration while 'amrecover' is used for individual file/directory recovery? I am beginning to question my sanity here . I am using the amrecover interface to recover it but it seems that it will first extract the entire tar'd up dle to /tmp/Amanda before extracting the small folder that I requested. Am I wrong about that? If this is the case (and it seems to be what I have experienced) then my problem is that the entire tar'd up dle will not fit on the partition which contains /tmp/Amanda/. So to get at this particular folder for this restore I need to change that default to another drive which does have enough free space. To further clarify, I am running Debian and using the packages in the debian archive for Amanda. I am using vtapes also. Thanks for the help, Gordon
Re: Best Amanda Setup for Restores
On Fri, Feb 22, 2008 at 01:17:26PM -0500, Jon LaBadie wrote: > On Fri, Feb 22, 2008 at 11:48:02AM -0600, Gordon J. Mills III wrote: > > I have recently run into a problem with restoring. I want to restore a > > folder on a DLE that is about 100G. The folder I want to restore is small > > but apparently Amanda has to restore the entire DLE to get at the 1 folder. > > It is restoring the large file to /tmp/Amanda/. Unfortunately, I do not have > > enough room there to extract the entire DLE. > > > > My first question is: How can I have Amanda use a different path for this > > task. I have an NFS mounted external drive that has much more room on it. > > > > 2nd question: Is there a way to setup Amanda so that it does not have to > > retrieve the entire DLE file? Is it just removing compression from the DLE > > def? Or chopping up the DLE to smaller chunks (this will be hard since most > > of the data is in 1 place on that dle). > > > > I would like for Amanda to behave in a similar way that I have had other > > backup software behave. That is, if I just want a single file or folder, > > then it scans the tape (in this case vtapes) and retrieves only what I want. > > When I have successfully retrieved files with Amanda before it took a very > > long time. Is there a way to set it up so that it will do this? > > > > Is this simply a case of not realizing that 'amrestore' is generally used > for complete dle restoration while 'amrecover' is used for individual > file/directory recovery? We never really configured amrecover and use amrestore for everything. Typically the command sequence looks like this # cd /amanda/restore (on the amanda work partition) # amrestore -p /dev/rmt/0n host /partition | restore -if - . -p for pipe the amrestore -i for interactive, I can walk down the directory structure. Similar method exists for tar "dump" type. My milage varies, yours will too. Depending on the OS, dumptype (ufsrestore and xfsrestore take somewhat different syntax and I'm certain linux restores, or MAC OS X, are in the near future since we do have amanda clients of those types ), and there are some cross platform restores that are trickier, Solaris amanda host and IRIX amanda client, but its all doable without having to bring back complete and large DLEs. > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 12027 Creekbend Drive(703) 787-0884 > Reston, VA 20194(703) 787-0922 (fax) --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: Best Amanda Setup for Restores
Gordon J. Mills III wrote: Is this simply a case of not realizing that 'amrestore' is generally used for complete dle restoration while 'amrecover' is used for individual file/directory recovery? I am beginning to question my sanity here . I am using the amrecover interface to recover it but it seems that it will first extract the entire tar'd up dle to /tmp/Amanda before extracting the small folder that I requested. Am I wrong about that? Let me assure, AFAIK Amanda does not do that. How did you come to that conclusion? What is the name of the file that is created in "/tmp/Amanda" (uppercase A in the name???) If this is the case (and it seems to be what I have experienced) then my problem is that the entire tar'd up dle will not fit on the partition which contains /tmp/Amanda/. So to get at this particular folder for this restore I need to change that default to another drive which does have enough free space. To further clarify, I am running Debian and using the packages in the debian archive for Amanda. I am using vtapes also. -- Paul Bijnens, xplanation Technology ServicesTel +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: Best Amanda Setup for Restores
>Is this simply a case of not realizing that 'amrestore' is generally used >for complete dle restoration while 'amrecover' is used for individual >file/directory recovery? I am beginning to question my sanity here . I am using the amrecover interface to recover it but it seems that it will first extract the entire tar'd up dle to /tmp/Amanda before extracting the small folder that I requested. Am I wrong about that? If this is the case (and it seems to be what I have experienced) then my problem is that the entire tar'd up dle will not fit on the partition which contains /tmp/Amanda/. So to get at this particular folder for this restore I need to change that default to another drive which does have enough free space. To further clarify, I am running Debian and using the packages in the debian archive for Amanda. I am using vtapes also. Thanks for the help, Gordon
Re: Best Amanda Setup for Restores
Dustin J. Mitchell wrote: On Fri, Feb 22, 2008 at 12:48 PM, Gordon J. Mills III <[EMAIL PROTECTED]> wrote: My first question is: How can I have Amanda use a different path for this task. I have an NFS mounted external drive that has much more room on it. If you're using amrecover, you should 'cd' into the directory into which you want to recover your files before starting amrecover. For safety, you should always start amrecover on an empty directory. Amrecover can erase files from the working directory. Jean-Louis
RE: Best Amanda Setup for Restores
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dustin J. Mitchell Sent: Friday, February 22, 2008 12:24 PM >Are you using amrestore or amrecover? Amrecover will only actually >write the files you have requested to disk, although your observation >that it reads the entire dump from tape is correct. Dustin, thanks for the response. I am using amrecover but it will extract the entire dle first. Is there a way I can redirect it to use a different directory for this so that I can extract this 100G dle? After that I will try to break it up. >> My first question is: How can I have Amanda use a different path for this >> task. I have an NFS mounted external drive that has much more room on it. >If you're using amrecover, you should 'cd' into the directory into >which you want to recover your files before starting amrecover. This is not really what I'm asking. Apparently Amanda has a default to restore the dle into /tmp/Amanda before actually extracting what you requested. I did cd to the proper directory first, but this is irrelevant here. I need to be able to change the location that it restores the dle (before doing the actual restore) because the drive that /tmp is on is not large enough to handle it. >Currently, that's the only solution -- smaller DLEs. That is a bummer. >Not yet, but that is a major aim of the Application API and transfer >architecture, which are under active development. For a hint as to >how complex this is, see >http://wiki.zmanda.com/index.php/User:Dustin/Data_Handling_Model. >There's no specific ETA on this development at the moment. Thanks for the link. I looked at it but I think most of it is beyond my understanding of things here. Gordon
Re: Best Amanda Setup for Restores
On Fri, Feb 22, 2008 at 11:48:02AM -0600, Gordon J. Mills III wrote: > I have recently run into a problem with restoring. I want to restore a > folder on a DLE that is about 100G. The folder I want to restore is small > but apparently Amanda has to restore the entire DLE to get at the 1 folder. > It is restoring the large file to /tmp/Amanda/. Unfortunately, I do not have > enough room there to extract the entire DLE. > > My first question is: How can I have Amanda use a different path for this > task. I have an NFS mounted external drive that has much more room on it. > > 2nd question: Is there a way to setup Amanda so that it does not have to > retrieve the entire DLE file? Is it just removing compression from the DLE > def? Or chopping up the DLE to smaller chunks (this will be hard since most > of the data is in 1 place on that dle). > > I would like for Amanda to behave in a similar way that I have had other > backup software behave. That is, if I just want a single file or folder, > then it scans the tape (in this case vtapes) and retrieves only what I want. > When I have successfully retrieved files with Amanda before it took a very > long time. Is there a way to set it up so that it will do this? > Is this simply a case of not realizing that 'amrestore' is generally used for complete dle restoration while 'amrecover' is used for individual file/directory recovery? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Need access to raw mailing list archives
Hey, folks! It's W. Curtis Preston, the author of Backup & Recovery and the webmaster of www.backupcentral.com. I'd like to add the Amanda-users list to the backup software mailing lists that I support on BackupCentral.com. I added the NetWorker, NetBackup, and TSM lists a year ago with great success, and I'd like to do the same for popular open source packages like Amanda. One of the things I do when I add a list is to import its archives into the forum engine for searchability. In order to do this, I need access to a raw version of the archives, not an HTML version such as is currently available to me for this list. Can anyone help me get this? Thanks in advance. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies
Re: Best Amanda Setup for Restores
On Fri, Feb 22, 2008 at 12:48 PM, Gordon J. Mills III <[EMAIL PROTECTED]> wrote: > I have recently run into a problem with restoring. I want to restore a > folder on a DLE that is about 100G. The folder I want to restore is small > but apparently Amanda has to restore the entire DLE to get at the 1 folder. > It is restoring the large file to /tmp/Amanda/. Unfortunately, I do not have > enough room there to extract the entire DLE. Are you using amrestore or amrecover? Amrecover will only actually write the files you have requested to disk, although your observation that it reads the entire dump from tape is correct. > My first question is: How can I have Amanda use a different path for this > task. I have an NFS mounted external drive that has much more room on it. If you're using amrecover, you should 'cd' into the directory into which you want to recover your files before starting amrecover. > 2nd question: Is there a way to setup Amanda so that it does not have to > retrieve the entire DLE file? Is it just removing compression from the DLE > def? Or chopping up the DLE to smaller chunks (this will be hard since most > of the data is in 1 place on that dle). Currently, that's the only solution -- smaller DLEs. > I would like for Amanda to behave in a similar way that I have had other > backup software behave. That is, if I just want a single file or folder, > then it scans the tape (in this case vtapes) and retrieves only what I want. > When I have successfully retrieved files with Amanda before it took a very > long time. Is there a way to set it up so that it will do this? Not yet, but that is a major aim of the Application API and transfer architecture, which are under active development. For a hint as to how complex this is, see http://wiki.zmanda.com/index.php/User:Dustin/Data_Handling_Model. There's no specific ETA on this development at the moment. Dustin -- Storage Software Engineer http://www.zmanda.com
Best Amanda Setup for Restores
I have recently run into a problem with restoring. I want to restore a folder on a DLE that is about 100G. The folder I want to restore is small but apparently Amanda has to restore the entire DLE to get at the 1 folder. It is restoring the large file to /tmp/Amanda/. Unfortunately, I do not have enough room there to extract the entire DLE. My first question is: How can I have Amanda use a different path for this task. I have an NFS mounted external drive that has much more room on it. 2nd question: Is there a way to setup Amanda so that it does not have to retrieve the entire DLE file? Is it just removing compression from the DLE def? Or chopping up the DLE to smaller chunks (this will be hard since most of the data is in 1 place on that dle). I would like for Amanda to behave in a similar way that I have had other backup software behave. That is, if I just want a single file or folder, then it scans the tape (in this case vtapes) and retrieves only what I want. When I have successfully retrieved files with Amanda before it took a very long time. Is there a way to set it up so that it will do this? Thanks for the help. Regards, Gordon
Re: Amanda failed.
* Jon LaBadie <[EMAIL PROTECTED]> [20080222 11:56]: > On Fri, Feb 22, 2008 at 09:24:33AM -0500, McGraw, Robert P wrote: > > > > OS: Solaris 10 SPARC > > AMANDA Version: 2.5.2P1 > > > > Last night my Soalris 10 sparc host Amanda failed with the following errors > > > > zorn /export/users-z lev 0 FAILED > > [/local/Amanda/amanda-2.5.2p1/libexec/runtar exited with status 1: see > > /tmp/amanda/client/daily/sendsize.20080221182142.debug] > > > > A section of the /tmp/amanda/client/daily/sendsize.20080221182142.debug] > > > > sendsize[13188]: time 23.002: estimate size for /export/users-a level 0: -1 > > KB [...] > > sendsize: time 23.915: pid 13196 finish time Thu Feb 21 18:22:06 2008 > > sendsize[13188]: time 23.999: sendsize: error [exec > > /local/Amanda/amanda-2.5.2p1/libexec/runtar: Permission denied] > > > > > > It seemed that everything with SUID that tried to run last night has > > permission denied. > > > > Here is an ls of the SUID files. > > > > -rwsr-x--- 1 root operator 23744 Jun 7 2007 calcsize* > > -rwsr-x--- 1 root operator 65820 Jun 7 2007 dumper* > > -rwsr-x--- 1 root operator 13524 Jun 7 2007 killpgrp* > > -rwsr-x--- 1 root operator 93424 Jun 7 2007 planner* > > -rwsr-x--- 1 root operator 11352 Jun 7 2007 rundump* > > -rwsr-x--- 1 root operator 14472 Jun 7 2007 runtar* > > > > The seem to be correct and have not been changed since Jun 7. > > > > All the other clients ran without problems. > > > > Any ideas on the cause or was this just a cosmic ray hitting my computer > > before the backup? > > They are not world executable. So the process executing them > must either be root or in the operator group. Might something > have caused a change in the identity of your executing backup > processes? Or your group memberships? Another thing to check: *if* the client is accessing those amanda suid execs through NFS, then the NFS server must not squash root on the client. Check how the server exports /local and how it is mounted on the client... jf > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 12027 Creekbend Drive(703) 787-0884 > Reston, VA 20194(703) 787-0922 (fax) -- <° ><
Re: Amanda failed.
On Fri, Feb 22, 2008 at 09:24:33AM -0500, McGraw, Robert P wrote: > > OS: Solaris 10 SPARC > AMANDA Version: 2.5.2P1 > > Last night my Soalris 10 sparc host Amanda failed with the following errors > > zorn /export/users-z lev 0 FAILED > [/local/Amanda/amanda-2.5.2p1/libexec/runtar exited with status 1: see > /tmp/amanda/client/daily/sendsize.20080221182142.debug] > > A section of the /tmp/amanda/client/daily/sendsize.20080221182142.debug] > > sendsize[13188]: time 23.002: estimate size for /export/users-a level 0: -1 > KB > sendsize[13188]: time 23.002: waiting for runtar "/export/users-a" child > sendsize[13188]: time 23.002: after runtar /export/users-a wait > errmsg is /local/Amanda/amanda-2.5.2p1/libexec/runtar exited with status 1: > see /tmp/amanda/client/daily/sendsize.20080221182142.debug > sendsize[13188]: time 23.003: getting size via gnutar for /export/users-a > level 4 > sendsize[13110]: time 23.038: getting size via dump for /export/varmail > level 2 > sendsize[13110]: time 23.042: calculating for device /dev/rdsk/c3t102d3s6 > with ufs > sendsize[13110]: time 23.042: running "/usr/sbin/ufsdump 2Ssf 1048576 - > /dev/rdsk/c3t102d3s6" > sendsize[13110]: time 23.171: running > /local/Amanda/amanda-2.5.2p1/libexec/killpgrp > sendsize[13110]: time 23.172: cannot execute > /local/Amanda/amanda-2.5.2p1/libexec/killpgrp: Permission denied > sendsize[13188]: time 23.908: spawning > /local/Amanda/amanda-2.5.2p1/libexec/runtar in pipeline > sendsize[13188]: time 23.908: argument list: runtar daily /opt/csw/bin/gtar > --create --file /dev/null --directory /export/fssnap/users --one-file-system > --listed-incremental /var/am > anda/gnutar-lists/zorn_export_users-a_4.new --sparse --ignore-failed-read > --totals --files-from > /tmp/amanda/sendsize._export_users-a.20080221182205.include > sendsize[13188]: time 23.915: error [exec > /local/Amanda/amanda-2.5.2p1/libexec/runtar: Permission denied] > sendsize: time 23.915: pid 13196 finish time Thu Feb 21 18:22:06 2008 > sendsize[13188]: time 23.999: sendsize: error [exec > /local/Amanda/amanda-2.5.2p1/libexec/runtar: Permission denied] > > > It seemed that everything with SUID that tried to run last night has > permission denied. > > Here is an ls of the SUID files. > > -rwsr-x--- 1 root operator 23744 Jun 7 2007 calcsize* > -rwsr-x--- 1 root operator 65820 Jun 7 2007 dumper* > -rwsr-x--- 1 root operator 13524 Jun 7 2007 killpgrp* > -rwsr-x--- 1 root operator 93424 Jun 7 2007 planner* > -rwsr-x--- 1 root operator 11352 Jun 7 2007 rundump* > -rwsr-x--- 1 root operator 14472 Jun 7 2007 runtar* > > The seem to be correct and have not been changed since Jun 7. > > All the other clients ran without problems. > > Any ideas on the cause or was this just a cosmic ray hitting my computer > before the backup? They are not world executable. So the process executing them must either be root or in the operator group. Might something have caused a change in the identity of your executing backup processes? Or your group memberships? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Amanda failed.
OS: Solaris 10 SPARC AMANDA Version: 2.5.2P1 Last night my Soalris 10 sparc host Amanda failed with the following errors zorn /export/users-z lev 0 FAILED [/local/Amanda/amanda-2.5.2p1/libexec/runtar exited with status 1: see /tmp/amanda/client/daily/sendsize.20080221182142.debug] A section of the /tmp/amanda/client/daily/sendsize.20080221182142.debug] sendsize[13188]: time 23.002: estimate size for /export/users-a level 0: -1 KB sendsize[13188]: time 23.002: waiting for runtar "/export/users-a" child sendsize[13188]: time 23.002: after runtar /export/users-a wait errmsg is /local/Amanda/amanda-2.5.2p1/libexec/runtar exited with status 1: see /tmp/amanda/client/daily/sendsize.20080221182142.debug sendsize[13188]: time 23.003: getting size via gnutar for /export/users-a level 4 sendsize[13110]: time 23.038: getting size via dump for /export/varmail level 2 sendsize[13110]: time 23.042: calculating for device /dev/rdsk/c3t102d3s6 with ufs sendsize[13110]: time 23.042: running "/usr/sbin/ufsdump 2Ssf 1048576 - /dev/rdsk/c3t102d3s6" sendsize[13110]: time 23.171: running /local/Amanda/amanda-2.5.2p1/libexec/killpgrp sendsize[13110]: time 23.172: cannot execute /local/Amanda/amanda-2.5.2p1/libexec/killpgrp: Permission denied sendsize[13188]: time 23.908: spawning /local/Amanda/amanda-2.5.2p1/libexec/runtar in pipeline sendsize[13188]: time 23.908: argument list: runtar daily /opt/csw/bin/gtar --create --file /dev/null --directory /export/fssnap/users --one-file-system --listed-incremental /var/am anda/gnutar-lists/zorn_export_users-a_4.new --sparse --ignore-failed-read --totals --files-from /tmp/amanda/sendsize._export_users-a.20080221182205.include sendsize[13188]: time 23.915: error [exec /local/Amanda/amanda-2.5.2p1/libexec/runtar: Permission denied] sendsize: time 23.915: pid 13196 finish time Thu Feb 21 18:22:06 2008 sendsize[13188]: time 23.999: sendsize: error [exec /local/Amanda/amanda-2.5.2p1/libexec/runtar: Permission denied] It seemed that everything with SUID that tried to run last night has permission denied. Here is an ls of the SUID files. -rwsr-x--- 1 root operator 23744 Jun 7 2007 calcsize* -rwsr-x--- 1 root operator 65820 Jun 7 2007 dumper* -rwsr-x--- 1 root operator 13524 Jun 7 2007 killpgrp* -rwsr-x--- 1 root operator 93424 Jun 7 2007 planner* -rwsr-x--- 1 root operator 11352 Jun 7 2007 rundump* -rwsr-x--- 1 root operator 14472 Jun 7 2007 runtar* The seem to be correct and have not been changed since Jun 7. All the other clients ran without problems. Any ideas on the cause or was this just a cosmic ray hitting my computer before the backup? I will just wait for tonight's backup to see if it happens again but just wanted to see if some saw a problem from the logs. Thanks Robert _ Robert P. McGraw, Jr. Manager, Computer SystemEMAIL: [EMAIL PROTECTED] Purdue UniversityROOM: MATH-807 Department of Mathematics PHONE: (765) 494-6055 150 N. University Street West Lafayette, IN 47907-2067 smime.p7s Description: S/MIME cryptographic signature
