since update to 687 loads of winbind errors [Solved]

[maulbongo]

Hi folks,

Yesterday I upgraded our company nas to 687 since then I get nearly every minute these errors:

Code: Select all

May 7 09:25:49	ewnas01	winbindd[19562]: [2013/05/07 09:25:49.935165, 0] lib/fault.c:51(fault_report)
May 7 09:25:49	ewnas01	winbindd[19562]: ===============================================================
May 7 09:25:49	ewnas01	winbindd[19562]: [2013/05/07 09:25:49.935212, 0] lib/fault.c:52(fault_report)
May 7 09:25:49	ewnas01	winbindd[19562]: INTERNAL ERROR: Signal 11 in pid 19562 (3.6.14)
May 7 09:25:49	ewnas01	winbindd[19562]: Please read the Trouble-Shooting section of the Samba3-HOWTO
May 7 09:25:49	ewnas01	winbindd[19562]: [2013/05/07 09:25:49.935227, 0] lib/fault.c:54(fault_report)
May 7 09:25:49	ewnas01	winbindd[19562]:
May 7 09:25:49	ewnas01	winbindd[19562]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
May 7 09:25:49	ewnas01	winbindd[19562]: [2013/05/07 09:25:49.935240, 0] lib/fault.c:55(fault_report)
May 7 09:25:49	ewnas01	winbindd[19562]: ===============================================================
May 7 09:25:49	ewnas01	winbindd[19562]: [2013/05/07 09:25:49.935250, 0] lib/util.c:1117(smb_panic)
May 7 09:25:49	ewnas01	winbindd[19562]: PANIC (pid 19562): internal error
May 7 09:25:49	ewnas01	winbindd[19562]: [2013/05/07 09:25:49.935300, 0] lib/util.c:1221(log_stack_trace)
May 7 09:25:49	ewnas01	winbindd[19562]: BACKTRACE: 0 stack frames:
May 7 09:25:49	ewnas01	winbindd[19562]: [2013/05/07 09:25:49.935335, 0] lib/fault.c:416(dump_core)
May 7 09:25:49	ewnas01	kernel: pid 19562 (winbindd), uid 0: exited on signal 6
May 7 09:25:49	ewnas01	winbindd[19562]: dumping core in /var/log/samba/cores/winbindd
May 7 09:25:49	ewnas01	winbindd[19562]:

Before we were running 636 without any problems.

The config did not change it was only an upgrade.
Although it is written that a core dump is created there is none, which I could provide.
AIO is disabled, smb2 is active, large read write is active and enable store dos attributes is enabled.
This is a productive server, so for the moment I'm not able to switch to full or debug log, but if this is needed I can switch it tonight.

[kkd]

I got the same, but everythings seems working fine.

[maulbongo]

For me not everything is working fine.
When these errors appear, also saving of files take longer.
Now I got 690 running with full log and I will keep an eye on it today.

[kkd]

Samba 3.6 got errors like that, samba 3.5 not

[maulbongo]

Nope, with the 636, which had samba 3.6.12 there I never had these errors.

[kkd]

Any news? Did you find anything in the full logs?

[maulbongo]

Just the moment you asked I got this:

Code: Select all

Please read the Trouble-Shooting section of the Samba3-HOWTO
May 13 10:35:39 ewnas01 winbindd[94927]: [2013/05/13 10:35:39.568879,  0] lib/fault.c:54(fault_report)
May 13 10:35:39 ewnas01 winbindd[94927]:   
May 13 10:35:39 ewnas01 winbindd[94927]:   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
May 13 10:35:39 ewnas01 winbindd[94927]: [2013/05/13 10:35:39.568898,  0] lib/fault.c:55(fault_report)
May 13 10:35:39 ewnas01 winbindd[94927]:   ===============================================================
May 13 10:35:39 ewnas01 winbindd[94927]: [2013/05/13 10:35:39.568912,  0] lib/util.c:1117(smb_panic)
May 13 10:35:39 ewnas01 winbindd[94927]:   PANIC (pid 94927): internal error
May 13 10:35:39 ewnas01 winbindd[94927]: [2013/05/13 10:35:39.568960,  0] lib/util.c:1221(log_stack_trace)
May 13 10:35:39 ewnas01 winbindd[94927]:   BACKTRACE: 0 stack frames:
May 13 10:35:39 ewnas01 winbindd[94927]: [2013/05/13 10:35:39.569004,  0] lib/fault.c:416(dump_core)
May 13 10:35:39 ewnas01 winbindd[94927]:   dumping core in /var/log/samba/cores/winbindd
May 13 10:35:39 ewnas01 winbindd[94927]: 
May 13 10:35:39 ewnas01 smbd[94926]: [2013/05/13 10:35:39.570742,  2] lib/module.c:64(do_smb_load_module)
May 13 10:35:39 ewnas01 smbd[94926]:   Module '/usr/local/lib/samba/vfs/zfsacl.so' loaded
May 13 10:35:39 ewnas01 smbd[94926]: [2013/05/13 10:35:39.570831,  2] lib/module.c:64(do_smb_load_module)
May 13 10:35:39 ewnas01 smbd[94926]:   Module '/usr/local/lib/samba/vfs/shadow_copy2.so' loaded
May 13 10:35:39 ewnas01 smbd[94926]: [2013/05/13 10:35:39.571053,  1] smbd/service.c:1114(make_connection_snum)

and this

Code: Select all

May 13 10:35:39 ewnas01 smbd[94926]: [2013/05/13 10:35:39.564770,  2] smbd/sesssetup.c:1291(setup_new_vc_session)
May 13 10:35:39 ewnas01 smbd[94926]:   setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
May 13 10:35:39 ewnas01 smbd[94926]: [2013/05/13 10:35:39.566634,  2] smbd/sesssetup.c:1291(setup_new_vc_session)
May 13 10:35:39 ewnas01 smbd[94926]:   setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
May 13 10:35:39 ewnas01 winbindd[94927]: [2013/05/13 10:35:39.568821,  0] lib/fault.c:51(fault_report)
May 13 10:35:39 ewnas01 winbindd[94927]:   ===============================================================
May 13 10:35:39 ewnas01 winbindd[94927]: [2013/05/13 10:35:39.568858,  0] lib/fault.c:52(fault_report)
May 13 10:35:39 ewnas01 winbindd[94927]:   INTERNAL ERROR: Signal 11 in pid 94927 (3.6.14)
May 13 10:35:39 ewnas01 winbindd[94927]:  CLOG

edit: This happened while saving a big file (it was a pdf with size of 15MB).
edit the second: this was a pdf created by indesign, which had the Project file on the same share, so read and write on this share at the same time, perhaps this is a hint.

[kkd]

while copying big file (84MB):

Code: Select all

May 13 13:43:36	fn	winbindd[13323]:
May 13 13:43:36	fn	winbindd[13323]: dumping core in /var/log/samba/cores/winbindd
May 13 13:43:36	fn	winbindd[13323]: [2013/05/13 13:43:36.088667, 0] lib/fault.c:416(dump_core)
May 13 13:43:36	fn	winbindd[13323]: BACKTRACE: 0 stack frames:
May 13 13:43:36	fn	winbindd[13323]: [2013/05/13 13:43:36.088620, 0] lib/util.c:1221(log_stack_trace)
May 13 13:43:36	fn	kernel: pid 13323 (winbindd), uid 0: exited on signal 6
May 13 13:43:36	fn	winbindd[13323]: PANIC (pid 13323): internal error
May 13 13:43:36	fn	winbindd[13323]: [2013/05/13 13:43:36.088573, 0] lib/util.c:1117(smb_panic)
May 13 13:43:36	fn	winbindd[13323]: ===============================================================
May 13 13:43:36	fn	winbindd[13323]: [2013/05/13 13:43:36.088560, 0] lib/fault.c:55(fault_report)
May 13 13:43:36	fn	winbindd[13323]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
May 13 13:43:36	fn	winbindd[13323]:
May 13 13:43:36	fn	winbindd[13323]: [2013/05/13 13:43:36.088542, 0] lib/fault.c:54(fault_report)
May 13 13:43:36	fn	winbindd[13323]: Please read the Trouble-Shooting section of the Samba3-HOWTO
May 13 13:43:36	fn	winbindd[13323]: INTERNAL ERROR: Signal 11 in pid 13323 (3.6.14)
May 13 13:43:36	fn	winbindd[13323]: [2013/05/13 13:43:36.088510, 0] lib/fault.c:52(fault_report)
May 13 13:43:36	fn	winbindd[13323]: ===============================================================

[maulbongo]

Ok, Zoon was that nice to push a 698 beta with samba 3.6.15 and I already upgraded.
I'll report again whats going on.

[raulfg3]

probably works fine, SAMBA update 3.6.14 due some winwind crashes: http://www.samba.org/samba/history/samba-3.6.15.html

[kkd]

should I brave enough to upgarde my prod n4f to 698 beta?

[maulbongo]

So, I tested a lot and now I can report no more problems.
Great, thanks a lot.

[kkd]

Good news

[CMDRSweeper]

How did you solve this? I am on version 690 and my winbindd flat out panics with Signal 11 and most likely desperatly needs an update.
Without it, the AD integration is kinda stranded.

[raulfg3]

you need ver 698 or up and SAMBA 3.6.15

[CMDRSweeper]

So there is no package I can update manually or a repository like system?

[kkd]

why sould you? firmware update is a very easy way to update

[CMDRSweeper]

Well for each update I need to burn a CD due to USB issues
So thats why it would be easier to do it manually, even from the command line, but I normally mess around with Debian based systems.

[kkd]

ohhh... thought having usb is not big deal today, but i understand. no free sata neither?

[CMDRSweeper]

All my USB attempts just gives me a useless corrupt USB device, so now I use an old IDE DVD burner I had lying around, and an Intel 80Gb SSD, sacrificing a SATA port for it.
I guess the only way to make it work properly is to get rolling on my setup of network installs.
Right now I am setting up the rsync backup, but I find the GUI method too annoying to get right, so I am doing the CLI and script way

[fsbruva]

If you are running an embedded installation, you can upgrade using the .img file from the webgui - no CD's needed.

Go to System --> FIrmware, and download the appropriate .img from soureforge. Then, upload to the NAS. It will complete the update and reboot. Magic!

[maulbongo]

you need ver 698 or up and SAMBA 3.6.15

Since this post it went Off topic open a New thread for your problems, please.