search for: samba_termin

...12:48:39.615787, 0] ../../source4/samba/process_prefork.c:630(prefork_child_pipe_handler) Dec 05 12:48:39 cobra samba[694]: prefork_child_pipe_handler: Parent 694, Child 719 exited with status 0 Dec 05 12:48:39 cobra samba[694]: [2023/12/05 12:48:39.622956, 0] ../../source4/samba/server.c:403(samba_terminate) Dec 05 12:48:39 cobra samba[694]: samba_terminate: samba_terminate of samba 694: winbindd child process exited Dec 05 12:48:39 cobra systemd[1]: samba-ad-dc.service: Main process exited, code=exited, status=1/FAILURE Dec 05 12:48:40 cobra systemd[1]: samba-ad-dc.service: Failed with result...

...source, run the classicupgrade, and see >> if it works. >> >> Many Thanx >> Best Regards >> ashley >> >> > Ah, 'classicupgrade' ???? > > Rowland Yes, classicupgrade. I have installed 4.8.9 from source. I get same error when starting up:    samba_terminate: samba_terminate of samba 24484: kdc failed to setup interfaces      -> samba_terminate: samba_terminate of samba 24484: kdc failed to setup interfaces Except now it doesn't run at all. # smbclient -L localhost -U% Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED)...

...sdb_get_schema failed [2016/03/02 11:27:17.050402, 0] ../source4/smbd/service_task.c:35(task_server_terminate) task_server_terminate: [kdc: krb5_init_context samdb connect failed] task_server_terminate: [cldapd failed to open samdb] [2016/03/02 11:27:17.072670, 0] ../source4/smbd/server.c:211(samba_terminate) samba_terminate: dreplsrv: Failed to connect to local samdb: WERR_DS_UNAVAILABLE [2016/03/02 11:27:17.073896, 0] ../source4/smbd/server.c:211(samba_terminate) samba_terminate: nbtd failed to open samdb [2016/03/02 11:27:17.075031, 0] ../source4/smbd/server.c:211(samba_terminate) samba_...

...3:12.807896, 0] ../../lib/util/become_daemon.c:136(daemon_ready) May 5 15:13:12 samba-02 samba[37571]: daemon_ready: daemon 'samba' finished starting up and ready to serve connections May 5 15:13:12 samba-02 samba[37571]: [2020/05/05 15:13:12.820106, 0] ../../source4/smbd/server.c:371(samba_terminate) May 5 15:13:12 samba-02 samba[37571]: samba_terminate: samba_terminate of samba 37571: nbtd failed to setup interfaces Before starting samba_server there are no listening processes. SO, whatever is attached to 137 was caused by samba_server itself. Am I missing something obvious here?...

..._terminate: [nbtd failed to setup interfaces] > [2019/02/17 18:15:35.396234, 0] ../lib/util/become_daemon.c:138(daemon_ready) > daemon_ready: STATUS=daemon 'samba' finished starting up and ready to serve connections > [2019/02/17 18:15:35.397963, 0] ../source4/smbd/server.c:288(samba_terminate) > samba_terminate: samba_terminate of samba 98006: nbtd failed to setup interfaces 10.1.2.34 is the jail's own IP and I'm sure nothing is running on port 137 there. Relevant part of my smb4.conf > [global] > allow dns updates=nonsecure > log level=1 &gt...

....615787, 0] ../../source4/samba/process_prefork.c:630(prefork_child_pipe_handler) > Dec 05 12:48:39 cobra samba[694]: prefork_child_pipe_handler: Parent 694, Child 719 exited with status 0 > Dec 05 12:48:39 cobra samba[694]: [2023/12/05 12:48:39.622956, 0] ../../source4/samba/server.c:403(samba_terminate) > Dec 05 12:48:39 cobra samba[694]: samba_terminate: samba_terminate of samba 694: winbindd child process exited > Dec 05 12:48:39 cobra systemd[1]: samba-ad-dc.service: Main process exited, code=exited, status=1/FAILURE > Dec 05 12:48:40 cobra systemd[1]: samba-ad-dc.service: Failed...

...16/03/02 11:27:17.050402, 0] > ../source4/smbd/service_task.c:35(task_server_terminate) > task_server_terminate: [kdc: krb5_init_context samdb connect failed] > task_server_terminate: [cldapd failed to open samdb] > [2016/03/02 11:27:17.072670, 0] > ../source4/smbd/server.c:211(samba_terminate) > samba_terminate: dreplsrv: Failed to connect to local samdb: > WERR_DS_UNAVAILABLE > > [2016/03/02 11:27:17.073896, 0] > ../source4/smbd/server.c:211(samba_terminate) > samba_terminate: nbtd failed to open samdb > [2016/03/02 11:27:17.075031, 0] > ../source4/smbd...

...5 19:16:06.375968, 0] ../../source4/smbd/service_task.c:36(task_server_terminate) Sep 15 19:16:06 samba samba[338]: task_server_terminate: task_server_terminate: [cldapd failed to setup interfaces] Sep 15 19:16:06 samba samba[213]: [2020/09/15 19:16:06.399691, 0] ../../source4/smbd/server.c:371(samba_terminate) Sep 15 19:16:06 samba samba[213]: samba_terminate: samba_terminate of samba 213: kdc failed to setup interfaces Sep 15 19:16:06 samba systemd[1]: samba-ad-dc.service: Main process exited, code=exited, status=1/FAILURE Sep 15 19:16:16 samba systemd[1]: samba-ad-dc.service: Failed with result &...

...02, 0] >> ../source4/smbd/service_task.c:35(task_server_terminate) >> task_server_terminate: [kdc: krb5_init_context samdb connect failed] >> task_server_terminate: [cldapd failed to open samdb] >> [2016/03/02 11:27:17.072670, 0] >> ../source4/smbd/server.c:211(samba_terminate) >> samba_terminate: dreplsrv: Failed to connect to local samdb: >> WERR_DS_UNAVAILABLE >> >> [2016/03/02 11:27:17.073896, 0] >> ../source4/smbd/server.c:211(samba_terminate) >> samba_terminate: nbtd failed to open samdb >> [2016/03/02 11:27:17.07...

...ions >> [2020/07/22 12:48:50.184811, 0] >> ../../source4/smbd/service_task.c:36(task_server_terminate) >> task_server_terminate: task_server_terminate: [nbtd failed to setup >> interfaces] >> [2020/07/22 12:48:50.300712, 0] >> ../../source4/smbd/server.c:371(samba_terminate) >> samba_terminate: samba_terminate of samba 86503: nbtd failed to setup >> interface >> >> >> Anyone know how to deal with this? >> > If you have lines in your smb.conf similar to these: > > ?????? bind interfaces only = yes > ?????? interfa...

...erve connections [2017/02/09 15:48:48.140769, 0] ../source4/smbd/service_task.c:35(task_server_terminate) task_server_terminate: [Failed to obtain server credentials, perhaps a standalone server?: NT_STATUS_CANT_ACCESS_DOMAIN_INFO ] [2017/02/09 15:48:48.148810, 0] ../source4/smbd/server.c:211(samba_terminate) samba_terminate: Failed to obtain server credentials, perhaps a standalone server?: NT_STATUS_CANT_ACCESS_DOMAIN_INFO [2017/02/09 15:48:49.385050, 0] ../source4/winbind/winbindd.c:47(winbindd_done) winbindd daemon died with exit status 1 [2017/02/09 15:48:49.386525, 0] ../source4/smbd/se...

...d the Samba Team 1992-2019 /opt/samba/sbin/winbindd: Failed to create directory /var/run for pid files - File exists samba_runcmd_io_handler: Child /opt/samba/sbin/winbindd exited 1 winbindd daemon died with exit status 1 task_server_terminate: task_server_terminate: [winbindd child process exited] samba_terminate: samba_terminate of samba 11462: winbindd child process exited I'm not sure why it's trying to create the /var/run directory... should I use a different configure option to attempt to remedy that? Thanks, Rich ----- On Oct 30, 2019, at 3:19 PM, samba samba at lists.samba.org wrote:...

On Sun, 20 Nov 2016 15:55:08 -0500 Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > > And it looks like nobody is listening on port 135 - > > [root at larkin26 ~]# netstat --listen --inet --program --numeric > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign > Address State PID/Program name

FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: running backup on dirs: /var/db/samba4/private /var/db/samba4 /usr/local/etc Starting transaction on /var/db/samba4/private/secrets At which point samba-tool enters a permanent wait state. 86064 root 1 52 0 131M 78M wait 3 0:01 0.00%

...Failed to bind to 10.1.2.34:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED > [2016/12/29 09:58:47.085993, 0] ../source4/smbd/service_task.c:35(task_server_terminate) > task_server_terminate: [nbtd failed to setup interfaces] > [2016/12/29 09:58:47.086946, 0] ../source4/smbd/server.c:210(samba_terminate) > samba_terminate: Failed to startup dcerpc server task > [2016/12/29 09:58:47.088478, 0] ../source4/smbd/server.c:210(samba_terminate) > samba_terminate: nbtd failed to setup interfaces > [2016/12/29 09:58:47.092845, 2] ../source4/lib/socket/interface.c:277(interpret_interfac...

.../sbin/winbindd: Failed to exec child - No such file or directory [2016/07/04 11:29:48.462580, 0] ../source4/winbind/winbindd.c:49(winbindd_done) winbindd daemon exited normally task_server_terminate: [winbindd child process exited] [2016/07/04 11:29:48.464159, 0] ../source4/smbd/server.c:211(samba_terminate) samba_terminate: winbindd child process exited Although the message about the daemon being ready seems to indicate that samba is running, as I said, ps aux shows that it isn't. Any ideas how I can get Samba back up? Uninstalling and reinstalling it didn't work.

...2019 00:50:13 +0200 > Ashley via samba <samba at lists.samba.org> wrote: > >>> Ah, 'classicupgrade' ???? >>> >>> Rowland >> Yes, classicupgrade. >> >> I have installed 4.8.9 from source. >> I get same error when starting up:    samba_terminate: >> samba_terminate of samba 24484: kdc failed to setup interfaces >>      -> samba_terminate: samba_terminate of samba 24484: kdc failed >> to setup interfaces >> >> Except now it doesn't run at all. >> # smbclient -L localhost -U% >> Connectio...

...../source4/smbd/service_task.c:35(task_server_terminate) >>> task_server_terminate: [kdc: krb5_init_context samdb connect failed] >>> task_server_terminate: [cldapd failed to open samdb] >>> [2016/03/02 11:27:17.072670, 0] >>> ../source4/smbd/server.c:211(samba_terminate) >>> samba_terminate: dreplsrv: Failed to connect to local samdb: >>> WERR_DS_UNAVAILABLE >>> >>> [2016/03/02 11:27:17.073896, 0] >>> ../source4/smbd/server.c:211(samba_terminate) >>> samba_terminate: nbtd failed to open samdb >>...

...context: failed to find endpoint server = 'winreg' > [2016/11/20 16:50:40.983724,  0] > ../source4/smbd/service_task.c:35(task_server_terminate) >   task_server_terminate: [Failed to startup dcerpc server task] > [2016/11/20 16:50:40.994293,  0] > ../source4/smbd/server.c:211(samba_terminate) >   samba_terminate of 2479: Failed to startup dcerpc server task > [2016/11/20 16:50:41.033979,  0] > ../source4/smbd/service.c:98(server_service_startup) >   Failed to start service 'smb' - NT_STATUS_INVALID_SYSTEM_SERVICE > [2016/11/20 16:50:41.038319,  0] > ../lib/...

...up > > interfaces] [2019/02/17 18:15:35.396234, > > 0] ../lib/util/become_daemon.c:138(daemon_ready) daemon_ready: > > STATUS=daemon 'samba' finished starting up and ready to serve > > connections [2019/02/17 18:15:35.397963, > > 0] ../source4/smbd/server.c:288(samba_terminate) samba_terminate: > > samba_terminate of samba 98006: nbtd failed to setup interfaces > > 10.1.2.34 is the jail's own IP and I'm sure nothing is running on > port 137 there. > > Relevant part of my smb4.conf > > > [global] > > allow dns upda...