Re: [Samba] samba3 upgrade misery
Felipe Augusto van de Wiel wrote: smbd is repeatedly spewing forth lists of socket options from print_socket_options: [...] What testparm tells you about your smb.conf parameters with regards to the socket options? If I put my old line through testparm, it comes out as: socket options = SO_KEEPALIVE=1 TCP_NODELAY=0 IPTOS_LOWDELAY SO_BROADCAST=1 without complaint. What options did you tried? Can you post more details about your smb.conf? Here's the global and printer sections of my smb.conf [global] workgroup = UNIQUE netbios name = SAMBA interfaces = 192.168.1.103 bind interfaces only = Yes passdb backend = tdbsam username map = /usr/local/etc/smb_usermap log file = /home/samba/samba3/var/log.%m time server = Yes socket options = SO_KEEPALIVE=1 TCP_NODELAY=0 IPTOS_LOWDELAY SO_BROADCAST=1 printcap name = cups logon script = timeset.bat logon path = logon home = "\\samba\%u" domain logons = Yes os level = 99 preferred master = Yes domain master = Yes wins support = Yes kernel oplocks = No pid directory = /var/run socket address = 192.168.1.103 idmap uid = 1 - 2 idmap gid = 1 - 2 hosts allow = 192.168.0.0/255.255.0.0 hosts deny = ALL printing = cups print command = lpq command = %p lprm command = oplocks = No level2 oplocks = No [printers] path = /var/spool/samba guest ok = Yes printable = Yes use client driver = Yes browseable = No With samba 2 I used the line: socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY SO_BROADCAST In recent version of Linux (2.6.x) it is the consensus on this list to drop some of the flags, I'm not so sure about Solaris kernel. The idea is that it allow multiple writes, should be faster and safer (because it uses internal locks). http://wiki.samba.org/index.php/TDB It also has nice backup tools to keep various different information about Samba and its network environment. Great... so now my samba state files are faster and more reliable, whilst the files samba is server are slower and prone to corruption. Other than that, we just need to share files (and because of some ridiculously old apps, printers). Nice, a standalone server would work great. Well, if I had the time to remove every machine from the domain and work that way, I'd love to... would sure save a lot of the stupidity when setting up new machines. As it is I don't have the time to be dealing with how broken samba 3 is behaving, but I don't have a choice. I read the migration docs on the web site, so if they're not current, someone should make them so. Seems fair, do you have any links? It'd be easier if someone would fix those damn menu links on the web site so they don't change size when you click them. Fortunately, it looks like I bookmarked the page. Must have been a prick to find in the first place, or I wouldn't have bothered: http://us4.samba.org/samba/docs/man/Samba-Guide/upgrades.html#id362605 -- Curtis Maloney [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba3 upgrade misery
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Curtis Maloney wrote, On 17-08-2007 02:45: > Well, just had a user come and show me a JPEG that's been > corrupted because the file copy died part way through. > The error was that the destination folder was no longer > available. > > I have no idea how much of the copious logs are relevant > to the debugging of this issue, as there are no log level > indications (why not??) so I'll paste as much as seems > relevant. > > Feel free to ask for more. > > [2007/08/17 15:38:59, 8] smbd/dosmode.c:dos_mode(371) >dos_mode: PROJS/R425_E1022_EV15_12 Scan Eng/EV12_assy_TB1.JPG > [2007/08/17 15:38:59, 8] smbd/dosmode.c:dos_mode_from_sbuf(188) >dos_mode_from_sbuf returning a > [2007/08/17 15:38:59, 8] smbd/dosmode.c:dos_mode(409) >dos_mode returning a[sparse] > [2007/08/17 15:38:59, 10] smbd/trans2.c:call_trans2qfilepathinfo(3539) >call_trans2qfilepathinfo: SMB_FILE_BASIC_INFORMATION > [2007/08/17 15:38:59, 5] smbd/trans2.c:call_trans2qfilepathinfo(3549) >SMB_QFBI - create: Fri Aug 17 15:34:36 2007 > access: Fri Aug 17 15:34:36 2007 > write: Fri Aug 17 15:34:36 2007 > change: Fri Aug 17 15:34:36 2007 > mode: 220 > [2007/08/17 15:38:59, 9] smbd/trans2.c:send_trans2_replies(712) >t2_rep: params_sent_thistime = 2, data_sent_thistime = 40, useable_space = > 131010 > [2007/08/17 15:38:59, 9] smbd/trans2.c:send_trans2_replies(714) >t2_rep: params_to_send = 2, data_to_send = 40, paramsize = 2, datasize = 40 > [2007/08/17 15:38:59, 5] lib/util.c:show_msg(484) > [2007/08/17 15:38:59, 5] lib/util.c:show_msg(494) >size=100 >smb_com=0x32 >smb_rcls=0 >smb_reh=0 >smb_err=0 >smb_flg=136 >smb_flg2=51265 >smb_tid=1 >smb_pid=2532 >smb_uid=101 >smb_mid=13570 >smt_wct=10 >smb_vwv[ 0]=2 (0x2) >smb_vwv[ 1]= 40 (0x28) >smb_vwv[ 2]=0 (0x0) >smb_vwv[ 3]=2 (0x2) >smb_vwv[ 4]= 56 (0x38) >smb_vwv[ 5]=0 (0x0) >smb_vwv[ 6]= 40 (0x28) >smb_vwv[ 7]= 60 (0x3C) >smb_vwv[ 8]=0 (0x0) >smb_vwv[ 9]=0 (0x0) >smb_bcc=45 > [2007/08/17 15:38:59, 10] lib/util.c:dump_data(2261) >[000] 00 00 00 00 00 00 7E 19 4C 90 E0 C7 01 00 7E 19 ..~. L.~. >[010] 4C 90 E0 C7 01 00 7E 19 4C 90 E0 C7 01 00 7E 19 L.~. L.~. >[020] 4C 90 E0 C7 01 20 02 00 00 00 00 00 00 L .. . > > For now, I can NOT afford for Samba to be destroying my files, so I'm going > to > switch back to 2.x and statically link the CUPS libs (the main driving reason > to > upgrade in the first place - samba2 doesn't support CUPS 1.2) Good luck. I remember that you said that the Samba 3 compilation was not very smooth on Solaris 9, did you check the compilation info from here: http://us4.samba.org/samba/ftp/Binary_Packages/solaris/sparc/ Kind regards, - -- Felipe Augusto van de Wiel <[EMAIL PROTECTED]> Coordenadoria de Tecnologia da Informação (CTI) - SEDU/PARANACIDADE http://www.paranacidade.org.br/ Phone: (+55 41 3350 3300) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGxaKbCj65ZxU4gPQRCEUvAJ4z8hjBiX3H8jEuoj0YPBwUipJ31QCgzgih rl4zyXMqyhrDCju4pKPB1U0= =gwqB -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] samba3 upgrade misery
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Curtis Maloney wrote, On 16-08-2007 21:08: > Felipe Augusto van de Wiel wrote: >> Curtis Maloney wrote, On 15-08-2007 21:07: [...] >> There are quite a few messages on the archive about >> different speed problems with regards to Samba serving files, > > Honestly, I think if I can stop smbd barfing and closing > sockets, the problems might just clear up... Seems reasonable. > smbd is repeatedly spewing forth lists of socket options from > print_socket_options: [...] What testparm tells you about your smb.conf parameters with regards to the socket options? >> What options did you tried? Can you post more details >> about your smb.conf? > > With samba 2 I used the line: > socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY SO_BROADCAST In recent version of Linux (2.6.x) it is the consensus on this list to drop some of the flags, I'm not so sure about Solaris kernel. > And things were just fine. Here are a few messages from threads about performance, maybe you can find something useful for your case. http://lists.samba.org/archive/samba/2007-April/131096.html http://lists.samba.org/archive/samba/2007-February/129562.html http://lists.samba.org/archive/samba/2007-April/131091.html http://lists.samba.org/archive/samba/2007-February/129139.html http://lists.samba.org/archive/samba/2007-January/128814.html http://lists.samba.org/archive/samba/2007-January/128645.html http://lists.samba.org/archive/samba/2007-February/129652.html http://lists.samba.org/archive/samba/2007-February/129797.html >>> 3) And what can I say to my boss who keeps asking "What does samba3 give us >>> over >>> samba2?" Because frankly, I'm coming up empty. >> >> First, maintainance, Samba2 is deprecated, no security >> updates. It is better to "talk" with client machines in several >> ways. It uses tdbs and/or LDAP, account policies, group mappings. > > Well, security's always a good point... Could you possibly elaborate at all > on > what advantage tdbs gives? I have switched to using it, but, again, the docs > aren't very specific on its gains. Check tdb source forge page: http://sourceforge.net/projects/tdb/ The idea is that it allow multiple writes, should be faster and safer (because it uses internal locks). http://wiki.samba.org/index.php/TDB It also has nice backup tools to keep various different information about Samba and its network environment. >> I'm not sure if you are using LDAP, it is a powerful >> resource, specially if you want to have PDC/BDC behaviour. The >> Samba3 changes a few points in the course of his development, I >> don't know what migration doc you read, but if it is not about >> 3.0.25, you need to check a few extra points from the release >> notes that will solve a few problems. > > The only feature of a PDC we use is the single point of authentication. Hmmm... PDC/BDC spreads the authentication among them, they do not use a single point. You can have a authentication server without being a PDC. :-) > Other than that, we just need to share files (and because of > some ridiculously old apps, printers). Nice, a standalone server would work great. > The possibility of using LDAP has surfaced a few times, but > as yet it's been avoided as grossly over complex for us, a > security hassle, and various other issues. I'm biased, but I would use LDAP for networks with 10 users. :-) > I read the migration docs on the web site, so if they're not > current, someone should make them so. Seems fair, do you have any links? Kind regards, - -- Felipe Augusto van de Wiel <[EMAIL PROTECTED]> Coordenadoria de Tecnologia da Informação (CTI) - SEDU/PARANACIDADE http://www.paranacidade.org.br/ Phone: (+55 41 3350 3300) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGxaHvCj65ZxU4gPQRCPQbAKC2d+i8dF9elM8SmVdO3CQCjyVbkQCcDJSn uiZ3OQ7pSyKc6ISmvoEaegg= =xwoG -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] samba3 upgrade misery
Felipe Augusto van de Wiel wrote: Curtis Maloney wrote, On 15-08-2007 21:07: Greetings, all Hey Curtis, Well, just had a user come and show me a JPEG that's been corrupted because the file copy died part way through. The error was that the destination folder was no longer available. I have no idea how much of the copious logs are relevant to the debugging of this issue, as there are no log level indications (why not??) so I'll paste as much as seems relevant. Feel free to ask for more. [2007/08/17 15:38:59, 8] smbd/dosmode.c:dos_mode(371) dos_mode: PROJS/R425_E1022_EV15_12 Scan Eng/EV12_assy_TB1.JPG [2007/08/17 15:38:59, 8] smbd/dosmode.c:dos_mode_from_sbuf(188) dos_mode_from_sbuf returning a [2007/08/17 15:38:59, 8] smbd/dosmode.c:dos_mode(409) dos_mode returning a[sparse] [2007/08/17 15:38:59, 10] smbd/trans2.c:call_trans2qfilepathinfo(3539) call_trans2qfilepathinfo: SMB_FILE_BASIC_INFORMATION [2007/08/17 15:38:59, 5] smbd/trans2.c:call_trans2qfilepathinfo(3549) SMB_QFBI - create: Fri Aug 17 15:34:36 2007 access: Fri Aug 17 15:34:36 2007 write: Fri Aug 17 15:34:36 2007 change: Fri Aug 17 15:34:36 2007 mode: 220 [2007/08/17 15:38:59, 9] smbd/trans2.c:send_trans2_replies(712) t2_rep: params_sent_thistime = 2, data_sent_thistime = 40, useable_space = 131010 [2007/08/17 15:38:59, 9] smbd/trans2.c:send_trans2_replies(714) t2_rep: params_to_send = 2, data_to_send = 40, paramsize = 2, datasize = 40 [2007/08/17 15:38:59, 5] lib/util.c:show_msg(484) [2007/08/17 15:38:59, 5] lib/util.c:show_msg(494) size=100 smb_com=0x32 smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=136 smb_flg2=51265 smb_tid=1 smb_pid=2532 smb_uid=101 smb_mid=13570 smt_wct=10 smb_vwv[ 0]=2 (0x2) smb_vwv[ 1]= 40 (0x28) smb_vwv[ 2]=0 (0x0) smb_vwv[ 3]=2 (0x2) smb_vwv[ 4]= 56 (0x38) smb_vwv[ 5]=0 (0x0) smb_vwv[ 6]= 40 (0x28) smb_vwv[ 7]= 60 (0x3C) smb_vwv[ 8]=0 (0x0) smb_vwv[ 9]=0 (0x0) smb_bcc=45 [2007/08/17 15:38:59, 10] lib/util.c:dump_data(2261) [000] 00 00 00 00 00 00 7E 19 4C 90 E0 C7 01 00 7E 19 ..~. L.~. [010] 4C 90 E0 C7 01 00 7E 19 4C 90 E0 C7 01 00 7E 19 L.~. L.~. [020] 4C 90 E0 C7 01 20 02 00 00 00 00 00 00 L .. . For now, I can NOT afford for Samba to be destroying my files, so I'm going to switch back to 2.x and statically link the CUPS libs (the main driving reason to upgrade in the first place - samba2 doesn't support CUPS 1.2) -- Curtis Maloney [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba3 upgrade misery
Felipe Augusto van de Wiel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Curtis Maloney wrote, On 15-08-2007 21:07: Greetings, all Hey Curtis, Hi... thanks for responding. There are quite a few messages on the archive about different speed problems with regards to Samba serving files, Honestly, I think if I can stop smbd barfing and closing sockets, the problems might just clear up... 1) Why are so many socket connections being aborted? How can I track down the cause? Try to increase the debug level (log level) to 10, you can also strace the process and/or capture the packages to try to figure out something. I've set the debug level to 10 (yay for smbcontrol) and will see what more info I can glean. smbd is repeatedly spewing forth lists of socket options from print_socket_options: [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(206) socket option SO_KEEPALIVE = 8 [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(206) socket option SO_REUSEADDR = 4 [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(206) socket option SO_BROADCAST = 0 [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(206) socket option TCP_NODELAY = 0 [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(206) socket option IPTOS_LOWDELAY = 0 [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(206) socket option IPTOS_THROUGHPUT = 0 [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(206) socket option SO_SNDBUF = 49152 [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(206) socket option SO_RCVBUF = 49640 [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(204) Could not test socket option SO_SNDLOWAT. [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(204) Could not test socket option SO_RCVLOWAT. [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(204) Could not test socket option SO_SNDTIMEO. [2007/08/17 10:00:53, 5] lib/util_sock.c:print_socket_options(204) Could not test socket option SO_RCVTIMEO. The workstation logs are filling up with so much stuff, I can't tell if any of it's an error. 2) Why does set_socket_options have errors for ANY options I specify? Samba2 didn't. What options did you tried? Can you post more details about your smb.conf? With samba 2 I used the line: socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY SO_BROADCAST And things were just fine. 3) And what can I say to my boss who keeps asking "What does samba3 give us over samba2?" Because frankly, I'm coming up empty. First, maintainance, Samba2 is deprecated, no security updates. It is better to "talk" with client machines in several ways. It uses tdbs and/or LDAP, account policies, group mappings. Well, security's always a good point... Could you possibly elaborate at all on what advantage tdbs gives? I have switched to using it, but, again, the docs aren't very specific on its gains. I'm not sure if you are using LDAP, it is a powerful resource, specially if you want to have PDC/BDC behaviour. The Samba3 changes a few points in the course of his development, I don't know what migration doc you read, but if it is not about 3.0.25, you need to check a few extra points from the release notes that will solve a few problems. The only feature of a PDC we use is the single point of authentication. Other than that, we just need to share files (and because of some ridiculously old apps, printers). The possibility of using LDAP has surfaced a few times, but as yet it's been avoided as grossly over complex for us, a security hassle, and various other issues. I read the migration docs on the web site, so if they're not current, someone should make them so. -- Curtis Maloney [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba3 upgrade misery
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Curtis Maloney wrote, On 15-08-2007 21:07: > Greetings, all Hey Curtis, [...] > Then the user complaints started. The network is _slow_. Files can take > minutes to load. I tried eliminating all the variables - disable the virus > checker, copy the file locally, etc etc. There are quite a few messages on the archive about different speed problems with regards to Samba serving files, frankly speaking, I couldn't tell you one idea, I've been fortunate enough to not have performance problems with my Samba boxes, but all in all, it seems to be related with several small good practices of oplocks, socket options and other smb.conf parameters. > It's samba. [...] > First, the details: > Solaris 9 > Samba 3.0.25b > GCC 3.4.6 > > 1) Why are so many socket connections being aborted? How can I track down > the > cause? Try to increase the debug level (log level) to 10, you can also strace the process and/or capture the packages to try to figure out something. > 2) Why does set_socket_options have errors for ANY options I specify? Samba2 > didn't. What options did you tried? Can you post more details about your smb.conf? > 3) And what can I say to my boss who keeps asking "What does samba3 give us > over > samba2?" Because frankly, I'm coming up empty. First, maintainance, Samba2 is deprecated, no security updates. It is better to "talk" with client machines in several ways. It uses tdbs and/or LDAP, account policies, group mappings. I'm not sure if you are using LDAP, it is a powerful resource, specially if you want to have PDC/BDC behaviour. The Samba3 changes a few points in the course of his development, I don't know what migration doc you read, but if it is not about 3.0.25, you need to check a few extra points from the release notes that will solve a few problems. I hope this helps. Kind regards, - -- Felipe Augusto van de Wiel <[EMAIL PROTECTED]> Coordenadoria de Tecnologia da Informação (CTI) - SEDU/PARANACIDADE http://www.paranacidade.org.br/ Phone: (+55 41 3350 3300) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGxEuACj65ZxU4gPQRCH9rAKCf7ioP3sB1PrL9K0c6SC0tboCKDACfUaB9 Uwva4paIZvFYIjs/d809sXM= =urGP -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba3 upgrade misery
Greetings, all We've been running samba2 for far too long - I'd just never found the time to upgrade, and it wasn't a priority since it WORKED. Our little Solaris9/SPARC64 box happily served our few gigs of files to 20 users, and played the part of a PDC. Then I upgraded CUPS, and discovered samba2 doesn't like cups-1.2 libs, and figured it was as good an excuse to make the time to upgrade. I found the online doco about upgrading 2 to 3 (the lack of which previously had been another major reason to avoid it). I downloaded the latest source, and it compiled _relatively_ OK. There was a libtool issue (it assumes you're using GNU binutils if you're using GCC, and messes up Solaris' ld, but building static fixes that). The actual upgrade seemed to go very smoothly. The most burdensome part was having to explicitly tell all the client machines the IP of the WINS server - even though all the doco I could find said I shouldn't need or want to. Then the user complaints started. The network is _slow_. Files can take minutes to load. I tried eliminating all the variables - disable the virus checker, copy the file locally, etc etc. It's samba. Checking the logs, I can see why! All the client machines are reconnecting periodically, most likely due to the smbd task choking off sockets: [2007/08/16 09:13:41, 0] smbd/server.c:open_sockets_smbd(527) open_sockets_smbd: accept: Software caused connection abort [2007/08/16 09:15:16, 0] lib/util_sock.c:set_socket_options(261) Failed to set socket option SO_KEEPALIVE (Error Invalid argument) [2007/08/16 09:15:16, 0] lib/util_sock.c:get_peer_addr(1232) getpeername failed. Error was Transport endpoint is not connected [2007/08/16 09:25:42, 0] smbd/server.c:open_sockets_smbd(527) open_sockets_smbd: accept: Software caused connection abort [2007/08/16 09:36:42, 0] smbd/server.c:open_sockets_smbd(527) open_sockets_smbd: accept: Software caused connection abort [2007/08/16 09:47:50, 0] smbd/server.c:open_sockets_smbd(527) open_sockets_smbd: accept: Software caused connection abort First, the details: Solaris 9 Samba 3.0.25b GCC 3.4.6 1) Why are so many socket connections being aborted? How can I track down the cause? 2) Why does set_socket_options have errors for ANY options I specify? Samba2 didn't. 3) And what can I say to my boss who keeps asking "What does samba3 give us over samba2?" Because frankly, I'm coming up empty. -- Curtis Maloney [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
