Re: amsamba breaks with samba-4.14?

Hi @Chris,

that sounds great.

We use 4.13.5 on the backup server

backup@chronos:~$ apt-cache show smbclient|less
Package: smbclient
Source: samba
Version: 2:4.13.5+dfsg-2

so I don't know about 4.14 yet but I just posted an smill diff fix which 
seemed to work at the moment for us. Maybe there are still other 
smbclient problems I am not aware of.

Greetings
Tobias


On 8/24/21 5:38 PM, Chris Hassell wrote:
> @Tobias:
> 
> We have a new version of the amsamba app that you can try.   We need to get it out to get reviewed but it's nearly all changed.   We were hoping to get a community build out ... but that keeps getting delayed.
> 
> It's been refined and corrected in several ways.  We have seen various versions of samba behave differently.  I  cannot say I saw this below, though.
> 
>          -- CH
> 
>> -----Original Message-----
>> From: [email protected] <owner-amanda-
>> [email protected]> On Behalf Of Tobias Koeck
>> Sent: Friday, August 20, 2021 7:54 AM
>> To: [email protected]; [email protected]
>> Subject: Re: amsamba breaks with samba-4.14?
>>
>> WARNING: This email originated from outside of BETSOL. Do not click links or
>> open attachments unless you recognize the sender and know the content is safe.
>>
>>
>> And in the log.error logs I have errors like
>>
>>
>> sendbackup: info BACKUP=APPLICATION
>> sendbackup: info APPLICATION=amsamba
>> sendbackup: info RECOVER_CMD=/usr/lib/amanda/application/amsamba
>> restore [./file-to-restore]+
>> sendbackup: info COMPRESS_SUFFIX=.gz
>> sendbackup: info end
>> ? smbclient: tarmode: unrecognised option quiet ? smbclient:
>> NT_STATUS_IO_TIMEOUT listing \#recycle\Vgen\db\revs\* ? smbclient:
>> NT_STATUS_CONNECTION_DISCONNECTED listing
>> \#recycle\Vgen\db\node-origins\*
>> ? smbclient: NT_STATUS_CONNECTION_DISCONNECTED listing
>> \#recycle\Vgen\db\revprops\*
>> ? smbclient: NT_STATUS_CONNECTION_DISCONNECTED listing
>> \#recycle\Vgen\db\locks\*
>> ? smbclient: NT_STATUS_CONNECTION_DISCONNECTED listing
>> \#recycle\Vgen\dav\activities.d\*
>>
>> That worked with earlier versions, too.
>>
>> Greetings
>> Tobias
>> On 8/20/21 3:34 PM, Tobias Koeck wrote:
>>> Well,
>>>
>>> it looked like the same problem but I have "estimate server"
>>> configured a long time ago
>>>
>>> The system is Debian 11 (stable) with the installed amanda-server and
>>> amanda-client packages and the samba version the distribution uses
>>>
>>> ---
>>>
>>> root@chronos:/var/log/amanda/client/a2g-3# apt-cache show smbclient
>>> Package: smbclient
>>> Source: samba
>>> Version: 2:4.13.5+dfsg-2
>>>
>>>
>>> ---Package: amanda-client
>>> Source: amanda
>>> Version: 1:3.5.1-7
>>> Installed-Size: 1088
>>> Maintainer: Jose M Calhariz <[email protected]>
>>>
>>> ---
>>> Thu Aug 19 14:36:44.929065295 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: pid 4992 ruid 34 euid 34 version 3.5.1: start at Thu Aug 19
>>> 14:36:44 2021
>>> Thu Aug 19 14:36:44.930225697 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: Arguments: backup
>>> Thu Aug 19 14:36:44.962332448 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: pid 4992 ruid 34 euid 34 version 3.5.1: rename at Thu Aug 19
>>> 14:36:44 2021
>>> Thu Aug 19 14:36:44.962380711 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: application: Amsamba
>>> Thu Aug 19 14:36:44.962432105 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: warning: Use of uninitialized value $regex_match in pattern
>>> match (m//) at /usr/lib/amanda/application/amsamba line 92.
>>> Thu Aug 19 14:36:44.962487075 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: Arguments: backup --message line --config a2g-3 --host
>>> localhost --disk //monster.someurl.de/sysadmin --device
>>> //monster.someurl.de/sysadmin --level 0 --index line --record
>>> --exclude-file ./ftp_data_hd --exclude-file ./privat --amandapass
>>> /etc/amandapass Thu Aug 19 14:36:44.962505169 2021: pid 4992:
>>> thd-0x55ad3da7ea00:
>>> Amsamba: command: backup
>>> Thu Aug 19 14:36:44.962644877 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: amandapass: /etc/amandapass
>>> Thu Aug 19 14:36:44.968353548 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: password_wtr 6
>>> Thu Aug 19 14:36:44.968387602 2021: pid 4994: thd-0x55ad3da7ea00:
>>> Amsamba: password_rdr 5
>>> Thu Aug 19 14:36:44.968472678 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: /bin/tar -tf -
>>> Thu Aug 19 14:36:44.968509209 2021: pid 4994: thd-0x55ad3da7ea00:
>>> Amsamba: execute: /usr/bin/smbclient /usr/bin/smbclient
>>> //monster.someurl.de/sysadmin -d 0 -U backup -E -c tarmode full reset
>>> hidden system quiet; tar cX - ./ftp_data_hd ./privat Thu Aug 19
>>> 14:36:44.990733785 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: index 7
>>> Thu Aug 19 14:36:45.842756883 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: stderr: tarmode: unrecognised option quiet Thu Aug 19
>>> 14:36:45.842868409 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: smbclient: tarmode: unrecognised option quiet Thu Aug 19
>>> 18:05:10.128160354 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: stderr: tarmode is now full, system, hidden, reset, noverbose
>>> Thu Aug 19 18:05:10.146256679 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: stderr: tar: dumped 7728 files and 0 directories Thu Aug 19
>>> 18:05:10.146297388 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: smbclient: tar: dumped 7728 files and 0 directories Thu Aug
>>> 19 18:05:10.146461082 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_utime   : 265
>>> Thu Aug 19 18:05:10.146478219 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_stime   : 302
>>> Thu Aug 19 18:05:10.146488377 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_maxrss  : 31644
>>> Thu Aug 19 18:05:10.146498114 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_ixrss   : 0
>>> Thu Aug 19 18:05:10.146507667 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_idrss   : 0
>>> Thu Aug 19 18:05:10.146517031 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_isrss   : 0
>>> Thu Aug 19 18:05:10.146526444 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_minflt  : 5177
>>> Thu Aug 19 18:05:10.146535912 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_majflt  : 0
>>> Thu Aug 19 18:05:10.146545258 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_nswap   : 0
>>> Thu Aug 19 18:05:10.146554645 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_inblock : 16
>>> Thu Aug 19 18:05:10.146564198 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_oublock : 24
>>> Thu Aug 19 18:05:10.146573594 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_msgsnd  : 0
>>> Thu Aug 19 18:05:10.146582972 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_msgrcv  : 0
>>> Thu Aug 19 18:05:10.146592333 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_nsignals: 0
>>> Thu Aug 19 18:05:10.146601797 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_nvcsw   : 5054926
>>> Thu Aug 19 18:05:10.146611355 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: ru_nivcsw  : 3985056
>>> Thu Aug 19 18:05:10.146909952 2021: pid 4992: thd-0x55ad3da7ea00:
>>> Amsamba: pid 4992 finish time Thu Aug 19 18:05:10 2021 ~
>>>
>>> They seem to drop something to stderr because they don't know an option.
>>>
>>> "tarmode: unrecognised option quiet"
>>>
>>>
>>>
>>> FAILURE DUMP SUMMARY:
>>>     localhost //monster.someurl.de/sysadmin lev 0  FAILED [missing size
>>> line from sendbackup]
>>>     localhost //monster.someurl.de/sysadmin lev 0  FAILED [missing size
>>> line from sendbackup]
>>>     localhost //monster.someurl.de/sysadmin lev 0  partial taper:
>>> successfully taped a partial dump
>>>
>>> Greetings
>>> Tobias
>>>
>>>
>>> On 8/18/21 5:04 PM, Stefan G. Weichinger wrote:
>>>   > Am 18.08.21 um 16:48 schrieb Tobias Koeck:
>>>   >> Yes I have the same problem.
>>>   >
>>>   > Ah, someone still alive here
>>>   >
>>>   > "estimate server" seems to work, can you test and confirm?
>>>
>>>
>>> On 8/18/21 5:04 PM, Stefan G. Weichinger wrote:
>>>> Am 18.08.21 um 16:48 schrieb Tobias Koeck:
>>>>> Yes I have the same problem.
>>>>
>>>> Ah, someone still alive here ;-)
>>>>
>>>> "estimate server" seems to work, can you test and confirm?
>>>>
> Confidentiality Notice | The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, re-transmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.
>