Bug 11854 - smbclient errors since badlock update
smbclient errors since badlock update
Status: NEW
Product: Samba 4.1 and newer
Classification: Unclassified
Component: libsmbclient
4.2.10
All All
: P5 major
: ---
Assigned To: Samba QA Contact
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-19 07:59 UTC by Alternativend
Modified: 2016-05-23 13:13 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alternativend 2016-04-19 07:59:24 UTC
Hello folks,
i have a quite huge problem with the smbclient and my backup software AMANDA since the badlock update. Im running several Amanda servers on Debian which is now shipping Samba 4.2.10. Everything worked fine since 4.1.17, but now im getting error messages like this:


FAILED DUMP DETAILS:
  /-- BACKUP02 //DC03/PUBLIC lev 0 FAILED [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset']
  sendbackup: info BACKUP=APPLICATION
  sendbackup: info APPLICATION=amsamba
  sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/lib/amanda/application/amsamba restore [./file-to-restore]+
  sendbackup: info COMPRESS_SUFFIX=.gz
  sendbackup: info end
  ? smbclient: Error reading password from file descriptor 5: empty password
  ? smbclient: 
  ? smbclient: tar:316  tarmode is now full, system, hidden, reset, quiet
  ? smbclient: tar:943  Fatal: Can't translate pathname './unfallanzeige.dot' to UTF-8
  sendbackup: error [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset']
  ? smbclient: NT_STATUS_UNSUCCESSFUL listing \\*
  ? smbclient: tar:704  do_list fail NT_STATUS_UNSUCCESSFUL
  ? smbclient: tar:711  Total bytes received: 101009857
  ? smbclient: tar:370  tar_process failed
  ? smbclient returned error
  ? Application (16495) amsamba returned 1


Well i hope this is the right place to report this issue and we can do something about it. If you need any additional informations about this let me know.

Thanks!
Comment 1 Stefan Metzmacher 2016-04-19 10:10:59 UTC
There where a lot of changes between 4.1 and 4.2 regarding tar support.

You may also want to file a bug in the debian bugzilla and cross reference
them.
Comment 2 Alternativend 2016-04-21 14:59:24 UTC
Hi,
i have done that (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821801).

Anyone who can have a look into this? I think it has to be fixed here at Samba, right?
Comment 3 Alternativend 2016-05-23 13:13:05 UTC
I have upgraded my system now to Debian Stretch which comes with Samba 4.4.

Here are some tries i have made:

Amanda Backup Client Hosts Check
--------------------------------
ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
ERROR: MYSERVER: smbclient: Error reading password from file descriptor 3: empty password
ERROR: MYSERVER: smbclient: 
ERROR: MYSERVER: Application 'amsamba': exited with status 1
ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
ERROR: MYSERVER: smbclient: Error reading password from file descriptor 3: empty password
ERROR: MYSERVER: smbclient: 
ERROR: MYSERVER: Application 'amsamba': exited with status 1
ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
ERROR: MYSERVER: smbclient: Error reading password from file descriptor 3: empty password



As you can see this command runs fine.

backup@MYSERVER:/home/backup$ smbclient "\\\\MYSERVER2\\Backup$" -U backup -E -W GSN2.local -Tc  Ziel.tar
WARNING: The "syslog" option is deprecated
Enter backup's password: 
Domain=[GSN2] OS=[Windows Server 2008 R2 Standard 7601 Service Pack 1] Server=[Windows Server 2008 R2 Standard 6.1]
tar:712  Total bytes received: 110498217

Maybe someone can tell more about the error we get here and can give some tips on how to avoid.