Created attachment 8700 [details] Core dump file Hi, I recently installed Samba on a Fedora Core 18 machine, and it is crashing about 20-30 times a day. I have attached the zipped core file, and config information below. I upgraded to 4.0.3, but it did not solve the problem. Any help would be much appreciated. I don't know if it is related, but many of our users (including myself) while working on Office applications often get an error message indicating that the connection to the network is lost, and the original file is named to a .tmp file. I see this reported a number of places, but none of the solutions apply to us. We are using Windows 7 x64, but a couple of users with Vista also see the problem. All windows computers are fully patched to the latest Windows updates. smbd -V Version 4.0.3 uname -a Linux host.domain.net 3.8.4-202.fc18.x86_64 #1 SMP Thu Mar 21 17:02:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux contents of smb.conf: [global] workgroup = OPTIMAL server string = Samba Server (Version %v) on OPTLNXSRV07 map to guest = Bad User hosts allow = 127. 192.168.88. 192.168.87. log file = /var/log/samba/log.%m max log size = 50 security = user passdb backend = tdbsam load printers = yes cups options = raw [homes] comment = Home Directories browseable = no writable = yes valid users = %S path = /personal/%S [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes [public] comment = Public Folder path = /business/public read only = No guest ok = Yes browseable = No directory mask = 0775 veto files = /business/public/.deleted vfs object = recycle recycle:repository = .deleted/%U recycle:keeptree = Yes recycle:touch = Yes recycle:versions = Yes recycle:maxsixe = 0 [scan] comment = Document Scan Folder path = /personal/docscan user = xeroxscanner read only = No guest ok = Yes browseable = No [operations] comment = Operations Folder path = /operations valid users = user1, user2, user3 force group = +operations read only = No create mask = 0770 directory mask = 0770 force directory mode = 0770 dos filemode = Yes browseable = No available = Yes veto files = /operations/.deleted vfs object = recycle recycle:repository = .deleted/%U recycle:keeptree = Yes recycle:touch = Yes recycle:versions = Yes recycle:maxsixe = 0 # Eight other shares configured exactly as [operations] above but with different path, force group, valid users, and veto files
Can you please upload the backtrace from log.smbd?
Created attachment 8708 [details] log.smbd files - tar'd and gzip'd log.smbd files uploaded as requested. These are all the logs since I installed samba on the new computer. Thank you for looking into this issue.
Unfortunately the file you uploaded does not contain any logfile with a panic inside. Next try: Please do a gdb /usr/sbin/smbd <path-to-corefile> and then at the gdb prompt do a bt full and upload the output.
Created attachment 8712 [details] log files with stack trace for smb_panic I believe the attached log.optpcdsk26 file has the information you may be looking for. The matching core dump is also attached. These are from one computer, however, I have the exact same error from over a dozen computers. I upgraded yesterday to Samba Version 4.0.4, but the problems continue. The attached logs and core dumps are all from after the upgrade.
Created attachment 8713 [details] Output of gdb bt full as requested I also listed all the object files referenced by the trace.
Created attachment 8714 [details] Object files referenced in the stack trace above Object files referenced in the stack trace are attached, in case it helps. Thanks.
Created attachment 8715 [details] Windows Error Corresponding to Crash OK, I think I can reliably cause this problem to occur it I perform the following steps in Windows: User 1 creates a file in share1 which User2 also has access to. User 2 modifies the file's name in Windows by clicking on the filename and editing it in place. As soon as I do this, I get the attached popup, and samba dumps core. If I press Try Again, the popup keeps appearing. If I press Cancel, and then refresh the Explorer Window (by pressing F5), the new file name appears, so it appears that the crash occurs after the renaming is completed. Hopefully you now have more information to resolve this issue. Thanks.
doesn't look like a generic samba bug bug like a problem of that specific compiled version. Please file a new report if you see such issues with a modern and supported samba version like 4.13 still.