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 \ --with-logfilebase=/var/log/samba Here is the command run with -d3: #> ./samba -i -d3 lpcfg_load: refreshing parameters from /etc/samba/smb.conf samba version 4.11.2 started. Copyright Andrew Tridgell and the Samba Team 1992-2019 GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'spnego' registered GENSEC backend 'schannel' registered GENSEC backend 'naclrpc_as_system' registered GENSEC backend 'sasl-EXTERNAL' registered GENSEC backend 'ntlmssp' registered GENSEC backend 'ntlmssp_resume_ccache' registered GENSEC backend 'http_basic' registered GENSEC backend 'http_ntlm' registered GENSEC backend 'http_negotiate' registered GENSEC backend 'krb5' registered GENSEC backend 'fake_gssapi_krb5' registered register_process_model: PROCESS_MODEL 'single' registered register_process_model: PROCESS_MODEL 'standard' registered register_process_model: PROCESS_MODEL 'prefork' registered AUTH backend 'sam' registered AUTH backend 'sam_ignoredomain' registered AUTH backend 'anonymous' registered AUTH backend 'winbind' registered AUTH backend 'name_to_ntstatus' registered AUTH backend 'unix' registered ldb_wrap open of privilege.ldb Unable to create directory /var/lock for file msg.lock. Error was File exists exit_daemon: daemon failed to start: Samba failed to setup parent messaging, error code -1073741801 Could be the /var/lock thing but the directory exists and with root privileges it should be able to create msg.lock. Not sure why that is happening. Thanks, Rich ----- On Oct 30, 2019, at 2:33 PM, samba samba at lists.samba.org wrote:> On 30/10/2019 18:04, Rich Webb via samba wrote: >> Hello, >> >> I am getting this when trying to run testparm and I'm also unable to start the >> samba daemon. I am trying to set up a AD DC. This is a fresh install of CentOS >> 7 minimal with the dependency script from the wiki run. The version is 4.11.2 >> and was successfully compiled. I believe the two issues are related but I'm >> unable to find anything on google that indicates what could be the problem. >> >> When running the samba daemon with -i this is the output I get: >> >> exit_daemon: daemon failed to start: Samba failed to setup parent messaging, >> error code -1073741801 > > The post subject could point to your error, it happens when you try to > do something on Samba as a normal user when it it should be done as root > or by using sudo. > > Try running the command with 'sudo' at the beginning and '-d3' at the end. > > As you have compiled Samba yourself, what was your configure line ? > > Rowland > > >> >> CentOS 7 Minimal >> All dependencies installed via script from the wiki >> Compiled from source >> > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
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 messaging context Anonymous login successful But if I use sudo, I get this: rowland at devstation:~$ sudo smbclient -L localhost -N [sudo] password for rowland: Anonymous login successful> > Configure line: > ./configure \ > --disable-cups \ > --without-ldb-lmdb \ > --prefix=/opt/samba \ > --sysconfdir=/etc/samba \ > --localstatedir=/var \ > --with-systemd \ > --systemd-install-services \ > --with-logfilebase=/var/log/samba > > Here is the command run with -d3: > #> ./samba -i -d3 > lpcfg_load: refreshing parameters from /etc/samba/smb.conf > samba version 4.11.2 started. > Copyright Andrew Tridgell and the Samba Team 1992-2019 > GENSEC backend 'gssapi_spnego' registered > GENSEC backend 'gssapi_krb5' registered > GENSEC backend 'gssapi_krb5_sasl' registered > GENSEC backend 'spnego' registered > GENSEC backend 'schannel' registered > GENSEC backend 'naclrpc_as_system' registered > GENSEC backend 'sasl-EXTERNAL' registered > GENSEC backend 'ntlmssp' registered > GENSEC backend 'ntlmssp_resume_ccache' registered > GENSEC backend 'http_basic' registered > GENSEC backend 'http_ntlm' registered > GENSEC backend 'http_negotiate' registered > GENSEC backend 'krb5' registered > GENSEC backend 'fake_gssapi_krb5' registered > register_process_model: PROCESS_MODEL 'single' registered > register_process_model: PROCESS_MODEL 'standard' registered > register_process_model: PROCESS_MODEL 'prefork' registered > AUTH backend 'sam' registered > AUTH backend 'sam_ignoredomain' registered > AUTH backend 'anonymous' registered > AUTH backend 'winbind' registered > AUTH backend 'name_to_ntstatus' registered > AUTH backend 'unix' registered > ldb_wrap open of privilege.ldb > Unable to create directory /var/lock for file msg.lock. Error was File exists > exit_daemon: daemon failed to start: Samba failed to setup parent messaging, error code -1073741801 > > Could be the /var/lock thing but the directory exists and with root privileges it should be able to create msg.lock. Not sure why that is happening.Is there a file called 'msg.lock' in /var/lock ? Rowland
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 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 messaging context > Anonymous login successful > > But if I use sudo, I get this: > > rowland at devstation:~$ sudo smbclient -L localhost -N > [sudo] password for rowland: > Anonymous login successful > >> >> Configure line: >> ./configure \ >> --disable-cups \ >> --without-ldb-lmdb \ >> --prefix=/opt/samba \ >> --sysconfdir=/etc/samba \ >> --localstatedir=/var \ >> --with-systemd \ >> --systemd-install-services \ >> --with-logfilebase=/var/log/samba >> >> Here is the command run with -d3: >> #> ./samba -i -d3 >> lpcfg_load: refreshing parameters from /etc/samba/smb.conf >> samba version 4.11.2 started. >> Copyright Andrew Tridgell and the Samba Team 1992-2019 >> GENSEC backend 'gssapi_spnego' registered >> GENSEC backend 'gssapi_krb5' registered >> GENSEC backend 'gssapi_krb5_sasl' registered >> GENSEC backend 'spnego' registered >> GENSEC backend 'schannel' registered >> GENSEC backend 'naclrpc_as_system' registered >> GENSEC backend 'sasl-EXTERNAL' registered >> GENSEC backend 'ntlmssp' registered >> GENSEC backend 'ntlmssp_resume_ccache' registered >> GENSEC backend 'http_basic' registered >> GENSEC backend 'http_ntlm' registered >> GENSEC backend 'http_negotiate' registered >> GENSEC backend 'krb5' registered >> GENSEC backend 'fake_gssapi_krb5' registered >> register_process_model: PROCESS_MODEL 'single' registered >> register_process_model: PROCESS_MODEL 'standard' registered >> register_process_model: PROCESS_MODEL 'prefork' registered >> AUTH backend 'sam' registered >> AUTH backend 'sam_ignoredomain' registered >> AUTH backend 'anonymous' registered >> AUTH backend 'winbind' registered >> AUTH backend 'name_to_ntstatus' registered >> AUTH backend 'unix' registered >> ldb_wrap open of privilege.ldb >> Unable to create directory /var/lock for file msg.lock. Error was File exists >> exit_daemon: daemon failed to start: Samba failed to setup parent messaging, >> error code -1073741801 >> >> Could be the /var/lock thing but the directory exists and with root privileges >> it should be able to create msg.lock. Not sure why that is happening. > > Is there a file called 'msg.lock' in /var/lock ? > > Rowland > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
Reasonably Related Threads
- Unable to initialize messaging context!
- Unable to initialize messaging context!
- Unable to initialize messaging context!
- After upgrade to 4.9.4, internal DNS no longer working
- Samba 4 AD - Samba Fails to Start, hdb_samba4_create_kdc (setup KDC database) failed