Re: [Samba] PDC migration: printing trouble. Summary.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Remy Zandwijk wrote: Second: all printers had an 'invalid users' setting in the share definition. It turned out that this considerably stresses the CPU. It took about 10 seconds for the properties to show up for a 'HP 4250PS driver' printer. While truss-ing the smbd process, we saw that the smbpasswd file was opened for 85 times (from the click on 'properties' to when the properties appeared). I think that's a lot. We have around 4700 entries in the smbpasswd file, so I can imagine why it takes long for the properties to show up when 6 invalid users are configured. Only one would expect that the smbpasswd file is opened just 6 to 10 times, and not 85 times. I guess this won't happen when using a tdbsam passdb backend (which is not an option for us for now). I can confirm that your results will be much improved in all respects when you move to a proper backend. In our situation, the PW file was always locked as a result of too many reads and we were entirely unable to change passwords for a period of time. In fact, I would encourage you to do something about this before you get bitten by it, because with the file being read so often, you may run into this problem too. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIH/qDmb+gadEcsb4RAunyAJ4lasxw461nCH54dxOlW+/Tm+QjQgCeIwXE YQg/Zb8tE//I537bvacM6RY= =AvXg -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] PDC migration: printing trouble. Summary.
Hi, try this, first set alle the properties from user Administrator ( root ) then disconnect the printers for all users. reconnect. try now how fast it is. This works for my if the printer properties are slow. Greetz, Louis -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Ryan Novosielski Verzonden: dinsdag 6 mei 2008 8:28 Aan: samba@lists.samba.org Onderwerp: Re: [Samba] PDC migration: printing trouble. Summary. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Remy Zandwijk wrote: Second: all printers had an 'invalid users' setting in the share definition. It turned out that this considerably stresses the CPU. It took about 10 seconds for the properties to show up for a 'HP 4250PS driver' printer. While truss-ing the smbd process, we saw that the smbpasswd file was opened for 85 times (from the click on 'properties' to when the properties appeared). I think that's a lot. We have around 4700 entries in the smbpasswd file, so I can imagine why it takes long for the properties to show up when 6 invalid users are configured. Only one would expect that the smbpasswd file is opened just 6 to 10 times, and not 85 times. I guess this won't happen when using a tdbsam passdb backend (which is not an option for us for now). I can confirm that your results will be much improved in all respects when you move to a proper backend. In our situation, the PW file was always locked as a result of too many reads and we were entirely unable to change passwords for a period of time. In fact, I would encourage you to do something about this before you get bitten by it, because with the file being read so often, you may run into this problem too. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIH/qDmb+gadEcsb4RAunyAJ4lasxw461nCH54dxOlW+/Tm+QjQgCeIwXE YQg/Zb8tE//I537bvacM6RY= =AvXg -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] PDC migration: printing trouble. Summary.
UPDATE: I've realized that this seems to be an issue with the compiler flags used to build samba. I've realized that i need to define _LARGEFILE_SOURCE, _LARGEFILE64_SOURCE, and _FILE_OFFSET_BITS=64. I've done this, but still have no luck reading files larger than 4GB. Anyone have suggestions? Thanks, Matt Hi guys, I'm attempting to move large files (4GB) from a PowerPC-based embedded system running a 2.4 kernel architecture to an PC running a 2.6 kernel. I've got samba compiled, installed, and running on the embedded box. I also have the directories from the PPC system mounted and accessible from the PC. I have two problems: larger file sizes do not list correctly, and large files transferred from the embedded box to the PC are not complete; IE they're dropping data along the way. I'm familiar with the 2GB file size limit on samba, and have mounted the PC side using the lfs flag. Problem 1: Incorrect listing Here's a list of the directory from the embedded box: -r--r--r-- 1 root root 52646396 Jan 5 06:46 file1.ch10 -r--r--r-- 1 root root 60755936 Jan 5 06:46 file2.ch10 -r--r--r-- 1 root root 47606684 Jan 5 06:46 file3.ch10 -r--r--r-- 1 root root 4920604376 Jan 5 05:51 file4.ch10 Here's that same listing, but of the samba mount of that directory on the PC: -r-xr-xr-x 1 root root 52646396 Jan 5 2007 file1.ch10 -r-xr-xr-x 1 root root 60755936 Jan 5 2007 file2.ch10 -r-xr-xr-x 1 root root 47606684 Jan 5 2007 file3.ch10 -r-xr-xr-x 1 root root 625637080 Jan 5 2007 file4.ch10 As you can see, files 1-3 list fine, but file4 is showing way short. I'm guessing this might be some sort of overflow condition, any ideas? Problem 2: Loss of data during transfer of large files. When I try to transfer file4, i only get 41 or so of the total file size. This is the more pressing issue. Also, I cannot mount the samba share using CIFS. I use the line mount -t smbfs //server/share/ path/to/local/ -o user=u,pass=p,lfs to mount with SMBFS, and it works correctly, just doesn't display the large files. However, when using the following: mount -t smbfs //server/share/ path/to/local/ -o user=u,pass=p,lfs I get Mount error 5= Input/output error Any thoughts? Thanks, Matt ***Teletronics Technology Corporation*** This e-mail is confidential and may also be privileged. If you are not the addressee or authorized by the addressee to receive this e-mail, you may not disclose, copy, distribute, or use this e-mail. If you have received this e-mail in error, please notify the sender immediately by reply e-mail or by telephone at 267-352-2020 and destroy this message and any copies. Thank you. *** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC migration: printing trouble. Summary.
On 2008-04-09 at 21:31 +0200 Remy Zandwijk sent off: Second: all printers had an 'invalid users' setting in the share definition. It turned out that this considerably stresses the CPU. It took about 10 seconds for the properties to show up for a 'HP 4250PS driver' printer. While truss-ing the smbd process, we saw that the smbpasswd file was opened for 85 I had a similar issue some days ago with an smbd torturing it's LDAP server quite a lot. There was a directory with lots of different group ACEs on the files and hide unreadable being activated on that share. As lots of clients having change notification on that directory, smbd had a really hard time asking the LDAP server for gid-to-sid and uid-to-sid resolution. As this was a PDC winbind coudn't cache the results from the LDAP server. The increased amount of requests were a result of the exact uid/sid mappings introducted in 3.0.23c. Hide unreadable was the trigger that was causing so may checks to be done. As a result each client triggered some hundreds of LDAP request every 5 seconds. It might be that your invalid users parameter also triggers a huge amount of requests. You might try to use the attached patch which Volker wrote to cache uid/gid to sid requests in memory with 1h TTL. The patch was done against 3.0.25. That patch reduced the load that smbd put on the LDAP server dramatically. How about this patch being commited upstream? Cheers Björn -- 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 pgp2lCqhuTD52.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC migration: printing trouble. Summary.
On 2008-04-11 at 12:39 +0200 Volker Lendecke sent off: On Fri, Apr 11, 2008 at 12:10:10PM +0200, Björn Jacke wrote: How about this patch being commited upstream? no patch attached :-) something has munched up my mail, there was the patch attached. The signature got broken, too. Strange. Attched is the patch again, now unsigned. Cheers Björn -- 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/listinfo/samba
Re: [Samba] PDC migration: printing trouble. Summary.
Hallo, Björn, Du (bj) meintest am 11.04.08: no patch attached :-) something has munched up my mail, there was the patch attached. The signature got broken, too. Strange. Attched is the patch again, now unsigned. No patch attached. Viele Gruesse! Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC migration: printing trouble. Summary.
On 2008-04-11 at 13:52 +0200 Helmut Hullen sent off: No patch attached. yes, it's useless as long as Mailman is removing the attached patch each time. Look at the mail header: X-Content-Filtered-By: Mailman/MimeDel 2.1.5 If Mailman thinks a mail has bogous attachments it should remove and bounce back the complete mailbut the mail should not be silently altered. Jerry (are you the list maintainer?), can you have look at the problem please? Cheers Björn -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC migration: printing trouble. Summary.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Björn Jacke wrote: | On 2008-04-11 at 13:52 +0200 Helmut Hullen sent off: | No patch attached. | | yes, it's useless as long as Mailman is removing the attached patch | each time. | | Look at the mail header: | | X-Content-Filtered-By: Mailman/MimeDel 2.1.5 | | If Mailman thinks a mail has bogous attachments it should remove and | bounce back the complete mailbut the mail should not be silently | altered. Jerry (are you the list maintainer?), can you have look at | the problem please? Tim normally deals with the postfix/mailman interaction. If he doesn't have time I'll look into it next week. cheers, jerry - -- = Samba--- http://www.samba.org Likewise Software - http://www.likewisesoftware.com What man is a man who does not make the world better? --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH/2rRIR7qMdg1EfYRAnBUAJ9y1gVYQBVtpOjzk0ddzqSKOAN68gCgyPiA I0V9rmX2ahGEvDJUJNv9eiQ= =Z8hO -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC migration: printing trouble. Summary.
On Fri, 2008-04-11 at 08:42 -0500, Gerald (Jerry) Carter wrote:
Björn Jacke wrote:
| On 2008-04-11 at 13:52 +0200 Helmut Hullen sent off:
| No patch attached.
|
| yes, it's useless as long as Mailman is removing the attached patch
| each time.
|
| Look at the mail header:
|
| X-Content-Filtered-By: Mailman/MimeDel 2.1.5
|
| If Mailman thinks a mail has bogous attachments it should remove and
| bounce back the complete mailbut the mail should not be silently
| altered. Jerry (are you the list maintainer?), can you have look at
| the problem please?
Tim normally deals with the postfix/mailman interaction.
If he doesn't have time I'll look into it next week.
The current behaviour of the samba list is to strip attachments that
aren't multipart/{mixed,alternative,signed}, various digital signature
types and text/plain.
There doesn't seem to be an official MIME type for patches, after a
quick browse through the list at:
http://www.iana.org/assignments/media-types/
What MIME type is your mailer sending?
Tim.
cheers, jerry
- --
=
Samba--- http://www.samba.org
Likewise Software - http://www.likewisesoftware.com
What man is a man who does not make the world better? --Balian
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH/2rRIR7qMdg1EfYRAnBUAJ9y1gVYQBVtpOjzk0ddzqSKOAN68gCgyPiA
I0V9rmX2ahGEvDJUJNv9eiQ=
=Z8hO
-END PGP SIGNATURE-
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC migration: printing trouble. Summary.
Hi all, Thanks for all replies regarding the subject. I took some time to debug the problem, which resulted in some interesting insights. I started with a clean printer driver repository, no ntforms, ntprinters and ntdrivers.tdb files. Then I installed and assigned the drivers to the printers. First of all: the server is a Solaris 10 machine, which has sendfile support. Sendfile is compiled in, but not enabled by default. I enabled sendfile in smb.conf, which should result in less CPU stress. Second: all printers had an 'invalid users' setting in the share definition. It turned out that this considerably stresses the CPU. It took about 10 seconds for the properties to show up for a 'HP 4250PS driver' printer. While truss-ing the smbd process, we saw that the smbpasswd file was opened for 85 times (from the click on 'properties' to when the properties appeared). I think that's a lot. We have around 4700 entries in the smbpasswd file, so I can imagine why it takes long for the properties to show up when 6 invalid users are configured. Only one would expect that the smbpasswd file is opened just 6 to 10 times, and not 85 times. I guess this won't happen when using a tdbsam passdb backend (which is not an option for us for now). After deleting the 'invalid users' setting, the properties showed up in about 2 seconds. Some more experimenting showed that adding the invalid users to the security tab (as in: deny user 'a' to print) resulted in about the same behaviour. Can't explain why the old Samba 2.2 server doesn't suffer from this though. Another thing is that 'guest ok = yes' on the print$ share resulted in lots of reads/opens of files as the user 'nobody'. This is unnecessary in our setup, since every user is authenticated. Obviously, I configured 'guest ok = no' now. Since uploading the drivers to the server is a lot of work in case of 78 printers, I looked for a way to use the 'old' drivers. I deleted all nt*.tdb files, copied the drivers and copied the ntdrivers.tdb from the old server. In the printer properties (advanced - driver) all drivers showed up. Only the association with printers was gone (which was expected). I could simply assign the printers the correct driver. Then, I did the same as above but not before renaming the server and workgroup to a temporary name. Assigned the local/domain SID of the original domain with 'net setlocalsid', etc. Assigned the drivers again, applied the correct settings etc. Then I renamed the server/workgroup to the original name again, checked if the local/domain SIDs were still OK (Samba apparently caches that). All associations were still there, with correct settings. This answers my question if printer-driver-associations survive server/workgroup name changes. -Remy we've been moving an old Samba 2.2.x PDC install to a Samba 3.0.28 PDC install. We copied the ntdrivers.tdb and ntprinters.tdb from to old to the new server. After the migration, everything was just fine, except printing seemed to be somewhat slower. As more and more user logged on, the machine got really sluggish and printing took quite long. We figured out we've got bitten by: http://www.usenet-forums.com/samba/311929-re-samba-slow-printing-print-properties-cups-samba.html The plan is to assign the new server a new 'workgroup' name, which divers from the workgroup settings of the old PDC, delete all .tdb files, assign the printers drivers and settings again. Then, turn off the old PDC, change the workgroup setting of the new PDC to match the old PDC, etc. Basically, we build new printing .tdb files. The question is: is this going to work? Do the .tdb files which have something to do with printers have references to the temporary workgroup name or do they use domain/local SID's (which are the same on the old and new server)? Any other gotcha's? Is there a more proper way to accomplish this? Thanks for your comments, Remy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] PDC migration: printing trouble.
I had this problem also. I was using the Point en Print Setup for upload the printer drivers. i also tried deleting the registry keys in windows, but my solution was. i reuploaded ( overwrited ) my printer drivers, set de settings per printer again, and my problem was solved. No slow printer properties screens, or slow selecting the printer. Louis -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Remy Zandwijk Verzonden: vrijdag 4 april 2008 20:43 Aan: John Drescher CC: samba@lists.samba.org Onderwerp: Re: [Samba] PDC migration: printing trouble. John Drescher wrote: we've been moving an old Samba 2.2.x PDC install to a Samba 3.0.28 PDC install. We copied the ntdrivers.tdb and ntprinters.tdb from to old to the new server. After the migration, everything was just fine, except printing seemed to be somewhat slower. As more and more user logged on, the machine got really sluggish and printing took quite long. We figured out we've got bitten by: Is there a lot of network activity and a long delay between clicking the print button on windows? Hi John. Yes, there is. -Remy -- 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
Re: [Samba] PDC migration: printing trouble.
For me this was a windows bug and not a samba bug. Apparently windows remembers every printer you ever had connected to your machine and for every operation that brings up a print dialog it tries to contact all of these printers even though the printer has been deleted from you list of available printers. To fix this open up regedit and look at HKEY_CURRENT_USER and then Printers. In that tab there 4 folders. Delete all keys that contain printers that no longer exist and the problem will go away. At least it did for the users on my network. This is a per user item so you have to do that for every user who has this problem... We did not delete any printer, we just migrated the PDC funtionality to another machine with a newer Samba version. Workgroup and the domain SID are the same. The only change is that we switched from a local to a remote CUPS server. Still would like to see an answer to this question: Do the .tdb files which have something to do with printers have references to the workgroup name or do they use domain/local SID's (which are the same on the old and new server)? In other words: are we safe when the workgroup settings is changed after adding printers? -Remy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC migration: printing trouble.
On Fri, Apr 4, 2008 at 12:20 PM, Remy Zandwijk [EMAIL PROTECTED] wrote: Hi all, we've been moving an old Samba 2.2.x PDC install to a Samba 3.0.28 PDC install. We copied the ntdrivers.tdb and ntprinters.tdb from to old to the new server. After the migration, everything was just fine, except printing seemed to be somewhat slower. As more and more user logged on, the machine got really sluggish and printing took quite long. We figured out we've got bitten by: Is there a lot of network activity and a long delay between clicking the print button on windows? John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC migration: printing trouble.
John Drescher wrote: we've been moving an old Samba 2.2.x PDC install to a Samba 3.0.28 PDC install. We copied the ntdrivers.tdb and ntprinters.tdb from to old to the new server. After the migration, everything was just fine, except printing seemed to be somewhat slower. As more and more user logged on, the machine got really sluggish and printing took quite long. We figured out we've got bitten by: Is there a lot of network activity and a long delay between clicking the print button on windows? Hi John. Yes, there is. -Remy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC migration: printing trouble.
Hi John. Yes, there is. For me this was a windows bug and not a samba bug. Apparently windows remembers every printer you ever had connected to your machine and for every operation that brings up a print dialog it tries to contact all of these printers even though the printer has been deleted from you list of available printers. To fix this open up regedit and look at HKEY_CURRENT_USER and then Printers. In that tab there 4 folders. Delete all keys that contain printers that no longer exist and the problem will go away. At least it did for the users on my network. This is a per user item so you have to do that for every user who has this problem... John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
