similar to: Re: Intermittent "internal error: signal 11" with 3.0.24

Hi all Follow up to this post, we've been able to capture a gdb backtrace. Can anyone help with guidance as to what this means. See below: (gdb) bt #0 0xffffe410 in ?? () #1 0x00000001 in ?? () #2 0x00000000 in ?? () #3 0xbfffc9d8 in ?? () #4 0x402b36e3 in __waitpid_nocancel () from /lib/tls/libc.so.6 #5 0x4025ef58 in do_system () from /lib/tls/libc.so.6 #6 0x402268dd in system ()

Hi Volker We run 3 x SLES9 SP3 and the same problem occurs in all three environments, the backtraces for panic'd smbd processes of all three hosts are essentially the same as what I posted before. Kernel: 2.6.5-7.97-bigsmp and Samba: Version 3.0.24-SerNet-SuSE. SMB.conf inline below (I've swapped <ad_domain> for our dom.tld): ------------------------------------- [global] workgroup

Hi Samba list, We're experiencing some issues with our Samba 3.0.24 environments. Hopefully somebody can offer suggestions or guidance. A bit of background. We have 3 application environments, which consist of a Samba host providing file sharing services to 7 Windows application servers. These Samba hosts intermittently experiencing problem providing file sharing. So far we haven't

Hello, after an update from Samba 2.2.12 to 3.0.22 and running the daemons 2-3 days my Samba Server freeze the whole Server. First the clients get connection problems, timing out to access the shares and then some minutes later the whole Server freeze, i can't even logon on the console. Only a cold reset is possible. I convert all files from latin-1 to a UTF-8 and then from UTF-8 to ISO-8859-1

Hi, I recently upgraded an older box running as a file server for a small company to Mandriva (Mandrake) 10.1. It's running Samba 3.0.10.1, the default Mandrake package. We have a custom script that mounts a Windows share using smbfs, backs up specific directories, and unmounts when it's done. The problem is, it's not mounting reliably. There is an entry in /etc/fstab for the

Hello, I'm hoping someone can help me. I have several pdf printers set up and when I print to them samba becomes unstable and several errors are dumped to the log. These pdf printers were working when I was using version 3.0.6. When I went to a newer version of samba the queue would not clear on the windows side and no errors were logged. Yesterday I upgraded to version 3.0.13-1 and the

Urs Rau wrote: >>I start to wonder what "dammage" it would do to set lpq to >>lpq command =/bin/true >>for my pdf printer? ;-) > > > > Well, wonder no more sir!!!!!! I set my lpq command = /bin/true and > ALL QUEUES CLEAR AND ACT PROPERLY!!!!!!!!!!!! I could kiss you! That was all I did, I can't believe it worked......thank you!!!!!! >

First, my installation is samba 2.2.8 running as a daemon (not inetd) on Solaris 8 configured to use a WINS server and provide authentication via a PDC (same host as WINS server). I do have an lmhosts file in the samba /lib directory with the PDC/WINS server address in it. My globals section; [global] workgroup = WORKGROUP netbios name = SAMBASERVER security =

I am not sure if your problem is similar to what we have just experienced. we are using samba 2.2.3a-12.3 on debian with winxp sp1 clients we are using roaming profiles first logon after reboot fails sortof Windows cannot find a server copy of roaming profile will logon with local profile funny thing we never saw any activity in hostname.log (seperate smb.log for each machine) smbstatus showed

This with Samba 4.4.3 on Solaris 10. I have been looking at the logs and see messages such as: [2016/06/13 14:20:37.074011, 0] ../source3/smbd/oplock.c:242(remove_oplock) remove_oplock: failed to lock share entry for file packages/winnt/adv084/8.4.1/8.4.1.6.iso [2016/06/13 14:20:37.075061, 0] ../source3/smbd/close.c:266(close_remove_share_mode) close_remove_share_mode: Could not get share

I recently installed Samba 3.4.5 on Ubuntu 8.04 64 bit and had to downgrad again because of massive core panics: I can't really tell you what caused that (maybe while printing via samba-cups) - can somebody give me a hint or tell me what information you need to analyze that please? [2010/01/25 13:46:52, 0] lib/fault.c:46(fault_report)

> On Tue, Jun 28, 2016 at 11:59:32AM -0400, Thomas Schulz wrote: >> This with Samba 4.4.3 on Solaris 10. >> >> I have been looking at the logs and see messages such as: >> >> [2016/06/13 14:20:37.074011, 0] ../source3/smbd/oplock.c:242(remove_oplock) >> remove_oplock: failed to lock share entry for file packages/winnt/adv084/8.4.1/8.4.1.6.iso >>

Hi, I'm setting up a Samba AD member server on CentOS 6. Everything seems to work, except that Windows users don't get automatically created in the idmap backend (which is an LDAP tree, btw). I do get the following errors in the winbind logging: [2012/01/26 13:04:20.634990, 1] winbindd/idmap_ldap.c:193(verify_idpool) Unable to verify the idpool, cannot continue initialization!

I was in the process of setting up a new Samba 3.5.4 PDC with LDAP backend, over CentOS 5.5, when I came across a very strange behavior. After executing the smbladp-populate script, I was trying to grant the needed privileges to the group "Domain Admins" in order no to use "root" to manage the Windows domain. After successfully granting rights to the "Admin"

Happened to be tail'ing <machine>.log during a login session from XP client and notice the PANIC in the output. Login proceeded as usual(?) so the following snippet of the log is just informational to the developers. Let me know if you need additional info. Bob --bs [2010/08/25 21:34:21.689597, 4] auth/pampass.c:472(smb_pam_start) smb_pam_start: PAM: Init user: rwsmith [2010/08/25

Hello, When I am using module acl_tdb and I am trying to get access to directory I am getting call trace in log.ip Best regards! /Adrian Berlin =============================================================== [2010/03/24 13:54:05.295901, 0] lib/fault.c:47(fault_report) INTERNAL ERROR: Signal 11 in pid 15556 (3.5.1) Please read the Trouble-Shooting section of the Samba3-HOWTO [2010/03/24

I have an Ubuntu Sever 9.10 setup running Samba as a PDC for a bunch of Windows clients. Everything is functioning perfectly except for the point and print delivery of printer drivers. I have tested this with Ubuntu 9.10's Samba (3.4.0) and two of the Debian Samba packages (3.4.3 and 3.4.5). All seem to demonstrate the same problem. *What works:* Adding a printer and manually installing the

Hi team! Samba 4.1.11 on Debian Wheezy here, configured as a DC. I recently started noticing long startup times for the Windows clients, whenever multiple clients are started at the same time. For example, at 8:00 AM (when around 30 PCs get started simoultaneously, I get this in smbd.log: ### [2014/09/16 08:01:21.320944, 0] ../source3/smbd/oplock.c:335(oplock_timeout_handler) Oplock break

Hi, I am running 2DCs and 1 member server. All are running samba 4.1.2 The member server hosts the file for access and it is full of log like: [2013/11/26 14:57:46.970108, 0] ../source3/smbd/oplock.c:333(oplock_timeout_handler) Oplock break failed for file Putonghua/aaa.pptx -- replying anyway [2013/11/26 14:57:50.069924, 0] ../source3/smbd/oplock.c:333(oplock_timeout_handler) Oplock

Hello, I have a problem with files locks on share. My server is running FreeBSD 10.2 (amd64) with ZFS pool (raidz) for windows share and samba 4.3.3 (ROLE_ACTIVE_DIRECTORY_DC). The server has approximately 100 users accounts and computers accounts. >From one windows workstation I open a file e. g. text file (file.txt) the smbstatus shows DENY_WRITE and everything seems right. But when I open