[Samba] smbd fails to start after upgrade to version 4.11.6
Roy Eastwood
spindles7 at gmail.com
Wed Jan 29 19:43:53 UTC 2020
On 29 January 2020 18:09 Rowland penny wrote:
>>On 29/01/2020 18:01, Roy Eastwood via samba wrote:
[..snip..]
>> Jan 29 17:38:17 pi4b smbd[585]: open_sockets_smbd: No sockets available to bind to.
>> Jan 29 17:38:17 pi4b smbd[585]: [2020/01/29 17:38:17.673510, 0] ../../source3/lib/util.c:824(smb_panic_s3)
>> Jan 29 17:38:17 pi4b smbd[585]: PANIC (pid 585): open_sockets_smbd() failed
>> Jan 29 17:38:17 pi4b smbd[585]: [2020/01/29 17:38:17.674090, 0] ../../lib/util/fault.c:265(log_stack_trace)
>> Jan 29 17:38:17 pi4b smbd[585]: BACKTRACE: 0 stack frames:
>> Jan 29 17:38:17 pi4b smbd[585]: [2020/01/29 17:38:17.674275, 0] ../../source3/lib/dumpcore.c:315(dump_core)
>> Jan 29 17:38:17 pi4b smbd[585]: dumping core in /var/log/samba/cores/smbd
>> Jan 29 17:38:17 pi4b smbd[585]:
>> Jan 29 17:38:17 pi4b systemd[1]: smbd.service: Main process exited, code=dumped, status=6/ABRT
>> Jan 29 17:38:17 pi4b systemd[1]: smbd.service: Failed with result 'core-dump'.
>>
>>
>Must be something on your Rpi, on my Rpi4:
>
>pi at raspberrypi:~ $ ps ax | grep -E 'nmbd|smbd|winbindd'
>27609 ? Ss 0:01 /usr/sbin/nmbd --foreground --no-process-group
>27612 ? Ss 0:00 /usr/sbin/smbd --foreground --no-process-group
>27614 ? S 0:00 /usr/sbin/smbd --foreground --no-process-group
>27615 ? S 0:00 /usr/sbin/smbd --foreground --no-process-group
>27683 ? Ss 0:00 /usr/sbin/winbindd --foreground --no-process-group
>27686 ? S 0:01 winbindd: domain child [SAMDOM]
>
>Upgraded this morning ;-)
>
>Rowland
Thanks for the prompt reply Rowland.
Fair enough, but what? (I upgraded a similar Rpi3 without issues, but this one is struggling.) Is it easiest to delete the computer account in the domain, remove and purge samba then re-install and rejoin? Or better to find out what is causing the problem?
Roy
More information about the samba
mailing list