similar to: Memory leak in samba-ad-dc on 4.5.x not related to aio?

Displaying 20 results from an estimated 1000 matches similar to: "Memory leak in samba-ad-dc on 4.5.x not related to aio?"

2017 May 05
2
Memory leak in samba-ad-dc on 4.5.x not related to aio?
On Fri, May 05, 2017 at 10:21:05AM +0200, Sven Schwedas wrote: > On 2017-05-05 10:09, Volker Lendecke wrote: > > On Fri, May 05, 2017 at 09:42:47AM +0200, Sven Schwedas via samba wrote: > >>> root 9988 0.8 59.4 1571936 606488 ? S Apr26 114:41 /usr/sbin/samba > > > > Can you post /proc/9988/smaps somewhere? > > Sure,
2017 May 05
1
Memory leak in samba-ad-dc on 4.5.x not related to aio?
On Fri, May 05, 2017 at 09:42:47AM +0200, Sven Schwedas via samba wrote: > > root 9988 0.8 59.4 1571936 606488 ? S Apr26 114:41 /usr/sbin/samba Can you post /proc/9988/smaps somewhere? Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-370000-0, fax: +49-551-370000-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kontakt at
2017 Nov 13
2
Winbind error "Could not fetch our SID - did we join?"
/etc/hostname:villach-file /etc/hosts:# The following lines are desirable for IPv6 capable hosts /etc/hosts:::1 localhost ip6-localhost ip6-loopback /etc/hosts:ff02::1 ip6-allnodes /etc/hosts:ff02::2 ip6-allrouters /etc/hosts:127.0.0.1 localhost /etc/hosts:192.168.16.214 villach-file /etc/krb5.conf:[libdefaults] /etc/krb5.conf: default_realm = AD.TAO.AT /etc/krb5.conf: dns_lookup_realm = true
2017 Sep 08
2
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
> -----Oorspronkelijk bericht----- > Van: Sven Schwedas [mailto:sven.schwedas at tao.at] > Verzonden: vrijdag 8 september 2017 14:40 > Aan: L.P.H. van Belle; samba at lists.samba.org > Onderwerp: Re: [Samba] Server GC/name.dom/dom is not > registered with our KDC: Miscellaneous failure (see text): > Server (GC/name/dom at DOM) unknown > > On 2017-09-08 10:37, L.P.H.
2017 Sep 08
2
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
On 2017-09-08 13:02, Rowland Penny via samba wrote: > On Fri, 8 Sep 2017 12:43:40 +0200 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> On 2017-09-08 12:26, Rowland Penny via samba wrote: >>> On Fri, 8 Sep 2017 12:03:53 +0200 >>> "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: >>> >>>>
2019 Jun 14
5
Spring Cleanup / Migrating Samba 4.5 to 4.10
With some slight delay, we did actually manage to get all our old wonky compatibility solutions nuked (turned out there were a few more lurking in the shadows than expected?). Mail servers are no longer domain joined, and unencrypted LDAP is finally gone, together with the terrible PHP scripts that needed it. Which allowed me to finally cleanup all the samba setups:
2019 May 21
1
Debugging Samba is a total PITA and this needs to improve
Hai, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Sven > Schwedas via samba > Verzonden: dinsdag 21 mei 2019 16:44 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Debugging Samba is a total PITA and > this needs to improve > > On 21.05.19 16:15, L.P.H. van Belle via samba wrote: > >> Since Cyrus
2017 Nov 13
2
Winbind error "Could not fetch our SID - did we join?"
We did, in fact, join mere seconds ago, but for some reason, winbind still can't find itself. ADUC etc meanwhile have no trouble finding the newly added computer account. Wiping /var/{lib,cache}/samba/ (and the computer account) makes no difference, the error persists. How do I proceed? -- Mit freundlichen Grüßen, / Best Regards, Sven Schwedas, Systemadministrator Mail/XMPP sven.schwedas
2019 May 21
2
Debugging Samba is a total PITA and this needs to improve
The smb.conf hasn't changed since the last three or four times I've posted here asking for help: https://up.tao.at/u/samba/villach-file.txt Top level error I'm seeing is that since today *some* Windows users are denied SMB access to this one member server ("Network password is invalid"), but not all users. Worked fine before today. wbinfo -p/-P work, wbinfo -a shows the
2019 May 22
2
Various AD issues; summary
On 22.05.19 15:31, L.P.H. van Belle wrote: > Hai, > > Well, good that your more relax and releaved in pressure.. > Apoligies accepted. ;-), i know the fealing but do understand, we are trying to help out.. > > As you know, it very frustration to ask the same things again, and you showing them again > But now as you showed with all the configs. It is needed.. (sorry)
2017 Nov 13
3
Winbind error "Could not fetch our SID - did we join?"
On 2017-11-13 13:31, Rowland Penny wrote: > On Mon, 13 Nov 2017 13:18:20 +0100 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> Could we please not waste a week poking at random unrelated stuff this >> time? These "I try the same stuff no matter what the problem is" >> boilerplate emails become really grating after the first few times. :/
2017 Nov 13
2
Winbind error "Could not fetch our SID - did we join?"
On 2017-11-13 12:33, Rowland Penny via samba wrote: > On Mon, 13 Nov 2017 12:05:33 +0100 > Sven Schwedas <sven.schwedas at tao.at> wrote: > >> /etc/hostname:villach-file >> /etc/hosts:# The following lines are desirable for IPv6 capable hosts >> /etc/hosts:::1 localhost ip6-localhost ip6-loopback >> /etc/hosts:ff02::1 ip6-allnodes >>
2019 Jul 04
2
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
On 03.07.19 18:04, Rowland penny via samba wrote: >>>> How do I get rid of these bogus Schema entries, and how do I fix the >>>> user account? >>> I do not think you can remove anything from the schema, but I believe >>> you can deactivate schema objects, try reading this: >>> >>>
2019 Jul 03
2
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
On 03.07.19 17:19, Rowland penny via samba wrote: >> All these object classes were tests we did? years ago, and which have >> been "deleted" (I don't even remember by what mechanism) for almost as >> long. No object should still be using any of these, and on graz-dc-sem >> that's true. > I would love to know how you deleted something from the schema, it
2019 May 23
2
Various AD issues; summary
Hi Sven, Ok, before i back to my packaging, i reviewed the changes. You still missed a bit but it looks much better already, your completely there, but we will get there. And you really need to be more precise, why im telling that... Well the review. ( thats not all, im still reviewing the base only) ... https://up.tao.at/u/samba/graz-file.info2.txt Checking file:
2019 May 21
4
Debugging Samba is a total PITA and this needs to improve
Hai Sven, And still i see/think you should change some things to get a better base setup. And no its not bike shedding.... It is making a standard setup, work from there. [libdefaults] default_realm = AD.TAO.AT dns_lookup_realm = true < if you have multple REALM, else false. (default_realm = AD.TAO.AT) dns_lookup_kdc = true Checking file: /etc/nsswitch.conf passwd: files
2019 May 21
3
Debugging Samba is a total PITA and this needs to improve
On 21.05.19 14:16, Rowland penny via samba wrote:> You need to investigate your DB problems Great, but how? > I see no reason to have different smb.conf files for different Unix > domain members, just don't have 'netbios name' in any smb.conf. There's also share definitions in the files which I omitted, which are the actual meat of the config files. > You will also
2017 Sep 06
6
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
Hai Sven, > -----Oorspronkelijk bericht----- > Van: Sven Schwedas [mailto:sven.schwedas at tao.at] > Verzonden: dinsdag 5 september 2017 17:13 > Aan: L.P.H. van Belle > CC: samba at lists.samba.org > Onderwerp: Re: [Samba] Server GC/name.dom/dom is not > registered with our KDC: Miscellaneous failure (see text): > Server (GC/name/dom at DOM) unknown > > On
2017 Sep 05
3
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
Today's episode of "why is AD break", brought to you by: > [2017/09/05 10:17:06.015617, 3] ../source4/auth/gensec/gensec_gssapi.c:613(gensec_gssapi_update) > Server GC/graz-dc-1b.ad.tao.at/ad.tao.at is not registered with our KDC: Miscellaneous failure (see text): Server (GC/graz-dc-1b.ad.tao.at/ad.tao.at at AD.TAO.AT) unknown > [2017/09/05 10:17:06.015717, 0]
2019 Jul 03
2
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
It's amazing how long Samba just keeps running even when apparently everything's broken. In preparation of finally upgrading our DCs to 41.0, I ran dbcheck on all of them, resulting in: graz-dc-sem: > Checking 3861 objects > Error: governsID CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId > Error: