Re: Oddity with the disklist

2018-06-07 Thread Dirk-Willem van Gulik


> On 3 Jun 2018, at 01:12, Nathan Stratton Treadway  wrote:
> 
> On Sat, Jun 02, 2018 at 13:05:16 +0200, Dirk-Willem van Gulik wrote:
>> On 1 Jun 2018, at 19:14, Chris Nighswonger  
>> wrote:
>>> 
>>> Based on the example disklist file, it looks like when using the multi-line 
>>> format, you need a leading slash before your diskname entry:
>>> 
>>> /tank/jail/webhost091
>>> 
>>> or some such.
>> 
>> Unfortunately - the disk is a ZFS volume - so one does not really want
>> the slash there. And the no-multi-line version of the same does work.
>> 
>> Or is there something special in the multi line code that uses a ^\\\w+ sort 
>> of regex ?  
>> 
> 
> I don't have v3.3.9 installed anywhere to look at specifically, and
> don't have experience with ZFS backups, but after looking at the code in
> disklist.c, off hand I don't believe the problem is likely to be with
> _parsing_ the "{"... "}" block.

As the logfiles you suggested some parsing issue - I upgraded to 3.5.1 — and 
that simply made the entire issue go away.

So I suspect it was a bug fixed years ago.

Thanks!

Dw.




Re: Oddity with the disklist

2018-06-02 Thread Nathan Stratton Treadway
On Sat, Jun 02, 2018 at 13:05:16 +0200, Dirk-Willem van Gulik wrote:
> On 1 Jun 2018, at 19:14, Chris Nighswonger  
> wrote:
> > 
> > Based on the example disklist file, it looks like when using the multi-line 
> > format, you need a leading slash before your diskname entry:
> > 
> > /tank/jail/webhost091
> > 
> > or some such.
> 
> Unfortunately - the disk is a ZFS volume - so one does not really want
> the slash there. And the no-multi-line version of the same does work.
> 
> Or is there something special in the multi line code that uses a ^\\\w+ sort 
> of regex ?  
> 

I don't have v3.3.9 installed anywhere to look at specifically, and
don't have experience with ZFS backups, but after looking at the code in
disklist.c, off hand I don't believe the problem is likely to be with
_parsing_ the "{"... "}" block.

Instead, from your error message I wonder if the ZFS-snapshotting isn't
actually happening as expected in the multi-line case, presumably because
some part of the definition of
"openssl-client-encrypt-best-zfssnapshot-jail" isn't getting carried
over to the "clone" dumptype created by the { ... } syntax.

You might find some useful information by comparing the
sendbackup.*.debug/sendsize.*.debug log files between a successful,
no-multi-line DLE entry run and a failed run with the multiline DLE.
(And if the ZFS script calls generate any separate log files, check
those as well.)


Meanwhile, if you post the amanda.conf definition of the
openssl-client-encrypt-best-zfssnapshot-jail dump tupe (along with any
script-tool and parent dump type definitions), that may give a hint as
to which component of the definition isn't getting copied correctly.

(For good measure, it might be useful to see the 
"DEFINE DUMPTYPE openssl-client-encrypt-best-zfssnapshot-jail" and
related DEFINE SCRIPT section from the output of "amadmin CONFIG config"
as well.)


Nathan



Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239


Re: Oddity with the disklist

2018-06-02 Thread Dirk-Willem van Gulik
On 1 Jun 2018, at 19:14, Chris Nighswonger  wrote:
> 
> Based on the example disklist file, it looks like when using the multi-line 
> format, you need a leading slash before your diskname entry:
> 
> /tank/jail/webhost091
> 
> or some such.

Unfortunately - the disk is a ZFS volume - so one does not really want the 
slash there. And the no-multi-line version of the same does work.

Or is there something special in the multi line code that uses a ^\\\w+ sort of 
regex ?  

Dw.

> On Fri, Jun 1, 2018 at 12:09 PM, Dirk-Willem van Gulik  <mailto:di...@webweaving.org>> wrote:
> I’ve got a bit of an oddity with the disklist - suspect it is really trivial; 
> but am not seeing it.
> 
> This works splendidly and as expected:
> 
> ...
> .webweaving.org <http://.webweaving.org/>
> tank/jail/webhost openssl-client-encrypt-best-zfssnapshot-jail
> 
> But this (with whitespace reduced to just space and a \n straight after every 
> line, no space in between):
> 
> .webweaving.org <http://.webweaving.org/>  
> tank/jail/webhost091 {   
> openssl-client-encrypt-best-zfssnapshot-jail
> exclude append "./usr/local/www/logs"
> }
> 
> Gives me the error:
> 
> ERROR: .webweaving.org <http://.webweaving.org/>: [can not 
> stat tank/jail/webhost091: No such file or directory]
> 
> And bringing it back to just:
> 
> .webweaving.org <http://.webweaving.org/>  
> tank/jail/webhost091 {   
> openssl-client-encrypt-best-zfssnapshot-jail
> }
> 
> gives me the same error. This is on Amanada 3.3.9, stock FreeBSD install 
> against a stock FreeBSD-11.1 remote host with zfs #28.
> 
> What am I missing. Must be trivial !
> 
> Thanks,
> 
> Dw.
> 
> 
> 



Re: Oddity with the disklist

2018-06-01 Thread Chris Nighswonger
Based on the example disklist file, it looks like when using the multi-line
format, you need a leading slash before your diskname entry:

/tank/jail/webhost091

or some such.

Kind regards,
Chris


On Fri, Jun 1, 2018 at 12:09 PM, Dirk-Willem van Gulik  wrote:

> I’ve got a bit of an oddity with the disklist - suspect it is really
> trivial; but am not seeing it.
>
> This works splendidly and as expected:
>
> ...
> .webweaving.orgtank/jail/webhost
> openssl-client-encrypt-best-zfssnapshot-jail
>
> But this (with whitespace reduced to just space and a \n straight after
> every line, no space in between):
>
> .webweaving.org  tank/jail/webhost091 {
>
> openssl-client-encrypt-best-zfssnapshot-jail
> exclude append "./usr/local/www/logs"
> }
>
> Gives me the error:
>
> ERROR: .webweaving.org: [can not stat tank/jail/webhost091:
> No such file or directory]
>
> And bringing it back to just:
>
> .webweaving.org  tank/jail/webhost091 {
>
> openssl-client-encrypt-best-zfssnapshot-jail
> }
>
> gives me the same error. This is on Amanada 3.3.9, stock FreeBSD install
> against a stock FreeBSD-11.1 remote host with zfs #28.
>
> What am I missing. Must be trivial !
>
> Thanks,
>
> Dw.
>
>
>


Re: Oddity with the disklist

2018-06-01 Thread J Chapman Flack
Where did the 091 come from? I don't see it in the first (working) example.

-Chap

On 06/01/18 12:09, Dirk-Willem van Gulik wrote:
> I’ve got a bit of an oddity with the disklist - suspect it is really trivial; 
> but am not seeing it.
> 
> This works splendidly and as expected:
> 
>   ...
>   .webweaving.orgtank/jail/webhost 
> openssl-client-encrypt-best-zfssnapshot-jail
> 
> But this (with whitespace reduced to just space and a \n straight after every 
> line, no space in between):
> 
>   .webweaving.org  tank/jail/webhost091 { 
>   
>   openssl-client-encrypt-best-zfssnapshot-jail
>   exclude append "./usr/local/www/logs"
>   }
> 
> Gives me the error:
> 
>   ERROR: .webweaving.org: [can not stat tank/jail/webhost091: No such 
> file or directory]
> 
> And bringing it back to just:
> 
>   .webweaving.org  tank/jail/webhost091 { 
>   
>   openssl-client-encrypt-best-zfssnapshot-jail
>   }
> 
> gives me the same error. This is on Amanada 3.3.9, stock FreeBSD install 
> against a stock FreeBSD-11.1 remote host with zfs #28.
> 
> What am I missing. Must be trivial !
> 
> Thanks,
> 
> Dw.
> 
> 


Re: Oddity with the disklist

2018-06-01 Thread Dirk-Willem van Gulik
On 1 Jun 2018, at 18:20, J Chapman Flack  wrote:
> 
> Where did the 091 come from? I don't see it in the first (working) example.

Sorry - that is me badly anonymising on sent. Corrected below.

— corrected --

I’ve got a bit of an oddity with the disklist - suspect it is really trivial; 
but am not seeing it.

This works splendidly and as expected:

...
.webweaving.orgtank/jail/webhost091 
openssl-client-encrypt-best-zfssnapshot-jail

But this (with whitespace reduced to just space and a \n straight after every 
line, no space in between):

.webweaving.org  tank/jail/webhost091 { 
  
openssl-client-encrypt-best-zfssnapshot-jail
exclude append "./usr/local/www/logs"
}

Gives me the error:

ERROR: .webweaving.org: [can not stat tank/jail/webhost091: No such 
file or directory]

And bringing it back to just:

.webweaving.org  tank/jail/webhost091 { 
  
openssl-client-encrypt-best-zfssnapshot-jail
}

gives me the same error. This is on Amanada 3.3.9, stock FreeBSD install 
against a stock FreeBSD-11.1 remote host with zfs #28.

What am I missing. Must be trivial !

Thanks,

Dw.







Oddity with the disklist

2018-06-01 Thread Dirk-Willem van Gulik
I’ve got a bit of an oddity with the disklist - suspect it is really trivial; 
but am not seeing it.

This works splendidly and as expected:

...
.webweaving.orgtank/jail/webhost 
openssl-client-encrypt-best-zfssnapshot-jail

But this (with whitespace reduced to just space and a \n straight after every 
line, no space in between):

.webweaving.org  tank/jail/webhost091 { 
  
openssl-client-encrypt-best-zfssnapshot-jail
exclude append "./usr/local/www/logs"
}

Gives me the error:

ERROR: .webweaving.org: [can not stat tank/jail/webhost091: No such 
file or directory]

And bringing it back to just:

.webweaving.org  tank/jail/webhost091 { 
  
openssl-client-encrypt-best-zfssnapshot-jail
}

gives me the same error. This is on Amanada 3.3.9, stock FreeBSD install 
against a stock FreeBSD-11.1 remote host with zfs #28.

What am I missing. Must be trivial !

Thanks,

Dw.