[Touch-packages] [Bug 1800462] [NEW] Request to add "ens" and "bond" interface to interface-order
Public bug reported: Can you please add new systemd interfaces "ens*" and "bond*" to interface-order? The interfaces are covered with the "*" in the last line, but IPv6 should be preferred to IPv4. Also, the rndssd interface is not covered. You should add something like *.rdnssd. The actual interface is called "000". /run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::x /run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::x /run/resolvconf/interface/ens3.dhclient:domain abz.com /run/resolvconf/interface/ens3.dhclient:search abz.com /run/resolvconf/interface/ens3.dhclient:nameserver 10.x.x.x root@host:/etc/resolvconf# dpkg -l | grep resolvconf ii resolvconf 1.78ubuntu6 all name server information handler root@host:/etc/resolvconf# dpkg -l | grep rdnssd ii rdnssd 1.0.1-1ubuntu2 amd64 IPv6 recursive DNS server discovery daemo root@host:/etc/resolvconf# cat /etc/issue Ubuntu 16.04.4 LTS \n \l root@host:/etc/resolvconf# uname -a Linux host 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1800462 Title: Request to add "ens" and "bond" interface to interface-order Status in resolvconf package in Ubuntu: New Bug description: Can you please add new systemd interfaces "ens*" and "bond*" to interface-order? The interfaces are covered with the "*" in the last line, but IPv6 should be preferred to IPv4. Also, the rndssd interface is not covered. You should add something like *.rdnssd. The actual interface is called "000". /run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::x /run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::x /run/resolvconf/interface/ens3.dhclient:domain abz.com /run/resolvconf/interface/ens3.dhclient:search abz.com /run/resolvconf/interface/ens3.dhclient:nameserver 10.x.x.x root@host:/etc/resolvconf# dpkg -l | grep resolvconf ii resolvconf 1.78ubuntu6 all name server information handler root@host:/etc/resolvconf# dpkg -l | grep rdnssd ii rdnssd 1.0.1-1ubuntu2 amd64 IPv6 recursive DNS server discovery daemo root@host:/etc/resolvconf# cat /etc/issue Ubuntu 16.04.4 LTS \n \l root@host:/etc/resolvconf# uname -a Linux host 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1800462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610479] Re: interface-order needs definitions for systemd predictable names
Hi, I've an issue using resolvconf in combination with rdnssd. The host is getting the nameserver stuff via RDNSS, not DHCPv6. The interface order doesn't cover the rdnssd method?! Interface name should be ens3. /run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::47 /run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::48 /run/resolvconf/interface/ens3.dhclient:domain abz.com /run/resolvconf/interface/ens3.dhclient:search abz.com /run/resolvconf/interface/ens3.dhclient:nameserver 10.x.x.47 root@host:/etc/resolvconf# cat /etc/network/interfaces # Interface lo auto lo iface lo inet loopback # Interface lo_ipv6 iface lo inet6 loopback # Interface ens3 auto ens3 iface ens3 inet dhcp # Interface ens3_ipv6 iface ens3 inet6 auto root@host:/etc/resolvconf# dpkg -l | grep resolvconf ii resolvconf 1.78ubuntu6 all name server information handler root@host:/etc/resolvconf# dpkg -l | grep rdnssd ii rdnssd 1.0.1-1ubuntu2 amd64IPv6 recursive DNS server discovery daemo root@host:/etc/resolvconf# cat /etc/issue Ubuntu 16.04.4 LTS \n \l root@host:/etc/resolvconf# uname -a Linux ermscn01 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1610479 Title: interface-order needs definitions for systemd predictable names Status in resolvconf package in Ubuntu: Confirmed Bug description: Another release, another round of interface name changes. This time systemd has gotten into the fray to make things even more interesting. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ As such, IPv4 resolvers are now being preferred over IPv6 again on these new interface names. kjotte@flounder:~$ grep '' /run/resolvconf/interface/ens3.* /run/resolvconf/interface/ens3.dhclient:search nivex.lan. /run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30 /run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net. /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10 /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 5 19:53:25 2016 InstallationDate: Installed on 2016-08-04 (1 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
Hi, this package fixes our slapd replication bug. we tested following version: # dpkg -l | grep 'slapd\|libldap' ii libldap-2.4-2:amd64 2.4.42+dfsg-2ubuntu3.3 amd64OpenLDAP libraries ii slapd 2.4.42+dfsg-2ubuntu3.3 amd64OpenLDAP server (slapd) Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Committed Bug description: [Impact] Concurrent SASL authentications could trigger a segfault. This was observed by the bug reporter during replication from a master to a slave, and can be reproduced with a test program. The fix is applied upstream, see comment #13. [Test Case] * Create a fresh xenial VM or container and login. Update the apt repositories: sudo apt update * Create a local directory and cd into it: mkdir test && cd test * Download the test attachments from this bug: Makefile, sasltest.c and testscript: wget https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript * Build with $ apt install libsasl2-dev libldap2-dev $ make * Execute the testscript with sudo once. It shall fail at the very end with a core dump: sudo sh ./testscript (...) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Export this var: export LDAPSASL_SECPROPS=none * Run the actual test script a few more times to confirm the crasH: $ ./sasltest rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Install the updated packages from proposed * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported: $ echo $LDAPSASL_SECPROPS none $ ./sasltest $ This time the test completes without crashing. [Regression Potential] This is SASL authentication, and with kerberos nonetheless (in the case of the bug reporter). I suspect not many people deploy this due to its complexity. The ones that have such a setup, however, tend to know what they are doing, so if they say the problem is fixed for them, I believe it is. About this particular change, it's committed upstream and also in debian, and @rtandy was kind enough to provide a sample test script that exhibits the problem. [Other Info] Since the fix is applied upstream and in Debian, there shouldn't be additional surprises here. [Original description] I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd"
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Committed Bug description: [Impact] Concurrent SASL authentications could trigger a segfault. This was observed by the bug reporter during replication from a master to a slave, and can be reproduced with a test program. The fix is applied upstream, see comment #13. [Test Case] * Create a fresh xenial VM or container and login. Update the apt repositories: sudo apt update * Create a local directory and cd into it: mkdir test && cd test * Download the test attachments from this bug: Makefile, sasltest.c and testscript: wget https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript * Build with $ apt install libsasl2-dev libldap2-dev $ make * Execute the testscript with sudo once. It shall fail at the very end with a core dump: sudo sh ./testscript (...) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Export this var: export LDAPSASL_SECPROPS=none * Run the actual test script a few more times to confirm the crasH: $ ./sasltest rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Install the updated packages from proposed * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported: $ echo $LDAPSASL_SECPROPS none $ ./sasltest $ This time the test completes without crashing. [Regression Potential] This is SASL authentication, and with kerberos nonetheless (in the case of the bug reporter). I suspect not many people deploy this due to its complexity. The ones that have such a setup, however, tend to know what they are doing, so if they say the problem is fixed for them, I believe it is. About this particular change, it's committed upstream and also in debian, and @rtandy was kind enough to provide a sample test script that exhibits the problem. [Other Info] Since the fix is applied upstream and in Debian, there shouldn't be additional surprises here. [Original description] I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2e95b79700 (LWP 42141)] 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (gdb) thr apply all bt Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)): #0
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
Hello Brian, I've updated 2 servers with the new package. Let me test few days, and I'll get back to you with the results. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Committed Bug description: [Impact] Concurrent SASL authentications could trigger a segfault. This was observed by the bug reporter during replication from a master to a slave, and can be reproduced with a test program. The fix is applied upstream, see comment #13. [Test Case] * Create a fresh xenial VM or container and login. Update the apt repositories: sudo apt update * Create a local directory and cd into it: mkdir test && cd test * Download the test attachments from this bug: Makefile, sasltest.c and testscript: wget https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript * Build with $ apt install libsasl2-dev libldap2-dev $ make * Execute the testscript with sudo once. It shall fail at the very end with a core dump: sudo sh ./testscript (...) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Export this var: export LDAPSASL_SECPROPS=none * Run the actual test script a few more times to confirm the crasH: $ ./sasltest rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Install the updated packages from proposed * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported: $ echo $LDAPSASL_SECPROPS none $ ./sasltest $ This time the test completes without crashing. [Regression Potential] This is SASL authentication, and with kerberos nonetheless (in the case of the bug reporter). I suspect not many people deploy this due to its complexity. The ones that have such a setup, however, tend to know what they are doing, so if they say the problem is fixed for them, I believe it is. About this particular change, it's committed upstream and also in debian, and @rtandy was kind enough to provide a sample test script that exhibits the problem. [Other Info] Since the fix is applied upstream and in Debian, there shouldn't be additional surprises here. [Original description] I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2e95b79700 (LWP 42141)] 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (gdb) thr apply all bt Thread 6
[Touch-packages] [Bug 1101825] Re: IPv6 static default route added incorrectly by network-manager
Hi Thiago, how did you fix the issue? On my 16.04 workstation i still have the issue. 2 Routers generate RAs, the routing table on the clients looks like: default via fe80::xx dev enp0s25 proto static metric 100 pref medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
Hi Andreas, here are my syncprov and syncrepl configurations: dn: olcOverlay={0}syncprov,olcDatabase={1}mdb,cn=config objectClass: olcOverlayConfig objectClass: olcSyncProvConfig olcOverlay: {0}syncprov olcSpCheckpoint: 5 5 dn: olcOverlay={0}syncprov,olcDatabase={2}mdb,cn=config objectClass: olcOverlayConfig objectClass: olcSyncProvConfig olcOverlay: {0}syncprov olcSpCheckpoint: 5 5 olcSyncrepl: rid=201 provider=ldap://master.example.com bindmethod=sasl timeout=0 network-timeout=0 saslmech=GSSAPI realm=EXAMPLE.COM keepalive=0 :0:0 starttls=yes tls_cert="/etc/ssl/certs/slave.pem" tls_key= "/etc/ssl/private/slave.key" tls_cacert="/etc/ssl/certs/ca-cer tificates.crt" tls_reqcert=demand tls_cipher_suite=NORMAL:-VERS-SSL3.0:-VER S-TLS-ALL:+VERS-TLS1.2:-CIPHER-ALL:-SHA1:-MD5:-RSA:+AES-256-CBC:+CAMELLIA-2 56-CBC:+AES-128-CBC:+RSA filter="(objectclass=*)" searchbase="dc=example,dc=com" s cope=sub schemachecking=off type=refreshAndPersist retry="5 10 15 +" olcSyncrepl: rid=202 provider=ldap://master.example.com bindmethod=sasl timeout=0 network-timeout=0 saslmech=GSSAPI realm=EXAMPLE.COM keepalive=0 :0:0 starttls=yes tls_cert="/etc/ssl/certs/slave.pem" tls_key= "/etc/ssl/private/slave.key" tls_cacert="/etc/ssl/certs/ca-cer tificates.crt" tls_reqcert=demand tls_cipher_suite=NORMAL:-VERS-SSL3.0:-VER S-TLS-ALL:+VERS-TLS1.2:-CIPHER-ALL:-SHA1:-MD5:-RSA:+AES-256-CBC:+CAMELLIA-2 56-CBC:+AES-128-CBC:+RSA filter="(objectclass=*)" searchbase="ou=db2" scope=sub schemachecking=off type=refreshAndPersist retry="5 10 15 +" krb5-kdc 1.13.2+dfsg-5ubuntu2 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Committed Status in openldap package in Ubuntu: In Progress Bug description: I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2e95b79700 (LWP 42141)] 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (gdb) thr apply all bt Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f2e95378700 (LWP 42142)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)): #0 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #1 0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #2 0x7f2ea5303d69 in
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
Thanks Ryan, I will wait... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Committed Status in openldap package in Ubuntu: In Progress Bug description: I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2e95b79700 (LWP 42141)] 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (gdb) thr apply all bt Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f2e95378700 (LWP 42142)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)): #0 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #1 0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #2 0x7f2ea5303d69 in sasl_client_init () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #3 0x7f2ea594da6c in ldap_int_sasl_init () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #4 0x7f2ea594db2c in ldap_int_sasl_open () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #5 0x7f2ea594e2d4 in ldap_int_sasl_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #6 0x7f2ea5951828 in ldap_sasl_interactive_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #7 0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #8 0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063 #9 0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) at ../../../../servers/slapd/syncrepl.c:618 #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at ../../../../servers/slapd/syncrepl.c:1548 #11 0x7f2ea59463a2 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at pthread_create.c:333 #13 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)): ---Type to continue, or q to quit--- #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e9637a700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
Hi Ryan, what would be the next step? Will you integrate it in the official repo? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Committed Status in openldap package in Ubuntu: In Progress Bug description: I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2e95b79700 (LWP 42141)] 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (gdb) thr apply all bt Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f2e95378700 (LWP 42142)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)): #0 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #1 0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #2 0x7f2ea5303d69 in sasl_client_init () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #3 0x7f2ea594da6c in ldap_int_sasl_init () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #4 0x7f2ea594db2c in ldap_int_sasl_open () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #5 0x7f2ea594e2d4 in ldap_int_sasl_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #6 0x7f2ea5951828 in ldap_sasl_interactive_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #7 0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #8 0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063 #9 0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) at ../../../../servers/slapd/syncrepl.c:618 #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at ../../../../servers/slapd/syncrepl.c:1548 #11 0x7f2ea59463a2 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at pthread_create.c:333 #13 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)): ---Type to continue, or q to quit--- #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e9637a700) at pthread_create.c:333 #3
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
Looks good. I've tested deleting and replicating the databases few times, 20-30 successive service restarts, no issues... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Committed Status in openldap package in Ubuntu: In Progress Bug description: I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2e95b79700 (LWP 42141)] 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (gdb) thr apply all bt Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f2e95378700 (LWP 42142)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)): #0 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #1 0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #2 0x7f2ea5303d69 in sasl_client_init () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #3 0x7f2ea594da6c in ldap_int_sasl_init () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #4 0x7f2ea594db2c in ldap_int_sasl_open () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #5 0x7f2ea594e2d4 in ldap_int_sasl_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #6 0x7f2ea5951828 in ldap_sasl_interactive_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #7 0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #8 0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063 #9 0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) at ../../../../servers/slapd/syncrepl.c:618 #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at ../../../../servers/slapd/syncrepl.c:1548 #11 0x7f2ea59463a2 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at pthread_create.c:333 #13 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)): ---Type to continue, or q to quit--- #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
I meant openldap... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Committed Status in openldap package in Ubuntu: New Bug description: I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2e95b79700 (LWP 42141)] 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (gdb) thr apply all bt Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f2e95378700 (LWP 42142)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)): #0 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #1 0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #2 0x7f2ea5303d69 in sasl_client_init () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #3 0x7f2ea594da6c in ldap_int_sasl_init () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #4 0x7f2ea594db2c in ldap_int_sasl_open () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #5 0x7f2ea594e2d4 in ldap_int_sasl_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #6 0x7f2ea5951828 in ldap_sasl_interactive_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #7 0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #8 0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063 #9 0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) at ../../../../servers/slapd/syncrepl.c:618 #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at ../../../../servers/slapd/syncrepl.c:1548 #11 0x7f2ea59463a2 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at pthread_create.c:333 #13 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)): ---Type to continue, or q to quit--- #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e9637a700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
Hi Ryan, thanks, I'll try to apply the patch by myself. Is libldap the only package to be patched? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Committed Status in openldap package in Ubuntu: New Bug description: I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2e95b79700 (LWP 42141)] 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (gdb) thr apply all bt Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f2e95378700 (LWP 42142)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)): #0 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #1 0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #2 0x7f2ea5303d69 in sasl_client_init () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #3 0x7f2ea594da6c in ldap_int_sasl_init () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #4 0x7f2ea594db2c in ldap_int_sasl_open () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #5 0x7f2ea594e2d4 in ldap_int_sasl_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #6 0x7f2ea5951828 in ldap_sasl_interactive_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #7 0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #8 0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063 #9 0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) at ../../../../servers/slapd/syncrepl.c:618 #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at ../../../../servers/slapd/syncrepl.c:1548 #11 0x7f2ea59463a2 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at pthread_create.c:333 #13 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)): ---Type to continue, or q to quit--- #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e9637a700) at pthread_create.c:333
[Touch-packages] [Bug 1688575] [NEW] Segmentation fault on a slave slapd (sync replication with kerberos authentication)
Public bug reported: I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2e95b79700 (LWP 42141)] 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (gdb) thr apply all bt Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f2e95378700 (LWP 42142)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)): #0 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #1 0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #2 0x7f2ea5303d69 in sasl_client_init () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #3 0x7f2ea594da6c in ldap_int_sasl_init () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #4 0x7f2ea594db2c in ldap_int_sasl_open () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #5 0x7f2ea594e2d4 in ldap_int_sasl_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #6 0x7f2ea5951828 in ldap_sasl_interactive_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #7 0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #8 0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063 #9 0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) at ../../../../servers/slapd/syncrepl.c:618 #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at ../../../../servers/slapd/syncrepl.c:1548 #11 0x7f2ea59463a2 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at pthread_create.c:333 #13 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)): ---Type to continue, or q to quit--- #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e9637a700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f2e96b7b700 (LWP 42139)): #0 0x7f2ea45b2e23 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84 #1 0x561fbc55a8f0 in slapd_daemon_task (ptr=) at ../../../../servers/slapd/daemon.c:2539 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e96b7b700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f2ea5d96740 (LWP 42138)): #0 0x7f2ea487d98d in pthread_join
[Touch-packages] [Bug 921489] Re: Segmentation fault in slapd (related to GSSAPI?)
Hi Ryan, is a new bug really necessary, because the problem from this bug is really similar? apport is not possible but I can provider other reports if necessary. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Strange... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/921489 Title: Segmentation fault in slapd (related to GSSAPI?) Status in openldap package in Ubuntu: Confirmed Bug description: In our installation slapd will crash with a Segmentation Fault about once a week. It has been seen on the producer while the consumers connect but also on both producer and consumers at random. It seems to be related to authentication with GSSAPI. syslog produces the followig message: kernel: [513493.152760] slapd[1610]: segfault at 7fb242df9000 ip 7fb242ad7122 sp 7fb127ffd900 error 4 in libcrypto.so.0.9.8[7fb242a61000+168000] gdb: Core was generated by usr/sbin/slapd -d 0 -h ldap:/// ldaps:/// -f /local/sukat/conf/slapd.conf'. Program terminated with signal 11, Segmentation fault. #0 sha1_block_data_order () at sha1-x86_64.s:133 133 sha1-x86_64.s: No such file or directory. in sha1-x86_64.s (gdb) bt #0 sha1_block_data_order () at sha1-x86_64.s:133 #1 0x005e1700 in ?? () #2 0x1700 in ?? () #3 0x in ?? () The backtrace is incomplete as the debug packages are broken. Trying to reproduce this bug I trigger another segfault. I will file reports on thease issues in separate tickets. ProblemType: Bug Architecture: amd64 Date: Wed Jan 25 11:13:22 2012 Dependencies: adduser 3.112ubuntu1 base-files 5.0.0ubuntu20.10.04.4 base-passwd 3.5.22 coreutils 7.4-2ubuntu3 debconf 1.5.28ubuntu4 debconf-i18n 1.5.28ubuntu4 debianutils 3.2.2 dpkg 1.15.5.6ubuntu4.5 [modified: sbin/start-stop-daemon] findutils 4.4.2-1ubuntu1 gcc-4.4-base 4.4.3-4ubuntu5 libacl1 2.2.49-2 libattr1 1:2.4.44-1 libbz2-1.0 1.0.5-4ubuntu0.2 libc-bin 2.11.1-0ubuntu7.8 libc6 2.11.1-0ubuntu7.8 libcomerr2 1.41.11-1ubuntu2.1 libdb4.7 4.7.25-9 libdb4.8 4.8.24-1ubuntu1 libgcc1 1:4.4.3-4ubuntu5 libgcrypt11 1.4.4-5ubuntu2 libgdbm3 1.8.3-9 libgnutls26 2.8.5-2 libgpg-error0 1.6-1ubuntu2 libgssapi-krb5-2 1.8.1+dfsg-2ubuntu0.10 libk5crypto3 1.8.1+dfsg-2ubuntu0.10 libkeyutils1 1.2-12 libkrb5-3 1.8.1+dfsg-2ubuntu0.10 libkrb5support0 1.8.1+dfsg-2ubuntu0.10 libldap-2.4-2 2.4.21-0ubuntu5.6 liblocale-gettext-perl 1.05-6 libltdl7 2.2.6b-2ubuntu1 libncurses5 5.7+20090803-2ubuntu3 libpam-modules 1.1.1-2ubuntu5.4 libpam0g 1.1.1-2ubuntu5.4 libperl5.10 5.10.1-8ubuntu2.1 libreadline6 6.1-1 libsasl2-2 2.1.23.dfsg1-5ubuntu1 libselinux1 2.0.89-4 libslp1 1.2.1-7.6ubuntu0.1 libstdc++6 4.4.3-4ubuntu5 libtasn1-3 2.4-1 libtext-charwidth-perl 0.04-6 libtext-iconv-perl 1.7-2 libtext-wrapi18n-perl 0.06-7 libwrap0 7.6.q-18 lzma 4.43-14ubuntu2 odbcinst 2.2.11-21 odbcinst1debian1 2.2.11-21 passwd 1:4.1.4.2-1ubuntu2.2 perl 5.10.1-8ubuntu2.1 perl-base 5.10.1-8ubuntu2.1 perl-modules 5.10.1-8ubuntu2.1 psmisc 22.10-1 readline-common 6.1-1 sensible-utils 0.0.1ubuntu3 tzdata 2011n-0ubuntu0.10.04 unixodbc 2.2.11-21 zlib1g 1:1.2.3.3.dfsg-15ubuntu1 DistroRelease: Ubuntu 10.04 NonfreeKernelModules: openafs Package: slapd 2.4.21-0ubuntu5.6 PackageArchitecture: amd64 ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LC_CTYPE=en_GB.UTF-8 ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 SourcePackage: openldap Tags: lucid Uname: Linux 2.6.32-37-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/921489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 921489] Re: Segmentation fault in slapd (related to GSSAPI?)
I have a similar problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault and 100% cpu. slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 Any suggestions or ideas? Br -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/921489 Title: Segmentation fault in slapd (related to GSSAPI?) Status in openldap package in Ubuntu: Confirmed Bug description: In our installation slapd will crash with a Segmentation Fault about once a week. It has been seen on the producer while the consumers connect but also on both producer and consumers at random. It seems to be related to authentication with GSSAPI. syslog produces the followig message: kernel: [513493.152760] slapd[1610]: segfault at 7fb242df9000 ip 7fb242ad7122 sp 7fb127ffd900 error 4 in libcrypto.so.0.9.8[7fb242a61000+168000] gdb: Core was generated by usr/sbin/slapd -d 0 -h ldap:/// ldaps:/// -f /local/sukat/conf/slapd.conf'. Program terminated with signal 11, Segmentation fault. #0 sha1_block_data_order () at sha1-x86_64.s:133 133 sha1-x86_64.s: No such file or directory. in sha1-x86_64.s (gdb) bt #0 sha1_block_data_order () at sha1-x86_64.s:133 #1 0x005e1700 in ?? () #2 0x1700 in ?? () #3 0x in ?? () The backtrace is incomplete as the debug packages are broken. Trying to reproduce this bug I trigger another segfault. I will file reports on thease issues in separate tickets. ProblemType: Bug Architecture: amd64 Date: Wed Jan 25 11:13:22 2012 Dependencies: adduser 3.112ubuntu1 base-files 5.0.0ubuntu20.10.04.4 base-passwd 3.5.22 coreutils 7.4-2ubuntu3 debconf 1.5.28ubuntu4 debconf-i18n 1.5.28ubuntu4 debianutils 3.2.2 dpkg 1.15.5.6ubuntu4.5 [modified: sbin/start-stop-daemon] findutils 4.4.2-1ubuntu1 gcc-4.4-base 4.4.3-4ubuntu5 libacl1 2.2.49-2 libattr1 1:2.4.44-1 libbz2-1.0 1.0.5-4ubuntu0.2 libc-bin 2.11.1-0ubuntu7.8 libc6 2.11.1-0ubuntu7.8 libcomerr2 1.41.11-1ubuntu2.1 libdb4.7 4.7.25-9 libdb4.8 4.8.24-1ubuntu1 libgcc1 1:4.4.3-4ubuntu5 libgcrypt11 1.4.4-5ubuntu2 libgdbm3 1.8.3-9 libgnutls26 2.8.5-2 libgpg-error0 1.6-1ubuntu2 libgssapi-krb5-2 1.8.1+dfsg-2ubuntu0.10 libk5crypto3 1.8.1+dfsg-2ubuntu0.10 libkeyutils1 1.2-12 libkrb5-3 1.8.1+dfsg-2ubuntu0.10 libkrb5support0 1.8.1+dfsg-2ubuntu0.10 libldap-2.4-2 2.4.21-0ubuntu5.6 liblocale-gettext-perl 1.05-6 libltdl7 2.2.6b-2ubuntu1 libncurses5 5.7+20090803-2ubuntu3 libpam-modules 1.1.1-2ubuntu5.4 libpam0g 1.1.1-2ubuntu5.4 libperl5.10 5.10.1-8ubuntu2.1 libreadline6 6.1-1 libsasl2-2 2.1.23.dfsg1-5ubuntu1 libselinux1 2.0.89-4 libslp1 1.2.1-7.6ubuntu0.1 libstdc++6 4.4.3-4ubuntu5 libtasn1-3 2.4-1 libtext-charwidth-perl 0.04-6 libtext-iconv-perl 1.7-2 libtext-wrapi18n-perl 0.06-7 libwrap0 7.6.q-18 lzma 4.43-14ubuntu2 odbcinst 2.2.11-21 odbcinst1debian1 2.2.11-21 passwd 1:4.1.4.2-1ubuntu2.2 perl 5.10.1-8ubuntu2.1 perl-base 5.10.1-8ubuntu2.1 perl-modules 5.10.1-8ubuntu2.1 psmisc 22.10-1 readline-common 6.1-1 sensible-utils 0.0.1ubuntu3 tzdata 2011n-0ubuntu0.10.04 unixodbc 2.2.11-21 zlib1g 1:1.2.3.3.dfsg-15ubuntu1 DistroRelease: Ubuntu 10.04 NonfreeKernelModules: openafs Package: slapd 2.4.21-0ubuntu5.6 PackageArchitecture: amd64 ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LC_CTYPE=en_GB.UTF-8 ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 SourcePackage: openldap Tags: lucid Uname: Linux 2.6.32-37-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/921489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp