[no subject]
[EMAIL PROTECTED] /sisges]# amrecover Mensal1 -s server1 -t server1 Added /linux.apps/test1.sh amrecover> extract Extracting files using tape drive /dev/null on host server1. The following tapes are needed: MENSAL01-0503 Restoring files into directory /sisges Continue? [Y/n]: Load tape MENSAL01-0503 now Continue? [Y/n]: EOF, check amidxtaped.debug file. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 -> On /tmp/amanda/amidxtaped. argv[3] = "/dev/null" argv[4] = "server1" argv[5] = "^hdb1$" argv[6] = "20030602" amrestore: missing file header block amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of tape: date trash amidxtaped: amrestore terminarted normally with status: 1 Rewinding tape: done amidxtaped: pid 836 finish time Mon Jun 2 10:22:01 2003
RE: client was working, now suddenly is getting self check "host down?" errors
Once upon a time I did run amdump on the server and canceled it (control-c) as I realized I need to make one last tweak before running it. I hadn't rebooted the client having this problem since then.. I'll try a reboot on the client and see if this happens again. If it does I'll check out the /tmp/amanda debug files etc. Thanks for all the suggestions everyone! I have been assigned some other tasks at work for now but I'll definitely be looking into this issue more when I get a chance. Jeremy
RE: UPDATE - Configuring RH7.2 Amanda out of the box - error accessing Amanda hosts file.
> Well - I bit the bullet and removed amanda and did a > re-install using the > RPM from my RH7.2 disks. > > Doing that I was able to determine that the RH7.2 > configuration expects the > .amandahosts file to be in /var/lib/amanda - I presume that's > why it wasn't > working - can anybody clarify this for me. Hi, I noticed this too with a RedHat 9 install. When installing RedHat if you tell it to install amanda, it creates the amanda account and ets /var/lib/amanda/ as its home directory, it looks like. If you don't install amanda during the RedHat install and install it manually later you'll need to set up a new amanda account which by default uses /home/amanda/ for ~
Re: client was working, now suddenly is getting self check "host down?" errors
On Monday, 02.06.2003 at 10:43 +0100, Martin Hepworth wrote: > >>>Any ideas of why a client would work for a while then randomly not > >>>be able to do a selfchecK? The other amanda client is still working > >>>great... > >> > >>I have a random problem like this as well running RH Linux. The > >>client occasionally fails amcheck in the afternoon. (Backups run at > >>nite.) When I look at portland, the client, I find the selfcheck > >>task "stuck" and I am unable to kill it, even with kill -9. See if > >>you have the same problem. On the client, try > >> > >>ps -ef | grep amand > >> > >>or grep with whatever your amanda user account is. > >> > >>If you see selfcheck running, you'll be unable to get amcheck on the > >>server to finish until it's gone. Just something to check. > > > > > >Interesting to see this problem reported - I've had this happen > >sporadically too. The 'host down' error relates to the localhost and > >it leaves 'selfcheck' and 'amandad' running in the background. The > >server is RH Linux 7.3, running AMANDA 2.4.2p2. > > > >However, killing those processes does not make everything better. > >The problem seems unrelated to the AMANDA configuration. The last > >time it happened here, we were fortunate enough to have a > >'maintenance window' and rebooted the server and after that amcheck > >ran without complaint. However, given that this is a production > >server, rebooting is not a good solution. > > do you use 'localhost' or 'hostname' in the disk list. > > I perfer to use 'hostname' for the reason that if you move the amanda > server to 'someotherhostname' all the tapes etc still reflect the > correct hosts! We use 'localhost' ... :-) > what do the debug logs in /tmp/amanda say when this happens, also > anything else in /var/log/messages indication anything odd at this > time? Nothing obviously helpful - the only difference between a working and non-working copy of the selfcheck and amcheck debugs are the timestamps and process IDs. The amandad debugs show "amandad: dgram_recv: timeout after 10 seconds" a few times followed by a "amandad: waiting for ack: timeout, giving up!" message a little later. As I said this is a Problem That Goes Away By Itself. I was wondering if there was some sort of DNS thing going on, but I couldn't get anywhere with that ... Dave. -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Epidemiology Unit, Oxford Cancer Research UK PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
Re: UPDATE - Configuring RH7.2 Amanda out of the box - error acce ssing Amanda hosts file.
On Mon, Jun 02, 2003 at 12:53:31PM +0100, Kevin Passey enlightened us: > Amanda Backup Client Hosts Check > > ERROR: dilmom: [could not access /dev/sda7 (/dev/sda7): Permission denied] > ERROR: dilmom: [could not access /dev/sda6 (/dev/sda6): Permission denied] > ERROR: dilmom: [could not access /dev/sda8 (/dev/sda8): Permission denied] > ERROR: dilmom: [could not access /dev/sda3 (/dev/sda3): Permission denied] > ERROR: dilmom: [could not access /dev/sda2 (/dev/sda2): Permission denied] > ERROR: dilmom: [could not access /dev/sda1 (/dev/sda1): Permission denied] > Client check: 1 host checked in 3.823 seconds, 6 problems found > Oh redhat, this should mean that /dev/sda* should be owned by root:disk, and chmod 660. Amanda is configured as a memeber of disk, so she should then be able to read the devices. Matt -- Matt Hyclak Department of Mathematics Ohio University (740) 593-1263 pgp0.pgp Description: PGP signature
RE: UPDATE - Configuring RH7.2 Amanda out of the box - error accessing Amanda hosts file.
Well - I bit the bullet and removed amanda and did a re-install using the RPM from my RH7.2 disks. Doing that I was able to determine that the RH7.2 configuration expects the .amandahosts file to be in /var/lib/amanda - I presume that's why it wasn't working - can anybody clarify this for me. Now my problem has moved on - my amcheck looks like this (all my windows shares are now configured) Amanda Tape Server Host Check - Holding disk /usr/amanda/dumps: 16945236 KB disk space available, that's plenty ERROR: /dev/nst0: rewinding tape: No medium found (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /var/lib/amanda/kdp/curinfo: does not exist NOTE: it will be created on the next run Server check took 30.095 seconds Amanda Backup Client Hosts Check ERROR: dilmom: [could not access /dev/sda7 (/dev/sda7): Permission denied] ERROR: dilmom: [could not access /dev/sda6 (/dev/sda6): Permission denied] ERROR: dilmom: [could not access /dev/sda8 (/dev/sda8): Permission denied] ERROR: dilmom: [could not access /dev/sda3 (/dev/sda3): Permission denied] ERROR: dilmom: [could not access /dev/sda2 (/dev/sda2): Permission denied] ERROR: dilmom: [could not access /dev/sda1 (/dev/sda1): Permission denied] Client check: 1 host checked in 3.823 seconds, 6 problems found (brought to you by Amanda 2.4.2p2) The installation notes specify 2.2 section B Set your raw disk devices so that the dumpuser can read themetc.etc Can somebody enlighted a "raw" linux user as to what this means. Thanks to everyone that has replied to this thread. Regards Kevin Passey -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED] Sent: 31 May 2003 09:35 To: Kevin Passey; Amanda (E-mail) Subject: Re: Configuring RH7.2 Amanda out of the box - error accessing Ama nda hosts file. On Saturday 31 May 2003 04:12, Kevin Passey wrote: >I thought that once I sent the mail so I added both it now looks > like > >dilmom.as400resource.com amanda >dilmom amanda > >Still no Joy !! Are the perms 0600, and its owned by amanda? -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% 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.
Virus Found in message "Submited (004756-3463)"
Title: Virus Found in message "Submited (004756-3463)" Norton AntiVirus found a virus in an attachment you ([EMAIL PROTECTED]) sent to Wayne Cochrane. To ensure the recipient(s) are able to use the files you sent, perform a virus scan on your computer, clean any infected files, then resend this attachment. Attachment: movie.pi Virus name: [EMAIL PROTECTED] Action taken: Clean failed : Quarantine succeeded : File status: Infected
Re: Problems to run 'amrecover' - Again
Roberto for the first bit try using the hostname for -s rather than localhost. for the last bit have you put in the correct tape. This is the error 'I' get when I put in the wrong tape for the recovery. -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 Roberto Samarone Araujo (RSA) wrote: Hi, After use the suggestion, it worked but, there are still some problems: I used the line: amrecover Daily1 -s localhost But, some erros occured: 501 No index record for host: server1.mydomain. Invalid? Trying Server1.mydomain ... 501 No index record for host: Server1.mydomain. Invalid? After that, the prompt appeared, I did 'ls' and the 'amrecover' returned me 'Must select a disk before listing file'. After sethost (sethost client1) and setdisk (setdisk hdb1 /usr), I could see the directory tree from the backup. I add a file and tried to extract it but, some errors appeared: Load tape XYZ01 now Continue? [Y/n] EOF, check amdxtaped.debug file on localhost. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue?[Y/n] I Can't recovery the file :///. What's hapenned ? Thanks, Roberto Samarone Araujo > > I've done a backup perfectly but, when I tried to run 'amrecover' from the server or from the clients, I received the messages: Contacting server on localhost ... 200 server1 AMANDA index server (2.4.2p2) ready. 500 Access not allowed: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed. I put on the /root/.amandahosts -> localhost root <- on the server. And -> server1.mydomain backup <- on the clients. I started amrecover on the server using: amrecover Daily1. On the clients I started using: amrecover Daily1 -t server1.mydomain, but the same error occured. What's the problem ? You need 'localhost root' in the .amandahosts in ~backup. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
Problems to run 'amrecover' - Again
Hi, After use the suggestion, it worked but, there are still some problems: I used the line: amrecover Daily1 -s localhost But, some erros occured: 501 No index record for host: server1.mydomain. Invalid? Trying Server1.mydomain ... 501 No index record for host: Server1.mydomain. Invalid? After that, the prompt appeared, I did 'ls' and the 'amrecover' returned me 'Must select a disk before listing file'. After sethost (sethost client1) and setdisk (setdisk hdb1 /usr), I could see the directory tree from the backup. I add a file and tried to extract it but, some errors appeared: Load tape XYZ01 now Continue? [Y/n] EOF, check amdxtaped.debug file on localhost. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue?[Y/n] I Can't recovery the file :///. What's hapenned ? Thanks, Roberto Samarone Araujo > > > > > I've done a backup perfectly but, when I tried to run > 'amrecover' > > > from the server or from the clients, I received the messages: > > > > > > Contacting server on localhost ... > > >200 server1 AMANDA index server (2.4.2p2) ready. > > >500 Access not allowed: [access as backup not allowed > > > from [EMAIL PROTECTED] amandahostsauth failed. > > > > > >I put on the /root/.amandahosts -> localhost root <- on the > > > server. And -> server1.mydomain backup <- on the clients. I started > > > amrecover on the server using: amrecover Daily1. On the clients I > started > > > using: amrecover Daily1 -t server1.mydomain, but the same error occured. > > > What's the problem ? > > > > You need 'localhost root' in the .amandahosts in ~backup. > > > > -- > > Joshua Baker-LePain > > Department of Biomedical Engineering > > Duke University
Re: client was working, now suddenly is getting self check "hostdown?" errors
Dave Ewart wrote: On Friday, 30.05.2003 at 15:04 -0400, Ron Bauman wrote: Any ideas of why a client would work for a while then randomly not be able to do a selfchecK? The other amanda client is still working great... I have a random problem like this as well running RH Linux. The client occasionally fails amcheck in the afternoon. (Backups run at nite.) When I look at portland, the client, I find the selfcheck task "stuck" and I am unable to kill it, even with kill -9. See if you have the same problem. On the client, try ps -ef | grep amand or grep with whatever your amanda user account is. If you see selfcheck running, you'll be unable to get amcheck on the server to finish until it's gone. Just something to check. Interesting to see this problem reported - I've had this happen sporadically too. The 'host down' error relates to the localhost and it leaves 'selfcheck' and 'amandad' running in the background. The server is RH Linux 7.3, running AMANDA 2.4.2p2. However, killing those processes does not make everything better. The problem seems unrelated to the AMANDA configuration. The last time it happened here, we were fortunate enough to have a 'maintenance window' and rebooted the server and after that amcheck ran without complaint. However, given that this is a production server, rebooting is not a good solution. Dave. Dave do you use 'localhost' or 'hostname' in the disk list. I perfer to use 'hostname' for the reason that if you move the amanda server to 'someotherhostname' all the tapes etc still reflect the correct hosts! what do the debug logs in /tmp/amanda say when this happens, also anything else in /var/log/messages indication anything odd at this time? -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
Re: client was working, now suddenly is getting self check "hostdown?" errors
On Friday, 30.05.2003 at 15:04 -0400, Ron Bauman wrote: I have a random problem like this as well running RH Linux. The client occasionally fails amcheck in the afternoon. (Backups run at nite.) When I look at portland, the client, I find the selfcheck task "stuck" and I am unable to kill it, even with kill -9. Kill -9 not working is usually a symptom of a kernel bug, or a hardware failure (usually related to a difficult to solve kernel bug that the kernel cannot respond properly to malfunctioning hardware). I've also noticed it when using "hard" NFS mounts, but I can't reproduce it when I wanted to investigate it. I've had gtar hanging and unkilleable on Solaris 2.6 sporadically more than a year ago. I installed some patches since then, but don't know if any patch cured such a problem, or if I'm just lucky. -- 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: client was working, now suddenly is getting self check "host down?" errors
On Friday, 30.05.2003 at 15:04 -0400, Ron Bauman wrote: > > Any ideas of why a client would work for a while then randomly not > > be able to do a selfchecK? The other amanda client is still working > > great... > > I have a random problem like this as well running RH Linux. The > client occasionally fails amcheck in the afternoon. (Backups run at > nite.) When I look at portland, the client, I find the selfcheck task > "stuck" and I am unable to kill it, even with kill -9. See if you > have the same problem. On the client, try > > ps -ef | grep amand > > or grep with whatever your amanda user account is. > > If you see selfcheck running, you'll be unable to get amcheck on the > server to finish until it's gone. Just something to check. Interesting to see this problem reported - I've had this happen sporadically too. The 'host down' error relates to the localhost and it leaves 'selfcheck' and 'amandad' running in the background. The server is RH Linux 7.3, running AMANDA 2.4.2p2. However, killing those processes does not make everything better. The problem seems unrelated to the AMANDA configuration. The last time it happened here, we were fortunate enough to have a 'maintenance window' and rebooted the server and after that amcheck ran without complaint. However, given that this is a production server, rebooting is not a good solution. Dave. -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Epidemiology Unit, Oxford Cancer Research UK PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
Re: Configuring RH7.2 Amanda out of the box - error accessing Amanda hosts file.
Jon LaBadie wrote: On Sat, May 31, 2003 at 12:14:08PM +0200, Wojciech Jedliczka wrote: I always RTFM many times. Inside all docs files in amanda distribution is no place giving suggestion about .amandahosts permissions. Amandahosts file is used for authorization and therefore it is important who owns these file and who has access to read and write. From the security point of view is better to has 600 than 660 but both are acceptable for me. In this case the guidelines are based on the BSD authentication scheme using the .rhosts file as a model. Remberance of either usage or past documentation would make me say 600 is the proper permissions as the programs specifically ignored a file even readable by group or other. However I don't see that on the manpage for rhosts on my system now. A similar file, .netrc does have those requirements (listed on the manpage too) but that has nothing to do with amanda. The man page "ruserok" on Linux does mention the strict permissions, but the Solaris man page does not. And indeed, a quick test revealed that even mode 666 on .rhosts makes no difference on Solaris or SunOS 4.1.4, but does invoke a password prompt on Linux. I surely remember struggling with the permissions of .rhosts when running HP/UX 7 and SunOS 4.1.2 (or was that still longer ago?). And indeed, nothing in the source code of Amanda 2.4.4 checks for too wide permissions of .amandahosts. You can learn something new every day :-) -- 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 * ***
confused
Hi I'm confused: In amanda.conf the bandwidth is in bps (Bits Per Second) or Bps (Bytes Per Second)? I'm asking this because before the remark it's written bps (which stands for bits per second), but in the remark it's written KB (which stands for Kilo Byte). Paolo
