Hi Martin, Am 26.01.23 um 22:57 schrieb Martin Schwenke:> winbindd and smbd are only started during the CTDB startup event, so > you have to enable the event scripts before you start CTDB. >That's what I did and that's where the problem starts ;-) As soon as I enable one of the two events the cluster chrashes :-( Stefan> That hasn't changed... ? > > peace & happiness, > martin-- Stefan Kania Landweg 13 25693 St. Michaelisdonn Signieren jeder E-Mail hilft Spam zu reduzieren und sch?tzt Ihre Privatsph?re. Ein kostenfreies Zertifikat erhalten Sie unter https://www.dgn.de/dgncert/index.html Download der root-Zertifikate: https://www.dgn.de/dgncert/downloads.html -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20230127/1ab1bebd/OpenPGP_signature.sig>
Hi Stefan, [Oops, this time to the list...] On Fri, 27 Jan 2023 08:57:17 +0100, Stefan Kania <stefan at kania-online.de> wrote:> Am 26.01.23 um 22:57 schrieb Martin Schwenke: > > winbindd and smbd are only started during the CTDB startup event, so > > you have to enable the event scripts before you start CTDB. > > > That's what I did and that's where the problem starts ;-) As soon as I > enable one of the two events the cluster chrashes :-(... but the cluster should not be up when you enable the event scripts, so nothing can go wrong. ;-) Sorry if I'm missing something... peace & happiness, martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20230127/eed051af/attachment.sig>
Hi Stefan, On 1/27/23 08:57, Stefan Kania via samba wrote:> Am 26.01.23 um 22:57 schrieb Martin Schwenke: >> winbindd and smbd are only started during the CTDB startup event, so >> you have to enable the event scripts before you start CTDB. >> > That's what I did and that's where the problem starts ? As soon as I > enable one of the two events the cluster chrashes ?you described, that you startup the cluster and wait until the nodes are "OK". Then you enabled the winbind script, which detects that the winbind is not running, because it is running in the "monitor" mode. The node goes "UNHEALTHY". This is expected. The monitor script does not try to start the winbind service in this case (monitor mode). CTDB only tries to start the enabled services when the node is in the "startup" run state. Best regards, Bj?rn -- SerNet GmbH - Bahnhofsallee 1b - 37081 Goettingen phone: +49.551.370000.0 - web: https://sernet.com http://www.sernet.com - mailto:contact at sernet.com AG Goettingen HRB2816, CEO: J.Loxen, CFO: R. Jung data privacy policy https://www.sernet.de/privacy