Re: [Samba] Clearcase, Samba, and mnode values
Yeah, that's actually what I ended up doing. I am now running 3.5.8, which is the blessed version of Samba with Clearcase 7.1.2.3, so they can't say I'm out of compliance anymore. :) We'll see what happens when we stress test it soon, hopefully next week. Kathy You might want to ask IBM for guidance to go to the supported version of Samba. Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Clearcase, Samba, and mnode values
I agree with you there, that it's not very much memory consumed. Even over 12 hours (what it took to drag all the 32 GB down into swap), I was not seeing any one or two processes consuming huge quantities of memory, Gdmgreeter and python (for Redhat updates) consumed more memory than any smbd process, but they were pretty static. This is why I am not necessarily convinced Samba was the problem, but I also do not know what is normal behavior for Clearcase in terms of memory management. And so far, IBM isn't sharing, either because the person I'm working with doesn't know, or hasn't asked the right person. On Wed, Sep 7, 2011 at 10:49 PM, Volker Lendecke volker.lende...@sernet.de wrote: That's a couple of megabytes overall. Trivial for 32GB RAM. It really looks like someone else must be the main consumer. Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Clearcase, Samba, and mnode values
That's possible and yesterday I was looking at possibly using Valgrind to see if I could dig further into that idea. I've never used it before, though, so not sure if there is an easier method to detect kernel memory leaks. And about static things in swap, I agree. I have noticed on our old Clearcase/Samba server, that it consumes all the memory down to about 150M plus 72k of swap and just sits there like that. Seems to be fine and can run for 2 months or longer like that. That server, though, has only 4 gigs of memory and so I was assuming that it did that because it didn't have a lot of memory. However, this new Clearcase server, which has 32 GB of memory appears to perhaps want to do the same thing. So I began to wonder if that is just normal behavior -- i.e., it caches all its memory. But I think it's a problem because people started to report Clearcase running really really slow when it got down to almost nothing left and it just seems odd that it would consume all 32 GB of memory in less than 12 hours. If you can't spot processes consuming memory in RSS might it be a kernel memleak? BTW, something statically in swap is not necessarily bad. Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Clearcase, Samba, and mnode values
Thanks Volker, regarding Valgrind. And thanks for the reply Jeff. You guys have made me feel better about Samba, because it supports what I was noticing in that although Samba memory usage was increasing, I was not seeing it consuming the amount of memory that I saw being cached. Maybe I should be asking Jeff this offline, since it isn't a Samba question, but I would love to know how (if possible) to tell how much is reclaimable RAM. I have seen certain applications bring a system to its knees (Cadence comes to mind) once all free memory is cached and we have to reboot because the application no longer works. To me, that is a problem with how Cadence is managing memory. Yet on our other Clearcase server, I see it running with everything cached and is completely happy. Perhaps the only way to know if the app is happy in this state is to let it run and see what happens? Unfortunately, the persons I have been talking with at IBM are still pointing at Samba and the fact that I was 0.01 out of spec on Samba version. I need to find another resource to talk to there. Thanks -- Kathy On Thu, Sep 8, 2011 at 11:55 AM, Jeff Layton jlay...@redhat.com wrote: On Thu, 8 Sep 2011 10:14:47 -0700 Kathy banshee...@gmail.com wrote: That's possible and yesterday I was looking at possibly using Valgrind to see if I could dig further into that idea. I've never used it before, though, so not sure if there is an easier method to detect kernel memory leaks. And about static things in swap, I agree. I have noticed on our old Clearcase/Samba server, that it consumes all the memory down to about 150M plus 72k of swap and just sits there like that. Seems to be fine and can run for 2 months or longer like that. That server, though, has only 4 gigs of memory and so I was assuming that it did that because it didn't have a lot of memory. However, this new Clearcase server, which has 32 GB of memory appears to perhaps want to do the same thing. So I began to wonder if that is just normal behavior -- i.e., it caches all its memory. But I think it's a problem because people started to report Clearcase running really really slow when it got down to almost nothing left and it just seems odd that it would consume all 32 GB of memory in less than 12 hours. That's normal. Linux will use up as much free RAM as it can to cache file data, based on the principle that free RAM is wasted RAM. What really matters is not free RAM, so much as *reclaimable* RAM. If the memory is clean (meaning that it doesn't have data that needs to be written back out), then the kernel can just free it on a least-recently-used basis when the need arises. If not, then the kernel will require more active participation to free up memory, which is comparatively slow. I think you'll probably need to step back and determine what the application is doing when it becomes slow. It may very well be that there is a problem with memory allocation at that time that's causing the slowdown. But, you can't really assume that or you might end up down a rabbit hole that has nothing to do with the real problem. Determining that will probably require help from IBM as only they have real insight into clearcase -- it's a closed source program, after all. Either way, it's highly doubtful that this has anything to do with samba. -- Jeff Layton jlay...@redhat.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Clearcase, Samba, and mnode values
Hi all -- I recently temporarily deployed an upgraded Clearcase server (7.1.2.3) on 64 bit RHEL 5.6. With it I was using Redhat's release of Samba for that version of the OS -- 3.0.33.The system has 32 GB of memory and within 12 hours, it would be down into swap. Maximum active licenses used is 36 but a more typical load is 18-25 users having a Clearcase license at once. Clearcase clients are on Windows. This server is the whole shebang -- license server, view and vob server. All disks are local, no NAS. Most of the time our developers are using snapshot views but merge into the dynamic views. It looks to me like I have a memory leak, and IBM is blaming Samba, seeing that I was using an unblessed version of the tool. Apparently 3.0.32 is blessed and 3.0.33 is not. Although I'm skeptical, I'm willing to entertain the idea that a 0.01 release change could be the problem, so I recently updated to 3.5.8, which apparently is blessed to work with 7.1.2.3. This system is now a test server so we can test it without impacting production use. We still need to do some load testing on it. The original server is on different hardware (still Dell, though), running 32 bit RHEL 5.2 and Clearcase 7.0.1.3, and Samba 3.0.28 (which also apparently isn't blessed by IBM but has never had any problems). I am using the samba smb.conf file for both releases/servers. For those of you who are familiar with how Clearcase and Samba work together, my questions are the following: 1. What is typical memory usage with Clearcase and Samba? Is it typical for it to cache all memory, eat into a little bit of swap (say 312k) and then sit there like that and work just fine? Or should I expect it to eat up initially a few gigs of memory and then stay relatively stable, recognizing that over time the running system will slowly eat up memory (but not all in 12 hours). 2. IBM has suggested making sure these conditions are met for mnode values on Windows clients and the MAX_OPEN_FILES is big enough on the Samba side: https://www-304.ibm.com/support/docview.wss?uid=swg21169548 Basically saying that for a 64 bit Clearcase/Samba server, the max mnode values should be set to 800 and not the default 1800. Anyone with experience with this? We have not seen the particular errors mentioned in this article, but IBM support is telling me about it as a guideline. Also mentioned in the article is MAX_OPEN_FILES. My current value for that is 16,384. How do you know what is an optimal value for that for your system? Thanks for any input. I have asked IBM to describe typical memory usage but so far I'm not getting any solid answers. Kathy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Clearcase, Samba, and mnode values
It looks to me like I have a memory leak, and IBM is blaming Samba,
Main question is: Do the smbd processes really consume all
that memory?
I did see smbd processes increase in memory over time, but since I
have never monitored smbd this closely before, I'm not sure if this is
normal or not. I was doing the following memory test every hour and I
was seeing a general trend up in RSS size.
ps -e -o user,pid,rss,args | sort -b -k3,3n | awk '{print
$1,$2,$3,$4}' | tail -n 20 /var/log/memory_usage.log
Here are a couple of smbd pids that were increasing over time, showing
the trend I was seeing. There were multiple smbd (typically around
18-20) running at the time.
PID RSS
root 9402 4176 smbd
root 9402 5364 smbd
root 9402 5752 smbd
root 9402 5752 smbd
root 9787 4124 smbd
root 9787 4556 smbd
root 9787 4560 smbd
root 9787 7448 smbd
root 9787 7460 smbd
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
[Samba] RESOLVED: Need urgent help. trust relationship problem during authentication
I am not sure if this first post made it to the list, but I wanted to
post the resolution, which was very simple and something I had
documented but buried and I had forgotten about it.
All these problems went away when I joined the domain using Samba's
version of net, not Redhat's. If you use Redhat's version, it looks
like it joins the domain but it really doesn't work correctly.
Kathy
On Wed, Mar 23, 2011 at 8:05 PM, Kathy banshee...@gmail.com wrote:
We have an urgent problem that we've been spending hours on to no avail.
We have a RHEL 5.2 server that is running Samba 3.2.8 and was set up
for domain authentication against our PDC. It was running fine until
I decided to try and change it to ads authentication. I then
realized that we needed to keep it on domain because of the version
of Clearcase we have on the machine, so I went to change it back and
ever since then, users can't authenticate. Our PDC is running
Microsoft 2008 R2.
The way I have changed back and forth is this:
1. Shut down Samba
2. Remove the Samba server (Flint) from the domain by going onto the
DC and removing it.
3. Run: kinit administra...@ourdomain.com
4. Run: net rpc join -U Administrator
5. Start Samba again
Whenever I do that, it appears to join the domain okay, but if you try
to connect to the Samba server via \\flint you get the following
pop-up from a Windows XP box:
The trust relationship between this workstation and the primary domain failed.
In the client logs we see:
check_ntlm_password: Authentication for user [banshee] - [banshee]
FAILED with error NT_STATUS_TRUSTED_RELATIONSHIP_FAILURE
I have tried this:
net rpc changetrustpw
Did not help.
It looks like it joined the domain okay, but for some reason
authentication is not happening.
[root@flint samba]# net rpc testjoin
Join to 'OURDOMAIN' is OK
Below are some outputs from testparam and what our krb.conf file looks like.
If anyone has any ideas, please let me know. This is causing an
entire group to be down while this isn't working.
Thanks!
Kathy
[root@flint samba]# testparm -s
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_DOMAIN_MEMBER
[global]
workgroup = OURDOMAIN
realm = OURDOMAIN.COM
server string = Flint Samba Server
security = DOMAIN
password server = togiak.ourdomain.com
username map = /etc/samba/username.map
log level = 2
log file = /var/log/samba/log.%m
max log size = 10
deadtime = 15
dns proxy = No
kernel oplocks = No
lock directory = /var/log/samba/locks
host msdfs = No
invalid users = @root, @wheel, @bin, @sys, @admin
create mask = 0775
directory mask = 0775
case sensitive = No
map archive = No
oplocks = No
level2 oplocks = No
dont descend = /proc,/dev
fake directory create times = Yes
/etc/krv5.conf looks like this:
[root@flint samba]# more /etc/krb5.conf
[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
[libdefaults]
default_realm= OURDOMAIN.COM
dns_lookup_realm = true
dns_lookup_kdc = true
[realms]
OURDOMAIN.COM= {
kdc= togiak.ourdomain.com
admin_server= togiak.ourdomain.com
default_domain= ourdomain.com
}
[domain_realm]
.togiak.ourdomain.com = OURDOMAIN.COM
ourdomain.com = OURDOMAIN.COM
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
[Samba] Need urgent help. trust relationship problem during authentication
We have an urgent problem that we've been spending hours on to no avail.
We have a RHEL 5.2 server that is running Samba 3.2.8 and was set up
for domain authentication against our PDC. It was running fine until
I decided to try and change it to ads authentication. I then
realized that we needed to keep it on domain because of the version
of Clearcase we have on the machine, so I went to change it back and
ever since then, users can't authenticate. Our PDC is running
Microsoft 2008 R2.
The way I have changed back and forth is this:
1. Shut down Samba
2. Remove the Samba server (Flint) from the domain by going onto the
DC and removing it.
3. Run: kinit administra...@ourdomain.com
4. Run: net rpc join -U Administrator
5. Start Samba again
Whenever I do that, it appears to join the domain okay, but if you try
to connect to the Samba server via \\flint you get the following
pop-up from a Windows XP box:
The trust relationship between this workstation and the primary domain failed.
In the client logs we see:
check_ntlm_password: Authentication for user [banshee] - [banshee]
FAILED with error NT_STATUS_TRUSTED_RELATIONSHIP_FAILURE
I have tried this:
net rpc changetrustpw
Did not help.
It looks like it joined the domain okay, but for some reason
authentication is not happening.
[root@flint samba]# net rpc testjoin
Join to 'OURDOMAIN' is OK
Below are some outputs from testparam and what our krb.conf file looks like.
If anyone has any ideas, please let me know. This is causing an
entire group to be down while this isn't working.
Thanks!
Kathy
[root@flint samba]# testparm -s
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_DOMAIN_MEMBER
[global]
workgroup = OURDOMAIN
realm = OURDOMAIN.COM
server string = Flint Samba Server
security = DOMAIN
password server = togiak.ourdomain.com
username map = /etc/samba/username.map
log level = 2
log file = /var/log/samba/log.%m
max log size = 10
deadtime = 15
dns proxy = No
kernel oplocks = No
lock directory = /var/log/samba/locks
host msdfs = No
invalid users = @root, @wheel, @bin, @sys, @admin
create mask = 0775
directory mask = 0775
case sensitive = No
map archive = No
oplocks = No
level2 oplocks = No
dont descend = /proc,/dev
fake directory create times = Yes
/etc/krv5.conf looks like this:
[root@flint samba]# more /etc/krb5.conf
[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
[libdefaults]
default_realm= OURDOMAIN.COM
dns_lookup_realm = true
dns_lookup_kdc = true
[realms]
OURDOMAIN.COM= {
kdc= togiak.ourdomain.com
admin_server= togiak.ourdomain.com
default_domain= ourdomain.com
}
[domain_realm]
.togiak.ourdomain.com = OURDOMAIN.COM
ourdomain.com = OURDOMAIN.COM
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Deletion of directory symlink via Samba deletes files in original subdirectory on Unix
Windows reports the Unix symbolic link as being type file folder, so it sees it as an actual folder. Kathy On Thu, Dec 3, 2009 at 12:07 AM, Diego Zuccato diego.zucc...@unibo.it wrote: Uhm... Just a wild guess: win sees that folder is not empty, then first removes all the files in it, then the folder itself. Too bad the folder was a symlink, but the files were not... Does win show the symlink as a link or as a real folder? -- Diego Zuccato Servizi Informatici Dip. di Astronomia - Università di Bologna Via Ranzani, 1 - 40126 Bologna - Italy tel.: +39 051 20 95786 mail: diego.zucc...@unibo.it -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Deletion of directory symlink via Samba deletes files in original subdirectory on Unix
I'm reposting this because I posted it last time and then ran off to Thanksgiving vacation. The last question regarding it was what version of Samba we are using. We have multiple versions on different flavors of Unix: 3.0.25a (Solaris 10 package), 3.0.33 (RHEL 4 package), and hand compiled 3.2.8 on RHEL 5. All versions behave the same and have the same issue. The issue: If you delete a Unix symlink via Samba that points to a directory full of files, it will not only delete the symlink, but also the files inside the pointed to subdirectory. The subdir remains intact, but now empty with no files. Any ideas? I am going to compile the latest and greatest Samba and put it on a test machine to see if it resolves the problem. Thanks -- Kathy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Deletion of directory symlink via Samba deletes files in original subdirectory on Unix
Hi Andy -- The directories are group owned by a bunch of engineers so all members of that group have permissions to delete all of it: symlink, subdir, and files in the subdir. If they do this on the Unix side, it only deletes the symlink and sometimes they have scripts on the Windows side that need to delete the symlinks, hence the issue we're seeing now. Kathy I don't have a solution to your problem, although I discovered a similar problem in Samba's behavior with symlinks to FILES. Getting good Level 10 logs was key to figuring out what the problem was -- and fixing it. That got fixed in 3.0.14 or 3.0.15 I believe. I myself make extensive use of symlinks to DIRECTORIES in my applications. If you're thinking about a workaround, here's a question: What are the permissions on the directories that the symlinks point to? If a user could directly see one of those directories, would he/she be able to delete it? Andy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Deletion of directory symlink via Samba deletes files in original subdirectory on Unix
My apologies for not getting back to you until now about this. Was out due to the holidays. We are using version 3.2.8 on RHEL 5.2. Kathy What version of Samba ? Jeremy This sounds a bit like the problem we (EditShare) discovered and that you patched a few years ago-- in the 3.0.14 days I think. Remember... We discovered a sort of delayed reaction. If you deleted a symlink to a file that some other user had open, when both users finally closed the file the FILE would get deleted rather than the SYMLINK. Could it be related? Maybe, it could *be* that problem, if the version they're running is old enough (which is why I asked :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Deletion of directory symlink via Samba deletes files in original subdirectory on Unix
Actually, that is only one of our servers. We have multiple Samba servers running here and it's possible that the folks are pointing at the 3.0.25a version our Solaris 10 ZFS server. The other possible server is version 3.0.33 running on RHEL 4. I know for a fact that the 3.0.25a version does it as I tested it out myself. Kathy On Mon, Nov 30, 2009 at 9:23 AM, Kathy banshee...@gmail.com wrote: My apologies for not getting back to you until now about this. Was out due to the holidays. We are using version 3.2.8 on RHEL 5.2. Kathy What version of Samba ? Jeremy This sounds a bit like the problem we (EditShare) discovered and that you patched a few years ago-- in the 3.0.14 days I think. Remember... We discovered a sort of delayed reaction. If you deleted a symlink to a file that some other user had open, when both users finally closed the file the FILE would get deleted rather than the SYMLINK. Could it be related? Maybe, it could *be* that problem, if the version they're running is old enough (which is why I asked :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Deletion of directory symlink via Samba deletes files in original subdirectory on Unix
I just confirmed that this problem exists on all our Samba servers, irregardless of version. Here is an example of how I'm testing it: On Unix SERVER I have a directory called /testdir/kathytest and inside of kathytest are file1, file2, and file3 Testdir is a Samba exported directory on SERVER. I create a soft link in /testdir to point to kathytest: ln -s ./kathytest ./testlink So now if I go to /testdir/testlink it will take me to /testdir/kathytest and I'll see file1, file2, and file3. Now, in Samba I go to \\SERVER\testdir and I see both the softlink testlink and my directory kathytest. Through Samba I delete \\SERVER\testdir\testlink. It then asks me from the Windows side Are you sure you want to remove the folder `testlink' and all its contents?. I say yes and it deleted the testlink symlink and deletes file1, file2, and file3 inside of kathytest. The subdir kathytest does not get deleted, however. This happens on both ext3 and zfs exported filesystems, so it's not just limited to ZFS. On Mon, Nov 30, 2009 at 9:27 AM, Kathy banshee...@gmail.com wrote: Actually, that is only one of our servers. We have multiple Samba servers running here and it's possible that the folks are pointing at the 3.0.25a version our Solaris 10 ZFS server. The other possible server is version 3.0.33 running on RHEL 4. I know for a fact that the 3.0.25a version does it as I tested it out myself. Kathy On Mon, Nov 30, 2009 at 9:23 AM, Kathy banshee...@gmail.com wrote: My apologies for not getting back to you until now about this. Was out due to the holidays. We are using version 3.2.8 on RHEL 5.2. Kathy What version of Samba ? Jeremy This sounds a bit like the problem we (EditShare) discovered and that you patched a few years ago-- in the 3.0.14 days I think. Remember... We discovered a sort of delayed reaction. If you deleted a symlink to a file that some other user had open, when both users finally closed the file the FILE would get deleted rather than the SYMLINK. Could it be related? Maybe, it could *be* that problem, if the version they're running is old enough (which is why I asked :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Deletion of directory symlink via Samba deletes files in original subdirectory on Unix
Hello -- We have a Solaris 10 ZFS server running Samba with follow symlinks=yes set. We're noticing that if you delete (via Samba) a file that is a symbolic link pointing to a subdirectory somewhere, with files in that subdir, it will not only delete the symbolic link file, but also delete the files in the target subdirectory. On Unix, if you delete a symbolic link, it will leave the original target subdir (and its files) untouched. This behavior only seems to happen if the symlink is pointing to a populated subdirectory. If you have a symlink that points to a file and delete the symlink via Samba, the original file remains intact. Does anyone know of a way to get around this particular behavior? We would like it to behave as in Unix. Only the symlink gets deleted and not the subdir/files it was pointing at. Thanks for the help -- Kathy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] can not access samba drive on Redhat ES 4
Hi, Our samba server is running Red Hat Enterprise Linux ES release 4 (Nahant Update 4) with samba version: samba-3.0.33-0.17.el4. We like to authenticate all the users with our Primary Domain Controller wnidows 2008. Some users keep getting asked to enter username and password. Even with the correct password, still can't access the drive. The strange thing is that some users are successful. These users all have valid accounts on windows. In this case user jrau is a valid user and JRAUXP is the PC name from which he is accessing the samba share. Wbinfo -u displays his username: STEC-INC=jrau But not the computer name, which makes me think that might be the problem. Also we are not using LDAP, just winbind. Here is some my config files and error logs: /var/log/samba/userlog: [2009/10/12 07:28:56, 0] lib/util_sock.c:read_data(534) read_data: read failure for 4 bytes to client .xxx.xx.xx. Error = Connection reset by peer [2009/10/12 07:28:56, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer [2009/10/12 07:28:56, 0] lib/util_sock.c:send_smb(761) Error writing 4 bytes to client. -1. (Connection reset by peer) [2009/10/12 07:47:19, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client xxx.xx.xx.xx. Error Connection reset by peer [2009/10/12 07:47:19, 0] lib/util_sock.c:send_smb(761) Error writing 4 bytes to client. -1. (Connection reset by peer) [2009/10/12 08:37:16, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client xxx.xx.xx.xx. Error Connection reset by peer [2009/10/12 08:37:16, 0] lib/util_sock.c:send_smb(761) Error writing 4 bytes to client. -1. (Connection reset by peer) [2009/10/12 12:11:02, 1] smbd/sesssetup.c:reply_spnego_kerberos(316) Failed to verify incoming ticket with error NT_STATUS_LOGON_FAILURE! - [2009/10/12 12:11:02, 0] lib/util_sock.c:read_data(534) read_data: read failure for 4 bytes to client xxx.x.xxx.xx. Error = Connection reset by peer [2009/10/13 10:26:30, 1] smbd/sesssetup.c:reply_spnego_kerberos(439) Username STEC-INC=jrau is invalid on this system [2009/10/13 10:26:30, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client xxx.xxx.xxx.xx. Error Connection reset by peer [2009/10/13 10:26:30, 0] lib/util_sock.c:send_smb(761) Error writing 4 bytes to client. -1. (Connection reset by peer) [2009/10/13 16:16:45, 0] lib/util_sock.c:read_data(534) read_data: read failure for 4 bytes to client xxx.xxx.xx.xx. Error = Connection reset by peer [2009/10/13 16:16:46, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client xxx.xx.xx.xx. Error Connection reset by peer [2009/10/13 16:16:46, 0] lib/util_sock.c:send_smb(761) Error writing 4 bytes to client. -1. (Connection reset by peer) [2009/10/13 16:51:19, 1] smbd/sesssetup.c:reply_spnego_kerberos(439) Username STEC-INC=JRAUXP$ is invalid on this system -- . Thank you for your help. Kathy PROPRIETARY-CONFIDENTIAL INFORMATION INCLUDED This electronic transmission, and any documents attached hereto, may contain confidential, proprietary and/or legally privileged information. The information is intended only for use by the recipient named above. If you received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of information received in error is strictly prohibited, and violators will be pursued legally. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] cli_session_setup: NT1 session setup failed: NT_STATUS_LOGON_FAILURE
MY OS is: Red Hat Enterprise Linux ES release 4 (Nahant Update 8) Samba version: samba-3.0.25b-0.4E.6 I'm map a share drive and I get asked for user name and password. Right now I'm just trouble shooting the samba part. smb service is running and winbind server is running too. The /var/log/samba/ log file has the following in it: libads/authdata.c:pac_io_pac_info_hdr_ctr(569) unknown PAC type 12 [2009/10/14 16:51:05, 3] smbd/sesssetup.c:reply_spnego_kerberos(321) Ticket name is [kkhagani...@stec-inc.ad] [2009/10/14 16:51:05, 1] smbd/sesssetup.c:reply_spnego_kerberos(439) Username STEC-INC=KKHAGANIXP$ is invalid on this system [2009/10/14 16:51:05, 3] smbd/error.c:error_packet_set(106) error packet at smbd/sesssetup.c(444) cmd=115 (SMBsesssetupX) NT_STATUS_LOGON_FAILURE [2009/10/14 16:51:05, 3] smbd/process.c:process_smb(1068) Transaction 3 of length 1854 [2009/10/14 16:51:05, 3] smbd/process.c:switch_message(926) switch message SMBsesssetupX (pid 31213) conn 0x0 [2009/10/14 16:51:05, 3] smbd/sec_ctx.c:set_sec_ctx(241) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2009/10/14 16:51:05, 3] smbd/sesssetup.c:reply_sesssetup_and_X(1244) wct=12 flg2=0xc807 [2009/10/14 16:51:05, 2] smbd/sesssetup.c:setup_new_vc_session(1200) setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources. [2009/10/14 16:51:05, 3] smbd/sesssetup.c:reply_sesssetup_and_X_spnego(1029) Doing spnego session setup [2009/10/14 16:51:05, 3] smbd/sesssetup.c:reply_sesssetup_and_X_spnego(1060) NativeOS=[Windows 2002 Service Pack 3 2600] NativeLanMan=[Windows 2002 5.1] PrimaryDomain=[] [2009/10/14 16:51:05, 3] smbd/sesssetup.c:reply_spnego_negotiate(697) reply_spnego_negotiate: Got secblob of size 1623 [2009/10/14 16:51:05, 3] libads/authdata.c:pac_io_pac_info_hdr_ctr(569) unknown PAC type 12 [2009/10/14 16:51:05, 3] smbd/sesssetup.c:reply_spnego_kerberos(321) Ticket name is [kkhag...@stec-inc.ad] [2009/10/14 16:51:05, 1] smbd/sesssetup.c:reply_spnego_kerberos(439) Username STEC-INC=kkhagani is invalid on this system [2009/10/14 16:51:05, 3] smbd/error.c:error_packet_set(106) error packet at smbd/sesssetup.c(444) cmd=115 (SMBsesssetupX) NT_STATUS_LOGON_FAILURE [2009/10/14 16:51:05, 3] smbd/process.c:timeout_processing(1328) timeout_processing: End of file from client (client has disconnected). [2009/10/14 16:51:05, 3] smbd/sec_ctx.c:set_sec_ctx(241) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2009/10/14 16:51:05, 3] smbd/connection.c:yield_connection(69) Yielding connection to [2009/10/14 16:51:05, 3] smbd/server.c:exit_server_common(768) Server exit (normal exit) [2009/10/14 16:51:06, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client xxx.xxx.xxx.xxx. Error Connection reset by peer [2009/10/14 16:51:06, 0] lib/util_sock.c:send_smb(769) Error writing 4 bytes to client. -1. (Connection reset by peer) [2009/10/14 16:51:06, 3] smbd/sec_ctx.c:set_sec_ctx(241) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2009/10/14 16:51:06, 3] smbd/connection.c:yield_connection(69) Yielding connection to [2009/10/14 16:51:06, 3] smbd/connection.c:yield_connection(76) yield_connection: tdb_delete for name failed with error Record does not exist. [2009/10/14 16:51:06, 3] smbd/server.c:exit_server_common(768) Server exit (process_smb: send_smb failed.) [2009/10/14 16:51:06, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer [2009/10/14 16:51:06, 0] lib/util_sock.c:send_smb(769) Error writing 4 bytes to client. -1. (Connection reset by peer) [2009/10/14 16:51:06, 3] smbd/sec_ctx.c:set_sec_ctx(241) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2009/10/14 16:51:06, 3] smbd/connection.c:yield_connection(69) Yielding connection to [2009/10/14 16:51:06, 3] smbd/connection.c:yield_connection(76) yield_connection: tdb_delete for name failed with error Record does not exist. [2009/10/14 16:51:06, 3] smbd/server.c:exit_server_common(768) Server exit (process_smb: send_smb failed.) Also the following command results: #smbclient -d 4 -U kkhagani -W STEC-INC -L ldaptest Connecting to xxx.xxx.xx.xxx at port 445 session request ok Password: cli_session_setup: NT1 session setup failed: NT_STATUS_LOGON_FAILURE session setup failed: NT_STATUS_LOGON_FAILURE Any information and suggestion is greatly appreciated. Regards, Kathy PROPRIETARY-CONFIDENTIAL INFORMATION INCLUDED This electronic transmission, and any documents attached hereto, may contain confidential, proprietary and/or legally privileged information. The information is intended only for use by the recipient named above. If you received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of information received in error is strictly prohibited, and violators will be pursued legally
Re: [Samba] File locking problem involving Samba, Clearcase, and Cygwin
I wanted to send a final post about this issue. I apologise for not responding until 2 months later. For those interested, we ended up just writing our logs to a Samba share that was outside of a Clearcase share and we had no further issues with files being locked. So that says that Clearcase did indeed have something to do with the issue in how it was playing with Samba, but having them write logs to another location was a lot easier solution than trying to debug it further. Our engineering department has tight schedules, so we went with the easy fix. I am still using the version of Samba that Jeremy suggested (3.2.8) but I suspect that it would have worked okay with the original 3.0.28 if we were writing elsewhere than the Clearcase view. Thanks for all the help you gave me back in February about this problem. I do appreciate it. Kathy On Tue, Feb 10, 2009 at 7:56 PM, Jeremy Allison j...@samba.org wrote: On Tue, Feb 10, 2009 at 02:24:10PM -0800, Kathy wrote: I wanted to post again with the results of using Samba 3.2.8. Looks like this did not solve our locking problem. We are still getting permission denied errors when we try to do a mv of a log file inside a Clearcase view via a Samba share to a different location. Again, this is inside a Cygwin window on a WindowsXP virtual machine. It is referencing a Clearcase dynamic view via Samba on //server/view_name. It does not matter if you try to move it to another Clearcase view (i.e. //server/views/ccase_view_name/dir) or if you try to move it to a Windows share or even to the local drive. Below is a snippet of what the Samba log shows when these two files can't be moved. ProcessExplorer program on the Windows XP machine did not show file handle holding on to either of these files. Smbstatus on the RHEL 5.2 Clearcase/Samba server reported NONE for oplocks, WRONLY for R/W, and DENY_NONE on DenyMode. We are now running new tests where the scripts are writing the logs to a Samba share, but not to a share that is also a Clearcase view. And if we still have issues we are going to then have the logs write to a local drive, leaving Samba completely out of it for the part of writing logs. (They will still be inside the CC view via Samba when firing off their scripts.) Ok, thanks for testing with the latest code. As Volker mentioned, what we need now if for you to test this against a Windows 2003 or 2008 server and see if this reproduces the problem. If not, a wireshark network trace of it working correctly against Windows 200[3|8] and it not working correctly against Samba 3.2.8 is needed. Thanks a lot, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] File locking problem involving Samba, Clearcase, and Cygwin
I wanted to post again with the results of using Samba 3.2.8. Looks like this did not solve our locking problem. We are still getting permission denied errors when we try to do a mv of a log file inside a Clearcase view via a Samba share to a different location. Again, this is inside a Cygwin window on a WindowsXP virtual machine. It is referencing a Clearcase dynamic view via Samba on //server/view_name. It does not matter if you try to move it to another Clearcase view (i.e. //server/views/ccase_view_name/dir) or if you try to move it to a Windows share or even to the local drive. Below is a snippet of what the Samba log shows when these two files can't be moved. ProcessExplorer program on the Windows XP machine did not show file handle holding on to either of these files. Smbstatus on the RHEL 5.2 Clearcase/Samba server reported NONE for oplocks, WRONLY for R/W, and DENY_NONE on DenyMode. We are now running new tests where the scripts are writing the logs to a Samba share, but not to a share that is also a Clearcase view. And if we still have issues we are going to then have the logs write to a local drive, leaving Samba completely out of it for the part of writing logs. (They will still be inside the CC view via Samba when firing off their scripts.) Kathy [2009/02/10 09:09:31, 3] smbd/sec_ctx.c:set_sec_ctx(324) setting sec ctx (20191, 1600) - sec_ctx_stack_ndx = 0 [2009/02/10 09:09:31, 3] smbd/dosmode.c:unix_mode(124) unix_mode(turbo_verification_2/vobs/c2test/C2Testsuite/magellan.sum) returning 0664 [2009/02/10 09:09:31, 3] smbd/error.c:error_packet_set(61) error packet at smbd/nttrans.c(532) cmd=162 (SMBntcreateX) NT_STATUS_SHARING_VIOLATION [2009/02/10 09:09:31, 3] smbd/process.c:process_smb(1550) Transaction 29647671 of length 238 (0 toread) [2009/02/10 09:09:31, 3] smbd/process.c:switch_message(1361) switch message SMBtrans2 (pid 5039) conn 0x927e338 [2009/02/10 09:09:31, 3] smbd/trans2.c:call_trans2qfilepathinfo(3929) call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004 [2009/02/10 09:09:31, 3] smbd/trans2.c:call_trans2qfilepathinfo(4043) call_trans2qfilepathinfo turbo_verification_3/vobs/c2test/C2Testsuite/mModeBasicMsrmnt_C25_ICT_NTSC.sum (fnum = -1) level=1004 call=5 total_data=0 [2009/02/10 09:09:31, 3] smbd/process.c:process_smb(1550) Transaction 29647672 of length 238 (0 toread) [2009/02/10 09:09:31, 3] smbd/process.c:switch_message(1361) switch message SMBtrans2 (pid 5039) conn 0x927e338 [2009/02/10 09:09:31, 3] smbd/trans2.c:call_trans2qfilepathinfo(3929) call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004 [2009/02/10 09:09:31, 3] smbd/trans2.c:call_trans2qfilepathinfo(4043) call_trans2qfilepathinfo turbo_verification_3/vobs/c2test/C2Testsuite/mModeBasicMsrmnt_C25_ICT_NTSC.sum (fnum = -1) level=1004 call=5 total_data=0 [2009/02/10 09:09:31, 3] smbd/process.c:process_smb(1550) snip [2009/02/10 09:09:33, 3] smbd/dosmode.c:unix_mode(124) unix_mode(turbo_verification_3/vobs/c2test/C2Testsuite/mModeBasicMsrmnt_C25_ICT_NTSC.sum) returning 0664 [2009/02/10 09:09:33, 3] smbd/error.c:error_packet_set(61) error packet at smbd/nttrans.c(532) cmd=162 (SMBntcreateX) NT_STATUS_SHARING_VIOLATION [2009/02/10 09:09:33, 3] smbd/process.c:process_smb(1550) Transaction 29647927 of length 206 (0 toread) [2009/02/10 09:09:33, 3] smbd/process.c:switch_message(1361) switch message SMBntcreateX (pid 5039) conn 0x927e338 [2009/02/10 09:09:33, 3] smbd/dosmode.c:unix_mode(124) On 2/6/09, Brian Cowan brco...@gmail.com wrote: Kathy, I work in ClearCase support, and this construct is not supported by IBM. It's not a tested configuration. There is a mechanism -- export_mvfs -- that allows hosts that do not have ClearCase installed to access files in dynamic views via NFS. You are trying to accomplish the same thing by sharing the MVFS root (/view -- translation for non-CC people: Think path=/net). Is there a pressing reason for doing this? Wouldn't it be simpler to install ClearCase on the PC's and access the files through the Windows-Native MVFS (which in turn would access the VOBs on your VOB server)? That being said, I doubt that it's the MVFS confusing Samba, but it is possible. If this turns out to be a load-related issue, the MVFS may show this issue more often because it does a lot more under the hood than most filesystems (version selection, getting cleartext constructed, etc). I would recommend testing to see if you can make the same thing happen with files in: 1) A local filesystem 2) a remote NFS-mounted filesystem. You may need to increase the load on the Samba server 2-fold or more to get it to fall over in the same way, but definitely try. If so, then ClearCase has been eliminated from the picture and you can start trying various debugging tricks to see why Samba thinks some users have oplocks when they shouldn't. By the way, I suspect
Re: [Samba] File locking problem involving Samba, Clearcase, and Cygwin
Thanks, Jeremy and Brian for your responses. First Jeremy -- I think I will first pursue with Brian a solution that uses a version of Samba that is at least more in line with what IBM has tested with Clearcase, but if it really does look like the issue is with Samba, I have no problem at least compiling a newer version and seeing if the issue goes away. Thanks for the suggestion. Brian -- I'll send you the PMR in a private email and we can discuss the Clearcase specifics off the Samba list. I have suggested to our test group probably at least 3 times to get them to put their logs on a local filesystem or Windows server share but they have never done the test for me (to my huge frustration) because of the perceived effort involved in modifying their scripts. I agree that it's a test that needs to be done and I will have to just be adamant about it this week. On 2/6/09, Brian Cowan brco...@gmail.com wrote: Kathy, I work in ClearCase support, and this construct is not supported by IBM. It's not a tested configuration. There is a mechanism -- export_mvfs -- that allows hosts that do not have ClearCase installed to access files in dynamic views via NFS. You are trying to accomplish the same thing by sharing the MVFS root (/view -- translation for non-CC people: Think path=/net). Is there a pressing reason for doing this? Wouldn't it be simpler to install ClearCase on the PC's and access the files through the Windows-Native MVFS (which in turn would access the VOBs on your VOB server)? That being said, I doubt that it's the MVFS confusing Samba, but it is possible. If this turns out to be a load-related issue, the MVFS may show this issue more often because it does a lot more under the hood than most filesystems (version selection, getting cleartext constructed, etc). I would recommend testing to see if you can make the same thing happen with files in: 1) A local filesystem 2) a remote NFS-mounted filesystem. You may need to increase the load on the Samba server 2-fold or more to get it to fall over in the same way, but definitely try. If so, then ClearCase has been eliminated from the picture and you can start trying various debugging tricks to see why Samba thinks some users have oplocks when they shouldn't. By the way, I suspect that you have a case open with us about this issue, if so, can you send me the PMR number? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] File locking problem involving Samba, Clearcase, and Cygwin
We are having some problems in our company's test group that did not exist when our Clearcase 2003.06 server existed on a Solaris 8 machine. Now we are running on RHEL 5.2 with Clearcase 7.0.1.3 with Samba 3.0.28 (despite the fact that IBM has only blessed up to 3.0.24) and running into some file locking issues with some scripts our test group runs. I am hoping that someone might have some ideas. The environment is this: Our test group has a PC that runs VMWare virtual machines (Windows XP). They log into one of the virtual Win XP machines and pop several Cygwin windows running bash. They have several Clearcase views that they might use at the same time but each view used is in a different Cygwin window. The views are located on a RHEL 5.2 Clearcase server named Flint running Samba 3.0.28. So, in each Cygwin window, they will cd //flint/views/view_name/vobs/c2test/C2Testsuite and in there they run some scripts that write to logs called magellan.log and magellan.sum. They are essentially using the views as a file server for their test scripts. They often run these scripts from different views at the same time, and each script that runs runs multiple sequential tests. Inside the master script (simple bourne shell), after a test is complete, it closes out the magellan.log (and .sum) files and does a mv to rename the file so the next iteration can use the same name for the log file. (Yeah, it would be easier to just make them unique names for each run, but this is old legacy stuff that would be a pain in the kazoo to change, so for the moment we're trying to just fix it before redesigning it all). What's happening is at random times, the mv command fails and they get permission denied because another process is holding on to the script and sometimes in the Samba log I will see NT_STATUS_SHARING_VIOLATION, which can make sense if another process has a lock on the file. In our smb.conf file, I have oplocks turned off because IBM requires this for Clearcase: # first statement is old and may not be obsolete but we still keep it just in case oplocks = no kernel oplocks = no level2 oplocks = no However, as shown below, we're seeing oplocks reported and I have no idea whether this is normal or not. I asked a Clearcase support guy and he did not know (sigh). So hence I'm hoping someone here has some experience with this. Again, we ran this same sort of set up before with a Solaris Clearcase/Samba server and we didn't see these problems. This may not be related to Clearcase at all and simply and issue of how file locking is working between RHEL 5.2 and Samba. What exactly is a LEVEL_II oplock and why am I seeing these if I have Samba oplocks turned off? Other than this, Clearcase is operating normally and Samba is operating normally on Flint for all other applications. It's just this situation where we're running these sequential scripts sitting in side the Clearcase view via Samba. Thanks for any insight -- Kathy Locked files: Pid UidDenyMode Access R/WOplock Share Path Name Time -- 1282520191 DENY_NONE 0x20196 WRONLY NONE /view turboS_verification_1/vobs/c2test/C2Testsuite/magellan.log Thu Jan 15 04:40 :30 2009 1282520191 DENY_NONE 0x20196 WRONLY EXCLUSIVE+BATCH /view turboS_verification_2/vobs/c2test/C2Testsuite/cozushell.cvf Thu Jan 15 05:1 5:59 2009 1282520191 DENY_NONE 0x20089 RDONLY NONE /view turboS_verification_4/vobs/c2test/C2Testsuite/magellan.she ll/S6_PU Wed Jan 14 18:00:20 2009 1282520191 DENY_NONE 0x20089 RDONLY NONE /view turboS_verification_1/vobs/c2test/C2Testsuite/magellan.she ll/TURBOS_TESTSUITE Wed Jan 14 17:54:21 2009 1282520191 DENY_NONE 0x20089 RDONLY LEVEL_II /view turboS_verification_1/vobs/c2test/C2Testsuite/magellan.she ll/TURBOS_TESTSUITE Wed Jan 14 17:56:41 2009 1282520191 DENY_NONE 0x20089 RDONLY LEVEL_II /view turboS_verification_1/vobs/c2test/C2Testsuite/magellan.she ll/TURBOS_TESTSUITE Wed Jan 14 17:57:23 2009 1282520191 DENY_NONE 0x20196 WRONLY NONE /view turboS_verification_4/vobs/c2test/C2Testsuite/cozushell.cv f Thu Jan 15 04:29:34 2009 1282520191 DENY_NONE 0x20196 WRONLY NONE /view turboS_verification_4/vobs/c2test/C2Testsuite/magellan.sum Thu Jan 15 04:29:34 2009 1282520191 DENY_NONE 0x20196 WRONLY NONE /view turboS_verification_1/vobs/c2test/C2Testsuite/magellan.sum Thu Jan 15 04:40:30 2009 1282520191 DENY_NONE 0x20196 WRONLY NONE /view turboS_verification_2/vobs/c2test/C2Testsuite/magellan.log Thu Jan 15 05:15:59 2009 1282520191 DENY_NONE 0x20196 WRONLY
Re: [Samba] File locking problem involving Samba, Clearcase, and Cygwin
Thanks for the reply Rob. That was my assumption that oplocks=no overrides everything (but put them all in there just in case). The Samba shares are all related to Clearcase, which is why we have oplocks definitions under global instead of individual shares. (Although I suppose the home directories don't apply to that statement I just made.) Originally we were using ads authentication instead of domain, but IBM wanted it changed to domain because that's what they claim to support for Clearcase. It didn't make any difference in how Samba is behaving. They also insisted on a username.map for the clearcase_albd account. Before that, we didn't have one due to authenticating to our Active Directory server. [r...@flint samba]# testparm Load smb config files from /etc/samba/smb.conf Processing section [homes] Processing section [vobstore] Processing section [scriptlogs] Processing section [vws] Processing section [views] Loaded services file OK. WARNING: You have some share names that are longer than 12 characters. These may not be accessible to some older clients. (Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.) Server role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions [global] workgroup = company realm = company.COM server string = Flint Samba Server security = DOMAIN password server = domain server name username map = /etc/samba/username.map log level = 2 log file = /var/log/samba/log.%m max log size = 0 deadtime = 15 dns proxy = No kernel oplocks = No lock directory = /var/log/samba/locks host msdfs = No invalid users = @root, @wheel, @bin, @sys, @admin create mask = 0775 directory mask = 0775 case sensitive = No map archive = No oplocks = No level2 oplocks = No dont descend = /proc,/dev fake directory create times = Yes [homes] comment = Home Directories read only = No create mask = 0755 browseable = No [vobstore] comment = vobstore path = /vobs write list = @cozcmusr read only = No [scriptlogs] comment = Flint /scriptlogs path = /vandv/scriptlogs write list = @cozcmusr read only = No [vws] comment = Flint /vws path = /vandv/vws write list = @cozcmusr read only = No [views] comment = Flint views path = /view read list = @cozcmusr, aramac write list = @cozcmusr read only = No On Fri, Feb 6, 2009 at 1:23 PM, Rob Shinn rob.sh...@gmail.com wrote: snip Note that oplocks parameter should be set per share. Please post the output of your 'testparm' command. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] File locking problem involving Samba, Clearcase, and Cygwin
Based on what Rob said (and what I'm reading about oplocks in the Using Samba guide), I decided to put the oplocks = no into each individual share. I won't know until Monday until the test group tries some test runs if it makes any difference or not. I was assuming if in global it would be applied to all shares, but perhaps that's not the case. So we'll see. Kathy [r...@flint samba]# testparm Load smb config files from /etc/samba/smb.conf Processing section [homes] Processing section [vobstore] Processing section [scriptlogs] Processing section [vws] Processing section [views] Loaded services file OK. WARNING: You have some share names that are longer than 12 characters. These may not be accessible to some older clients. (Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.) Server role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions [global] workgroup = company realm = company.COM server string = Flint Samba Server security = DOMAIN password server = domain server name username map = /etc/samba/username.map log level = 2 log file = /var/log/samba/log.%m max log size = 0 deadtime = 15 dns proxy = No kernel oplocks = No lock directory = /var/log/samba/locks host msdfs = No invalid users = @root, @wheel, @bin, @sys, @admin create mask = 0775 directory mask = 0775 case sensitive = No map archive = No oplocks = No level2 oplocks = No dont descend = /proc,/dev fake directory create times = Yes [homes] comment = Home Directories read only = No create mask = 0755 browseable = No [vobstore] comment = vobstore path = /vobs write list = @cozcmusr read only = No [scriptlogs] comment = Flint /scriptlogs path = /vandv/scriptlogs write list = @cozcmusr read only = No [vws] comment = Flint /vws path = /vandv/vws write list = @cozcmusr read only = No [views] comment = Flint views path = /view read list = @cozcmusr, aramac write list = @cozcmusr read only = No -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Slowness problems with Samba 3.0.1, Solaris, and Clearcase
Hello -- I recently installed Samba 3.0.1 on our Solaris 8 servers (as well as our RedHat servers) and I wanted to see if I could get some feedback on a few things. We are using Samba in conjunction with Clearcase for our software developers and because of that, we have oplocks turned off (also level2 oplocks = no as well). We are authenticating to our ADS server, but joining the domain with security=domain. We are seeing that initial authentication tends to be slow, and we see log files of the sort of log.38.255.38.1 being created as it does initial setup. Then after authenticating, these logs are closed and we start seeing logs based on the hostname of the pc (i.e. log.kkostpc). I had not noticed this type of logging before we started using security=domain. In the past we used security=server, but had problems and have since noticed the docs warning against using this. Is this typical behavor when initially authenticating a connection? I'm concerned about why the initial authentication slowness. Also, one of our developers saw a huge increase in the amount of time to build a dynamic Clearcase view (12 hours instead of the usual 6 hours). This may be an unrelated problem, but I thought I'd mention it. I'm also seeing the following errors and would like to know some info about them. THe first is: [2004/01/03 10:49:26, 0] lib/util_sock.c:set_socket_options(160) Failed to set socket option SO_KEEPALIVE (Error Invalid argument) I noticed that SO_KEEPALIVE is compiled by default into Samba, and on Solaris it is on by default. The value of tcp_keepalive_interval is 720. I can change this value, but don't want to mess with it unless I'm really sure of what I'm doing. Why the invalid argument error? Next one is this: [2004/01/10 00:06:12, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 0, length 922337203685477900 0 returned [2004/01/10 00:06:12, 0] locking/posix.c:posix_fcntl_lock(658) an Invalid argument error. This can happen when using 64 bit lock offsets [2004/01/10 00:06:12, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit NFS mounted file systems. [2004/01/10 00:06:12, 0] locking/posix.c:posix_fcntl_lock(673) Count greater than 31 bits - retrying with 31 bit truncated length. I got a lot more of these before I turned oplocks off. My assumption so far is that this is probably not a major problem and due to the client requesting an invalid lock request address. I am not sharing out any NFS files systems, though, so I sometimes wonder where this is coming from. I see in the docs that on unix, Samba assumes 32 bit lock offsets, even when compiled on a 64 bit machine. Any more info on this would be helpful. And finally, here is the last: [2004/01/12 09:54:48, 0] lib/util_sock.c:set_socket_options(160) Failed to set socket option TCP_NODELAY (Error Invalid argument) [2004/01/12 09:54:48, 0] lib/util_sock.c:get_peer_addr(948) getpeername failed. Error was Transport endpoint is not connected [2004/01/12 10:16:45, 0] smbd/server.c:open_sockets_smbd(377) open_sockets_smbd: accept: Software caused connection abort (Note: I get the getpeername failed error also on RedHat, but not the keepalive or tcpdelay errors) Again, not sure why the failure to set this option. Any clues on this is appreciated. Thanks for the help on any of these subjects. Kathy -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Problem with Samba on Home Network
I have Samba set up on my Gentoo Linux Box. Our access to the internet is through a broadband modem/router. Internet access in all instances is fine. The problem is that one computer is not showing up in even its own Network Neighborhood. I can access the files on this computer though from the other computer. Samba setup is as follows: The Gentoo Linux box Computer A running samba server: ip 192.168.0.b broadcast 255.255.255.0 Windows ME setup through Win4Lin on Computer A ip 192.168.0.d broadcast 255.255.255.0 These both show up in the Network Neighborhood of the Win4Lin desktop. Can access computer B if do add network \\computername\c Husband's ME computer computer B: ip 192.168.0.c broadcast 255.255.255.0. Computer A and the Win4Lin files are accessible in this network neighborhood. This computer does not show up in the network neighborhood. He is able to use the printer that is attached to computer A. All have the same group name. Computer B has been added as a machine to Samba. What have I got wrong? Attached is a copy of my smb.conf. -- Kathy Wills + + Genealogy Web Site: http://www.kathywillsfamily.com + + + + # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Date: 2003/03/03 23:44:42 # Global parameters [global] workgroup = MDKGROUP netbios name = GUNGHOLADY encrypt passwords = Yes security = user os level = 65 preferred master = yes domain master = yes local master = yes logon path = \\%n\profiles\%u logon drive = h: logon home = \\gungholady\%u printcap name = cups wins support = yes [netlogon] path = /var/lib/samba/netlogon guest ok = yes writeable = no share modes = no [homes] read only = No browseable = No [music] path = /data/mp3 browseable = yes write list = phil, kathy [everyone] path = /data/everyone read only = no browseable = yes [apps] path = /data/apps browseable = yes valid users = @admins, root write list = @admins, root [printers] comment = Canon BJC6000 path = /var/spool/samba create mask = 0700 printable = Yes print command = lpr -l -r -P%d %s # using client side printer drivers. printer name = Canon_BJC6000 browseable = No -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Intermittent problems copying files
We are using SAMBA 2.2.7 on a Solaris 8 so that we can utilize the Solaris Computer as a PDF file server on our Windows 2000 network. We get intermittent error messages when copying files to a SAMBA share. It does not happen every time nor can we get the error twice on the same file and it is not always the same error message. The error messages we get are as follows: Cannot copy [file]: an unexpected network error occurred Cannot copy [file]: The session was cancelled Has anyone else experienced this problem? If so, how did you fix the problem? I previously included the configuration file, but it made this message too big and needed to go through moderator. I can provided a cut down version if need be. Thanks for the assistance. Kathy M. Pavelock IAC Support Team Engineering Applications Division Alion Science and Technology 201 Mill Street Rome, NY 13440 (315)339-7128 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printer
Hello, I am using Samba 2.2.3a on a Solaris 2.8 machine, I have this message on my printer setting status column (Access denied, unable to connect), I still can print, but could not check the queue or see anything show up on the queue when I print. Kathy Chan 800 Tower Drive Troy, MI 48098 Mail Stop: 5276 * phone: 248-265-7229 (8-365) * mailto:[EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
