Displaying 20 results from an estimated 8000 matches similar to: "winbindd crashing -- how to auto-heal?"
2018 Sep 03
7
winbindd crashing -- how to auto-heal?
On Sun, 2 Sep 2018 22:37:05 -0400
Jamie Jackson via samba <samba at lists.samba.org> wrote:
> Thanks for the workaround, Luca. I might end up going with:
>
> #!/bin/bash
> getent group | grep -q 'Domain Users' && exit 0
> echo "restarting winbind"
> sudo systemctl restart winbind
>
>
> Rowland, it crashed again. Here's some info.
2018 Sep 02
3
winbindd crashing -- how to auto-heal?
El 2/9/18 a les 10:39, Rowland Penny via samba ha escrit:
> All of this is just a sticking plaster on the problem, if winbind is
> crashing on a regular basis, we need to know this and will need
> level 10 logs, debug info etc. Without this info, it will never get
> fixed.
Meanwhile, I need my server to keep running, so the plaster looks fine.
Besides, winbind isn't crashing,
2018 Sep 02
2
winbindd crashing -- how to auto-heal?
El 2/9/18 a les 01:03, Luca Olivetti via samba ha escrit:
> El 1/9/18 a les 03:03, Jamie Jackson via samba ha escrit:
>> Hi folks,
>>
>> Every couple days any one of my project's 10 or so RHEL VMs can't be
>> logged
>> into with a domain account (active directory integration). Our admin goes
>> in with a local account and restarts winbind to fix it.
2018 Sep 03
2
winbindd crashing -- how to auto-heal?
El 3/9/18 a les 16:35, Jamie Jackson via samba ha escrit:
> I didn't set this up, but I assume the sysadmins didn't run it because
> they, like Luca, probably assumed that smbd was for server functionality
I didn't assume, it's the documentation that says so.
In fact, the winbindd man page says that the winbind daemon provides
services to smbd and ntlm_auth, not the
2018 Sep 03
2
winbindd crashing -- how to auto-heal?
On 09/01/2018 07:03 PM, Luca Olivetti via samba wrote:
> El 1/9/18 a les 03:03, Jamie Jackson via samba ha escrit:
>> Hi folks,
>>
>> Every couple days any one of my project's 10 or so RHEL VMs can't be
>> logged
>> into with a domain account (active directory integration). Our admin goes
>> in with a local account and restarts winbind to fix it.
2018 Sep 03
1
winbindd crashing -- how to auto-heal?
On Mon, 3 Sep 2018 10:35:38 -0400
Jamie Jackson <jamiejaxon at gmail.com> wrote:
> On Mon, Sep 3, 2018 at 5:17 AM Rowland Penny via samba <
> samba at lists.samba.org> wrote:
>
> > Why isn't 'smbd' running ?
> >
>
> I didn't set this up, but I assume the sysadmins didn't run it because
> they, like Luca, probably assumed that smbd
2018 Sep 01
2
winbindd crashing -- how to auto-heal?
Hi Rowland,
Here's the info you asked for.
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.5 (Maipo)
$ smbcontrol --version
Version 4.7.1
smb.conf:
------------------------------
[global]
security = ADS
realm = REDACTED.WAN
encrypt passwords = true
workgroup = REDACTED
winbind enum users = yes
winbind enum groups = yes
2018 Sep 03
5
winbindd crashing -- how to auto-heal?
El 3/9/18 a les 17:13, Rowland Penny via samba ha escrit:
> Yes, but it depends on how you run Samba. If you run Samba as a
> standalone server you only need to run 'smbd', but running 'nmbd' as
> well would be a good idea.
>
> If you run Samba as a PDC or BDC, the same as a standalone server goes.
>
> Anything else needs both smbd and winbind running.
It
2016 Apr 12
4
[Half OT?] Waiting for completion of Startupscript before logon
Rowland penny <rpenny at samba.org> schrieb:
> Can you be a bit more specific, it sounds like you mean users can logon
> somewhere even though Samba isn't running, or do you mean that windows
> users are not running a logon script when they log in.
No, of course Samba runs...
I mean, Windows boots and starts a Startup-Script (or will shutdown and call
a Shutdown-Script).
2018 Sep 03
2
winbindd crashing -- how to auto-heal?
On Mon, 3 Sep 2018 15:37:03 +0200
Luca Olivetti via samba <samba at lists.samba.org> wrote:
> El 3/9/18 a les 15:23, Robert Marcano via samba ha escrit:
>
> >>
> >> I run this cron job every minute. Winbind usually crashes once or
> >> twice a day
> >>
> >> #!/bin/bash
> >> getent group | grep -q 513 && exit 0
>
2019 Oct 11
4
dns replication error due to deleted records
El 11/10/19 a les 16:59, Luca Olivetti via samba ha escrit:
> El 11/10/19 a les 16:12, Rowland penny via samba ha escrit:
>> Try running this on a DC:
>>
>> samba-tool ldapcmp ldap://DC1 ldap://DC2
>> --filter='whenChanged,dc,DC,cn,CN,ou,OU'
>>
>> Replace 'DC1' and 'DC2' with your actual DC short hostnames
>>
>> It should
2018 Sep 03
0
winbindd crashing -- how to auto-heal?
On Mon, Sep 3, 2018 at 5:17 AM Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Sun, 2 Sep 2018 22:37:05 -0400
> Jamie Jackson via samba <samba at lists.samba.org> wrote:
>
> > Thanks for the workaround, Luca. I might end up going with:
> >
> > #!/bin/bash
> > getent group | grep -q 'Domain Users' && exit 0
> > echo
2015 Jun 02
7
Can't join machine without full access
Sernet samba 4.2.2 in ubuntu 14.04.2 LTS, a fresh migration from samba 3
(I'm still in the testing phase).
I'm experimenting with task delegation.
Using the ADUC wizard, I select the "Join machine to domain" task to add
to my userid (I also tried a group I'm a member of with the same
result), at the domain level (rough translation, this is on a localized
windows 7).
Adding
2010 May 03
3
win 7, samba 3.4.7, error 0x000003e6 with some printers
Hello,
I'm testing windows 7 with samba 3.4.7 and I'm using PrintUIEntry to
connect the printers.
With some of those printers the connection fails (client side) with
error 0x000003e6.
The strange thing is that:
1) trying the same connection against samba 3.0.11 works (alas, no
domain functionality with that old version) and
2) two of the failing printers share the same driver with
2015 Apr 28
2
[Samba4] List of Distro currently with 4.2.X samba package
El 28/04/15 a les 12:52, Mario Pio Russo ha escrit:
> hi all
>
> the sernet package is actually a good alterrnative, however I can't make
> the repository work with ubuntu 14.04
>
> has anyone used these repo?
Yes, I'm using them on a test machine with ubuntu 14.04 lts.
Did you replace USERNAME:ACCESSKEY with your data?
Bye
--
Luca Olivetti
Wetron Automation
2015 Mar 31
7
sssd-ad cannot be installed with sernet samba
On 31/03/15 03:54, Sketch wrote:
> On Mon, 30 Mar 2015, Rowland Penny wrote:
>
>> On 30/03/15 16:33, Luca Olivetti wrote:
>>> Right, the correct solution would be to package samba in a way that
>>> doesn't break sssd.
>>
>> You could also say that sssd should be packaged in a way that works
>> with the sernet packages.
>
> I'm with
2015 Mar 30
3
sssd-ad cannot be installed with sernet samba
On 30/03/15 15:49, Luca Olivetti wrote:
> El 30/03/15 a les 15:43, L.P.H. van Belle ha escrit:
>> The problem here is that
>>
>> sssd does not know sernet-samba-libs is also providing samba-libs
> Not only that, the layout is also different (at least, trying to force
> the installation of sssd-ad/sssd-ad-common I see that it doesn't find
> libndr-nbt.so.0, which
2019 Oct 11
2
dns replication error due to deleted records
On 11/10/2019 14:58, Luca Olivetti via samba wrote:
> El 10/10/19 a les 20:23, Luca Olivetti via samba ha escrit:
>> Today I noticed something that has been going on for some weeks:
>>
>> I have 2 dc, (dc1 and dc2) both debian buster with the distro
>> provided samba (4.9.5), recently upgraded from stretch.
>>
>> samba-tool drs showrepl on dc2 says
>>
2019 Oct 10
4
dns replication error due to deleted records
Today I noticed something that has been going on for some weeks:
I have 2 dc, (dc1 and dc2) both debian buster with the distro provided
samba (4.9.5), recently upgraded from stretch.
samba-tool drs showrepl on dc2 says
DC=DomainDnsZones,DC=samba,DC=wetron,DC=es
Default-First-Site-Name\DC1 via RPC
DSA object GUID: 89812346-9037-43b0-86ab-c5052f55125d
2015 Apr 03
2
Member server - winbind unable to resolve users/groups
El 03/04/15 a les 20:33, Andrey Repin ha escrit:
> Eh? What the? Why? Google says it may be an issue with DNS, but mine works
> fine. Especially since a few lines before it successfully contact AD DC.
Probably not related, but I had an issue with kerberos and it turns out
I had the wrong host name for 127.0.0.1 in /etc/hosts
Bye
--
Luca Olivetti
Wetron Automation Technology