Thank you for the patch and your investigations. In the next few days,
I cannot install the patched package on my production machines. I'll let
you know when I can.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Stephane,
I can't reproduce the hang on my test machine with gdb. (Despite your
investigation seems right for me). CPU usage stay low, as usual on this machine
(same slapd config than the production servers, but only 1 CPU is available).
To prove I made the right steps :-) :
$ gdb --args ldaps
My bad..
You're right, in my test, the second write() is performed on stdout cause my
ldapsearch command is wrong. I missed the '-H' arg to properly set the LDAP
URI (but you too :-p ).
Consequently, the connection was in LDAP not LDAPS, and "ldaps://..." was the
requested attributs :-s
So sin
OK the patch fix the issue for me too in my test env.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
To manage notifications about
Thanks for all )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
To manage notifications about this bug go to:
https://bugs.launchpa
Hi Bryce, when will the fix be officially released ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
To manage notifications about t
OK perfect )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Seems the patch is so hard to backport (?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
To manage notifications about this bug go
Hi Sergio,
Thanks I appreciate your answer.
Yes I can use the package provided in your PPA, even if it's not very
convenient to install and update it on Production machines. About that, will
you maintain these packages with further security updates ?
--
You received this bug notification becaus
Thanks for your support.
> - Your full openldap configuration (please remove any confidential bits, of
> course).
There is lots of ldif files with many private datas. Do you need a particular
configuration ?
> - Any log messages from slapd or related services.
olcLogLevel is "sync stats". Durin
I plan to migrate BDB backend to MDB. Maybe it could help ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
To manage notifications
Nice day, 2 slapd malfunction in the same time, maybe du to network
connectivity issue.
I have the backtrace for one of them.
Please the the attachment.
Thanks.
** Attachment added: "slapd backtrace during sched_yield loop"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+att
issue occured today to.
This time, I join a *full* backtrace .
** Attachment added: "2021010_backtrace_front01_FULL.txt"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+attachment/5496108/+files/2021010_backtrace_front01_FULL.txt
--
You received this bug notification because
** Changed in: openldap (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
To manage notifica
** Attachment removed: "slapd backtrace during sched_yield loop"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+attachment/5495540/+files/2021070_backtrace_front02_..txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Hi, yes it can occur on any machine (slave or master) with the same
configuration / OS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield sysca
Public bug reported:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So
Same error after upgrading krb5 packages from 1.12+dfsg-2ubuntu5.3 to
1.12+dfsg-2ubuntu5.4.
Adding a principal in a subtree outside the realm container fails.
Realm container DN is
"cn=TEST.EXAMPLE.COM,cn=krbContainer,dc=example,dc=com"
But realm has subtree "dc=example,dc=com", with scope = SUB
Even explicitly added subtree doesn't work:
# kdb5_ldap_util -D "cn=admin,dc=example,dc=com" -H
ldap://ldapserver.example.com modify -r TEST.EXAMPLE.COM -subtrees
'dc=example,dc=com:ou=People,dc=example,dc=com"
# kdb5_ldap_util -D "cn=admin,dc=example,dc=com" -H
ldap://ldapserver.example.com vie
Is the fix released in Trustu ESM repository ? I don't see it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817955
Title:
Getting new "DN is out of the realm subtree" error on adding principal
To
This bug it too old I have no information about it status because I no
longer work on the affected machines.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you ar
Hello,
I have regularly the same issue on a production environment.
The command used is wput -R -v -t 3 ftp:/// -i .
I have no .wputrc file.
Whenever the job fails, it generally run with success on next execution (with
the same file - same size - ).
# wput --version
wput version: 0.6.2
See below
I precise aboutr my previous comment I'm running wput on Trusty :
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
It 's seems overflow occur from one of the "sprintf" lines in
progress.c, cause my log stopped like this :
--11:20:12-- `file01.log.gz'
=> ftp://translog:x@X:21//file01.log.gz
==> SIZE file01.log.gz ... failed.
==> PASV ... done.
==> STOR file01.log.gz ... done.
Length: 68,786,837
Impossible for me to run apport-collect and to upgrade to the latest upstream
kernel cause these servers are in production (and I can't reproduce the issue
in other environment , it's XEN VM).
Could it be related to workload ? I have some others machines (ProLiant DL380
G7) with different apps,
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479362
Title:
.hpacucli: page allocation failure: order:4, mode:0x40d0
To manage
Public bug reported:
On LTS Precise, there is no possibility to install/upgradeto libxerces v3
(libxerces-c-dev package) and keep libxalan librairies.
Precise distrib has only libxalan v1.10 packages (libxalan110,
libxalan110-dev), which works with libxerces-c2-dev but not libxerces-c-dev.
The l
** Package changed: openssh (Ubuntu) => xalan (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449637
Title:
no libxalan package version available with libxerces-c-dev
To manage notification
Hi Sergio,
Sorry I don't understand why the bug's importance has decreased to "medium".
Du to client side behavior, issue is totally unpredictable, and slapd no longer
respond to requests.
Morever, the hot fix is not suited for production machines, and can introduce
regression.
Thanks.
--
You r
Public bug reported:
The problem seems to incriminate systemd-networkd (v229-4ubuntu21.1), not the
network/bonding configuration.
When a full bonding configuration is made with systemd in /etc/systemd/network,
on 2 two differents physical hosts, same hardware and in same VLAN:
- bond0.netde
A workaround is to set manually a different MAC address in bond0.netdev:
[NetDev]
Name=bond0
Kind=bond
MACAddress=16:d6:b0:24:16:3c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791245
Title:
bon
Problem solved: root cause wa the same id on the 2 machines in /etc
/machine-id
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791245
Title:
bonding 802.3ad with systemd-networkd: duplicate MAC addr
32 matches
Mail list logo
