Still getting:
dovecot: 2009-07-08 16:28:07 Error: auth-worker(default): malloc: 197212:
Cannot allocate memory
dovecot: 2009-07-08 16:28:07 Error: auth-worker(default): Unable to allocate
memory for mutexes from the region
dovecot: 2009-07-08 16:28:07 Error: auth-worker(default): PANIC: Cannot
free -m
total used free sharedbuffers cached
Mem: 3650 2987663 0108 1587
-/+ buffers/cache: 1292 2358
Swap: 1172 8 1163
--
auth-worker(default): malloc: 197212: Cannot allocate me
Public bug reported:
Dovecot auth-worker crashes with the following, happens a couple of
times a day, the auth-worker automatically restarts when you are forced
to log back in.
Description:Ubuntu 9.04
Release:9.04
dovecot-common:
Installed: 1:1.1.11-0ubuntu4
Candidate: 1:1.1.11-0
I have just upgraded to:
slapd and libldap-2.4.2 to version 2.4.15-1ubuntu1
libsasl2-2, libsasl2-2-modules and libsasl2-2-modules-gssapi-mit to version
2.1.22.dfsg1-23ubuntu3
And slapd is no longer crashing. There has been no change in config,
just the upgrade.
** Changed in: openldap (Ubunt
** Changed in: openldap (Ubuntu)
Status: New => Confirmed
--
SASL/GSSAPI problem in OpenLDAP
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.
--
Ubuntu-server-bugs mailing
Phew someone else is experiencing the same problem, I thought that I was
going mad!
--
SASL/GSSAPI problem in OpenLDAP
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.
--
Ubuntu-s
Once slapd logs this error it then crashes and you have to restart slapd
--
SASL/GSSAPI problem in OpenLDAP
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.
--
Ubuntu-server-bugs
oot,cn=djdvant.com,cn=gssapi,cn=auth to a DN
Feb 27 07:14:49 virt-kim-jaunty slapd[4702]: slap_parseURI: parsing
uid=root,ou=people,dc=djdvant,dc=com
Feb 27 07:14:49 virt-kim-jaunty slapd[4702]: >>> dnNormalize:
Feb 27 07:14:49 virt-kim-jaunty slapd[4702]: <<< dnNormalize:
I commented out the [printers] and [print$] statements and smb starts,
but when I run smbtree, the following error is displayed: Receiving
SMB: Server stopped responding
And the logfile:
[2009/02/20 19:29:03, 0] lib/fault.c:fault_report(40)
Confirmed I have the same bug
smbd version 3.3.0 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
===
INTERNAL ERROR: Signal 11 in pid 27822 (3.3.0)
Please read the Trouble-Shooting section of the Samba3-HOWTO
From: http:/
I have also taken a working Intrepid virtual machine and dist-upgraded
to Jaunty. Once upgraded OpenLDAP crashes when trying to use GSSAPI
method to access the DB.
--
SASL/GSSAPI problem in OpenLDAP
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a membe
I also have a third virtual machine, running Jaunty and using it as an
LDAP/Kerberos client with the latest version of SASL and GSSAPI modules
without any problem.
--
SASL/GSSAPI problem in OpenLDAP
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a member
I have downgraded these packages to the Intrepid version:
slapd (2.4.11-0ubuntu6.1), libldap (2.4.11-0ubuntu6.1), libsasl2-2
(2.1.22.dfsg1-21ubuntu2), libsasl2-modules (2.1.22.dfsg1-21ubuntu2)
And now I can login using Kerberos and LDAP
** Summary changed:
- SASL/GSSAPI ldap_sasl_interactive_b
And the ldap and krb5 config files are the same, except for host names.
--
SASL/GSSAPI ldap_sasl_interactive_bind_s Can't contact LDAP Server
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap i
Jaunty Packages shows which version of debs are installed.
Testing Log shows the tests that I performed on each Ubuntu version
Debug Log is just that
--
SASL/GSSAPI ldap_sasl_interactive_bind_s Can't contact LDAP Server
https://bugs.launchpad.net/bugs/328436
You received this bug notification b
** Attachment added: "Intrepid Debug Log"
http://launchpadlibrarian.net/22546124/IntrepidDebugLog.txt
--
SASL/GSSAPI ldap_sasl_interactive_bind_s Can't contact LDAP Server
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a member of Ubuntu
Server Team,
** Attachment added: "Jaunty Debug Log"
http://launchpadlibrarian.net/22546094/JuntyDebugLog.txt
--
SASL/GSSAPI ldap_sasl_interactive_bind_s Can't contact LDAP Server
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a member of Ubuntu
Server Team, whic
** Attachment added: "Intrepid Testing Log"
http://launchpadlibrarian.net/22546072/IntrepidTesting.txt
--
SASL/GSSAPI ldap_sasl_interactive_bind_s Can't contact LDAP Server
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a member of Ubuntu
Server Team
** Attachment added: "Jaunty Testing Log"
http://launchpadlibrarian.net/22546060/JauntyTesting.txt
--
SASL/GSSAPI ldap_sasl_interactive_bind_s Can't contact LDAP Server
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a member of Ubuntu
Server Team, wh
** Attachment added: "Jaunty Packages"
http://launchpadlibrarian.net/22546043/JauntyPackages.txt
--
SASL/GSSAPI ldap_sasl_interactive_bind_s Can't contact LDAP Server
https://bugs.launchpad.net/bugs/328436
You received this bug notification because you are a member of Ubuntu
Server Team, whic
Public bug reported:
Bug Description: OpenLDAP, Kerberos5 are installed, but when trying to
use, for eg, ldapwhoami, openldap reports: ldap_sasl_interactive_bind_s:
Can't contact LDAP Server
I have built two virtual machines, one running Intrepid amd64 and one with
Jaunty amd64.
Description:
21 matches
Mail list logo
