Re: [Samba] samba 3.0.26a-1 / Debian/Lenny sendfile(?) performance problems
Am Samstag, 29. September 2007 20:00 schrieb Justin Piszcz: > Package: samba > Version: 3.0.26a-1 > > Kernel: 2.6.22 > > samba 3.0.26a-1 performance < 900 KiB/s, but FTP = 30-90 MiB/s > > Let me start out by saing this is an oddball problem: > > SAMBA: > LINUX -> WINDOWS = < 900 KiB/s (varies between 100 - 900 KiB/s) > WINDOWS -> LINUX = 30-90 MiB/s (always) > > FTP: > Either direction, 30-90 MiB/s (always) > > I do not see any nasty errors in the logs even with verbose = 5. > > Any ideas here? I am not using any special options. > > # cat /etc/samba/smb.conf > > [global] > log level = 5 > workgroup = WORKGROUP > server string = %h - Pentium IV 3.4GHZ > security = user > encrypt passwords = true > > [user] >comment = user >path= /home/user >writable= yes >valid users = user >create mask = 644 > > -- > > Here, FTP for pulling files from Linux. > > ftp> mget * > 200 TYPE is now 8-bit binary > 200 PORT command successful > 150-Connecting to port 1255 > 150 715924.0 kbytes to download > 226-File successfully transferred > 226 13.687 seconds (measured here), 51.08 Mbytes per second > ftp: 733106176 bytes received in 13.69Seconds 53562.23Kbytes/sec. > 200 PORT command successful > 150-Connecting to port 1256 > 150 716272.0 kbytes to download > 226-File successfully transferred > 226 13.032 seconds (measured here), 53.67 Mbytes per second > ftp: 733462528 bytes received in 13.05Seconds 56216.95Kbytes/sec. > 200 PORT command successful > 150-Connecting to port 1257 > 150 713200.0 kbytes to download > 226-File successfully transferred > 226 12.869 seconds (measured here), 54.12 Mbytes per second > ftp: 730316800 bytes received in 12.88Seconds 56723.63Kbytes/sec. > > Here, FTP for pushing files to Linux. > > ftp> mput 1 2 3 > 200 PORT command successful > 150 Connecting to port 1263 > 226-File successfully transferred > 226 12.802 seconds (measured here), 54.61 Mbytes per second > ftp: 733106176 bytes sent in 12.80Seconds 57287.35Kbytes/sec. > 200 PORT command successful > 150 Connecting to port 1264 > 226-File successfully transferred > 226 12.949 seconds (measured here), 54.02 Mbytes per second > ftp: 733462528 bytes sent in 12.95Seconds 56624.92Kbytes/sec. > 200 PORT command successful > 150 Connecting to port 1265 > 226-File successfully transferred > 226 15.400 seconds (measured here), 45.23 Mbytes per second > ftp: 730316800 bytes sent in 15.38Seconds 47500.28Kbytes/sec. > > But (all I can offer is packet dumps/traces or bandwidth measurements): > > Incoming: Outgoing: > Curr: 0.00 MByte/s Curr: 0.07 MByte/s > Avg: 0.00 MByte/s Avg: 0.07 MByte/s > Min: 0.00 MByte/s Min: 0.07 MByte/s > Max: 0.00 MByte/s Max: 0.07 MByte/s > Ttl: 1898.08 MByte Ttl: 2954.92 MByte > > LOCAL <-> REMOTE TXBPS RXBPS > TOTALBPS > (IP) PORT PROTO (IP) PORT TX RX > TOTAL > linuxbox <-> p4w.internal.lan 546k/s 4.74k/s 551k/s > 192.168.0.1 445TCP 192.168.0.212596.88m106k 6.99m > > Why do I get such poor performance when trying to retrieve a file off the > Linux box? This is a very strange problem. > > Linux: > > $ netstat -i > Kernel Interface table > Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR > Flg > eth0 1500 0 14049682 0 0 0 11354070 0 0 0 > BMRU > lo16436 0 45335 0 0 045335 0 0 0 LRU > > Windows: > > netstat -s > > IPv4 Statistics > >Packets Received = 5053597 >Received Header Errors = 0 >Received Address Errors= 19 >Datagrams Forwarded= 0 >Unknown Protocols Received = 0 >Received Packets Discarded = 2 >Received Packets Delivered = 5053595 >Output Requests= 3655144 >Routing Discards = 0 >Discarded Output Packets = 0 >Output Packet No Route = 0 >Reassembly Required= 0 >Reassembly Successful = 0 >Reassembly Failures= 0 >Datagrams Successfully Fragmented = 0 >Datagrams Failing Fragmentation= 3 >Fragments Created = 0 > > ICMPv4 Statistics > > ReceivedSent >Messages 47 24 >Errors0 0 >Destination Unreachable 25 2 >Time Exceeded 0 0 >Parameter Problems0 0 >Source Quenches 0 0 >Redirects 0 0 >Echos 0 22 >Echo Replies 22
Re: [Samba] wbinfo -u fails on RHEL5
Matthew Nelson wrote: make sure that you have ntp setup to sync with your DC and do a 'net time set' I'm aware of the Kerberos time requirements and do a 'net time set -S w.x.y.z' with the ADS from cron.hourly, so this is not the issue. I can join the domain, which uses Kerberos, so Kerberos is happy. I can also do 'kinit [EMAIL PROTECTED]', but 'smbclient -k ...' fails, 'wbinfo -u' returns nothing and login doesn't work since the username isn't found. I'm beginning to suspect that it is an ADS configuration issue and has something to do with how I define security groups, which causes winbindd to blow up. So, I'm going to try the latest version of Samba and see how that goes, if I can just figure out how to compile the thing with the options that RedHat needs. Anyhoo, glad to hear that it is stable for you, so it must be something I do different in the configuration. Cheers, H. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] wbinfo -u fails on RHEL5
i run centos5 on several machines, that all auth via active directory. i've found that they will occasionally fail because of a slight change in the time. make sure that you have ntp setup to sync with your DC and do a 'net time set' On 9/30/07, herman <[EMAIL PROTECTED]> wrote: > > Hi guys, > > Pulling my hair out... > > Version: RHEL5 straight off the CDs, no patches. > Active Directory: Win2003 with SP2 > > I'm experiencing confusing problems when logging onto an Active > Directory system. I have gotten it to work perfectly, but after a few > days/weeks it screws up for no apparent reason. Windows XP clients > still work perfectly. Linux clients show signature and packet errors, > 'wbinfo -u' is unable to retrieve user information and login fails. > > I have installed everything from scratch on a test machine on Friday and > it fails right off the bat with the same errors as the systems that > worked before. I am now installing the whole kettle of fish on VMware > so I can experiment better. > > Has anyone seen this and know where I should start digging? > > Cheers, > > Herman > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] wbinfo -u fails on RHEL5
Hi guys, Pulling my hair out... Version: RHEL5 straight off the CDs, no patches. Active Directory: Win2003 with SP2 I'm experiencing confusing problems when logging onto an Active Directory system. I have gotten it to work perfectly, but after a few days/weeks it screws up for no apparent reason. Windows XP clients still work perfectly. Linux clients show signature and packet errors, 'wbinfo -u' is unable to retrieve user information and login fails. I have installed everything from scratch on a test machine on Friday and it fails right off the bat with the same errors as the systems that worked before. I am now installing the whole kettle of fish on VMware so I can experiment better. Has anyone seen this and know where I should start digging? Cheers, Herman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Linux in a Windows 2k3 domain - odd lockout issue
Christopher Dick wrote: I am currently running an openSuSE 10.2 machine in a Windows 2k3 domain. I have upgraded to Samba 3.0.26a, hoping it would solve my issue, but so far no luck. I was successful in adding my machine to the domain, and the DC logs show repeated successful authentications, and those few typo'd attempts, but nothing that is a sequence of failed logins. I get tickets and can access shares from machines all over the network without needing to re-authenticate. The problem is, at approx. 3:30 every afternoon, the domain controller locks my user ID as if I had failed repeatedly to type in the correct password. Though the DC does not show this in the logs. I only know of logon hours under the user account on the AD. Maybe your systems require a more frequent machine password change than one week. It would be helpful to know what steps you take to re-enable the account or how long you have to wait. Does samba manage the keytab or did you manually add the kerberos keytab principals? Regards, Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Authentication Question; WAS: installing Samba as non-root user
On Wed, 2007-09-26 at 11:39 -0700, [EMAIL PROTECTED] wrote: > It's amazing how indignant people get when they think someone hasn't > done > his homework. I've read the man pages in depth, and the official > HOWTO. > Unless I overlooked something, no where does it explain the > authentication > in the kind of detail that is necessary to understand if there's a way > to > have multiple users have proper access to their home directories when > the > daemon is not being run as root. You will not find this knowledge in the Samba material simply because it is basic unix architecture knowledge. In unix only root owned process (modulo SELinux) can change privileges. File access is controlled by the kernel and based on said privileges. So logical consequence is: 1. no root -> no change in privileges -> no access to files beyond existing privileges 2. root -> impersonation (change in privileges) -> access to files with provided privileges For the password part, I only say that authentication is not magic, it is just an exchange of information (usually involving encryption of some sort to protect said information) to establish a remote process is who it claim it is (or represent). If your app performs authentication, it is the only one that knows about it, and unless it has mighty powers (root) it can't force the rest of the system to believe it. Simo. -- Simo Sorce Samba Team GPL Compliance Officer email: [EMAIL PROTECTED] http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Linux in a Windows 2k3 domain - odd lockout issue
I am currently running an openSuSE 10.2 machine in a Windows 2k3 domain. I have upgraded to Samba 3.0.26a, hoping it would solve my issue, but so far no luck. I was successful in adding my machine to the domain, and the DC logs show repeated successful authentications, and those few typo'd attempts, but nothing that is a sequence of failed logins. I get tickets and can access shares from machines all over the network without needing to re-authenticate. The problem is, at approx. 3:30 every afternoon, the domain controller locks my user ID as if I had failed repeatedly to type in the correct password. Though the DC does not show this in the logs. In exchange for running Linux, I am told I can't call help desk for support, and no changes can be made to systems expressly to make them "linux compatible." Any help is appreciated, if someone might have an idea of what this might be. Thanks! Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
