similar to: upgrade ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19

05.12.2023 17:21, Joachim Lindenberg via samba: > I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. > > systemctl status samba-ad-dc shows: > > Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) > Dec 05 12:48:39 cobra samba[749]:

It?s always recommend to demote the DC, upgrade samba, and join the DC again. Did you do it this way ? You may have a broken DC, or a broken installation. Instead of troubleshooting, which you can of course do, I?d demote (or force-demote), reinstall and re join. http://samba.bigbird.es/doku.php?id=samba:upgrade-sama LP On 5 Dec 2023 at 15:45 +0100, Joachim Lindenberg via samba <samba at

On Tue, 5 Dec 2023 15:21:50 +0100 Joachim Lindenberg via samba <samba at lists.samba.org> wrote: > I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> > 4.19, but the Dc is not yet working again. How did you upgrade ? If I remember correctly, both 20.04 and 22.04 come with 4.15.13 (latest Samba version available), so could it be that the upgrade from 20.04 to

05.12.2023 17:51, Luis Peromarta via samba : > It?s always recommend to demote the DC, upgrade samba, and join the DC again. Did you do it this way ? This is rarely needed and in almost all cases is unnecessary and just an extra work. The only good reason to do that is when you upgrade a very old version of samba, skipping 5..10 or more releases in between, and even there it almost always

Hello to the samba users list again. I've got an emergency here, a Samba AD DC I've got deployed has crashed again, this is the third time since 12/17/2015 that this domain has failed completely. No power outages or unexpected shutdowns, samba simply fails to start, it appears my database is yet again corrupt: [2016/03/02 11:27:17.025235, 0]

In addition to Rowland comment. if you still able to test it. Remove 1 setting at a time, restart and test it. Start with these, in this order. logging = syslog only prefork children = 8 I think if the logging line is removed your problem is solved. man smb.conf /logging should explain more. Because I cant/find the setting : logging = syslog only Greetz, Louis

On 02/03/16 20:46, IT Admin wrote: > Any further information required? Any troubleshooting steps? I need to > get this domain functional ASAP. > > Please advise. > > JS > On Mar 2, 2016 11:39 AM, "IT Admin" <it at cliffbells.com> wrote: > >> Hello to the samba users list again. I've got an emergency here, a Samba >> AD DC I've got

>How did you upgrade ? >If I remember correctly, both 20.04 and 22.04 come with 4.15.13 (latest Samba version available), so could it be that the upgrade from 20.04 to >22.04 managed to install unrequired packages ? I did a do-release-upgrade first to go from 20.04 to 22.04, and then updated my /etc/apt/sources.list.d/mjt.list to go from focal/samba-4.18 to jammy/samba-4.19. I also

OS = Ubuntu 18.04 LXD container Samba version = 4.11.12 Repo = Louis' (many thanks) I recently upgraded from 4.10.14->4.10.17->4.11.12 Now the samba-ad-dc service fails with the following upon reboot: --- root at samba:~# systemctl status samba-ad-dc ? samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled)

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%

I touched the two missing files /var/db/samba4/private/dns_update_list /var/db/samba4/private/spn_update_list And restarted the Samba44 service. This is what I see now: [2017/02/09 15:48:47.507874, 0] ../source4/smbd/server.c:372(binary_smbd_main) samba version 4.4.8 started. Copyright Andrew Tridgell and the Samba Team 1992-2016 [2017/02/09 15:48:47.922389, 0]

I am working on a FreeBSD jail (12.1p4) using samba410. I have joined this service to our existing Samab DC DOMAIN using samba-tool domain join. This worked as far as I can tell. I have these entries in smb4.conf # BOF # Global parameters [global] netbios name = SAMBA-02 realm = BROCKLEY-2016.HARTE-LYNE.CA server role = active directory domain controller workgroup = BROCKLEY-2016

Hello. On several FreeBSD 11.2/amd64 servers, I've got a jail dedicated to running Samba as an AD DC. Some days ago I upgraded one of them from 4.8.7 to 4.8.9 and suddenly everything stopped working. Since it was a production box, I immediately restored the whole jail from a backup, with no chance to better investigate. Today, with more time, I tried on another server and again I run

On Sun, 2016-11-20 at 16:50 -0500, Adam Tauno Williams via samba wrote: > On Sun, 2016-11-20 at 21:11 +0000, Rowland Penny via samba 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

OK I recompiled with --with-lockdir=/var/lib/samba/lock and it's now getting further... now I'm getting this when I try to start the samba daemon: Calling SPN name update script /opt/samba/sbin/winbindd: winbindd version 4.11.2 started. /opt/samba/sbin/winbindd: Copyright Andrew Tridgell and the Samba Team 1992-2019 /opt/samba/sbin/winbindd: Failed to create directory /var/run for pid

Hello Cristian, Well, nothing to say about your steps, these looks good. And lmdb could be disable in the sernet packages, cant say, i dont know. And only one DC has these problems or all? If only one DC crashed. Which DC crashes. Last added? Oldest? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Christian

On Wed, July 8, 2020 04:23, Rowland penny wrote: > On 08/07/2020 08:50, Mani Wieser via samba wrote: >> >> On 07.07.2020 22:14, Mani Wieser via samba wrote: >> Found it (while having my morning walk with the dog): same as with >> SOA: this is a zone/domain thing and not record >> >> Usage: samba-tool dns delete <server> <zone> <name>

On 2019/02/14 21:12, Rowland Penny via samba wrote: > On Thu, 14 Feb 2019 19:14:19 +0200 > Ashley via samba <samba at lists.samba.org> wrote: > >> Hi there >> >> I have migrated from an older version of Samba DC to Samba 4.9.4 AD. >> Running Centos 7. One server with everything on...  (AD and file >> server) Bind 9.9.4 >> >> Built from

Hello. I'm trying to perform a classic upgrade from Samba 3.6.6 with LDAP backend on Debian to 4.1.6 on Ubuntu on a new machine. The samba-tools creates the following *smb.con*f: *# cat /etc/samba/smb.conf** *[global] workgroup = SOMEDOM realm = somedom.local netbios name = SOMEDOM server role = member server passdb backend = samba_dsdb server