similar to: Re: Intermittent "INTERNAL ERROR: Signal 11" with 3.0.24

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.

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

Hi all, sorry for the long posting. Samba 2.2.x is outdated. Trying to switch to 3.0.7 with no success. The vfs layer is one of my current problems. Googled some time for an solution for this: [2004/10/21 20:04:00, 0] smbd/server.c:main(760) smbd version 3.0.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2004 [2004/10/21 22:12:07, 0] smbd/server.c:main(760) smbd version

Hi all, We are trying to print the log messages pertaining to each share in a different log file for auditing purposes. We are using Samba v3.0.20b. We are trying to modify the file smbd/service.c::make_connection_snum() function by changing the log file full path. The code changes that is done are as follows: char logfilefullpath[70]; char sharename[256]; safe_strcpy_fn

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 would like to compile samba-latest on an old Linux system (SuSE 7.2). Everything seems to run quite well until it comes to the vfs-modules: ---snip--- Linking libsmbclient non-shared library bin/libsmbclient.a Linking libsmbclient shared library bin/libsmbclient.so Compiling modules/vfs_recycle.c with -fPIC Building plugin bin/recycle.so modules/vfs_recycle.po: In function

I am seeing these in smb.log and each time I do it appears that the user in question is unable to retrieve their roaming profile. Does anyone know what is going on and more importantly, how to cure it? . . . [2017/03/28 16:24:37.426162, 0] ../source3/smbd/oplock.c:713(oplock_timeout_handler) Oplock break failed for file Administrator/AppData/Roaming/Microsoft/Internet Explorer/Quick

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 guys. I´m experiencing some problems with corrupted files with samba 4.x. I´m using samba 4.4.4 and some files like excell, word, libreoffice are getting corrupted. The only thing that i saw at log files is this: [2016/09/19 13:54:00.312578, 0] ../source3/rpc_server/svcctl/srv_svcctl_nt.c:326(_svcctl_OpenServiceW) [2016/09/19 14:06:02.591121, 0]

I recently upgraded from samba 3.0.10-1.fc3 to 3.0.21b-2 running on FC5. Today was the first day of a typing class which uses the network version of Mavis Beacon Typing which depends on file sharing. The users are hanging and then getting an error message during logging into the product. In /var/log/message, I can see the following message for each user similar to: [2006/04/24

I'm attempting to compile the latest samba on an old Mandrake 8.1 system. (Current samba there is 2.2.? and doesn't allow login from XP). During compiling I get a number of error message such as modules/vfs_recycle.po: In function `recycle_connect': modules/vfs_recycle.po(.text+0x23): undefined reference to `DEBUGLEVEL_CLASS' modules/vfs_recycle.po(.text+0x31): undefined

Greetings, I am attempting to compile samba-.1.0 on a machine with these:- --cpu amd64 3cores --ozs blfs linux gcc-4.8.1, linux-3.10.17, glibc-2.17 waf build ( i.e. make ) ends like so"":- ################################## In file included from ../source3/lib/smbconf/smbconf_reg.c:26:0: ../source3/registry/reg_api_util.h:39:17: warning: 'enum winreg_CreateAction' declared

Hi I have problems with Samba and hope some of you can help me. Below if I have add the error messages that are relevant. [root at roskilde mosek]# emacs /var/log/samba/log.172.16.0.108 File Edit Options Buffers Tools Help [2014/02/06 10:18:29.562405, 0] smbd/oplock.c:330(oplock_timeout_handler) Oplock break failed for file windows/intel/Composer-XE-2013.198/Documentation/csupport.txt --

Hi all After running samba 3.0.0 for a couple of days I get messages like this in my logs which look a bit suspicious :-) to me. Anyone knows what this is all about? The result ist that copy jobs etc. are just signing off. Sorry for not entering this in the bugzilla thing. I am not too familiar using it. The samba version is 3.0.0 running against ldap 2.1.22 Here the globals from my smb.conf

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)

Hello! Our users created very large excel file - about 60 Mb, then when they want to open it from samba share, they can't. I see in log: [2006/07/26 12:33:20, 0] smbd/oplock.c:oplock_timeout_handler(366) Oplock break failed for file file.xls -- replying anyway Could you tell me what can I do to solve this problem? btw, there are no problems in network, looks like file is too large and

Hallo, in a neighbourhood school Samba (versions 3.5.7 and 3.5.10) show (for only one machine) the following log: ... [2012/02/02 11:08:34.974139, 0] lib/fault.c:326(dump_core) dumping core in /var/log/samba/cores/smbd [2012/02/02 11:37:33.245678, 0] smbd/sesssetup.c:1401(shutdown_other_smbds) shutdown_other_smbds: shutting down pid 18379 (IP 192.168.0.175) [2012/02/02 11:37:33.245983,

This problem has several elements but it did not evidence itself until we moved from a MicroSoft AD-DC to a Samba AD-DC. The environment is is a FreeBSD-10.3 Bhyve VM hosted on a 16 core host also running FreeBSD-10.3. The version of Samba is 4.3.11 obtained through FreeBSD ports. The AD clients are all running MSWin7pro patched up-to-date. Roaming profiles are in use. We have an intermittent

On 18/03/15 13:17, Adriana Moga wrote: > Hello, > > I have manually mounted the SYSVOL share, sync it with samba and run > samba-tool ntacl sysvolreset. What do you mean 'manually mounted the SYSVOL share' ? how did you do this ? > But I'm not sure if all windows policies are acceptable by samba because of > errors logs: > > 2015/03/18 09:30:52.197934, 0]