Re: amrecover fails in rel 2.5.1 with NAK: amindexd: invalid service

[Frank Smith]

David Trusty wrote:
> Hi,
> 
> I just installed release 2.5.1 on a SUSE 10.1 machine.  I was able
> to do a backup fine, but when I try to run amrecover, I get this error:
> 
> # amrecover Monthly
> AMRECOVER Version 2.5.1. Contacting server on localhost ...
> NAK: amindexd: invalid service

Do you have the amindexd service configured in (x)inetd?
Does it show up in a 'netstat -l' ?

> The amcheck command shows no errors.

amcheck only checks to see if backups would work, not restores,
so it won't tell you if index or tape services are available.

> 
> Any ideas?

See above.  Also, not related to your current problem, you
should look in the list archives for threads on how using
'localhost' in your disklist can cause problems later on.

Frank

> 
> Thanks,
> 
> David
> 
> 


-- 
Frank Smith  [EMAIL PROTECTED]
Sr. Systems Administrator   Voice: 512-374-4673
Hoover's Online   Fax: 512-374-4501

RE: amrecover fails in rel 2.5.1 with NAK: amindexd: invalid service

[kevin . till]

David Trusty <[EMAIL PROTECTED]> said:
> I just installed release 2.5.1 on a SUSE 10.1 machine.  I was able
> to do a backup fine, but when I try to run amrecover, I get this error:
> 
> # amrecover Monthly
> AMRECOVER Version 2.5.1. Contacting server on localhost ...
> NAK: amindexd: invalid service
> 
> The amcheck command shows no errors.
> 
> Any ideas?

In Amanda 2.5.1, amrecover uses Security API. Changes to xinetd configuration 
is required. Please see the following wiki page for detail:

http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication

amrecover fails in rel 2.5.1 with NAK: amindexd: invalid service

[David Trusty]

Hi,

I just installed release 2.5.1 on a SUSE 10.1 machine.  I was able
to do a backup fine, but when I try to run amrecover, I get this error:

# amrecover Monthly
AMRECOVER Version 2.5.1. Contacting server on localhost ...
NAK: amindexd: invalid service

The amcheck command shows no errors.

Any ideas?

Thanks,

David

Small update on testgtar

[Olivier Nicole]

Hi,

I did a very minor change on testgtar (the small script that tests
gnutar exclude list) to remove an error when checking for broken
version of tar.

testgtar is being referenced at
http://wiki.zmanda.com/index.php/Exclude_and_include_lists

Bests,

Olivier

Re: amrecover 2.5.1

[Jean-Francois Malouin]

* Jean-Louis Martineau <[EMAIL PROTECTED]> [20060921 14:33]:
> Hi,
> 
> Irix doesn't have the same return value for vsnprintf as linux have.
> Could you try this patch.

Thanks Jean-Louis.
I've applied the patch, recompiled and started a amrecover session.
It seems to work but the restore hasn't completed yet.
But I can see the history of the DLEs etc...

I will confirm that it works when amrecover completes
(should take an hour or so).

jf

> 
> Jean-Louis
> 
> Jean-Francois Malouin wrote:
> >* Jean-Louis Martineau <[EMAIL PROTECTED]> [20060921 13:04]:
> >  
> >>Jean-Francois,
> >>
> >>Could you send the amrecover..debug and 
> >>amindexd..debug files?
> >>
> >
> >here they come attached.
> >jf
> >
> >  
> >>Jean-Louis
> >>
> >>Jean-Francois Malouin wrote:
> >>
> >>>Hello,
> >>>
> >>>amanda-2.5.1 on irix-6.5.x using bsdtcp auth
> >>>amrecover don't want to play ball:
> >>>
> >>>yorick 130# /opt/amanda/amanda10/sbin/amrecover
> >>>AMRECOVER Version 2.5.1. Contacting server on yorick ...
> >>>220 
> >>>Setting restore date to today (2006-09-21)
> >>>200 
> >>>Scanning /holddisk/conf10/stk_180...
> >>>200 
> >>>200 
> >>>Use the setdisk command to choose dump disk to recover
> >>>amrecover> setdate 2006-09-20
> >>>200 
> >>>amrecover> setdisk /data/nihpd/nihpd3/backup
> >>>200 
> >>>bad reply: missing date field
> >>>oc!È
> >>>amrecover> ls
> >>>amrecover> pwd
> >>>/data/nihpd/nihpd3/backup
> >>>mrecover> listhost
> >>>200-
> >>>201-
> >>>200 
> >>>amrecover> listdisk
> >>>200-
> >>>201-
> >>>[ large numbers of 201- lines ]
> >>>200 
> >>>amrecover> add .
> >>>File . doesn't exist in directory
> >>>
> >>>
> >>>Now I'm nervous!
> >>>jf
> >>> 
> >>>  
> 

> diff -u -r --show-c-function --exclude-from=amanda.diff 
> amanda-2.5.1.new/common-src/packet.c 
> amanda-2.5.1.new.amindexd/common-src/packet.c
> --- amanda-2.5.1.new/common-src/packet.c  2006-05-25 06:44:35.0 
> -0400
> +++ amanda-2.5.1.new.amindexd/common-src/packet.c 2006-09-21 
> 14:26:08.0 -0400
> @@ -54,6 +54,7 @@ printf_arglist_function2(void pkt_init, 
>  const char *, fmt)
>  {
>  va_list  argp;
> +int len;
>  
>  assert(pkt != NULL);
>  assert(strcmp(pkt_type2str(type), "BOGUS") != 0);
> @@ -62,14 +63,16 @@ printf_arglist_function2(void pkt_init, 
>  pkt->type = type;
>  pkt->packet_size = 1000;
>  pkt->body = alloc(pkt->packet_size);
> -arglist_start(argp, fmt);
> -while (vsnprintf(pkt->body, pkt->packet_size, fmt, argp) >=
> - (int)(pkt->packet_size - 1)) {
> +while(1) {
> + arglist_start(argp, fmt);
> + len = vsnprintf(pkt->body, pkt->packet_size, fmt, argp);
> + arglist_end(argp);
> + if (len < (int)(pkt->packet_size - 1))
> + break;
>   pkt->packet_size *= 2;
>   amfree(pkt->body);
>   pkt->body = alloc(pkt->packet_size);
>  }
> -arglist_end(argp);
>  pkt->size = strlen(pkt->body);
>  }
>  
> @@ -79,6 +82,7 @@ printf_arglist_function2(void pkt_init, 
>  printf_arglist_function1(void pkt_cat, pkt_t *, pkt, const char *, fmt)
>  {
>  size_t   len;
> +int lenX;
>  va_list  argp;
>  char *   pktbody;
>  
> @@ -87,19 +91,19 @@ printf_arglist_function1(void pkt_cat, p
>  
>  len = strlen(pkt->body);
>  
> -arglist_start(argp, fmt);
> -while (vsnprintf(pkt->body + len, pkt->packet_size - len, fmt,argp) >=
> - (int)(pkt->packet_size - len - 1)) {
> +while(1) {
> + arglist_start(argp, fmt);
> +lenX = vsnprintf(pkt->body + len, pkt->packet_size - len, fmt,argp);
> + arglist_end(argp);
> + if (lenX < (int)(pkt->packet_size - len - 1))
> + break;
>   pkt->packet_size *= 2;
>   pktbody = alloc(pkt->packet_size);
>   strncpy(pktbody, pkt->body, len);
>   pktbody[len] = '\0';
>   amfree(pkt->body);
>   pkt->body = pktbody;
> - arglist_end(argp);
> - arglist_start(argp, fmt);
>  }
> -arglist_end(argp);

Re: amrecover 2.5.1

[Jean-Louis Martineau]

Hi,

Irix doesn't have the same return value for vsnprintf as linux have.
Could you try this patch.

Jean-Louis

Jean-Francois Malouin wrote:

* Jean-Louis Martineau <[EMAIL PROTECTED]> [20060921 13:04]:
  

Jean-Francois,

Could you send the amrecover..debug and 
amindexd..debug files?



here they come attached.
jf

  

Jean-Louis

Jean-Francois Malouin wrote:


Hello,

amanda-2.5.1 on irix-6.5.x using bsdtcp auth
amrecover don't want to play ball:

yorick 130# /opt/amanda/amanda10/sbin/amrecover
AMRECOVER Version 2.5.1. Contacting server on yorick ...
220 
Setting restore date to today (2006-09-21)
200 
Scanning /holddisk/conf10/stk_180...
200 
200 
Use the setdisk command to choose dump disk to recover

amrecover> setdate 2006-09-20
200 
amrecover> setdisk /data/nihpd/nihpd3/backup
200 
bad reply: missing date field

oc!È
amrecover> ls
amrecover> pwd
/data/nihpd/nihpd3/backup
mrecover> listhost
200-
201-
200 
amrecover> listdisk

200-
201-
[ large numbers of 201- lines ]
200 
amrecover> add .

File . doesn't exist in directory


Now I'm nervous!
jf
 
  


diff -u -r --show-c-function --exclude-from=amanda.diff 
amanda-2.5.1.new/common-src/packet.c 
amanda-2.5.1.new.amindexd/common-src/packet.c
--- amanda-2.5.1.new/common-src/packet.c2006-05-25 06:44:35.0 
-0400
+++ amanda-2.5.1.new.amindexd/common-src/packet.c   2006-09-21 
14:26:08.0 -0400
@@ -54,6 +54,7 @@ printf_arglist_function2(void pkt_init, 
 const char *, fmt)
 {
 va_listargp;
+int len;
 
 assert(pkt != NULL);
 assert(strcmp(pkt_type2str(type), "BOGUS") != 0);
@@ -62,14 +63,16 @@ printf_arglist_function2(void pkt_init, 
 pkt->type = type;
 pkt->packet_size = 1000;
 pkt->body = alloc(pkt->packet_size);
-arglist_start(argp, fmt);
-while (vsnprintf(pkt->body, pkt->packet_size, fmt, argp) >=
-   (int)(pkt->packet_size - 1)) {
+while(1) {
+   arglist_start(argp, fmt);
+   len = vsnprintf(pkt->body, pkt->packet_size, fmt, argp);
+   arglist_end(argp);
+   if (len < (int)(pkt->packet_size - 1))
+   break;
pkt->packet_size *= 2;
amfree(pkt->body);
pkt->body = alloc(pkt->packet_size);
 }
-arglist_end(argp);
 pkt->size = strlen(pkt->body);
 }
 
@@ -79,6 +82,7 @@ printf_arglist_function2(void pkt_init, 
 printf_arglist_function1(void pkt_cat, pkt_t *, pkt, const char *, fmt)
 {
 size_t len;
+int lenX;
 va_listargp;
 char * pktbody;
 
@@ -87,19 +91,19 @@ printf_arglist_function1(void pkt_cat, p
 
 len = strlen(pkt->body);
 
-arglist_start(argp, fmt);
-while (vsnprintf(pkt->body + len, pkt->packet_size - len, fmt,argp) >=
-   (int)(pkt->packet_size - len - 1)) {
+while(1) {
+   arglist_start(argp, fmt);
+lenX = vsnprintf(pkt->body + len, pkt->packet_size - len, fmt,argp);
+   arglist_end(argp);
+   if (lenX < (int)(pkt->packet_size - len - 1))
+   break;
pkt->packet_size *= 2;
pktbody = alloc(pkt->packet_size);
strncpy(pktbody, pkt->body, len);
pktbody[len] = '\0';
amfree(pkt->body);
pkt->body = pktbody;
-   arglist_end(argp);
-   arglist_start(argp, fmt);
 }
-arglist_end(argp);
 pkt->size = strlen(pkt->body);
 }
 
diff -u -r --show-c-function --exclude-from=amanda.diff 
amanda-2.5.1.new/server-src/amindexd.c 
amanda-2.5.1.new.amindexd/server-src/amindexd.c
--- amanda-2.5.1.new/server-src/amindexd.c  2006-07-25 14:27:57.0 
-0400
+++ amanda-2.5.1.new.amindexd/server-src/amindexd.c 2006-09-21 
13:47:19.0 -0400
@@ -295,7 +295,7 @@ printf_arglist_function1(static void rep
len = vsnprintf(reply_buffer, reply_buffer_size, fmt, args);
arglist_end(args);
 
-   if (len > -1 && (size_t)len < reply_buffer_size)
+   if (len > -1 && (size_t)len < reply_buffer_size-1)
break;
 
reply_buffer_size *= 2;
@@ -334,7 +334,7 @@ printf_arglist_function1(static void lre
len = vsnprintf(reply_buffer, reply_buffer_size, fmt, args);
arglist_end(args);
 
-   if (len > -1 && (size_t)len < reply_buffer_size)
+   if (len > -1 && (size_t)len < reply_buffer_size-1)
break;
 
reply_buffer_size *= 2;
@@ -375,7 +375,7 @@ printf_arglist_function1(static void fas
len = vsnprintf(reply_buffer, reply_buffer_size, fmt, args);
arglist_end(args);
 
-   if (len > -1 && (size_t)len < reply_buffer_size)
+   if (len > -1 && (size_t)len < reply_buffer_size-1)
break;
 
reply_buffer_size *= 2;
diff -u -r --show-c-function --exclude-from=amanda.diff 
amanda-2.5.1.new/server-src

Re: amrecover 2.5.1

[Jean-Francois Malouin]

* Jean-Louis Martineau <[EMAIL PROTECTED]> [20060921 13:04]:
> Jean-Francois,
> 
> Could you send the amrecover..debug and 
> amindexd..debug files?

here they come attached.
jf

> 
> Jean-Louis
> 
> Jean-Francois Malouin wrote:
> >Hello,
> >
> >amanda-2.5.1 on irix-6.5.x using bsdtcp auth
> >amrecover don't want to play ball:
> >
> >yorick 130# /opt/amanda/amanda10/sbin/amrecover
> >AMRECOVER Version 2.5.1. Contacting server on yorick ...
> >220 
> >Setting restore date to today (2006-09-21)
> >200 
> >Scanning /holddisk/conf10/stk_180...
> >200 
> >200 
> >Use the setdisk command to choose dump disk to recover
> >amrecover> setdate 2006-09-20
> >200 
> >amrecover> setdisk /data/nihpd/nihpd3/backup
> >200 
> >bad reply: missing date field
> >oc!È
> >amrecover> ls
> >amrecover> pwd
> >/data/nihpd/nihpd3/backup
> >mrecover> listhost
> >200-
> >201-
> >200 
> >amrecover> listdisk
> >200-
> >201-
> >[ large numbers of 201- lines ]
> >200 
> >amrecover> add .
> >File . doesn't exist in directory
> >
> >
> >Now I'm nervous!
> >jf
> >  

-- 
<° ><
amrecover: debug 1 pid 5906786 ruid 0 euid 0: start at Thu Sep 21 12:21:38 2006
Could not open conf file "/opt/amanda/amanda10/etc/amanda/amanda-client.conf": 
No such file or directory
Reading conf file 
"/opt/amanda/amanda10/etc/amanda/stk_180-conf10/amanda-client.conf".
amrecover: debug 1 pid 5906786 ruid 0 euid 0: rename at Thu Sep 21 12:21:38 2006
security_getdriver(name=bsdtcp) returns 5ffb4ea8
security_handleinit(handle=10032b20, driver=5ffb4ea8 (BSDTCP))
security_streaminit(stream=1003e058, driver=5ffb4ea8 (BSDTCP))
amrecover: connect_port: Skip port 512: Owned by exec.
amrecover: connect_port: Skip port 513: Owned by login.
amrecover: connect_port: Skip port 514: Owned by shell.
amrecover: connect_port: Skip port 515: Owned by printer.
amrecover: connect_port: Try  port 516: Available   - amrecover: connected to 
132.206.178.10.10116
amrecover: our side is 0.0.0.0.516
amrecover: try_socksize: send buffer size is 65536
amrecover: try_socksize: receive buffer size is 65536
security_streaminit(stream=10046098, driver=5ffb4ea8 (BSDTCP))
security_close(handle=10032b20, driver=5ffb4ea8 (BSDTCP))
security_stream_close(1003e058)
add_glob (.) -> ^\.$
add_file: Looking for "\.[/]*$"
add_file: Converted path="\.[/]*$" to path_on_disk="/\.[/]*$"
add_file: (Failed) File . doesn't exist in directory
add_glob (.) -> ^\.$
add_file: Looking for "\.[/]*$"
add_file: Converted path="\.[/]*$" to path_on_disk="/\.[/]*$"
add_file: (Failed) File . doesn't exist in directory
security_stream_close(10046098)
amrecover: pid 5906786 finish time Thu Sep 21 12:25:20 2006
amindexd: debug 1 pid 5033716 ruid 666 euid 666: start at Thu Sep 21 12:21:38 
2006
amindexd: version 2.5.1
amindexd: < 220 
amindexd: > FEATURES feff9ffeff7f
amindexd: < 200 
amindexd: > DATE 2006-09-21
amindexd: < 200 
amindexd: > SCNF stk_180-conf10
amindexd: debug 1 pid 5033716 ruid 666 euid 666: rename at Thu Sep 21 12:21:38 
2006
amindexd: < 200 
amindexd: > HOST yorick
amindexd: < 200 
amindexd: > DATE 2006-09-20
amindexd: < 200 
amindexd: > DISK /data/nihpd/nihpd3/backup
append_to_tapelist(tapelist=0, label='stk_180-conf10-12', , file=1, 
isafile=0)
dump_tapelist(1001f100):
  1001f100->next = 0
  1001f100->label= stk_180-conf10-12
  1001f100->isafile  = 0
  1001f100->numfiles = 1
  1001f100->files[0] = 1
  1001f100 count = 1
amindexd: - 2006-09-20 1 stk_180-conf10-12 1 -1
append_to_tapelist(tapelist=0, label='stk_180-conf10-3', , file=24, 
isafile=0)
dump_tapelist(10051db8):
  10051db8->next = 0
  10051db8->label= stk_180-conf10-3
  10051db8->isafile  = 0
  10051db8->numfiles = 1
  10051db8->files[0] = 24
  10051db8 count = 1
amindexd: - 2006-09-19 1 stk_180-conf10-3 24 -1
append_to_tapelist(tapelist=0, label='stk_180-conf10-2', , file=8, 
isafile=0)
dump_tapelist(10051df8):
  10051df8->next = 0
  10051df8->label= stk_180-conf10-2
  10051df8->isafile  = 0
  10051df8->numfiles = 1
  10051df8->files[0] = 8
  10051df8 count = 1
amindexd: - 2006-09-18 0 stk_180-conf10-2 8 -1
amindexd: < 200 
amindexd: > OISD /
amindexd: uncompress command: /usr/sbin/gzip -dc 
'/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/index/yorick/_data_nihpd_nihpd3_backup/20060920_1.gz'
 2>/dev/null | (LC_ALL=C; export LC_ALL ; sort)  > 
'/opt/amanda/amanda10/usr/adm/amanda/stk_180-conf10/index/yorick/_data_nihpd_nihpd3_bac

Re: amrecover 2.5.1

[Jean-Louis Martineau]

Jean-Francois,

Could you send the amrecover..debug and 
amindexd..debug files?


Jean-Louis

Jean-Francois Malouin wrote:

Hello,

amanda-2.5.1 on irix-6.5.x using bsdtcp auth
amrecover don't want to play ball:

yorick 130# /opt/amanda/amanda10/sbin/amrecover
AMRECOVER Version 2.5.1. Contacting server on yorick ...
220 
Setting restore date to today (2006-09-21)
200 
Scanning /holddisk/conf10/stk_180...
200 
200 
Use the setdisk command to choose dump disk to recover

amrecover> setdate 2006-09-20
200 
amrecover> setdisk /data/nihpd/nihpd3/backup
200 
bad reply: missing date field

oc!È
amrecover> ls
amrecover> pwd
/data/nihpd/nihpd3/backup
mrecover> listhost
200-
201-
200 
amrecover> listdisk

200-
201-
[ large numbers of 201- lines ]
200 
amrecover> add .

File . doesn't exist in directory


Now I'm nervous!
jf
  

amrecover 2.5.1

[Jean-Francois Malouin]

Hello,

amanda-2.5.1 on irix-6.5.x using bsdtcp auth
amrecover don't want to play ball:

yorick 130# /opt/amanda/amanda10/sbin/amrecover
AMRECOVER Version 2.5.1. Contacting server on yorick ...
220 
Setting restore date to today (2006-09-21)
200 
Scanning /holddisk/conf10/stk_180...
200 
200 
Use the setdisk command to choose dump disk to recover
amrecover> setdate 2006-09-20
200 
amrecover> setdisk /data/nihpd/nihpd3/backup
200 
bad reply: missing date field
oc!È
amrecover> ls
amrecover> pwd
/data/nihpd/nihpd3/backup
mrecover> listhost
200-
201-
200 
amrecover> listdisk
200-
201-
[ large numbers of 201- lines ]
200 
amrecover> add .
File . doesn't exist in directory


Now I'm nervous!
jf

Re: WARNING: got empty schedule from planner

[Thomas Ginestet]

What is the estimate time report by the sendsize log ?
Your timeout is maybe too shorttry to play with the etimeout in 
amanda.conf.


Did your change any rule from your firewall  ?
Have a look at http://wiki.zmanda.com/index.php/Amdump:_results_missing

Hope it will help you.

Thomas

Tim Butler a écrit :

Does everyone know why I receive this error during a dump?
 
START driver date 20060920

DISK planner ascm01 /sqlbackup
DISK planner ascm01 /P4ROOT
DISK planner ascm01 /asp
START planner date 20060920
START taper datestamp 20060920 label Daily19 tape 0
FAIL planner ascm01 /asp 20060920 0 [Estimate timeout from ascm01]
FAIL planner ascm01 /P4ROOT 20060920 0 [Estimate timeout from ascm01]
FAIL planner ascm01 /sqlbackup 20060920 0 [Estimate timeout from ascm01]
FINISH planner date 20060920
WARNING driver WARNING: got empty schedule from planner
STATS driver startup time 5402.179
INFO taper tape Daily19 kb 0 fm 0 [OK]
FINISH driver date 20060920 time 5404.178
 
 
These dumps were to tape Daily19.

The next tape Amanda expects to use is: Daily04.
 
FAILURE AND STRANGE DUMP SUMMARY:

  ascm01 /asp lev 0 FAILED [Estimate timeout from ascm01]
  ascm01 /P4ROOT lev 0 FAILED [Estimate timeout from ascm01]
  ascm01 /sqlbackup lev 0 FAILED [Estimate timeout from ascm01]

STATISTICS:
  Total   Full  Daily
      
Estimate Time (hrs:min)1:30
Run Time (hrs:min) 1:30
Dump Time (hrs:min)0:00   0:00   0:00
Output Size (meg)   0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0  0  0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00   0:00   0:00
Tape Size (meg) 0.00.00.0
Tape Used (%)   0.00.00.0
Filesystems Taped 0  0  0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
  Label Time  Size  %Nb
  Daily19   0:00   0.00.0 0

NOTES:
  driver: WARNING: got empty schedule from planner
  taper: tape Daily19 kb 0 fm 0 [OK]

DUMP SUMMARY:
 DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
-- - 
ascm01   /P4ROOT 0 FAILED ---
ascm01   /asp0 FAILED ---
ascm01   /sqlbackup  0 FAILED ---
(brought to you by Amanda version 2.4.4p3)

Re: Release of amanda-2.5.1

[Gene Heskett]

On Thursday 21 September 2006 10:21, Geert Uytterhoeven wrote:
>On Thu, 21 Sep 2006, Gene Heskett wrote:
>> On Thursday 21 September 2006 05:09, Geert Uytterhoeven wrote:
>> >On Wed, 20 Sep 2006, Paul Bijnens wrote:
>> >> On 2006-09-20 11:56, Geert Uytterhoeven wrote:
>> >> > On Mon, 11 Sep 2006, Geert Uytterhoeven wrote:
>> >> > > On Sat, 9 Sep 2006, Josef Wolf wrote:
>> >> > > > On Tue, Sep 05, 2006 at 03:34:42PM -0400, Jean-Louis Martineau
>>
>> wrote:
>> >> > > > >* Works with GNU tar 1.15.91 - work with new gtar state
>> >> > > > > file format.
>> >> > > >
>> >> > > > Can someone please explain what this exactly means?
>> >> > >
>> >> > > The format to store information about the incrementals was
>> >> > > changed. Since Amanda made some assumptions about this format
>> >> > > (while she shouldn't have cared,
>> >> > > and just considered it as opaque files), this broke Amanda.
>> >> > > After the fix, Amanda just treats the files as opaque files.
>> >> > >
>> >> > > But be careful, at least the tar 1.15.91-2 from Debian is
>> >> > > broken: it ignores
>> >> > > the --one-file-system option when doing incrementals, causing
>> >> > > exorbitant backup
>> >> > > sizes for any level > 0. I don't know about the upstream
>> >> > > version, but since
>> >> > > this bug has been reported almost 2 months ago, I'm afraid that
>> >> > > one is broken,
>> >> > > too.
>> >> >
>> >> > Apparently the problem is more subtle. Thanks to the Debian bug
>> >> > tracking system, I noticed this:
>> >> >
>> >> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384508
>> >> > tar: -l option changed meaning, without any warning!
>> >>
>> >> OK. But AFAIK (grep *.c in the sources), Amanda does NOT use the
>> >> -l option, but only the --one-file-system option, since a very long
>> >> time already.
>> >>
>> >> So I think this option name change has nothing to do with the
>> >> use of gnutar by Amanda.  (AFAIK the format of the incremental-state
>> >> files has changed, and Amanda assumed they were in some
>> >> line-oriented format instead of handling it as opaque objects.)
>> >
>> >Indeed, thanks for reminding me! I just send a clarification to the
>> > Debian BTS: - 384508 is about -l no longer meaning --one-file-system
>> >  - 377124 is about --one-file-system breaking when combined with
>> >--listed-incremental (Amanda does pass --one-file-system (not -l)
>> > to tar)
>>
>> And how does this breakage manifest itself again?  Is it by not
>> following and counting out-of-filesystem links in the estimate phase,
>> but including them during the backup?  This would of course result in
>> "small estimate" notations.
>
>I noticed 2 things when doing non-level-zero backups:
>  1. Warnings about weird files in /proc, while tar shouldn't have
> entered /proc as it's a different file system

I see,  and I'd never see that as I don't have a dle for /, I'm all broken 
down into subdirs of / 
here, /etc, /bin/home/root, /home/gene, /usr/src, /opt, yadda yadda.

>  2. Backups being way too large, as tar escaped from the file system it
> was backing up.

The obvious result if its broken.

>Gr{oetje,eeting}s,
>
>  Geert
>
>--
>Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> [EMAIL PROTECTED]
>
>In personal conversations with technical people, I call myself a hacker.
> But when I'm talking to journalists I just say "programmer" or something
> like that. -- Linus Torvalds

-- 
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)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

Re: Release of amanda-2.5.1

[Geert Uytterhoeven]

On Thu, 21 Sep 2006, Gene Heskett wrote:
> On Thursday 21 September 2006 05:09, Geert Uytterhoeven wrote:
> >On Wed, 20 Sep 2006, Paul Bijnens wrote:
> >> On 2006-09-20 11:56, Geert Uytterhoeven wrote:
> >> > On Mon, 11 Sep 2006, Geert Uytterhoeven wrote:
> >> > > On Sat, 9 Sep 2006, Josef Wolf wrote:
> >> > > > On Tue, Sep 05, 2006 at 03:34:42PM -0400, Jean-Louis Martineau 
> wrote:
> >> > > > >* Works with GNU tar 1.15.91 - work with new gtar state file
> >> > > > > format.
> >> > > >
> >> > > > Can someone please explain what this exactly means?
> >> > >
> >> > > The format to store information about the incrementals was changed.
> >> > > Since Amanda made some assumptions about this format (while she
> >> > > shouldn't have cared,
> >> > > and just considered it as opaque files), this broke Amanda.
> >> > > After the fix, Amanda just treats the files as opaque files.
> >> > >
> >> > > But be careful, at least the tar 1.15.91-2 from Debian is broken:
> >> > > it ignores
> >> > > the --one-file-system option when doing incrementals, causing
> >> > > exorbitant backup
> >> > > sizes for any level > 0. I don't know about the upstream version,
> >> > > but since
> >> > > this bug has been reported almost 2 months ago, I'm afraid that one
> >> > > is broken,
> >> > > too.
> >> >
> >> > Apparently the problem is more subtle. Thanks to the Debian bug
> >> > tracking system, I noticed this:
> >> >
> >> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384508
> >> > tar: -l option changed meaning, without any warning!
> >>
> >> OK. But AFAIK (grep *.c in the sources), Amanda does NOT use the
> >> -l option, but only the --one-file-system option, since a very long
> >> time already.
> >>
> >> So I think this option name change has nothing to do with the
> >> use of gnutar by Amanda.  (AFAIK the format of the incremental-state
> >> files has changed, and Amanda assumed they were in some line-oriented
> >> format instead of handling it as opaque objects.)
> >
> >Indeed, thanks for reminding me! I just send a clarification to the
> > Debian BTS: - 384508 is about -l no longer meaning --one-file-system
> >  - 377124 is about --one-file-system breaking when combined with
> >--listed-incremental (Amanda does pass --one-file-system (not -l) to
> >tar)
> >
> And how does this breakage manifest itself again?  Is it by not following 
> and counting out-of-filesystem links in the estimate phase, but including 
> them during the backup?  This would of course result in "small estimate" 
> notations.

I noticed 2 things when doing non-level-zero backups:
  1. Warnings about weird files in /proc, while tar shouldn't have entered
 /proc as it's a different file system
  2. Backups being way too large, as tar escaped from the file system it was
 backing up.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

Re: Release of amanda-2.5.1

[Gene Heskett]

On Thursday 21 September 2006 05:09, Geert Uytterhoeven wrote:
>On Wed, 20 Sep 2006, Paul Bijnens wrote:
>> On 2006-09-20 11:56, Geert Uytterhoeven wrote:
>> > On Mon, 11 Sep 2006, Geert Uytterhoeven wrote:
>> > > On Sat, 9 Sep 2006, Josef Wolf wrote:
>> > > > On Tue, Sep 05, 2006 at 03:34:42PM -0400, Jean-Louis Martineau 
wrote:
>> > > > >* Works with GNU tar 1.15.91 - work with new gtar state file
>> > > > > format.
>> > > >
>> > > > Can someone please explain what this exactly means?
>> > >
>> > > The format to store information about the incrementals was changed.
>> > > Since Amanda made some assumptions about this format (while she
>> > > shouldn't have cared,
>> > > and just considered it as opaque files), this broke Amanda.
>> > > After the fix, Amanda just treats the files as opaque files.
>> > >
>> > > But be careful, at least the tar 1.15.91-2 from Debian is broken:
>> > > it ignores
>> > > the --one-file-system option when doing incrementals, causing
>> > > exorbitant backup
>> > > sizes for any level > 0. I don't know about the upstream version,
>> > > but since
>> > > this bug has been reported almost 2 months ago, I'm afraid that one
>> > > is broken,
>> > > too.
>> >
>> > Apparently the problem is more subtle. Thanks to the Debian bug
>> > tracking system, I noticed this:
>> >
>> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384508
>> > tar: -l option changed meaning, without any warning!
>>
>> OK. But AFAIK (grep *.c in the sources), Amanda does NOT use the
>> -l option, but only the --one-file-system option, since a very long
>> time already.
>>
>> So I think this option name change has nothing to do with the
>> use of gnutar by Amanda.  (AFAIK the format of the incremental-state
>> files has changed, and Amanda assumed they were in some line-oriented
>> format instead of handling it as opaque objects.)
>
>Indeed, thanks for reminding me! I just send a clarification to the
> Debian BTS: - 384508 is about -l no longer meaning --one-file-system
>  - 377124 is about --one-file-system breaking when combined with
>--listed-incremental (Amanda does pass --one-file-system (not -l) to
>tar)
>
And how does this breakage manifest itself again?  Is it by not following 
and counting out-of-filesystem links in the estimate phase, but including 
them during the backup?  This would of course result in "small estimate" 
notations.

But here, with one or two exceptions usually caused by me, the errors have 
generally been under the 10 meg range.  But they combined one night a week 
or so ago, to leave 1.5GB of data in the holding disk.  I have 45 DLE's in 
an attempt to help amanda achieve balance easier, all but 2 or 3 in the 1 
GB size range.  That same night, it promoted several level 0's from 3 days 
ahead, which I thought was a bit odd.

Since I was about to fill the disk, I added another day to dumpcycle and 
runspercycle a week ago, but true balance is still elusive.

[EMAIL PROTECTED] root]# su amanda -c "amadmin Daily balance"

 due-date  #fsorig MB out MB   balance
--
 9/21 Thu   13 8926 5433 +4.0%
 9/22 Fri5 5404 4727 -9.5%
 9/23 Sat   21 6306 3489-33.2%
 9/24 Sun6 10284 4659-10.8%
 9/25 Mon4 13862 7824+49.7%
--
TOTAL   49 44782 26132 5226
DISTINCT45 41182 24820
  (estimated 5 runs per dumpcycle)
 (2 filesystems overdue, the most being overdue 1 day)

No idea if this is good, or suboptimal.

>Gr{oetje,eeting}s,
>
>  Geert
>
>--
>Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> [EMAIL PROTECTED]
>
>In personal conversations with technical people, I call myself a hacker.
> But when I'm talking to journalists I just say "programmer" or something
> like that. -- Linus Torvalds

-- 
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)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

RE: Release of amanda-2.5.1

[Geert Uytterhoeven]

On Thu, 21 Sep 2006, McGraw, Robert P. wrote:
> I am running gnu tar 1.15.1 on my solaris hosts and it does not show a "-l"
> parameter. I did tar --help | grep "\-l".
> 
> >From the --help I have the following:
> 
>   --check-links  print a message if not all links are dumped
> 
> On a RH X86_64 system I have gnu tar 1.14 and it shows 
> 
> -l, --one-file-systemstay in local file system when creating archive

`-l' wasn't recycled before 1.15.91, according to the changelog.

On a Debian testing box:

| tux$ tar --version
| tar (GNU tar) 1.15.91
| Copyright (C) 2006 Free Software Foundation, Inc.
| This is free software.  You may redistribute copies of it under the terms of
| the GNU General Public License .
| There is NO WARRANTY, to the extent permitted by law.
| 
| Written by John Gilmore and Jay Fenlason.
| tux$ tar --help | grep -- -l
|   -t, --list list the contents of an archive
|   --test-label   test the archive volume label and exit
|   -g, --listed-incremental=FILE   handle new GNU-format incremental backup
|  --diff, --extract or --list and when a list of
|   --force-local  archive file is local even if it has a colon
|   -L, --tape-length=NUMBER   change tape after writing NUMBER x 1024 bytes
|   -V, --label=TEXT   create archive with volume name TEXT; at
|   -l, --check-links  print a message if not all links are dumped
| tux$

> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > On Behalf Of Charles Stroom
> > Sent: Wednesday, September 20, 2006 12:25 PM
> > To: amanda-users@amanda.org
> > Subject: Re: Release of amanda-2.5.1
> > 
> > 
> > on  Wed, 20 Sep 2006 10:33:15 EDT
> > Gene Heskett <[EMAIL PROTECTED]> wrote:
> > >
> > > On Wednesday 20 September 2006 05:56, Geert Uytterhoeven wrote:
> > > >On Mon, 11 Sep 2006, Geert Uytterhoeven wrote:
> > > >>
> > > >> But be careful, at least the tar 1.15.91-2 from Debian is broken: it
> > > >> ignores the --one-file-system option when doing incrementals, causing
> > > >> exorbitant backup sizes for any level > 0. I don't know about the
> > > >> upstream version, but since this bug has been reported almost 2
> > months
> > > >> ago, I'm afraid that one is broken, too.
> > > >
> > > >Apparently the problem is more subtle. Thanks to the Debian bug
> > tracking
> > > >system, I noticed this:
> > > >
> > > >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384508
> > > >tar: -l option changed meaning, without any warning!
> > > >
> > > >Gr{oetje,eeting}s,
> > > >
> > > >  Geert
> > > >
> > > Good Grief Charley Brown!
> > >
> > > Tar is supposed to be a stable, mature utility is it not?  I mean its
> > what,
> > > 30 years old, existing in the various *nix's long before gnu took over?
> > > Whyinhell can't the folks over at gnu.org find something else to screw
> > > with besides tar?  It doesn't _need_ to be on their WPA or CCC lists as
> > a
> > > makework project when there's nothing else to do around the office.
> > >
> > 
> > On my Suse 10.0 system:
> > 
> > (2): cs> tar --version
> > tar (GNU tar) 1.15.1
> > (0): cs> tar -l dum dum
> > tar: Semantics of -l option will change in the future releases.
> > tar: Please use --one-file-system option instead.
> > 
> > So, at least there were warnings (not really an excuse I think)

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

RE: Release of amanda-2.5.1

[McGraw, Robert P.]

FYIW

I am running gnu tar 1.15.1 on my solaris hosts and it does not show a "-l"
parameter. I did tar --help | grep "\-l".

>From the --help I have the following:

  --check-links  print a message if not all links are dumped

On a RH X86_64 system I have gnu tar 1.14 and it shows 

-l, --one-file-systemstay in local file system when creating archive

Robert



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of Charles Stroom
> Sent: Wednesday, September 20, 2006 12:25 PM
> To: amanda-users@amanda.org
> Subject: Re: Release of amanda-2.5.1
> 
> 
> on  Wed, 20 Sep 2006 10:33:15 EDT
> Gene Heskett <[EMAIL PROTECTED]> wrote:
> >
> > On Wednesday 20 September 2006 05:56, Geert Uytterhoeven wrote:
> > >On Mon, 11 Sep 2006, Geert Uytterhoeven wrote:
> > >>
> > >> But be careful, at least the tar 1.15.91-2 from Debian is broken: it
> > >> ignores the --one-file-system option when doing incrementals, causing
> > >> exorbitant backup sizes for any level > 0. I don't know about the
> > >> upstream version, but since this bug has been reported almost 2
> months
> > >> ago, I'm afraid that one is broken, too.
> > >
> > >Apparently the problem is more subtle. Thanks to the Debian bug
> tracking
> > >system, I noticed this:
> > >
> > >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384508
> > >tar: -l option changed meaning, without any warning!
> > >
> > >Gr{oetje,eeting}s,
> > >
> > >  Geert
> > >
> > Good Grief Charley Brown!
> >
> > Tar is supposed to be a stable, mature utility is it not?  I mean its
> what,
> > 30 years old, existing in the various *nix's long before gnu took over?
> > Whyinhell can't the folks over at gnu.org find something else to screw
> > with besides tar?  It doesn't _need_ to be on their WPA or CCC lists as
> a
> > makework project when there's nothing else to do around the office.
> >
> 
> On my Suse 10.0 system:
> 
> (2): cs> tar --version
> tar (GNU tar) 1.15.1
> (0): cs> tar -l dum dum
> tar: Semantics of -l option will change in the future releases.
> tar: Please use --one-file-system option instead.
> 
> So, at least there were warnings (not really an excuse I think)
> 
> Regards,
> 
> Charles
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Does a mixed environment of 2.5.1 server with pre-2.5.1 clients work?

[Jean-Louis Martineau]

Bruce,

I committed the suggested fix to the 2.5.1 tree.

Thanks

Jean-Louis

Bruce Thompson wrote:

Hi Paddy,

I've located what appears to be the source of the _keytable errors.

in common-src/util.h there appears:

- BEGIN -
typedef struct {/* token table entry */
char *keyword;
tok_t token;
} keytab_t;

keytab_t *keytable;
- END -

This is declaring an externally visible variable named "keytable" in 
every source file that includes util.h.


From what I can tell, this is better done as:

- BEGIN -
typedef struct {/* token table entry */
char *keyword;
tok_t token;
} keytab_t;

extern keytab_t *keytable;
- END -

and adding

keytab_t *keytable

to util.c.

Making this change has resulted in the complete elimination of this 
error. I do still see warnings about regex (the global library is used 
rather than amanda's conflicting symbols), but I suspect this is not a 
significant issue.


I'm checking against the latest subversion sources now to see if I get 
the same errors around keytable. If so then I'll post a patch here 
(unless of course someone yells at me that this fix will break 
something).


Cheers,
Bruce.


On Sep 20, 2006, at 9:44 AM, Paddy Sreenivasan wrote:

Re: WARNING: got empty schedule from planner

[Tim Butler]

 
 Thomas, 
  I'll have go at your suggests and post 
another message if required.   Thanks 
for the advise,   Tim Butler 
Beamline IT Support Australian Synchrotron Project 
   -Original Message-From: Thomas Ginestet 
<[EMAIL PROTECTED]>To: Tim Butler 
<[EMAIL PROTECTED]>Cc: "'Amanda List'" 
Date: Thu, 21 Sep 2006 10:50:51 +0200
Subject: Re: WARNING: got empty schedule from planner What is the estimate 
time report by the sendsize log ?Your timeout is maybe too shorttry 
to play with the etimeout in amanda.conf.Did your change any 
rule from your firewall  ?Have a look at http://wiki.zmanda.com/index.php/Amdump:_results_missing
Hope it will help you.ThomasTim Butler a écrit :
> Does everyone know why I receive this error during a dump?> 
 > START driver date 20060920> DISK planner ascm01 
/sqlbackup> DISK planner ascm01 /P4ROOT> DISK planner ascm01 
/asp> START planner date 20060920> START taper datestamp 
20060920 label Daily19 tape 0> FAIL planner ascm01 /asp 20060920 0 
[Estimate timeout from ascm01]> FAIL planner ascm01 /P4ROOT 20060920 
0 [Estimate timeout from ascm01]> FAIL planner ascm01 /sqlbackup 
20060920 0 [Estimate timeout from ascm01]> FINISH planner date 
20060920> WARNING driver WARNING: got empty schedule from planner
> STATS driver startup time 5402.179> INFO taper tape Daily19 kb 0 
fm 0 [OK]> FINISH driver date 20060920 time 5404.178> 
 >  > These dumps were to tape Daily19.> The 
next tape Amanda expects to use is: Daily04.>  > FAILURE 
AND STRANGE DUMP SUMMARY:>   ascm01     /asp lev 0 
FAILED [Estimate timeout from ascm01]>   ascm01     
/P4ROOT lev 0 FAILED [Estimate timeout from ascm01]>   ascm01 
    /sqlbackup lev 0 FAILED [Estimate timeout from ascm01]
>> STATISTICS:>             
              Total       
Full      Daily>           
                  
  > Estimate Time (hrs:min)    1:30> 
Run Time (hrs:min)         1:30> Dump Time 
(hrs:min)        0:00       0:00   
    0:00> Output Size (meg)         
  0.0        0.0        0.0
> Original Size (meg)         0.0     
   0.0        0.0> Avg Compressed Size 
(%)     --         --       
  --> Filesystems Dumped           
 0          0         
 0> Avg Dump Rate (k/s)         --   
      --         --> Tape Time 
(hrs:min)        0:00       0:00   
    0:00> Tape Size (meg)         
    0.0        0.0       
 0.0> Tape Used (%)             
  0.0        0.0        0.0
> Filesystems Taped             0   
       0          0> Avg 
Tp Write Rate (k/s)     --         --   
      --> USAGE BY TAPE:>   Label   
      Time      Size      % 
   Nb>   Daily19       0:00   
    0.0    0.0     0> > 
NOTES:>   driver: WARNING: got empty schedule from planner
>   taper: tape Daily19 kb 0 fm 0 [OK]> > DUMP 
SUMMARY:>                 
                    
 DUMPER STATS            TAPER STATS
> HOSTNAME     DISK        L ORIG-KB OUT-KB 
COMP% MMM:SS  KB/s MMM:SS  KB/s> -- 
- > ascm01     
  /P4ROOT     0 FAILED 
---> ascm01       
/asp        0 FAILED 
---> ascm01       
/sqlbackup  0 FAILED ---> 
(brought to you by Amanda version 2.4.4p3)

Re: Release of amanda-2.5.1

[Geert Uytterhoeven]

On Wed, 20 Sep 2006, Paul Bijnens wrote:
> On 2006-09-20 11:56, Geert Uytterhoeven wrote:
> > On Mon, 11 Sep 2006, Geert Uytterhoeven wrote:
> > > On Sat, 9 Sep 2006, Josef Wolf wrote:
> > > > On Tue, Sep 05, 2006 at 03:34:42PM -0400, Jean-Louis Martineau wrote:
> > > > 
> > > > >* Works with GNU tar 1.15.91 - work with new gtar state file
> > > > > format.
> > > > Can someone please explain what this exactly means?
> > > The format to store information about the incrementals was changed. Since
> > > Amanda made some assumptions about this format (while she shouldn't have
> > > cared,
> > > and just considered it as opaque files), this broke Amanda.
> > > After the fix, Amanda just treats the files as opaque files.
> > > 
> > > But be careful, at least the tar 1.15.91-2 from Debian is broken: it
> > > ignores
> > > the --one-file-system option when doing incrementals, causing exorbitant
> > > backup
> > > sizes for any level > 0. I don't know about the upstream version, but
> > > since
> > > this bug has been reported almost 2 months ago, I'm afraid that one is
> > > broken,
> > > too.
> > 
> > Apparently the problem is more subtle. Thanks to the Debian bug tracking
> > system, I noticed this:
> > 
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384508
> > tar: -l option changed meaning, without any warning!
> 
> 
> OK. But AFAIK (grep *.c in the sources), Amanda does NOT use the
> -l option, but only the --one-file-system option, since a very long
> time already.
> 
> So I think this option name change has nothing to do with the
> use of gnutar by Amanda.  (AFAIK the format of the incremental-state
> files has changed, and Amanda assumed they were in some line-oriented format
> instead of handling it as opaque objects.)

Indeed, thanks for reminding me! I just send a clarification to the Debian BTS:
  - 384508 is about -l no longer meaning --one-file-system
  - 377124 is about --one-file-system breaking when combined with
--listed-incremental (Amanda does pass --one-file-system (not -l) to
tar)

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

WARNING: got empty schedule from planner

[Tim Butler]

Title: Message



Does 
everyone know why I receive this error during a dump?
 
START driver date 20060920DISK planner ascm01 
/sqlbackupDISK planner ascm01 /P4ROOTDISK planner ascm01 /aspSTART 
planner date 20060920START taper datestamp 20060920 label Daily19 tape 
0FAIL planner ascm01 /asp 20060920 0 [Estimate timeout from ascm01]FAIL 
planner ascm01 /P4ROOT 20060920 0 [Estimate timeout from ascm01]FAIL planner 
ascm01 /sqlbackup 20060920 0 [Estimate timeout from ascm01]FINISH planner 
date 20060920WARNING driver WARNING: got empty schedule from 
plannerSTATS driver startup time 5402.179INFO taper tape Daily19 kb 0 fm 
0 [OK]FINISH driver date 20060920 time 5404.178
 
 
These dumps were to tape Daily19.The next tape Amanda 
expects to use is: Daily04.
 
FAILURE AND STRANGE DUMP SUMMARY:  
ascm01 /asp lev 0 FAILED [Estimate timeout from 
ascm01]  ascm01 /P4ROOT lev 0 FAILED [Estimate 
timeout from ascm01]  ascm01 /sqlbackup lev 0 
FAILED [Estimate timeout from ascm01]
STATISTICS:  
Total   Full  
Daily    
      Estimate Time 
(hrs:min)    1:30Run Time 
(hrs:min) 1:30Dump Time 
(hrs:min)    
0:00   
0:00   0:00Output Size 
(meg)   
0.0    
0.0    0.0Original Size 
(meg) 
0.0    
0.0    0.0Avg Compressed Size 
(%) -- 
-- -- Filesystems 
Dumped    
0  
0  0Avg Dump Rate 
(k/s) 
-- 
-- -- 
Tape Time (hrs:min)    
0:00   
0:00   0:00Tape Size 
(meg) 
0.0    
0.0    0.0Tape Used 
(%)   
0.0    
0.0    0.0Filesystems 
Taped 
0  
0  0Avg Tp Write Rate 
(k/s) -- 
-- -- 
USAGE BY TAPE:  
Label 
Time  Size  
%    Nb  Daily19   
0:00   0.0    
0.0 0
NOTES:  driver: WARNING: got empty schedule from 
planner  taper: tape Daily19 kb 0 fm 0 [OK]
DUMP 
SUMMARY: 
DUMPER STATS    
TAPER STATS HOSTNAME 
DISK    L ORIG-KB OUT-KB COMP% 
MMM:SS  KB/s MMM:SS  KB/s-- 
- 
ascm01   
/P4ROOT 0 FAILED 
---ascm01   
/asp    0 FAILED 
---ascm01   
/sqlbackup  0 FAILED ---
(brought to you by Amanda version 
2.4.4p3)