Re: [Dar-support] version 2.5.14 backup script failure in opensuse leap 15.3

[Aardric <aa...@aa...>]

On 2021-12-15 8:31 a.m., Graham Cobb wrote:
>
> On 15/12/2021 16:11, Aardric via Dar-support wrote:
>>
>>
>> On 2021-12-15 2:08 a.m., Graham Cobb wrote:
>>> On 15/12/2021 04:21, Aardric via Dar-support wrote:
>>>> Hail,
>>>>      A tried and true (over a decade) incremental back up bash script
>>>> failed after an o/s upgrade (opensuse leap 15.3). It is an old distro
>>>> package; dar version 2.5.14.
>>>> The offending lines:
>>>> -va \
>>>> -K aes256:
>>>> -* 50000 \
>>>> -J aes256:
>>>>
>>>> produced error:
>>>> Data corruption may have occurred, cannot decrypt data
>>>> ./dar_I211214d: line 43: -*: command not found
>>>
>>> If the script was not previously producing the last error shown above
>>> then ***someone*** has recently changed it.
>>>
>>> What you show does not appear to be an extract from a valid bash
>>> script!! Hint: the backslash is missing from the end of the line
>>> starting -K. Also, unless you have set noglob, you almost certainly want
>>> to put -* in quotes. I suggest you get someone who knows bash to take a
>>> look. I am guessing the missing continuation, causing the -* and -J
>>> options to be ignored, is also causing the first error messsage.
>>>
>>>> The archive has tested OK with dar -t.
>>>> Something obvious?
>>>
>>> Yes, see above.
>>>
>>
>> I should clarify a couple of points.
>> the missing backslashes cause the script to prompt me to enter a
>> password. These scripts are usually run with the password embedded as "
>> :some_password \" and the results are the same.
>
> So, you are saying that the script HAS been edited - to remove the
> password? It looks like the continuation backslash was removed as well
> when the password was removed.
>
> The error message from the shell is pretty clear:
>
> ./dar_I211214d: line 43: -*: command not found
>
> The shell is interpreting '-*' as a command, not as a continuation of
> the previous command. I think you need a \ at the end of the line before.
>
> Once you get rid of that shell error, you can start to track down if
> there is an actual dar problem.
>
You are correct! The back slash was indeed missing from the line
starting with -K. I needed to run diff to see it (despite you having
pointed it out). Now I have concerns about the onset of early dementia.
Thanks again.