Bug 204240
Summary: | Samba 3.0.23a is completely broken | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew Zabolotny <anpaza> | ||||
Component: | samba | Assignee: | Simo Sorce <ssorce> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5 | CC: | bugzilla, christopher.murtagh, jmoore, jplans | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 3.0.23c-1 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-03-23 21:10:53 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
Andrew Zabolotny
2006-08-27 15:15:51 UTC
Also encountered problems as above on an FC4 Server with upgrade to this samba version Upgraded to FC5 & initially found I had to uninstall samba, remove config files & samba users & re install samba from scratch, initially also had to separate samba users from unix users Still suffering intermitant network pauses and "windows delayed write failures" on XP Pro workstations & "network drive no longer available" on 98 workstations Funny thing is the errror message can be given & then the file write or copy etc can be seen to complete ok Seems it is a timing issue ??? Also encountered problems as above on an FC4 Server with upgrade to this samba version Upgraded to FC5 & initially found I had to uninstall samba, remove config files & samba users & re install samba from scratch, initially also had to separate samba users from unix users Still suffering intermitant network pauses and "windows delayed write failures" on XP Pro workstations & "network drive no longer available" on 98 workstations Funny thing is the errror message can be given & then the file write or copy etc can be seen to complete ok Seems it is a timing issue ??? I found a patch that resolves this bug (at least it solves it on my box). I found it on the samba list, applied it and modified the spec file. The patch can be found here: http://lists.samba.org/archive/samba/2006-August/123664.html Can someone please look into it and apply it if it's ok. Like I said, the problem is resolved on my box, but it would be nice to be running the same version as upstream. I experienced similar issues. Specifically, the Windows XP SP2 box mounting the Samba share would time out on file copies and complain "the specified network name is no longer available". (Nonetheless, the drive remained mounted and could be browsed.) I downloaded the samba-3.0.23c-2.src.rpm from soon-to-be-FC6 rawhide, and built and installed the RPMS on the FC5 samba server. Bye-bye problems. I had the same problem as well. Client and server running samba-3.0.23a-fc5. Older Samba clients do not have the problem. Running the server with log level = 3 revealed that the server tried to pull up the client user's SID and ended up with his username instead. This looks suspiciously like the bug fixed in Samba 3.0.23 (See bug #199148), but in a different context. In any case, I took Jack's suggestion in Comment #4 and that fixed the problem. I'm pretty dissapointed in the speed that this bug is being addressed. The worst part is that it affects my FC boxes only. There are now two fixes in the comments (the patch and the rawhide src.rpm), why can't someone fix this in the distro? Problem seems fixed in 3.0.23c-1.fc5 on my FC5 i386 and FC5 x86_64 boxes. Thanks very much Jay! The promlem is NOT fixed in version 3.0.23c-1. In Version 3.0.23a write permission was gone, in version 3.0.23c-1 the mount permission is also gone. samba works if you are runnig clients on 3.0.23a and servers on 3.0.23. The promlem is NOT fixed in version 3.0.23c-1. In Version 3.0.23a write permission was gone, in version 3.0.23c-1 the mount permission is also gone. samba works if you are runnig clients on 3.0.23c-1 and servers on 3.0.23. Created attachment 140982 [details]
sabma-server-log (client)
ok, i want to describe the problem when installing 3.0.23c-1 on a 64-bit machine. - installation from the rpm: no problem - testparm /etc/samba/smb.conf: OK - when trying to mount the share from the client there is an error in the log: "no such user" (may be samba deleted the user?) - adding the user again - when trying to mount the share again, there is another error in the log: (see atachment) and here is the solution: if you have a "@" in your smb.conf e.g: write list = @group, replace it with a "+". this solves the problem. With kernel 2.16.18-1.2239 and Samba 3.0.23c-1 on one client and server, everything worked. The same combination on another client/server pair led to a "Permission denied" on the client and the following log on the server: Dec 1 17:11:57 cyclops smbd[2126]: domain_client_validate: unable to validate password for user 潭牯e䥃卆䱟义塕䑟䵏䰀湩硵瘠牥楳湯㈠㘮ㄮⴸ⸱㈲㤳昮㕣䌀䙉⁓� ⁓汃敩 瑮映牯䰠湩硵 in domain EVANSCITY to Domain controller GARRISON.THEBANK.C OM. Error was NT_ Huh? I can also mount shares on servers running any earlier version of Samba. When attempting to mount a Windows 2003 Server SP1 share, I get a "Permission denied" error. Checked the server event viewer and found that mount.cifs was not pulling domain information from smb.conf, but supplied a default 'CIFS_LINUX_DOM.' If I specified the domain in the mount options, everything worked. All the Samba clients and servers are using LDAP via nss_ldap for user resolution. (In reply to comment #12) > and here is the solution: > > > if you have a "@" in your smb.conf e.g: write list = @group, replace it with a > "+". this solves the problem. The problem is NOT fixed in samba version 3.0.24-1.fc6! Steven you hijacked the original bug with a known glibc bug in FC5. I am closing this bug as the original bug is fixed. If you still have the nisplus related crash problem after a full update of the distribution (or at least all libc related packages) please file a new bug against glibc. |