search for: smbd_claim_version

...d running? What do > the smbd logs say? no, root at ctdb-<HOST>:~# ps auxwww | grep smbd root     13192  0.0  0.0  12780   940 pts/0    S+   13:05   0:00 grep smbd There is no smbd, nmbd is running. Ahh, but the log says: [2019/05/16 11:26:38.702593,  0] ../source3/smbd/server.c:1519(smbd_claim_version)   smbd_claim_version: smbd 4.9.4-SerNet-Debian-11.stretch already running, refusing to start version 4.9.8-SerNet-Debian-13.stretch I think I will reinstall the Sernet-Packages. Best Bene -- forumZFD Entschieden für Frieden|Committed to Peace Benedikt Kaleß Leiter Team IT|Head team IT For...

...at the smbd process failed after one minute (before that I was probably not patient enough to see smbd fail), reporting that samba 4.7.1 was running and it refused to start 4.7.4 (at this time I tried to directly upgrade to 4.7.4): [2018/02/04 20:18:16.968393, 0] ../source3/smbd/server.c:1532(smbd_claim_version) Feb 4 20:18:16 fileb smbd[5835]: smbd_claim_version: smbd 4.7.1 already running, refusing to start version 4.7.4 The next thing was to stop ctdb on both file servers to do an offline upgrade. This worked fine without any problems. So it seems that a rolling upgrade from 4.7.1 to 4.7.4 did no...

...er one minute > (before that I was probably not patient enough to see smbd fail), > reporting that samba 4.7.1 was running and it refused to start 4.7.4 (at > this time I tried to directly upgrade to 4.7.4): > > [2018/02/04 20:18:16.968393, 0] > ../source3/smbd/server.c:1532(smbd_claim_version) > Feb 4 20:18:16 fileb smbd[5835]: smbd_claim_version: smbd 4.7.1 > already running, refusing to start version 4.7.4 > > The next thing was to stop ctdb on both file servers to do an offline > upgrade. This worked fine without any problems. So it seems that a > rolling upgr...

Hi everybody, I just updated my ctdb node from Samba version 4.9.4-SerNet-Debian-11.stretch to Samba version 4.9.8-SerNet-Debian-13.stretch. After restarting the sernet-samba-ctdbd service the node doesn't come back and remains in state "UNHEALTHY". I can find that in the syslog: May 16 11:25:40 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445 May 16

Am Do 01.02.2018 um 12:04 schrieb Martin Schwenke: > Hi Nicolas, > > On Thu, 1 Feb 2018 10:57:59 +0100, Nicolas Zuber via samba > <samba at lists.samba.org> wrote: > >> I try to update two clustered samba file servers. Right now samba 4.7.0 >> with ctdb is running on both of them. To update samba I stopped ctdb on >> one of the servers, and compiled and