Re: Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148
Hello Jean-Louis, Am Mittwoch, den 04.06.2008, 09:34 -0400 schrieb Jean-Louis Martineau: > A bug in amstatus should not prevent your backup to run correctly. > Changing amdump.1 can't help to start a backup run (amdump). > Your backup should run correctly even if amstatus crash. > > Can you send me a copy of the bogus amdump.1 file? I would like to look > at it. I have to check if I can do this. Amanda is running on a customer server I administer so I have to check the file for any critical customer information before I can send it to you. > Which locale are you using? At the moment I don't have access to the system. Tomorrow I send the status of the amanda run I started today after the little change on the amdump.1 file. So more information tomorrow. Thanks, Dominik
Re: Amanda 2.5.0 spanning
In 2.5.0, it write a message to /dev/tty, if you start the command from an interactive shell, you should see a message, if you run it from cron, then the message is lost. Newer version allow to send an email message. Jean-Louis Johan Booysen wrote: Hi, I've now gotten as far as getting Amanda to think the tape drive has 2 slots (I believe)...well at least I can do an amcheck successfully... One question: When amdump runs and fills up the first tape, what should I expect to see? Does Amanda simply eject the first tape and just waits until the second tape is inserted? Does it give any sort of indication that it's time to insert the second tape? Just a little confused over that issue. Thanks very much. -Original Message- From: Jean-Louis Martineau [mailto:[EMAIL PROTECTED] Sent: 30 May 2008 12:56 To: Johan Booysen Cc: Amanda user's group Subject: Re: Amanda 2.5.0 spanning Johan Booysen wrote: Well, there wasn't any email report because it was waiting for the job to finish... I eventually manually killed the job, but the email report only says: *** THE DUMPS DID NOT FINISH PROPERLY! These dumps were to tape daily-3. The next 2 tapes Amanda expects to use are: a new tape, a new tape. The next 2 new tapes already labelled are: daily-4, daily-5 It tell me the tapes should have been accepted. I'm not surprise there is nothing in the log, the taper log the error when it find a tape, but you killed it before. You can change the "lastslot=99" to "lastslot=3" in the chg-manual scripts. That way, the taper will exit after you feed 3 tapes and it will log error messages. Jean-Louis
RE: Amanda 2.5.0 spanning
Ah, ok - but this would only apply to version 2.6, like Jean-Louis said? I'm using the 2.5.0 RHEL5 version of Amanda. We tend to stick to installing "official" Red Hat packages... I'm running a test amdump, so will see what happens. Thanks very much for the replies. Johan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dustin J. Mitchell Sent: 04 June 2008 16:28 To: Johan Booysen Cc: Amanda user's group Subject: Re: Amanda 2.5.0 spanning On Wed, Jun 4, 2008 at 11:04 AM, Johan Booysen <[EMAIL PROTECTED]> wrote: > One question: That's *three* questions ;) > When amdump runs and fills up the first tape, what should I expect to > see? > Does Amanda simply eject the first tape and just waits until the second > tape is inserted? > Does it give any sort of indication that it's time to insert the second > tape? But they do have a single answer: it depends on the changer you're using. From previous emails in the thread, you don't have a changer, so you should be using chg-manual. Here are the comments from the header of that file: # # Changer config file (changerfile) # # resend_mail=900 # 15 minutes # timeout_mail=604800 # 7 days # request="tty" # Use the tty to ask the user to change tape. # # Can't be use by cron # request="email" # Send an email to ask the user to change tape. # request="tty_email" # Use the tty if it exist or send an email. # #Default is "tty_email" # mtx_binary="/path/to/mtx" # path of 'mtx'; default is value discovered by # # configure So you probably want request="email". The other defaults should probably be fine. That way, when Amanda needs a new tape, it will send you an email. You then take the previous tape out of the drive, stick in a new one, and Amanda picks right up where it left off. VOLUNTEER OPPORTUNITY: The changer documentation on the wiki could use some help. If you use chg-manual, head over to http://wiki.zmanda.com/index.php/Changers and make it better! Dustin -- Storage Software Engineer http://www.zmanda.com
Re: Amanda 2.5.0 spanning
On Wed, Jun 4, 2008 at 11:04 AM, Johan Booysen <[EMAIL PROTECTED]> wrote: > One question: That's *three* questions ;) > When amdump runs and fills up the first tape, what should I expect to > see? > Does Amanda simply eject the first tape and just waits until the second > tape is inserted? > Does it give any sort of indication that it's time to insert the second > tape? But they do have a single answer: it depends on the changer you're using. From previous emails in the thread, you don't have a changer, so you should be using chg-manual. Here are the comments from the header of that file: # # Changer config file (changerfile) # # resend_mail=900 # 15 minutes # timeout_mail=604800 # 7 days # request="tty" # Use the tty to ask the user to change tape. # # Can't be use by cron # request="email" # Send an email to ask the user to change tape. # request="tty_email" # Use the tty if it exist or send an email. # #Default is "tty_email" # mtx_binary="/path/to/mtx" # path of 'mtx'; default is value discovered by # # configure So you probably want request="email". The other defaults should probably be fine. That way, when Amanda needs a new tape, it will send you an email. You then take the previous tape out of the drive, stick in a new one, and Amanda picks right up where it left off. VOLUNTEER OPPORTUNITY: The changer documentation on the wiki could use some help. If you use chg-manual, head over to http://wiki.zmanda.com/index.php/Changers and make it better! Dustin -- Storage Software Engineer http://www.zmanda.com
RE: Amanda 2.5.0 spanning
Hi, I've now gotten as far as getting Amanda to think the tape drive has 2 slots (I believe)...well at least I can do an amcheck successfully... One question: When amdump runs and fills up the first tape, what should I expect to see? Does Amanda simply eject the first tape and just waits until the second tape is inserted? Does it give any sort of indication that it's time to insert the second tape? Just a little confused over that issue. Thanks very much. -Original Message- From: Jean-Louis Martineau [mailto:[EMAIL PROTECTED] Sent: 30 May 2008 12:56 To: Johan Booysen Cc: Amanda user's group Subject: Re: Amanda 2.5.0 spanning Johan Booysen wrote: > Well, there wasn't any email report because it was waiting for the job > to finish... > > I eventually manually killed the job, but the email report only says: > > *** THE DUMPS DID NOT FINISH PROPERLY! > > These dumps were to tape daily-3. > The next 2 tapes Amanda expects to use are: a new tape, a new tape. > The next 2 new tapes already labelled are: daily-4, daily-5 It tell me the tapes should have been accepted. I'm not surprise there is nothing in the log, the taper log the error when it find a tape, but you killed it before. You can change the "lastslot=99" to "lastslot=3" in the chg-manual scripts. That way, the taper will exit after you feed 3 tapes and it will log error messages. Jean-Louis
Re: Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148
A bug in amstatus should not prevent your backup to run correctly. Changing amdump.1 can't help to start a backup run (amdump). Your backup should run correctly even if amstatus crash. Can you send me a copy of the bogus amdump.1 file? I would like to look at it. Which locale are you using? Jean-Louis Dominik Schips wrote: Hello, since Saturday (2008-05-31) my ananda backup didn't run. A closer look when I run the command /usr/sbin/amstatus DailyFull get me this output: Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148 using /var/lib/amanda/DailyFull/log/amdump.1 from Sa Mai 21 15:30:08 CEST I coudn't find any errors or someting else in the logs. Because I didn't know what went wrong I had to fake (change) the date in /var/lib/amanda/DailyFull/log/amdump.1 from 31 to 30... Know the backup starts and I hope that it finish correct without problem. The question is what can cause this error "Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148"? I use Amanda 2.4.4p3 from Debian sarge. I know it's old, but there wasn't time to make a update to Etch. This is on my todo within the nex 4 weeks. Best regards, Dominik
Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148
Hello, since Saturday (2008-05-31) my ananda backup didn't run. A closer look when I run the command /usr/sbin/amstatus DailyFull get me this output: Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148 using /var/lib/amanda/DailyFull/log/amdump.1 from Sa Mai 21 15:30:08 CEST I coudn't find any errors or someting else in the logs. Because I didn't know what went wrong I had to fake (change) the date in /var/lib/amanda/DailyFull/log/amdump.1 from 31 to 30... Know the backup starts and I hope that it finish correct without problem. The question is what can cause this error "Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148"? I use Amanda 2.4.4p3 from Debian sarge. I know it's old, but there wasn't time to make a update to Etch. This is on my todo within the nex 4 weeks. Best regards, Dominik
