similar to: Unable to initialize messaging context!

Contrary to best practices, on my boxes I'm always root so it is doing this when run as root. I'm getting the error for the daemon also when run as a system service in systemd. Configure line: ./configure \ --disable-cups \ --without-ldb-lmdb \ --prefix=/opt/samba \ --sysconfdir=/etc/samba \ --localstatedir=/var \ --with-systemd \ --systemd-install-services \

No, it's as if it can't create the file for some reason... permissions are 755 on that directory - owned by root. Thanks, Rich ----- On Oct 30, 2019, at 3:08 PM, samba samba at lists.samba.org wrote: > On 30/10/2019 18:40, Rich Webb via samba wrote: >> Contrary to best practices, on my boxes I'm always root so it is doing this when >> run as root. I'm getting

On 30/10/2019 18:40, Rich Webb via samba wrote: > Contrary to best practices, on my boxes I'm always root so it is doing this when run as root. I'm getting the error for the daemon also when run as a system service in systemd. Hmm, if I run smbclient as a normal user (output cut for brevity), I get this: rowland at devstation:~$ smbclient -L localhost -N Unable to initialize

Then I don't know what caused it. I had no problems prior to the upgrade, and the upgrade was done without errors.. Unfortunately, no, I don't have backups. 'sam.ldb' is still there, though, and so are the databases unter 'sam.ldb.d'. Yes, I tried restarting Samba, even rebooted the server but to no avail. Here are the results from running samba in the shell: lpcfg_load:

Oh, that doesn't sound good... Arch Linux. I did a regular system upgrade using pacman -Syu which automatically upgrades all packages to their latest version. I have another, practically identical system and I didn't have this issue there. Though I might have had a smaller jump between versions. On Sat, 22 Dec 2018 at 22:21, Rowland Penny via samba <samba at lists.samba.org>

Hello to the Samba Mailing List, This is my first post, so please, should I commit any faux pas, nudge me in the right direction and I will adjust accordingly. I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've deployed for a client. Samba failed a few days ago and I've been unable to resolve the issue on my own. Google searches are leading me in circles,

I've been trying to run samba4 alpha11 on a FreeBSD 8.1 system as a domain controller but I'm having trouble starting the cldapd server. For some reason it won't bind to the specified address or interface whatever I specify in smb.conf. I managed running the provision script without any trouble but I have no clue how to solve this problem in order to start the samba server. bitrot#

Hi, It's my first try to setup RODC using Samba 4.8. We have latest Samba 4.7 environnement with 2 DC and some file servers. Joining the DC to the domain is OK using samba-tool domain join command. The domain controller appears in the DC list (MMC) However, users cannot be authenticated. Samba is running but these ports are closed : netbios-ssn 139/tcp # NETBIOS session service

OK I recompiled with --with-lockdir=/var/lib/samba/lock and it's now getting further... now I'm getting this when I try to start the samba daemon: Calling SPN name update script /opt/samba/sbin/winbindd: winbindd version 4.11.2 started. /opt/samba/sbin/winbindd: Copyright Andrew Tridgell and the Samba Team 1992-2019 /opt/samba/sbin/winbindd: Failed to create directory /var/run for pid

Dear list, with linux compiling samba 4 works pretty fine but with opensolaris 'snv_111b' 64bit I have problems with the prototype declaration of getpwent_r(): (Using /opt/SunStudioExpress/bin/cc) Compiling torture/../../lib/nss_wrapper/testsuite.c "torture/../../lib/nss_wrapper/testsuite.c", line 336: prototype mismatch: 4 args passed, 3 expected

Hello, I test samba 4.9.5 in my debian buster . Almost everything works. My last problem concerns the printers. I? could need some help explaining my logs .I have this : /usr/sbin/smbd: reloading printcap cache /usr/sbin/smbd: reload status: ok /usr/sbin/smbd: pid_to_procid: messaging_dgm_get_unique failed: Aucun fichier ou dossier de ce type /usr/sbin/smbd: send_all_fn: messaging_send_buf

Hi everyone After almost 2 days up-time with Samba 4, it failed again. This time it simply will not restart. The krb5.conf had got corrupted. I replaced it with this one from /usr/local/samba/private /etc/krb5.conf [libdefaults] default_realm = HH3.SITE dns_lookup_realm = false dns_lookup_kdc = true It starts up OK: samba -i -d 3 lpcfg_load: refreshing parameters from

Hello, Sorry for my english and for this very long email. I want to create samba-ad server with the package debian buster. I have follow the url : https://github.com/thctlo/samba4/blob/master/howtos/stretch-base-2.0-samba-minimal-ad.txt I have generated mon samba ad with the following command : samba-tool domain provision --use-rfc2307 --interactive Realm [LENZSPITZE2.CALAIS.FR]: Domain

On Thu, 10 Aug 2017 08:14:33 +0700 Vladimir Frelikh via samba <samba at lists.samba.org> wrote: > > >> > > >> <https://mail.google.com/mail/u/0/?ui=2&ik=7f6f030913&view= > > att&th=15dc2ba7d7a63129&attid=0.1&disp=safe&realattid=f_j63tfts50&zw> > > >> > > >> > > >> -- > > >> Best

I've googled and I believe that SASL method DIGEST-MD5 is supported and I see it in the samba startup, but it doesn't work. ldapsearch -Y DIGEST-MD5 -h dc03.mediture.dom SASL/DIGEST-MD5 authentication started ldap_sasl_interactive_bind_s: Operations error (1) additional info: SASL:[DIGEST-MD5]: Failed to start authentication backend: NT_STATUS_INVALID_PARAMETER [root at dc03 ~]# samba

Hi, Thank your for your answers. @Rowland: Yes, Winbind is installed but it seems it is not started (or cannot start) @Andrew: Please find extract in log level 4 during a service restart and a connection test with smbclient from another machine. I hope this could help, this is not clear to me : ==> /var/log/samba/log.samba <== [2018/05/29 10:54:00.173894, 0]

Hi Rowland, I just realized that I actually do have backups of everything in /var/lib/samba (which is the main folder for Samba on Arch). I'd still be interested how to recover from this situation without a backup but priority is to get the AD back up and running again. How would you suggest I proceed? On Sat, 22 Dec 2018 at 23:01, Viktor Trojanovic <viktor at troja.ch> wrote: >

Hi, I setup a test envirement on a dedicatet server. OS: debian stretch samba: 4.5.8 smbclient: 4.5.8 I set it up as DC, the provision work well, yes I've delete the smb.conf in advance. When I test kinit I got an kerberos ticket, but I've problems with smbclient either I use kerberos or password auth. Myabee someone could help me? my smb.conf: # Global parameters [global]

Hi Marc, Thanks for getting back to me. Marc Muehlfeld wrote on 24-2-2015 21:12: > Hello Bram, > > Am 24.02.2015 um 12:37 schrieb Bram Matthys: >> Is there a way to re-initialize/re-provision DNS? > > No. > That would be a pitty. >> well.. I suppose since I started with 4.0.6 (migrated from Samba 3.x) but >> from a users' point of view everything

Hi I got some strange issues on my samba4.0.1 install yesterday. It happened a while after updating my xubuntu server 13.04 not 13.10. Everything seems to be working fine except shares. Kerberos authentication seem to function properly, also DNS works fine but shares seem semi-broken. I can't mount any shares on my Windows box, including netlogon, profiles. I have one share that is