Bug 447820
Summary: | Samba 3.2.0 incompatible for smb backups using BackupPC 3.1.0 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Brent <fix> | ||||||
Component: | samba | Assignee: | Simo Sorce <ssorce> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 9 | CC: | gdeschner, jbayes | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-07-14 16:31:19 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Brent
2008-05-21 22:26:59 UTC
Can you please provide a network trace of the failure (3.2.0) and the success (3.0.28a) ? Created attachment 308899 [details]
Failed capture using 3.2.0
Since I'm having the same problem, I'll try to provide you with the network trace. If I did this wrong, and you want something different, please let me know exactly what it is you want. Attached is the failure using 3.2.0 Can't get 3.0.26a to compile (both the plain vanilla package and the source rpm)-- I keep getting smbd/oplock_linux.c:37: error: conflicting types for 'capget' /usr/include/sys/capability.h:111: error: previous declaration of 'capget' was here (In reply to comment #3) > Since I'm having the same problem, I'll try to provide you with the network > trace. If I did this wrong, and you want something different, please let me know > exactly what it is you want. > > Attached is the failure using 3.2.0 Thanks for that. What we need is a dumpfile generated with tcpdump -i $YOURINTERFACE -s 0 -w dumpfile though. > Created attachment 309043 [details]
output of tcpdump using Samba 3.2.0
output of spoo:/home/jbayes# tcpdump -i eth0 -s 0 -w dumpfile
You're trying to access \\JANE\C$ anonymously (as the provided creds of MYGROUP\administrator that come along, either have an invalid password, or that user is invalid completly on that box). Can you try to set "client lanman auth = yes" in smb.conf ? That should be BAYES\administrator -- perhaps that's part of the problem? I just changed "workgroup = MYGROUP" to "workgroup = BAYES" in smb.conf, but it didn't fix anything. I also added "client lanman auth = yes" to the "global" section in /etc/samba/smb.conf. I also added "-W BAYES" to the SmbClientFullCmd and SmbClientIncrCmd lines in the GUI, which also didn't fix anything. I don't think that the "administrator" user is invalid, or that the password is invalid, as this was working fine under Fedora 8. Perhaps the upgrade changed a setting somewhere... Typing "smbclient //jane/c\$ -U administrator%password" into the command line works just fine. I think I found the problem, and have a workaround. PASSWD=<password> /usr/bin/smbclient //jane/C\$ -U Administrator -N fails but PASSWD=<password> /usr/bin/smbclient //jane/C\$ -U Administrator succeeds. So it seems that adding -N to the command line doesn't merely suppress the password prompt, but causes smbclient to ignore the PASSWD variable as well! I don't think this was the case with samba-3.0.26a. So the solution is to remove the "-N" from the SmbClient{Full,Incr,Restore}Cmd variables. And also, to either restore the old behavior in samba, or document the new behavior in the smbclient manpage. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Bug still exists in Fedora 10 (BackupPC 3.1.0, samba 3.2.11), probably in Fedora 11 as well. Just to be clear, the fix is: 1) Remove "-N" from all smbclient commands in BackupPC's config.pl 2) Change the smbclient manpage to say, -N Causes smbclient to use no password when accessing the service. Any password in the command line or in the $PASSWD variable will be silently ignored. The user will not be prompted for a password. Bugzilla won't let me change the "version" field of this bug, but "version" should be changed to 10. Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. This bug is still present in Fedora 12. The language of the smbclient manpage has been changed, it is now confusing and overly wordy, but at least it's technically correct. The "-N" still needs to be removed from all smbclient commands in BackupPC's config.pl. And this bug should be reopened with "version" field set to 12, but Bugzilla won't let me. |