Displaying 20 results from an estimated 2000 matches similar to: "winbind causing huge timeouts/delays since 4.8"
2019 Feb 22
2
winbind causing huge timeouts/delays since 4.8
On Fri, 22 Feb 2019 15:35:53 +0100
Ralph Böhme via samba <samba at lists.samba.org> wrote:
> Hi,
>
> On Fri, Feb 22, 2019 at 01:59:15PM +0100, Alexander Spannagel via
> samba wrote:
> >I want to share some findings with the community about hugh
> >timeouts/delays since upgraded to samba 4.8 end of last year and a
> >patch fixing this in our setup. It would
2019 Feb 22
0
winbind causing huge timeouts/delays since 4.8
Hi,
On Fri, Feb 22, 2019 at 01:59:15PM +0100, Alexander Spannagel via samba wrote:
>I want to share some findings with the community about hugh
>timeouts/delays since upgraded to samba 4.8 end of last year and a
>patch fixing this in our setup. It would be great if someone from
>samba dev team could take a look and if acceptable apply the patch to
>the common code base. It may
2019 Feb 22
0
winbind causing huge timeouts/delays since 4.8
Am 22.02.19 um 15:42 schrieb Rowland Penny via samba:
> On Fri, 22 Feb 2019 15:35:53 +0100
> Ralph Böhme via samba <samba at lists.samba.org> wrote:
>
>> Hi,
>>
>> On Fri, Feb 22, 2019 at 01:59:15PM +0100, Alexander Spannagel via
>> samba wrote:
s.
>>
>> hm, can't reproduce:
>>
>> slow at titan:~/git/samba/scratch$ git describe
2019 Feb 22
6
winbind causing huge timeouts/delays since 4.8
On Fri, 22 Feb 2019 16:40:46 +0100
Alexander Spannagel via samba <samba at lists.samba.org> wrote:
> Am 22.02.19 um 15:42 schrieb Rowland Penny via samba:
> > On Fri, 22 Feb 2019 15:35:53 +0100
> > Ralph Böhme via samba <samba at lists.samba.org> wrote:
> >
> >> Hi,
> >>
> >> On Fri, Feb 22, 2019 at 01:59:15PM +0100, Alexander Spannagel
2019 Feb 23
0
winbind causing huge timeouts/delays since 4.8
On Sat, 23 Feb 2019 21:54:31 +0100
Alexander Spannagel via samba <samba at lists.samba.org> wrote:
> Am 23.02.19 um 15:48 schrieb Rowland Penny via samba:
> >>>>>>> If you have, as you have, 'files sss winbind' in the the
> >>>>>>> passwd & group line in nsswitch.conf, means this:
> >>>>>>> First
2019 Feb 23
3
winbind causing huge timeouts/delays since 4.8
Am 23.02.19 um 15:48 schrieb Rowland Penny via samba:
>>>>>>> If you have, as you have, 'files sss winbind' in the the passwd
>>>>>>> & group line in nsswitch.conf, means this:
>>>>>>> First /etc/passwd or /etc/group is searched and if the user or
>>>>>>> group is found, this info is returned.
2019 Feb 28
2
winbind causing huge timeouts/delays since 4.8
Am 26.02.19 um 12:26 schrieb Ralph Böhme:
> On Tue, Feb 26, 2019 at 11:19:45AM +0100, Alexander Spannagel via samba
> wrote:
>> The huge delays are seen, when user isn't known to sssd and winbind
>> tries to look that user without explicitly a domain given and the
>> option "winbind use default domain" is on it's default of "No" in
>>
2019 Feb 28
1
winbind causing huge timeouts/delays since 4.8
Am 28.02.19 um 17:25 schrieb Ralph Böhme:
> On Thu, Feb 28, 2019 at 05:08:50PM +0100, Alexander Spannagel wrote:
>> Beside log.winbindd i also added log.wb-CENTOS7DEV64 as it may be of
>> interest too. So let me know if there is something i can test once more.
>
> thnks. We also need log.winbindd-idmap.
>
> You may want to file a bug and attach the logs there, so they
2019 Feb 26
3
winbind causing huge timeouts/delays since 4.8
Am 23.02.19 um 22:23 schrieb Rowland Penny via samba:
> On Sat, 23 Feb 2019 21:54:31 +0100
> Alexander Spannagel via samba <samba at lists.samba.org> wrote:
>
>> Am 23.02.19 um 15:48 schrieb Rowland Penny via samba:
>>>>>>>>> If you have, as you have, 'files sss winbind' in the the
>>>>>>>>> passwd & group line
2020 Jun 21
1
About support for AMD ROME CPUs
Hi, all
We use AMD Rome CPUs, like EPYC 7452.
RHEL said that RHEL 7.6.6 began to support these cpus(detials:
https://access.redhat.com/support/policy/amd)
, but we found that CentOS7.6 with kernel 3.10.0-957.21.3.el7.x86_64 also
works fine.
So, my questions are:
1) Is there any place that i can find the cpu support info?
2) Dose the kernel 3.10.0-957.21.3.el7.x86_64 from CentOS7.6 already
2019 Jun 04
1
centos7.6 nvme support
Hello:
I create a centos7.6 virtual machine which use 3.10.0-957 kernel?using
pci passthrough to support nvme device? and I found interrupt can
not distribute to target CPU which in smp_affinity set?the problem solved
when I update kernel to 5.0.20,is anyone can tell me how to solve this
problem without updating kernel??
thanks advance!!
-------------- next part --------------
An HTML
2019 Jun 19
2
libvirtd does not update VM .xml configuration on filesystem after virsh blockcommit
Hi,
Recently We've upgraded some KVM hosts from Fedora 29 to Fedora 30 and
now experience broken VM configurations on filesystem after virsh blockcommit.
Commands "virsh dumpxml ..." and "virsh dumpxml --inactive ..." is showing diffrent configuration than the one on filesystem.
In case of restart libvirtd or system reboot, there are broken VM xml configurations on
2018 Jul 02
2
usb problem on Dell Latitude 3570
Hello All,
after update to Centos7.5 all our Latitudes 3570 - some 150- suffer usb problems.
Plug and play doesn't work any more, people need to insert usb devices - mouse, keyboard, eidreader - first and then boot
in order to use them.
dmesg | tail -n15 gives these EM:
[ 25.164396] usb 1-8: device descriptor read/64, error -110
[ 25.418387] usb 1-8: new full-speed USB device number 6
2014 Apr 11
1
4.0 stopped working after updating xubuntu 13.04
Hi
I got some strange issues on my samba4.0.1 install yesterday. It
happened a while after updating my xubuntu server 13.04 not 13.10.
Everything seems to be working fine except shares. Kerberos
authentication seem to function properly, also DNS works fine but shares
seem semi-broken.
I can't mount any shares on my Windows box, including netlogon,
profiles. I have one share that is
2013 Sep 22
2
mdbox index directories: bug?
Hi,
I'm using mdbox now (Dovecot 2.2.4), with indexes on a
separate disk. Works fine, but the directories for indexes are also
present in the storage folder, and are empty. Userdb (sql) returns this:
home /var/vmail/domains/somedomain/someuser
mail
mdbox:~/mdbox:INDEX=/mnt/spool/dovecot/index/somedomain/s/someuser
And
the created directory structure is:
2019 Feb 23
2
winbind causing huge timeouts/delays since 4.8
> On 23 Feb 2019, at 14:52, Rowland Penny via samba <samba at lists.samba.org> wrote:
>
> On Sat, 23 Feb 2019 14:21:57 +0100
> Remy Zandwijk via samba <samba at lists.samba.org> wrote:
>
>>
>>
>>> On 23 Feb 2019, at 14:07, Rowland Penny via samba
>>> <samba at lists.samba.org> wrote:
>>>
>>> On Sat, 23 Feb 2019
2020 Oct 21
2
Users unable to login
Yes, something came up here:
Oct 21 15:34:18 auth: Debug: auth client connected (pid=1706005)
Oct 21 15:34:18 auth: Debug: client in: AUTH 1 DIGEST-MD5 service=imap
secured session=EQqBZy6yBJQAAAAAAAAAAAAAAAAAAAAB lip=::1rip=::1
lport=143 rport=37892
Oct 21 15:34:18 auth: Debug: client passdb out: CONT 1
2013 Jun 05
3
Samba4 and NVSv4
Short story: cannot get Kerberized NFSv4 to work. I've googled a great
deal and cannot find where I have goofed (and there sure is a lot of
misleading and just plain incorrect information out there), so would
appreciate another pair of eyes. NFSv4 without Kerberos does work fine, as
does ID mapping. We're using NFSv4 in production with sec=sys, but I'm not
happy with that. My
2013 Jun 05
3
Samba4 and NVSv4
Short story: cannot get Kerberized NFSv4 to work. I've googled a great
deal and cannot find where I have goofed (and there sure is a lot of
misleading and just plain incorrect information out there), so would
appreciate another pair of eyes. NFSv4 without Kerberos does work fine, as
does ID mapping. We're using NFSv4 in production with sec=sys, but I'm not
happy with that. My
2007 Sep 25
2
Yikes! Polycom 501 chokes on BootRom 4.0.0?
I was progressively upgrading this phone from 3.1.2
to 3.2.3, then to 4.0.0. v3.2.3 worked fine, but
when I went to 4.0.0 (Even adding the more specific
2345-11500-040.bootrom.ld), it won't run, and
just keeps rebooting.
Now I've got a really nice doorstop unless someone
knows how to get out of this predicament. Help!
0925003705|cfg |3|00|Beginning to provision phone
0925003705|dns