similar to: winbind error after startup on Samba member server

On Thu, 13 Jun 2024 16:26:17 +0200 Peter Milesson via samba <samba at lists.samba.org> wrote: > Hi folks, > > The last log record from journalctl -xeu winbind directly after > winbind startup is: > > Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate > failed with exit status 1 > > For completeness, the log entries for winbind startup is

On 13.06.2024 17:21, Rowland Penny via samba wrote: > On Thu, 13 Jun 2024 16:26:17 +0200 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> Hi folks, >> >> The last log record from journalctl -xeu winbind directly after >> winbind startup is: >> >> Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate >>

On 13.06.2024 20:33, Peter Milesson via samba wrote: > > > On 13.06.2024 17:21, Rowland Penny via samba wrote: >> On Thu, 13 Jun 2024 16:26:17 +0200 >> Peter Milesson via samba <samba at lists.samba.org> wrote: >> >>> Hi folks, >>> >>> The last log record from journalctl -xeu winbind directly after >>> winbind startup is:

Hello, Centos 7.5 samba 4.8.3 installation, compiled from source working as AD DC. It was an update from 4.7 (not an in place update, but added new DC's to existing domain and demoted 4.7.x DC's). After adding to my smb.conf: /apply group policies = yes/ I see errors on samba star: ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler)   /usr/local/samba/sbin/samba_gpoupdate: SID

I joined an existing domain according to: https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC My var/log.samba shows the following error message ... and unfortunately ... I have no idea what that means. [2013/05/29 20:48:00, 0] ../lib/util/util_runcmd.c:334(samba_runcmd_io_handler) /usr/local/samba/sbin/samba_dnsupdate: tkey query failed: GSSAPI error: Major = Unspecified

On 9/18/2016 6:23 PM, Garming Sam wrote: > Hi, > > For the unsorted attributeID values errors, can you first try: > > samba-tool dbcheck --cross-ncs --fix --yes 'fix_replmetadata_unsorted_attid' > > There's too much going on, and it does look like it might be bailing > out. Running it with 'fix_replmetadata_unsorted_attid' should fix those > first

Hi, I have two problems with my 2 Samba AD-DC. I don't know if the two problems are related. Both domain controllers show the same error pattern for problem 1.The second problem only occurs with the second domain controller. The domain itself seems to work and be in order. Does someone know where this comes from and how to solve it? ## Issue 1 ## By doing my random log checking, I saw the

On Wed, 02 Jan 2019 20:09:44 +0100 Král Gergely via samba <samba at lists.samba.org> wrote: > 2018-12-31 20:50 időpontban L.P.H. van Belle via samba ezt írta: > > Can you try to upgrade to any 4.8 version then to 4.9.4? > > might work, atleast my guess this will have a better chance get > > passed this bug. > > > > I can confirm that an upgrade to 4.7.3 to

On Sat, 8 Jun 2024 17:05:25 +0200 Ronny Preiss via samba <samba at lists.samba.org> wrote: > Hi, > > I have two problems with my 2 Samba AD-DC. I don't know if the two > problems are related. > Both domain controllers show the same error pattern for problem 1.The > second problem only occurs with the second domain controller. > The domain itself seems to work and

Hi, i have the same problem. Inplace upgrade and i get the following error. Mar 23 13:46:50 orion2 systemd[1]: Started Session 30346 of user root. Mar 23 13:46:50 orion2 systemd-logind[1316]: Removed session 30346. Mar 23 13:46:50 orion2 sernet-samba-ad[7358]: Shutting down SAMBA AD services : ..done Mar 23 13:46:50 orion2 systemd[1]: Stopped LSB: initscript for the SAMBA AD services. Mar 23

> On 2 Jan 2019, at 22:43, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Wed, 2 Jan 2019 19:35:04 +0000 > Rowland Penny via samba <samba at lists.samba.org> wrote: > >> On Wed, 02 Jan 2019 20:09:44 +0100 >> Král Gergely via samba <samba at lists.samba.org> wrote: >> >>> 2018-12-31 20:50 időpontban L.P.H. van Belle

Hello, I have recently compiled, installed and configured samba4 to run on a FreeBSD server. samba -V reports the version to be Version 4.1.0pre1-GIT-57990cb. The server has working BIND 9.9 and ISC-DHCP services running on it. I have provisioned samba 4 to use the BIND_DLZ DNS backend. On the whole things seem to be working. local names are being resolved. phpLDAPAdmin shows the new

Good afternoon, I have installed a fileserver with samba4 environment. This is configured to works as AD-DC even if I only use it as a fileserver (at the moment). All seems to works fine but, every 10 minutes, the log print these messages: Mar 22 11:53:17 fileserver samba[1946]: [2016/03/22 11:53:17.557554, 0] ../lib/util/util_runcmd.c:324(samba_runcmd_io_handler) Mar 22 11:53:17 fileserver

Am 23.07.2018 um 23:27 schrieb Rowland Penny via samba: > On Mon, 23 Jul 2018 23:09:58 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > >> Am 19.07.2018 um 17:50 schrieb Rowland Penny via samba: >>> On Thu, 19 Jul 2018 17:33:46 +0200 >>> Anton Blau via samba <samba at lists.samba.org> wrote: >>> >>>> Am 19.07.2018 um

Hello, please excuse my bad englisch. I am not a native speaker. I try to install Samba 4 as a active directory domain controller but I get always this message in the /var/log/syslog: Jul 18 11:42:41 file winbindd[1100]: [2018/07/18 11:42:41.609594,  0] ../source3/winbindd/winbindd_cache.c:3235(initialize_winbindd_cache) Jul 18 11:42:41 file winbindd[1100]:   initialize_winbindd_cache:

Hi, It's my first try to setup RODC using Samba 4.8. We have latest Samba 4.7 environnement with 2 DC and some file servers. Joining the DC to the domain is OK using samba-tool domain join command. The domain controller appears in the DC list (MMC) However, users cannot be authenticated. Samba is running but these ports are closed : netbios-ssn 139/tcp # NETBIOS session service

Hi all, I've set up a simple domain using Samba 4.4.2 from source under Ubuntu 16.04. I accepted the usual defaults and basically followed wiki.samba.org to the letter. The main thing is I'm using Samba's internal DNS and not Bind (Bind is not even installed on the system). In the log.samba file on the first DC I kept getting this: [2016/04/28 17:01:02.716292, 0]

Hi, I have restarted, but it didn't solve the problem. /etc/init.d/samba-ad-dc status samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-08-12 15:32:18 -03; 9s ago Docs: man:samba(8) man:samba(7) man:smb.conf(5) Main PID: 575 (samba)

Am 19.07.2018 um 17:50 schrieb Rowland Penny via samba: > On Thu, 19 Jul 2018 17:33:46 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > >> Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: >>> On Wed, 18 Jul 2018 23:21:41 +0200 >>> Anton Blau via samba <samba at lists.samba.org> wrote: >>> >>>> Am 18.07.2018 um

Hello, I am getting these errors in /var/log/messages : Oct 12 16:36:15 sambadc samba[7147]: [2013/10/12 16:36:15.817541, 0] ../source4/dsdb/kcc/kcc_periodic.c:664(kccsrv_samba_kcc) Oct 12 16:36:15 sambadc samba[7147]: Calling samba_kcc script Oct 12 16:36:15 sambadc abrt: detected unhandled Python exception in '/usr/local/samba/sbin/samba_kcc' Oct 12 16:36:15 sambadc