similar to: Failure to move object from one site to another

Hi There, We are getting INTERNAL ERROR: Signal 11 in pid on multiple different servers (Debian Wheezy, using Samba 4.0.13 and 4.1.3, using kernel 3.2.0-4 and 3.11.6-2), the outcome is always the same. The group policies can no longer be applied to the clients until a Samba4 restart. The locations with these issues do have in common that they have multiple Samba4 DC's although i am not

Any further information required? Any troubleshooting steps? I need to get this domain functional ASAP. Please advise. JS On Mar 2, 2016 11:39 AM, "IT Admin" <it at cliffbells.com> wrote: > Hello to the samba users list again. I've got an emergency here, a Samba > AD DC I've got deployed has crashed again, this is the third time since > 12/17/2015 that this

I built this machine, and while it isn't the most robust box in the world it has been stable otherwise. The RAID array is configured RAID1, I can't see how that could cause corruption issues and I haven't experienced any other data corruption issues apart from SAMBA collapsing. I did start seeing samba failures about two weeks ago, restarting the machine brought the domain up in

Hi Folks. I have installed an ipa server on a linux CentOS release 6.4 (Final). It is using outside DNS. I have https console access authenticating admin user through kerberos, and have migrated information on 80+ users and groups to it from a LDAP server. Packages related to ipa installed are: [root ~]# rpm -qa | grep ipa ipa-server-selinux-3.0.0-26.el6_4.2.x86_64

Hello to the samba users list again. I've got an emergency here, a Samba AD DC I've got deployed has crashed again, this is the third time since 12/17/2015 that this domain has failed completely. No power outages or unexpected shutdowns, samba simply fails to start, it appears my database is yet again corrupt: [2016/03/02 11:27:17.025235, 0]

Hi all, I am currently trying to set up a new samba server based on Samba 4.1.6 / CentOS 6.5 / CUPS in a production environment . Everything seems to be ok for AD DC setup . I am now in the step of making the print server running with Point?n?Print . I have followed as close as possible the HowTo : https://wiki.samba.org/index.php/Samba_as_a_print_server Everything is OK until the uploading

Hi again. I apologize for my vague previous question. After some investigation I can be much more precise in my consult. Furthermore, I think I found a bug... Context: -Samba4 AD DC working fine with many user and machine accouns. -Windows7 client trying to connect via sqlplus to an oracle database residing in a Windows2008 server. Both machines are in the domain. -Server database is using

On 02/03/16 20:46, IT Admin wrote: > Any further information required? Any troubleshooting steps? I need to > get this domain functional ASAP. > > Please advise. > > JS > On Mar 2, 2016 11:39 AM, "IT Admin" <it at cliffbells.com> wrote: > >> Hello to the samba users list again. I've got an emergency here, a Samba >> AD DC I've got

Thanks for your suggestions. Fortunately, the problem was probably because of a wrong configuration of kerberos. I since upgraded to 4.1.7 and it works ok. Thanks. 2014-04-25 9:38 GMT+04:00 henri transfert <hb.transfert at gmail.com>: > Thanks for your suggestions. > > Fortunately, the problem was probably because of a wrong configuration of > kerberos. > I since upgrade

Hello Rowland, Find the _*smb.conf :*_ [global] netbios name = DC4 realm = KTKBANKLTD.COM server role = active directory domain controller workgroup = KTKBANKLTD [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No [netlogon] path = /usr/local/samba/var/locks/sysvol/ktkbankltd.com/scripts ??????read only = No *Logs:* {"timestamp":

On 03/03/15 09:56, Izan D?ez S?nchez wrote: > Hi again. I apologize for my vague previous question. After some > investigation I can be much more precise in my consult. Furthermore, I > think I found a bug... > > Context: > -Samba4 AD DC working fine with many user and machine accouns. > -Windows7 client trying to connect via sqlplus to an oracle database > residing in a

Good evening, We have been dealing with an incident for several weeks during peak load times, either due to authentications or service accesses that rely on Samba 4 AD. Below are the details of the current Samba version and OS: **Samba version 4.19.2** ```bash ~$ uname -r 5.15.0-41-generic ~$ sudo lsb_release No LSB modules are available. ~$ sudo lsb_release -a No LSB modules are available.

Good evening, > > We have been dealing with an incident for several weeks during peak load > times, either due to authentications or service accesses that rely on Samba > 4 AD. Below are the details of the current Samba version and OS: > > **Samba version 4.19.2** > > ```bash > ~$ uname -r > 5.15.0-41-generic > ~$ sudo lsb_release > No LSB modules are

hi Gabriel, >> /usr/local/samba/private/sam.ldb: Error (24) Too many open files - I have not seen other reports of 4.19 or similar versions running out of open files, so I suspect it is a peculiarity of your machine. This message from 2018 has some hints for diagnosis and fixes: https://lists.samba.org/archive/samba/2018-April/215130.html And you could also look at the output of

Hi all, My samba 4.2 server sudden display the following error message after I issue the command <https://www.google.com.hk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja& uact=8&ved=0CCcQrAIoAjAA&url=https%3A%2F%2Flists.samba.org%2Farchive%2Fsamba %2F2013-November%2F176857.html&ei=BQFjVK3PMoPTmgWbxYHAAw&usg=AFQjCNGDXvPcdfZ

Thanks, Douglas. Due to these recurring incidents, we have migrated the entire SAMBA 4 farm (11 domain controllers) to version 4.20.5. We have realized that the current issue is caused by LDAP queries, primarily coming from port 3269 (Global Catalog). There is a proxy service that queries our domain controller to authenticate the user and authorize access via security groups, assigning the

Hi Aleksey, did you find any solution for this? I just updated from 4.8.2 to 4.8.3 and had very similar effects: Login was no longer possible with 4.8.3 - log file was full of "ldb: Failed to unlock db" messages. I had to downgrade to 4.8.2 in order to make samba work again. Bye, Marcel June 28, 2018 10:28 AM, "Aleksey Vladimirov via samba" <samba at

Hi list, for future reference: we haven't been able to fix it. Upgrading to 4.9.18 didn't help, so in the end we decided to downgrade to our previous version (4.5.12) which doesn't have this problem. Hooray for tdbbackup! Thanks Louis for thinking with us. Best regards, Roel And for Google: smbd[16461]: ldb: Failure during ltdb_lock_read(): Locking error ? Busy smbd[16461]:

Good time! After upgrading samba 4.5.10 to 4.9.13, name resolution in AD hangs. # /etc/init.d/samba status ?* status: crashed But the domain itself works, but hangs when resolving user names. What can be done? [2019/10/13 12:24:52.896473, 10, pid=17379, effective(0, 0), real(0, 0), class=ldb] ../lib/ldb-samba/ldb_wrap.c:77(ldb_wrap_debug) ? ldb: Added timed event

Am 20.02.19 um 15:58 schrieb samba.x.eliezer613--- via samba: > Hi, not having much luck getting samba 4.8.3 to start on a CentOS 7.6 VM.... > > used samba-4.8.3.tar.gz > ./configure > make > make install > samba-tool domain provision --use-rfc2307 --interactive > > In /etc/samba there is one file, smb.conf with content of: > # Global parameters > [global] >