Re: [Samba] XP Pro client perm issues after joining samba domain
On 8/24/12 7:42 AM, Chris Nighswonger cnighswon...@foundations.edu wrote: No takers? I googled for internet explorer crashes when administrator Figuring that samba wasn't to blame here. The first hit I got might be your cause.. (protected mode) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] ongoing printer issues
So I continue to work through the various printing issues I've had with Samba. Hopefully the indexing of my messages will prove useful to others :) Anyway, while my previous fixes have gotten us printing for the most part, we still experience random issues (mostly with PDF printing to certain printers and printing from speciality programs). Anyway, our current issue is as such. User can print from Word/Outlook/Firefox/etc just fine. User prints from speciality program to same printer (as word/etc) and it does not print. Samba reports (at log level 3) a slew of stuff, the most unusual part though is [2012/02/01 16:43:55.319563, 3] smbd/error.c:81(error_packet_set) error packet at smbd/ipc.c(137) cmd=37 (SMBtrans) STATUS_BUFFER_OVERFLOW I should note that this is a Win7 64bit system printing to 3.6.3 I've found some posts on the 'net relating to regressions in samba and 64bit clients, but I was hoping if anyone had some other suggestions. Many thanks! Tom -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] issues with printing
On 1/6/12 3:31 PM, Jeremy Allison j...@samba.org wrote: The problem I can see from the pastebin is an authentication issue. The client is trying to connect via a machine account. If you don't allow the machine account access to the print share then it'll get access denied. The error above is the machine account not being present on the box, so we can't allow such a user to connect. You could set map to guest = bad user, and allow guest access to the print shares, or use a username map to map the incoming machine account to another (known) user, but the underlying problem here isn't in the print subsystem. Jeremy. Jeremy, This is true. I would not have the issue (I suspect) if I used winbind. I read somewhere prior to Samba 3, machine account auths were dropped (I forget the exact wording). In my case (I want 3.6.x for the print notice setting due to client firewalls), I think the fix would be an option to ignore (or silently map to guest account?) machine account auth requests? I don't know the best fix.. I just fixed it by manually adding the accounts.. Ugh.. But now at least it works. Tom -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] issues with printing
On 1/4/12 5:44 PM, Tom Ryan tomr...@camlaw.rutgers.edu wrote: I've included a full log from a failed print session here: http://pastebin.com/WBA4PEnG Ok, I've managed to determine that every user who is having an issue printing has an error message like [2012/01/05 09:18:54.928729, 3] auth/auth_util.c:1028(check_account) Failed to find authenticated user DOMAIN\machinename$ via getpwnam(), denying access. [2012/01/05 09:18:54.929709, 2] auth/auth.c:319(check_ntlm_password) check_ntlm_password: Authentication for user [machinename$] - [machinename$] FAILED with error NT_STATUS_NO_SUCH_USER [2012/01/05 09:18:54.929807, 3] smbd/error.c:81(error_packet_set) error packet at smbd/sesssetup.c(124) cmd=115 (SMBsesssetupX) NT_STATUS_LOGON_FAILURE You might recall that we don't use winbind so I'm at a loss as to why this happens sporadically and what I can do (short of editing the code) to work around it. Thoughts? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] issues with printing
On 1/5/12 9:31 AM, Tom Ryan tomr...@camlaw.rutgers.edu wrote: [2012/01/05 09:18:54.928729, 3] auth/auth_util.c:1028(check_account) Failed to find authenticated user DOMAIN\machinename$ via getpwnam(), denying access. [2012/01/05 09:18:54.929709, 2] auth/auth.c:319(check_ntlm_password) check_ntlm_password: Authentication for user [machinename$] - [machinename$] FAILED with error NT_STATUS_NO_SUCH_USER [2012/01/05 09:18:54.929807, 3] smbd/error.c:81(error_packet_set) error packet at smbd/sesssetup.c(124) cmd=115 (SMBsesssetupX) NT_STATUS_LOGON_FAILURE You might recall that we don't use winbind so I'm at a loss as to why this happens sporadically and what I can do (short of editing the code) to work around it. Thoughts? Ok, so I have found out if I put DOMAIN\machinename$ And machinename$ In /etc/passwd Then everything works.. However, that really isn't acceptable. Does anyone have a solution?? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] issues with printing
We have recently started having an odd problem with printing via samba (3.6.1). Samba is joined via security = ads to our domain. We do not use winbind on this system. Our account usernames are provided via openldap. User starts system (generally windows 7 64bit, but we've seen it on 32bit windows 7 and XP), sometimes they can print, sometimes they can't. If they reboot, they can almost always print. I've turned the logging up to level 3 and have noticed repeated errors like [2012/01/04 09:10:32.252107, 2] auth/auth.c:319(check_ntlm_password) check_ntlm_password: Authentication for user [MACHINENAME$] - [MACHINENAME$] FAILED with error NT_STATUS_NO_SUCH_USER [2012/01/04 09:10:32.252212, 3] smbd/error.c:81(error_packet_set) error packet at smbd/sesssetup.c(124) cmd=115 (SMBsesssetupX) NT_STATUS_LOGON_FAILURE Which I suspect has to do with the lack of winbind and not having machine names in our ldap service. I should note that this all worked perfectly up until a few weeks ago and then just started breaking randomly.. Isn't that always the case? I appreciate any pointers. Thanks. Tom -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] issues with printing
On 1/4/12 9:13 AM, Tom Ryan tomr...@camlaw.rutgers.edu wrote: We have recently started having an odd problem with printing via samba (3.6.1). Samba is joined via security = ads to our domain. We do not use winbind on this system. Our account usernames are provided via openldap. User starts system (generally windows 7 64bit, but we've seen it on 32bit windows 7 and XP), sometimes they can print, sometimes they can't. If they reboot, they can almost always print. I've turned the logging up to level 3 and have noticed repeated errors like [2012/01/04 09:10:32.252107, 2] auth/auth.c:319(check_ntlm_password) check_ntlm_password: Authentication for user [MACHINENAME$] - [MACHINENAME$] FAILED with error NT_STATUS_NO_SUCH_USER [2012/01/04 09:10:32.252212, 3] smbd/error.c:81(error_packet_set) error packet at smbd/sesssetup.c(124) cmd=115 (SMBsesssetupX) NT_STATUS_LOGON_FAILURE Which I suspect has to do with the lack of winbind and not having machine names in our ldap service. I should note that this all worked perfectly up until a few weeks ago and then just started breaking randomly.. Isn't that always the case? I appreciate any pointers. Thanks. Tom I've included a full log from a failed print session here: http://pastebin.com/WBA4PEnG Thanks for any consideration. Tom -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] issues with printing
On 1/4/12 9:57 AM, Tom Ryan tomr...@camlaw.rutgers.edu wrote: I've included a full log from a failed print session here: http://pastebin.com/WBA4PEnG Some additional info.. On one of our interim firewalls, we're noticing various dropped connections from our client hosts to this particular samba server's port 135. Any comments or suggestions would be appreciated. Thanks. Tom -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba print notifications
I remember conversing with Jeremy at the beginning of the year re: issues with samba's print notifications to clients (specifically XP) with firewalls enabled. I believe that an option to turn this behavior off was going to be added. Does anyone know if the option was added and if so, beginning in what version and the name of the option? I'm not having much luck (other then finding my original message :) Tom -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Odd printing issue
On 1/5/11 11:34 AM, Tom Ryan tomr...@camlaw.rutgers.edu wrote: Over the last few days, our users have started experiencing delays in printing. In the log files (for the client), we now see [2011/01/05 11:12:34.360166, 1] libsmb/cliconnect.c:2216(cli_start_connection) cli_start_connection: failed to connect to MACHINENAME20 (:::IPADDRESS). Error NT_STATUS_UNSUCCESSFUL As new systems are affected, these errors appear. We get about 7 of them (every 10 seconds) and then the print job completes. I saw Jeremy¹s reply to this on the website (Sorry, I think a spam filter blocked it). Anyway, I was wondering if you had an eta on this as its causing us quite a few issues and we¹d like to resolve it asap (i.e. Whether we wait for the samba team to address or look into it ourselves). Thanks Jeremy! Tom -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Odd printing issue
Over the last few days, our users have started experiencing delays in printing. In the log files (for the client), we now see [2011/01/05 11:12:34.360166, 1] libsmb/cliconnect.c:2216(cli_start_connection) cli_start_connection: failed to connect to MACHINENAME20 (:::IPADDRESS). Error NT_STATUS_UNSUCCESSFUL As new systems are affected, these errors appear. We get about 7 of them (every 10 seconds) and then the print job completes. Suggestions? Thoughts? Tom -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 3.0.6 Problems w/AD and Kerberos
I submitted a ticket (bugzilla) to redhat on this.. with the 3.0.6 update from them, coupled with their recent kerberos updates, it fails unless you use the FQDN.. its completely reproducable (at least on my end). I moved to security = domain and have it at least working again.. Tom On Fri, 10 Sep 2004, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Merrill wrote: | Well from my end (Redhat) the behavior is indicative of | a known issue with the MIT kerberos 1.2.x packages | that we currently support and Win2k3 DC's...however Win2k | DC's have been operating fine as far as I know. What I | am seeing are customers who were previously running | upgrade to the 3.0.6 samba package and then start to | encounter these errors. If they downgrade the samba | package the problem goes away. I've also noticed a few | other posts from users on other distros such as | Debian encountering very similar behavior. | On the surface it really looks like a kerberos problem, | but people are reporting that it seems to be directly | linked to the samba package. My current test environment | is on 2k3 so I'm still in the process of setting up a | 2k AD environment to do testing on...at this point just | relaying feedback that I am getting from others. I spent some time on this today without any luck reproducing the problem. My test server was SuSE 9.1 pro however with heimdal 0.6.1rc3. I've updated the comments in https://bugzilla.samba.org/show_bug.cgi?id=1717 And I checked the ticket cache produced by smbclient //server/share -k from 3.0.5 and 3.0.6. Same host principal is used ([EMAIL PROTECTED]). So far, I've not learned of any common thread from the people who posted on this. I'm open to suggestions. (off to review abartlet's mail to samba-technical about this). cheers, jerry - - Alleviating the pain of Windows(tm) --- http://www.samba.org GnuPG Key- http://www.plainjoe.org/gpg_public.asc If we're adding to the noise, turn off this song--Switchfoot (2003) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBQgLaIR7qMdg1EfYRAhVvAJ9skQtebUDF4QgAMFgxE+3IblGBNACgpnzi atDsjikhg3nr7PyaWuVXaLY= =odE/ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden IT Help Desk: 856-225-2343 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.6 Problems w/AD and Kerberos
Christian, another reason I think this is also kerberos related is that I am also having problems with ssh on my (admittedly) odd round robin dns setup.. I used to be able to ssh to the common hostname and get access to either box, now I get an unknown kerberos error and have to login to either host by name. couple that with my samba issues and how it works with FQDN, and I was inclined to think it was kerberos.. but hey.. I admit it.. you guys know better than I do :) Tom On Tue, 7 Sep 2004, Christian Merrill wrote: Tom Ryan wrote: I submitted a ticket (bugzilla) to redhat on this.. with the 3.0.6 update from them, coupled with their recent kerberos updates, it fails unless you use the FQDN.. its completely reproducable (at least on my end). I moved to security = domain and have it at least working again.. Tom On Fri, 10 Sep 2004, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Merrill wrote: | Well from my end (Redhat) the behavior is indicative of | a known issue with the MIT kerberos 1.2.x packages | that we currently support and Win2k3 DC's...however Win2k | DC's have been operating fine as far as I know. What I | am seeing are customers who were previously running | upgrade to the 3.0.6 samba package and then start to | encounter these errors. If they downgrade the samba | package the problem goes away. I've also noticed a few | other posts from users on other distros such as | Debian encountering very similar behavior. | On the surface it really looks like a kerberos problem, | but people are reporting that it seems to be directly | linked to the samba package. My current test environment | is on 2k3 so I'm still in the process of setting up a | 2k AD environment to do testing on...at this point just | relaying feedback that I am getting from others. I spent some time on this today without any luck reproducing the problem. My test server was SuSE 9.1 pro however with heimdal 0.6.1rc3. I've updated the comments in https://bugzilla.samba.org/show_bug.cgi?id=1717 And I checked the ticket cache produced by smbclient //server/share -k from 3.0.5 and 3.0.6. Same host principal is used ([EMAIL PROTECTED]). So far, I've not learned of any common thread from the people who posted on this. I'm open to suggestions. (off to review abartlet's mail to samba-technical about this). cheers, jerry - - Alleviating the pain of Windows(tm) --- http://www.samba.org GnuPG Key- http://www.plainjoe.org/gpg_public.asc If we're adding to the noise, turn off this song--Switchfoot (2003) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBQgLaIR7qMdg1EfYRAhVvAJ9skQtebUDF4QgAMFgxE+3IblGBNACgpnzi atDsjikhg3nr7PyaWuVXaLY= =odE/ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden IT Help Desk: 856-225-2343 Tom we have had multiple reports of this and I imagine your ticket is probably one of many in my queue right now. We are working on it internally as well but so far have not made any real progress narrowing down the problem. It *appears* that this is actually unrelated to our kerberos update. As I mentioned previously this looks like the problems we have been seeing in win2k3 environments -- almost as if something helped spread this issue to win2k as well. Christian ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden IT Help Desk: 856-225-2343 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.6 Problems w/AD and Kerberos
I found that if you use the FQDN it works.. (which was not acceptable to us).. we (unfortuantely) went to security = domain. Tom On Wed, 8 Sep 2004, Blindauer Emmanuel wrote: Le dimanche 05 Septembre 2004 13:38, Christian Merrill a écrit : Running into a lot of people upgrading to the 3.0.6 package that all of a sudden begin to experience the Failed to verify incoming ticket! errors etc., that are generally associated with a kerberos package incompatibility. However many of these people are running later versions of kerberos *and* reverting to a previous version of Samba appears to fix the issue. Is there something new setting wise that has taken place, is something really wrong with this new package, or is this all just a strange coincidence? Christian I confirm the problem: I'm running win2k SP4, AD, mixed mode, no other special conf. the samba is 3.0.6, compiled from sources. I use winbind too. winbind has some krb5_cc_get_principal failed (No credentials cache found) but nothing special. but the samba daemon get, for some users, smbd/sesssetup.c:reply_spnego_kerberos(173) Failed to verify incoming ticket and this prevent user from acceding their share. the used kerberos is 1.3.4 The 2000 domain has been started from scratch, no NT4 migration. Emmanuel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden IT Help Desk: 856-225-2343 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] issues with samba / shares
After upgrading to 3.0.6 (RHEL's version), I can no longer access shares (file or printer) on the server by referencing the short hostname. I must now enter the FQDN.. any ideas? Tom -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: issues with samba / shares (potential issue)
ok.. I dug around a bit more and it would appear that the problem is related to the kerberos libraries I now have (which RH also updated). short of remapping all of my shares, is there any workaround? Tom On Tue, 7 Sep 2004, Tom Ryan wrote: After upgrading to 3.0.6 (RHEL's version), I can no longer access shares (file or printer) on the server by referencing the short hostname. I must now enter the FQDN.. any ideas? Tom ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden IT Help Desk: 856-225-2343 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: issue with running samba on two separate systems under 1 hostname
ok.. at this point, I think I have 0 issues EXCEPT constant corruption of my printing TDBs.. is there anyway to cut down on this/prevent this? should I upgrade my samba beyond the RHEL provided one? Tom On Wed, 25 Aug 2004, Tom Ryan wrote: I have a read only share and a couple of printers exported that I would like to be available under a single hostname. to that end, I have a created a hostname that refers to two ip addresses, each being a separate machine. I have configured samba identically on each system and everything appears to work ok for a little while until our printing tdb becomes corrupted and everything hangs up.. (at least the printing).. deleting the tdbs and restarting samba appears to correct the issue until the next hang.. this is samba-3.0.4-6.3E (yep on RHEL 3). is there anything else I should be doing or am I at this point, stuck.. Tom p.s. for what its worth, I can't get both machines to register (of course) under the same netbios name, but I'm not sure thats an issue.. ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden IT Help Desk: 856-225-2343 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] issue with running samba on two separate systems under 1 hostname
I have a read only share and a couple of printers exported that I would like to be available under a single hostname. to that end, I have a created a hostname that refers to two ip addresses, each being a separate machine. I have configured samba identically on each system and everything appears to work ok for a little while until our printing tdb becomes corrupted and everything hangs up.. (at least the printing).. deleting the tdbs and restarting samba appears to correct the issue until the next hang.. this is samba-3.0.4-6.3E (yep on RHEL 3). is there anything else I should be doing or am I at this point, stuck.. Tom p.s. for what its worth, I can't get both machines to register (of course) under the same netbios name, but I'm not sure thats an issue.. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba NTFS permissions
true.. if you use a unix filesystem, but there's reasons to still use samba :) samba with ssl would be much more secure (for several reasons) over nfs (and easier to use than the afs/etc). We have some machines that I don't trust enough to give NFS access to (and I don't particulary like having to setup X number of exports). come on.. samba works for *everything* :) Tom On Mon, 8 Dec 2003, Jeremy Allison wrote: Think of the taxpayers ! Convert the desktops to Linux also, then you won't need the Samba servers :-). Jeremy. -- ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA and FreeRadius
As freeradius supports PAM for authentication, this is trivial. Simply configure freeradius to use pam (see config files for freeradius) and then set your pam config for radius to use smb (via winbind) for authentication. Tom On Wed, 3 Dec 2003 [EMAIL PROTECTED] wrote: I need to use CHAP on my NAS. Is it possible to authenticate FreeRadius against SAMBA 3.x? Thanks in advance for any help! Bob -- ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
Jeremy (and all), just wanted to say that we moved (quicker than we wanted) to 3.0.x and everything is fine! Thanks so much ! Tom On Wed, 19 Nov 2003, Jeremy Allison wrote: On Wed, Nov 19, 2003 at 03:57:56PM -0500, Tom Ryan wrote: yes.. but I was having problems before with that enabled previously. The client behaviour changes once spoolss is enabled. If you're claiming to see the same issue on the clients you need to restart the spooler service on them in order for them to notice the now open spoolss pipe. 3.0.x has a *much* improved version of the printing code we use on the HP PSA (Print Server Appliance), so I can definately recommend it. Jeremy. -- ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
I've kept looking for an answer to this to no avail.. any ideas?
strace -p reveals
fcntl64(14, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=684, len=1},
0xb180) = 0
fcntl64(14, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=684, len=1},
0xb150) = 0
fcntl64(14, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=5676,
len=1}, 0xb160) = 0
fcntl64(14, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=684, len=1},
0xb150) = 0
fcntl64(14, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=688, len=1},
0xb150) = 0
fcntl64(14, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=688, len=1},
0xb150) = 0
fcntl64(16, F_SETLKW64, {type=F_RDLCK, whence=SEEK_SET, start=528, len=1},
0xbfffda40) = 0
fcntl64(16, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=528, len=1},
0xbfffda40) = 0
time(NULL) = 1069272774
fcntl64(16, F_SETLKW64, {type=F_RDLCK, whence=SEEK_SET, start=548, len=1},
0xbfffc8a0) = 0
fcntl64(16, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=548, len=1},
0xbfffc8e0) = 0
thanks!
On Thu, 9 Oct 2003, Tom Ryan wrote:
Looking around on the net, I saw that someone else had a similar issue
when they were running all of their users behind terminal server. Our
users are all behind two NAT'd firewalls.
Is it possible that there is some confusion going on? should I stop the
service and remove locking.tdb? (that's what 14 references right?)
Thanks.
tom
On Wed, 8 Oct 2003, Tom Ryan wrote:
2.4.20-19.8 on redhat 8
strace reports
fcntl64(14, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=628, len=1},
0xb150) = 0
fcntl64(14, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=632, len=1},
0xb150) = 0
over and over again (with different start points)
Tom
On Wed, 8 Oct 2003, Jeremy Allison wrote:
On Wed, Oct 08, 2003 at 02:29:31PM -0400, Tom Ryan wrote:
I have a samba box that has around 70 users on it at any given time.
When I run ps axu there are certain smbd processes (and usually always
by the same login) that look like
username 26126 39.4 0.1 6652 2912 ?S13:44 17:12 smbd -D
any ideas why CPU is running at 39.4??
What OS ? Try doing an strace on it to see what the process is doing.
Jeremy.
--
___
Tom RyanVoice: 856-225-6361
Consulting System Administrator Fax: 856-969-7900
Rutgers School of Law - Camden
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
Jeremy,
(gdb) bt
#0 0x08173176 in tdb_brlock ()
#1 0x0817349a in tdb_unlock ()
#2 0x0817517a in tdb_next_lock ()
#3 0x081752a6 in tdb_traverse ()
#4 0x08179de4 in print_queue_status ()
#5 0x0807a6de in api_DosPrintQGetInfo ()
#6 0x0807fdd8 in api_reply ()
#7 0x08077e03 in reply_trans ()
#8 0x080af1af in switch_message ()
#9 0x080af3a9 in construct_reply ()
#10 0x080af528 in process_smb ()
#11 0x080b01b4 in smbd_process ()
#12 0x0806ab4b in main ()
#13 0x420158f7 in __libc_start_main () from /lib/i686/libc.so.6
(gdb)
On Wed, 19 Nov 2003, Jeremy Allison wrote:
On Wed, Nov 19, 2003 at 03:14:02PM -0500, Tom Ryan wrote:
I've kept looking for an answer to this to no avail.. any ideas?
strace -p reveals
fcntl64(14, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=684, len=1},
0xb180) = 0
fcntl64(14, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=684, len=1},
0xb150) = 0
Ok, it's in a tdb call. Can you attach with gdb and get a stack backtrace ?
Jeremy.
--
___
Tom RyanVoice: 856-225-6361
Consulting System Administrator Fax: 856-969-7900
Rutgers School of Law - Camden
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
2.2.7 on redhat 8. i uped lpq cache time = 60. doesn't seem to help. Tom On Wed, 19 Nov 2003, Jeremy Allison wrote: On Wed, Nov 19, 2003 at 03:23:31PM -0500, Tom Ryan wrote: Jeremy, (gdb) bt #0 0x08173176 in tdb_brlock () #1 0x0817349a in tdb_unlock () #2 0x0817517a in tdb_next_lock () #3 0x081752a6 in tdb_traverse () #4 0x08179de4 in print_queue_status () #5 0x0807a6de in api_DosPrintQGetInfo () #6 0x0807fdd8 in api_reply () #7 0x08077e03 in reply_trans () #8 0x080af1af in switch_message () #9 0x080af3a9 in construct_reply () #10 0x080af528 in process_smb () #11 0x080b01b4 in smbd_process () #12 0x0806ab4b in main () #13 0x420158f7 in __libc_start_main () from /lib/i686/libc.so.6 (gdb) Ok, this is a Win9x client scanning for print jobs. Up the lpq cache time I would suggest. What Samba version ? Jeremy. -- ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
Jeremy, All clients are windows xp. Tom On Wed, 19 Nov 2003, Jeremy Allison wrote: On Wed, Nov 19, 2003 at 03:36:15PM -0500, Tom Ryan wrote: 2.2.7 on redhat 8. i uped lpq cache time = 60. doesn't seem to help. How many print jobs do you have on this box ? Hmmm. As I recall, a Win9x client with an open print monitor will just continually scan the server - pounding it with requests. We redesigned this for 3.0.x (try 3.0.1pre3) but it won't fix the problem that Win9x clients will continuously scan the print server - this is a problem of the Win9x design, not of Samba. The same thing happens to WinNT/2k/2k3. Can you get people to close down the print monitors ? Jeremy. -- ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
yes.. but I was having problems before with that enabled previously. On Wed, 19 Nov 2003, Jeremy Allison wrote: On Wed, Nov 19, 2003 at 03:42:11PM -0500, Tom Ryan wrote: Jeremy, All clients are windows xp. Ok, then you're not using the spoolss pipe code on the Samba server, as this scanning behaviour goes away once WNT or above clients can open the SPOOLSS pipe (they use a strange form of change notify instead of scanning). Do you have disable spoolss set in your smb.conf ? Jeremy. -- ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
I enabled that.. but I'm still having the same issue. On Wed, 19 Nov 2003, Tom Ryan wrote: yes.. but I was having problems before with that enabled previously. On Wed, 19 Nov 2003, Jeremy Allison wrote: On Wed, Nov 19, 2003 at 03:42:11PM -0500, Tom Ryan wrote: Jeremy, All clients are windows xp. Ok, then you're not using the spoolss pipe code on the Samba server, as this scanning behaviour goes away once WNT or above clients can open the SPOOLSS pipe (they use a strange form of change notify instead of scanning). Do you have disable spoolss set in your smb.conf ? Jeremy. -- ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
We are in the middle of planning our upgrade. Thanks will try this and report back! Tom On Wed, 19 Nov 2003, Jeremy Allison wrote: On Wed, Nov 19, 2003 at 03:57:56PM -0500, Tom Ryan wrote: yes.. but I was having problems before with that enabled previously. The client behaviour changes once spoolss is enabled. If you're claiming to see the same issue on the clients you need to restart the spooler service on them in order for them to notice the now open spoolss pipe. 3.0.x has a *much* improved version of the printing code we use on the HP PSA (Print Server Appliance), so I can definately recommend it. Jeremy. -- ___ Tom RyanVoice: 856-225-6361 Consulting System Administrator Fax: 856-969-7900 Rutgers School of Law - Camden -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
Does anyone have any thoughts on this? Any things that I can try? I'm open
to suggestions :)
Tom
On Thu, 9 Oct 2003, Tom Ryan wrote:
Ok.. still researching this. should i try disabling kernel oplocks? also,
any thoughts on why it only happens to certain user processes?
could it be a corrupted file or patch level of their machine?
Tom
On Thu, 9 Oct 2003, Tom Ryan wrote:
Looking around on the net, I saw that someone else had a similar issue
when they were running all of their users behind terminal server. Our
users are all behind two NAT'd firewalls.
Is it possible that there is some confusion going on? should I stop the
service and remove locking.tdb? (that's what 14 references right?)
Thanks.
tom
On Wed, 8 Oct 2003, Tom Ryan wrote:
2.4.20-19.8 on redhat 8
strace reports
fcntl64(14, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=628, len=1},
0xb150) = 0
fcntl64(14, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=632, len=1},
0xb150) = 0
over and over again (with different start points)
Tom
On Wed, 8 Oct 2003, Jeremy Allison wrote:
On Wed, Oct 08, 2003 at 02:29:31PM -0400, Tom Ryan wrote:
I have a samba box that has around 70 users on it at any given time.
When I run ps axu there are certain smbd processes (and usually always
by the same login) that look like
username 26126 39.4 0.1 6652 2912 ?S13:44 17:12 smbd -D
any ideas why CPU is running at 39.4??
What OS ? Try doing an strace on it to see what the process is doing.
Jeremy.
--
___
Tom RyanVoice: 856-225-6361
Consulting System Administrator Fax: 856-969-7900
Rutgers School of Law - Camden
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
Looking around on the net, I saw that someone else had a similar issue
when they were running all of their users behind terminal server. Our
users are all behind two NAT'd firewalls.
Is it possible that there is some confusion going on? should I stop the
service and remove locking.tdb? (that's what 14 references right?)
Thanks.
tom
On Wed, 8 Oct 2003, Tom Ryan wrote:
2.4.20-19.8 on redhat 8
strace reports
fcntl64(14, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=628, len=1},
0xb150) = 0
fcntl64(14, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=632, len=1},
0xb150) = 0
over and over again (with different start points)
Tom
On Wed, 8 Oct 2003, Jeremy Allison wrote:
On Wed, Oct 08, 2003 at 02:29:31PM -0400, Tom Ryan wrote:
I have a samba box that has around 70 users on it at any given time.
When I run ps axu there are certain smbd processes (and usually always
by the same login) that look like
username 26126 39.4 0.1 6652 2912 ?S13:44 17:12 smbd -D
any ideas why CPU is running at 39.4??
What OS ? Try doing an strace on it to see what the process is doing.
Jeremy.
--
___
Tom RyanVoice: 856-225-6361
Consulting System Administrator Fax: 856-969-7900
Rutgers School of Law - Camden
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] extremely high %CPU and TIME
Jeremy,
2.4.20-19.8 on redhat 8
strace reports
fcntl64(14, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=628, len=1},
0xb150) = 0
fcntl64(14, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=632, len=1},
0xb150) = 0
over and over again (with different start points)
Tom
On Wed, 8 Oct 2003, Jeremy Allison wrote:
On Wed, Oct 08, 2003 at 02:29:31PM -0400, Tom Ryan wrote:
I have a samba box that has around 70 users on it at any given time.
When I run ps axu there are certain smbd processes (and usually always
by the same login) that look like
username 26126 39.4 0.1 6652 2912 ?S13:44 17:12 smbd -D
any ideas why CPU is running at 39.4??
What OS ? Try doing an strace on it to see what the process is doing.
Jeremy.
--
___
Tom RyanVoice: 856-225-6361
Consulting System Administrator Fax: 856-969-7900
Rutgers School of Law - Camden
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Domain Trust and smbclient error.
I am trying to get a W2K server to trust a samba 3.0 server. I followed the directions in the InterdomainTrusts.html file and receive an error that the domain is not found when trying to trust it. my samba server is configured to use pam to authenticate. I had to add a user named w2kdomain$ on the machine before I could run smbpasswd -a -i w2kdomain. Once I did that, it created the user just fine. If I run smbclient -L sambaserver -U localusername and enter my password, it uses pam to authenticate it (i am running log level 5 to verify this). If I run the same command on another box (different version of samba/smbclient), it fails. The log file shows that at the same point of authentication, there's some pop_sec_ctx calls and then unix authentication failed for user username. I'm scratching my head at this point.. my smb.conf is miminal, security = user, encrypt passwords = no any ideas? tom -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
