similar to: remove_oplock: failed to lock share entry...

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

> On Wed, Jun 29, 2016 at 12:11:51PM -0400, Thomas Schulz wrote: > > > > Here is what I could find. The iso file is created on a Solaris system on > > a file system that is NFS mounted from our main file server. Then it is > > burned to a CD on a Windows 7 PC through a Samba server running on a > > different Solaris machine (Solaris 10) that is also NFS mounting

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

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.

Sorry for my previous email it was something wrong with my email client. Now is the corrected version: 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

Hello, last friday I switched my users from an old server running 2.2.12 to a new one running 3.0.10 (that I've been testing myself and with smbtorture). After a while I had to switch back to the old server because some users were having serious problems. This is one of the logs (the others are very similar): [2005/03/04 12:25:05, 0] tdb/tdbutil.c:tdb_log(725)

Hey folks... I'm using the Redhat Samba package (samba-3.0.33-3.15.el5_4.1) and I'm having a problem with one specific user. When she opens a project for her program, there are several shape files which need to open. Unfortunately, performance is EXTREMELY slow for her; everyone else who accesses the project can open it up quickly and normally. A tail of /var/log/samba/<IP

We have been using samba for years now and are generally very happy. But since a recent upgrade to 2.2.8 we have seen samba slowing down periodically to a crawl every 2 or 3 days. BTW the start of these problems coincided with the upgrade to samba 2.2.8 and a partial cabling upgrade to 100 MBit, which also coincided with the introduction of the first Win XP Pro machines to our LAN. ;-( We have

Hello. I'm seeing several of the above messages in my smbd logs. I see three different kinds: > close_directory: Could not delete share entry for . > close_directory: Could not delete share entry for {filename} > close_remove_share_mode: Could not delete share entry for file {filename} I could find no explanation on their meaning. Anyone has a pointer? bye & Thanks av.

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

I would really appreciate some help figuring out why one of my students has "disappeared" from the user list, and what to do about it. I'm using Samba3 on Fedora; the client machines are running WinXP. The system has been up and running since the beginning of September. Today one of my 4th-graders was unable to log on; she didn't read the error message carefully, so she

Hi, I'm hoping somebody can point me in the right direction. My samba version is samba-4.2.10-6.2.el7_2.x86_64. I have lots of daily core dumps (~20 on each machine daily) and I have no clear idea why. I'm including the stack trace below. It looks like the problem is related to "invalid lock_order". Any ideas? Thanks, Sergei #0 0x00007fc5a34945f7 in raise () from

On Fri, 6 Jan 2017 22:28:11 -0600 Sergei Gerasenko via samba <samba at lists.samba.org> wrote: > Hi, > > I'm hoping somebody can point me in the right direction. My samba > version is samba-4.2.10-6.2.el7_2.x86_64. I have lots of daily core > dumps (~20 on each machine daily) and I have no clear idea why. I'm > including the stack trace below. It looks like the

All, I am using the tcltk package (under macos 10.3.8, running R from ESS, R 2.0.0). I am using tcltk libraries from fink: i tcltk 8.4.1-12 Tool Command Language and the Tk toolkit i tcltk-dev 8.4.1-12 Tool Command Language and the Tk toolkit i tcltk-shlibs

Hello, I have Dovecot configured with Solr for the indexes. I have need your support for upgrade solr 7.7.2 to 8.4.1. Solr 7.7.2 has a security issue CVE-2019-12409. It's possible upgrade of Solr? Dovecot work correctly with Solr 8.x? The Solr documentation recommended after updating: "It is always strongly recommended that you fully reindex your documents after a major version

On 2020-01-22 8:42 am, Domenico Pastore wrote: > Hello, > I have Dovecot configured with Solr for the indexes. > > I have need your support for upgrade solr 7.7.2 to 8.4.1. > Solr 7.7.2 has a security issue CVE-2019-12409. > > It's possible upgrade of Solr? > Dovecot work correctly with Solr 8.x? > > The Solr documentation recommended after updating: >

Hi, thanks for your answer. I confirm, mitigate this issue is very very easy. There are other issues with high severity for example CVE-2019-17558. Description: Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter I think for this issue there is only a solution, upgrade Solr to 8.4. It's Correct? So, with Dovecot is it possible

Using 2.3.8 and mail_location = maildir:/var/mail/%Ln:CONTROL=/var/lib/dovecot/control/%Ln:VOLATILEDIR=/var/lib/dovecot/control/%Ln:INDEX=/var/lib/dovecot/control/%Ln + also user_query = SELECT ... CONCAT('maildir:/var/mail/', LOWER(u.login), '/:CONTROL=/var/lib/dovecot/control/%Ln:VOLATILEDIR=/var/lib/dovecot/control/%Ln:INDEX=/var/lib/dovecot/control/%Ln') AS mail, ... but I

Wouldn't it make programming more error-resistant if vectors were initialized with missing data, instad of zeroes or ""? That way, if you assign values to a vector elementwise and you miss some elements (because their indices were not selected or because the assignment didn't work out, see below for code examples) this would be immediately obvious from the value of the vector

Le 25/11/2019 ? 09:15, L.P.H. van Belle via samba a ?crit?: > I tested Friday also with a W7 pc. > Not working, im try to see what i can do today on this problem. > > Greetz, > > Louis Hi Louis, Thanks for your help. I'm still investigating on it, but sadly i cannot upgrade to 4.11 as those servers cannot reach external repositories for security reasons (those servers