similar to: Panic / internal error signal 11 on access samba share

Hello All, I'm trying to figure out where the problem is, but I'm not having much luck as I seem to get conflicting information from the various logs on my FreeBSD 6.1 system. I'm getting this in the /var/log/samba/log.smbd: [2006/06/05 12:31:43, 0] smbd/oplock.c:release_level_2_oplocks_on_change(771) release_level_2_oplocks_on_change: failed to lock share mode entry for

Hello, I have a problem with samba 3.0.26a (from ports) on FreeBSD (amd64, SMP, 6.2 RELEASE). My log.smbd looks like below: --- samba starts normally: [2007/11/24 16:55:22, 0] smbd/server.c:main(944) smbd version 3.0.26a started. Copyright Andrew Tridgell and the Samba Team 1992-2007 --- but an error is reported: [2007/11/24 16:55:22, 0]

I'm using libvirt_lxc to create and manage various containers. I need to enable certain capabilities in a container to support ctdb, and as a quick solution I decided to just enable them all. I *thought* this would do the trick, adding the following XML to my container config: <features> <capabilities policy='allow'> </capabilities> </features> After

Hi All, I have a Samba server on a system, running and i386 Centos 5.1, version samba-3.0.25b-1.el5_1.4. The server is working well, as can share files etc with any issues. However when I try to add a windows XP printer driver, I get a Signal 11 error, and the drivers don't install, and windows gives an error messages, saying that the operation could not be completed. The files are actually

We're transitioning from a VM based environment to one that uses LXC based containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. The same packages running under LXC however seem to have issues: # systemctl start ctdb.service Job for ctdb.service failed. See 'systemctl status ctdb.service' and 'journalctl -xn' for details. # systemctl status ctdb.service

This morning I got two users come down to me saying their word doc was lost. Apparently they tried to save their docs to their home folder which is on samba share. XP had given an error along the lines 'Network connection to network drive is lost and word is unable to save the document' and then Word crashed. I went to smb logs and found this. [2004/01/22 10:03:11, 0]

Hi, winbindd (v 3.4.2) crashed last night and in the winbind-log I found following output: [2009/10/14 22:41:13, 0] lib/fault.c:41(fault_report) =============================================================== [2009/10/14 22:41:13, 0] lib/fault.c:42(fault_report) INTERNAL ERROR: Signal 11 in pid 1472 (3.4.2) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/10/14

Hello all, I'm having problems with samba 3.0, having the same problem with both the 3.0.0 and the 3.0.1pre3, below is the tail of the winbindd.log. winbindd runs for a bit, but after about 10 minutes it crashes with the error. I'm very new to linux, setting up samba is one of my first experiments with it. Am running fedora 1.0, don't know what other information you might need,

> I have just upgraded to Samba 2.0.6 and can no longer connect to Samba > shares on my FreeBSD 3.4-RELEASE machine. When I attempt to connect, the > smb.log contains the following information: > > [2000/01/04 17:54:42, 3] libsmb/namequery.c:resolve_lmhosts(566) > resolve_lmhosts: Attempting lmhosts lookup for name > NTWEB2.AIS.MSU.EDU<0x20> > [2000/01/04

I've got two brand-new, fully-patched XP SP2 clients who are suffering a mysterious malaise. These two machines will cause a smbd panic when printing or accessing files on a somewhat random basis. Now, the puzzling thing is that three other XP SP2 clients, including one of the exact same configuration, have no issues whatsoever. I've basically ruled out hardware failure on the server,

Hi, I'm seeing nmbd dying from segmentation violation in 2.0 beta4. Trying to track that down right now. For the moment it holds steady but once it died within 1 minute and once in under 5 minutes. This machine shares it's interface with another nmbd (1.9.18-10) which works fine. Additionally, it serves from an automounted nfs disk from another linux (2.0) server. (this machine is

My network consists of a Linksys WRT54GX wireless router connecting a Macintosh running OS X 10.4 (Samba version 3.0.10) and a Windows XP notebook. I can connect to the OS X shares wirelessly via the XP machine, but then one of two things happens: either the connection is immediately lost, the directory refreshes and I'm left staring at an empty folder. Or, what happens more

Hallo list, I am running a samba server on Arch Linux. From time to time I get this error message in the system log (journalctrl, log from systemd). I have read the Trouble-Shooting section of the Samba HOWTO as pointed out in the error, but I could not find anything related. Can s.o. please tell me how to approach this error, or even tell me that the reason could be. Any help is really

Hello list users. In my journey to world of Linux/Windows interoperability, I have now almost reached my goal to successfully authenticate Linux users using Windows Server 2003 SP2. The (hopefully) last obstacle is that "wbinfo -i <username>" causes the following error to be produced in log.wb-<DOMAIN> file (consequently, logins are failing also of course). Samba version is

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 ()

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, just installed and tested 3.0.2 for debian from backports.org. After some time I got an internal error: [2004/02/10 14:06:14, 0] smbd/posix_acls.c:create_canon_ace_lists(1481) create_canon_ace_lists: malformed ACL in file ACL ! Deny entry after Allow entry. Failing to set on file Projekt 2/klaus/Siehst du - geht doch.txt. [2004/02/10

Hi, Am running SAMBA 3.0.4 on RHEL 3.0 ( 2.4.21-9.ELsmp ) It was running fine till today when i restarted my server and started getting this nmbd log!! I might have overlooked, but if anyone could point me to any previous post with answers or any other link please mail me or if there is something new or anything more you want to help me solve this, please let me know. Any help is greatly

Hi all Follow up to this post, as it didn't seem to go through the first time. We have a common problem occurring with our Samba setups. We run 3 (identical) processing environments that each contain a Samba host sharing approx .5TB of data to 6 Wintel machines. Normally these hosts operate fine, though we intermittently experience a Samba panic (intermittent = every 2-3 days) as per below.

Hello! It seems my struggle with Samba isn't quite over. My latest problem is exactly what you see above, followed by an attempt to core dump. This occurs upon authentication to the system. My system is part of a W2K3 domain. I looked at the Samba HOWTO, but apparently I have a system (FC5), that doesn't allow core dumps when the PID changes, since no core dumps are being created.

I'm using libvirt_lxc and that has an XML based configuration. Based on what I've read, I think I need to add this to the ctdb container's config: <features> <capabilities policy='default'> <sys_nice state='on'/> </capabilities> </features> That didn't do the trick though. I need to figure out how to turn on all caps to