nmbd fails to start with locking error on ctdb/samba upgrade

Amitay Isaacs amitay at gmail.com
Fri Feb 17 00:13:52 UTC 2017


On Wed, Feb 15, 2017 at 7:43 AM, Steve French <smfrench at gmail.com> wrote:

> The machine looks like it just got recycled (checking on that with our
> testers) but the log.nmbd included the following:
>
> [2017/02/09 18:37:31.546793,  0] ../lib/util/become_daemon.c:
> 124(daemon_ready)
>   STATUS=daemon 'nmbd' finished starting up and ready to serve connections
> [2017/02/09 18:37:54.574835,  0]
> ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
>   *****
>
>   Samba name server P08 is now a local master browser for workgroup
> MYGROUP on subnet 192.168.1.13
>
>   *****
> [2017/02/09 18:37:54.574926,  0]
> ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
>   *****
>
>   Samba name server P08 is now a local master browser for workgroup
> MYGROUP on subnet 10.20.26.13
>
>   *****
> [2017/02/09 19:49:51.020635,  0] ../source3/nmbd/nmbd.c:58(terminate)
>   Got SIGTERM: going down...
>
>
>From these logs it appears that nmbd was up and running.  nmbd got SIGTERM
more than an hour later.

Are you sure these are the correct logs?

Amitay.


More information about the samba-technical mailing list