similar to: Winbind crash on Samba 4.7.2

Hai, This looks like tevent tdb or ldb has an incorrect version. Can you post more about the os and installed packages. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Jacek Fefli?ski via samba > Verzonden: maandag 18 december 2017 13:49 > Aan: samba at lists.samba.org > Onderwerp: [Samba] Winbind crash

Hi all, on a recently installed samba file server, the winbind service crashes apparently randomly. Every few hours it's necessary to restart the winbind service and then it works for a few more hours. Any ideas are welcome. 1) the environment: 2 debian stretch DC's with round-robind bind+dhcp with dns-update. 1 fileserver also (AD backend) on debian stretch. All on self compiled samba

Hi there, I'm doing some tests upgrading from 4.8.6 to 4.9.0 (and also 4.9.1) and I'm having some issues with bind 9.10 in a debian 9 vm. When Bind is running, if a machine updates, it crashes with the following error: /kernel: [ 7948.941528] named[22947]: segfault at 0 ip 00007ffa89f87a50 sp 00007ffa8c6588a0 error 6 in libdnsserver-common-samba4.so[7ffa89f82000+9000]/ Also, when

Hi Rowland, thank you for another quick reply. 1) I did all the changes on the smb.conf you suggested and restart samba-ad-dc on both DCs. 2) Changed file server log to 10 and rebooted it just because. 3) Winbind crashed. 3.1) I have a gut felling that if I leave it alone, it lasts longer. If I do a wbinfo -u it's ok, but if I go and check it often, it eventually crashes. Again, gut felling,

I had this error when I did it from Windows 10. I usede a Windows 7 PC and everything was fine again. Daniel Müller -----Ursprüngliche Nachricht----- Von: Andreas Oster via samba [mailto:samba at lists.samba.org] Gesendet: Freitag, 9. November 2018 11:16 An: samba at lists.samba.org Betreff: [Samba] Samba panic when accessing DNS domain entry with RSAT DNS tool Hi everybody, for some

Hi everybody, for some time now I have an issue with our samba/bind9-DLZ setup which became worse lately. I use the RSAT DNS tool to configure DNS records. In the past it sometimes happened, that DNS died when accessing the domain zone. This condition could only be resolved by restarting samba on the affected DC. Unfortunately the situation got worse and configuration/modification of entries

Hi all, I am currently having some problems managing DNS on our Samba servers with bind9 backend. Whenever I try to access the AD domain zone from the MS DNS tool the DNS part crashes and services need to be restarted. After the crash DNS is not working anymore. I get the following in log.samba: [2019/09/20 09:39:10.681745,? 0]

Hey all, up until 2 weeks ago my samba DC was running just fine, then it began crashing randomly. I was using 4.8.0 before, now upgraded to a self-compiled 4.8.3 with default build parameters on an up-to-date centos 7.5 with disabled SELinux and bind9 as DNS backend with samba_dlz. The log output at log level = 10 is as follows: Jul 17 14:49:20 hostname samba[4998]: [2018/07/17 14:49:20.587655,

Hello Daniel, thank you for the fast reply. I am also using Windows 10. I'll setup a temporary Win7 VM to test if this will make any difference. Do you know if this a known issue with RSAT on Windows 10 ? Best regards Andreas Am 09.11.2018 um 11:23 schrieb Mueller: > I had this error when I did it from Windows 10. > I usede a Windows 7 PC and everything was fine again. > >

Hi, I used Samba 4.0.5 in Wheezy. Here is that I have done: --------------------------------------------------------------- samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI \ --server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123' echo "nameserver 192.168.0.21" > /etc/resolv.conf samba ln -s /usr/local/samba/lib/libnss_winbind.so

Hi, this is the first time I've tryed to build a 64 Bit Version with acl's enabled - so I expect I could duplicate this with older versions too... Here's the build info: System: AIX 6100-07-01-1141 Compiler: IBM xlc CC=xlc_r -g CXX=xlC_r CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51 -D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O

In samba 4 log I get the following message: [2013/04/29 00:44:30,? 0] ../source4/smbd/server.c:369(binary_smbd_main) ? samba version 4.1.0pre1-GIT-5727bfa started. ? Copyright Andrew Tridgell and the Samba Team 1992-2013 [2013/04/29 00:44:31,? 0] ../source4/smbd/server.c:475(binary_smbd_main) ? samba: using 'standard' process model [2013/04/29 00:44:32,? 1]

I would suggest, downgrade to a "release" samba version. Check if it happens again.. 4.10.9-GIT-e3f51924971 < 4.10.9 is not released yet. If is also craches with 4.10.8, then submit a bug in bugzilla. (note: > ? Please read the Trouble-Shooting section of the Samba HOWTO ) ;-) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at

I do not know. But after I did it one time from a windos 10 machine with RSAT my whole dns was broken. The only thing could cure that was to open RSAT on my windows 7 admin PC and delete the entries I added on Windows 10 and save the changes. Daniel Müller -----Ursprüngliche Nachricht----- Von: Andreas Oster [mailto:aoster at novanetwork.de] Gesendet: Freitag, 9. November 2018 11:52 An:

I've got a CTDB 2.5.2 Samba 4.1.5 cluster where I'm seeing smbd processes using too much CPU after the client connection is closed. Doing a truss against the smbd processes shows nothing during this time, so no syscalls seem to be involved. I rebuilt with debug enabled and took stack traces from an offending process spaces about 1 minute apart. Can anyone from the team tell me if

Server: Debian Wheezy 7.3, ECC RAM, updated via cron-apt Version: 4.1.4 Clients: Windows 8.1 Pro Environment: Active Directory, installed from scratch (no migration), roaming profiles, group policies for printers, network mappings, ... Hello everyone, I've upgraded my Samba installation from 4.0.14 (which was working more or less fine) to 4.1.4 yesterday - via Sernet packages, i. e. just

? Hi, sometimes this error appears in our log files. Ist this a bug? Jun 11 12:38:00 barbarella smbd[7036]: [2015/06/11 12:38:00.286985, 0] ./source3/smbd/smb2_server.c:668(smb2_validate_message_id) Jun 11 12:38:00 barbarella smbd[7036]: smb2_validate_message_id: client used more credits than granted, mid 4, charge 1, credits_granted 0, seqnum low/range: 4/0 Jun 11 12:38:01 barbarella

Hi, sometimes this error appears in our log files. Ist this a bug? Jun 11 12:38:00 barbarella smbd[7036]: [2015/06/11 12:38:00.286985, 0] ./source3/smbd/smb2_server.c:668(smb2_validate_message_id) Jun 11 12:38:00 barbarella smbd[7036]: smb2_validate_message_id: client used more credits than granted, mid 4, charge 1, credits_granted 0, seqnum low/range: 4/0 Jun 11 12:38:01 barbarella

Hmm… I see that there is a patch in the bugzilla page for that bug. I guess I could try that one… :-) I notice in the patch that there is a lot of talk about SMB2 - we use SMB3 mostly now. But perhaps there is some code sharing? Or perhaps SMB2 is used when talking to the AD servers? Or the few SMB2-talking clients causes the problem for all of the other users? When testing the “timeout” issue I