[Bug 1386869] Re: -host in auto.master not mounting nfs exports
Is there a reason we can't just go get the patches that Ian Kent already provided for Fedora (see my link to the Red Hat bugzilla entry, which contains references to RPM versions that fix the problem) and apply them here and/or in Debian since the bug exists there as well? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1386869 Title: -host in auto.master not mounting nfs exports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1387459] Re: autofs stops working after upgrade to 14.10
I believe this is a duplicate of Bug #1386869 There's a workaround in the comments of that bug. HTH! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1387459 Title: autofs stops working after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1387459/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1386869] Re: -host in auto.master not mounting nfs exports
This appears to be a bug in the version of autofs that Ubuntu is shipping. See this report from ArchLinux: https://bugs.archlinux.org/task/38379 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1386869 Title: -host in auto.master not mounting nfs exports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1386869] Re: -host in auto.master not mounting nfs exports
Also there's a problem reported in Fedora against 5.0.7, but apparently still present for 5.0.8: https://bugzilla.redhat.com/show_bug.cgi?id=1038356 ** Bug watch added: Red Hat Bugzilla #1038356 https://bugzilla.redhat.com/show_bug.cgi?id=1038356 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1386869 Title: -host in auto.master not mounting nfs exports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 213574] Re: Autofs fails to start with maps from NIS
*** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 Please undo the duplicate status of this bug. This bug still exists in Precise 12.04 and 12.04.1: when I start my system autofs cannot see any maps that are stored in NIS. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/213574 Title: Autofs fails to start with maps from NIS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/213574/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 488696] Re: syntax error in nsswitch config near [ syntax error ]
Steve's comment #18 is not correct. Automount was first created in the late 1980's, and when Sun released the first version of name service switch in the early 1990's, it was already being used to manage automount maps. Automount maps have been considered a standard, basic name service ever since, on every version of UNIX that has ever implemented nsswitch.conf. I think that it's a great idea that autofs be enhanced so that if there's no entry in nsswitch.conf, autofs will not fail but will instead assume files. However, the bug against base-files is NOT invalid. Automount entries DO belong in nsswitch.conf and the standard value is automount: files nis and this should be preserved in Ubuntu. I agree that _ideally_ someone would modify libc to support /etc/nsswitch.d and individual packages (like autofs) could add their own files there containing name service switch configuration. However, until that day comes please add back the automount entry to nsswitch.conf in base-files. The fact that it's not there is a legitimate bug. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/488696 Title: syntax error in nsswitch config near [ syntax error ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/488696/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1040846] [NEW] Missing content in /etc/nsswitch.conf causes failure
Public bug reported: I can't find any package that /etc/nsswitch.conf belongs to, so I'm reporting this issue here since it's related to automount. I use NIS to distribute automount databases, and the autofs5 package. My /etc/auto.master file contains: +auto.master and I can run ypcat -k auto.master and it works fine. However, when I start automount -f -v I get these errors: ~# automount -f -v Starting automounter version 5.0.6, master map /etc/auto.master using kernel protocol version 5.02 syntax error in nsswitch config near [ syntax error ] lookup(file): failed to read included master map auto.master no mounts in table Looking at /etc/nsswitch.conf I see that there is NO entry for automount at all in this file. I added a line like this: automount: files nis and after that, it worked fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: autofs 5.0.6-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Thu Aug 23 15:45:04 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: autofs5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: autofs5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/1040846 Title: Missing content in /etc/nsswitch.conf causes failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1040846/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1040846] Re: Missing content in /etc/nsswitch.conf causes failure
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/1040846 Title: Missing content in /etc/nsswitch.conf causes failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1040846/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 912030] Re: The auto.net script that comes with autofs5 is broken
** Bug watch added: Red Hat Bugzilla #782169 https://bugzilla.redhat.com/show_bug.cgi?id=782169 ** Also affects: autofs5 (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=782169 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/912030 Title: The auto.net script that comes with autofs5 is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/912030/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 111612] Re: The auto.net script that comes with autofs is broken
FYI, just discovered that the fix made here for autofs4 was never applied to autofs5, and the same bug exists there; filed: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/912030 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/111612 Title: The auto.net script that comes with autofs is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/111612/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 912030] [NEW] The auto.net script that comes with autofs5 is broken
Public bug reported: A long time ago I reported a bug in the autofs package: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/111612 That bug was fixed, but now I've discovered that the same bug still exists in the autofs5 package. Please see the above bug for the issue and the fix (I applied the fix by hand to my current system and it did solve the problem). Without this fix, the autofs /net map is simply non-functioning in many common Enterprise environments. ~$ dpkg -S auto.net autofs5: /usr/share/autofs5/conffiles/auto.net ~$ lsb_release -r -d Description:Ubuntu 10.10 Release:10.10 ~$ apt-cache policy autofs5 autofs5: Installed: 5.0.5-0ubuntu2.1 Candidate: 5.0.5-0ubuntu2.1 Version table: *** 5.0.5-0ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ maverick-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.0.5-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages ** Affects: autofs5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/912030 Title: The auto.net script that comes with autofs5 is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/912030/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 691329] [NEW] dnsmasq init file has incorrect DNSMASQ_INTERFACE reference
Public bug reported:
Binary package hint: dnsmasq
Looking at the /etc/init.d/dnsmasq file I see a bug; in the start()
function it says:
${DNSMASQ_INTERFACE:+ $DNSMASQ_INTERFACES} \
This is wrong; the variable names should both be the same. Assuming the
right variable name is DNSMASQ_INTERFACES (plural) for example this
should be:
${DNSMASQ_INTERFACES:+ $DNSMASQ_INTERFACES} \
~$ lsb_release -rd
Description:Ubuntu 10.10
Release:10.10
~$ apt-cache policy dnsmasq
dnsmasq:
Installed: 2.55-1
Candidate: 2.55-1
Version table:
*** 2.55-1 0
500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe amd64
Packages
100 /var/lib/dpkg/status
** Affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in ubuntu.
https://bugs.launchpad.net/bugs/691329
Title:
dnsmasq init file has incorrect DNSMASQ_INTERFACE reference
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 50430] Re: NIS has problems starting before the network comes up
Here's what I use. This works for me in 10.04 (and below) but I haven't
tried it with 10.10 yet.
It sure as heck would be nice if someone paid a little attention to this
bug.
Save this as reautofs, then follow the directions in the comments.
#!/bin/sh
#
# Stupid NetworkManager doesn't wait for NIS to start before starting
# autofs, so we have no maps. Restart it.
#
# Install with:
# sudo cp ~/Downloads/reautofs /etc/init.d
# sudo update-rc.d reautofs defaults 99
#
#
# Author: Paul Smith psm...@gnu.org
start () {
nohup /bin/sh -c '
while true; do
ypwhich break;
sleep 1;
done;
/etc/init.d/autofs restart
' /dev/null /dev/null 21
}
case $1 in
start) start ;;
*) : no op ;;
esac
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 213574] Re: Autofs fails to start with maps from NIS
*** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 Chuck, can you please undo the duplicate status of this bug? This is NOT a duplicate of bug 50430 -- Autofs fails to start with maps from NIS https://bugs.launchpad.net/bugs/213574 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 90681] Re: resolv.conf overwritten using VPN/PPP etc...
I'm not sure why you think retrieving domain info from the DHCP server will do anything to help the problem, which is that the Ubuntu DHCP client is overwriting the resolv.conf file and replacing nameservers that were added due to VPN connections. -- resolv.conf overwritten using VPN/PPP etc... https://bugs.launchpad.net/bugs/90681 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 90681] Re: resolv.conf overwritten using VPN/PPP etc...
Is anyone ever going to do anything about this? I know it's not an easy problem but there are solutions here which will help at least some of the people and which are not harmful (for example, not updating /etc/resolv.conf on RENEW if the old nameserver is still present). If we could do at least that, then we'd solve this problem for a lot of people with little effort and no deleterious effects. Please?? -- resolv.conf overwritten using VPN/PPP etc... https://bugs.launchpad.net/bugs/90681 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 213574] Re: Autofs fails to start with maps from NIS
*** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 On Tue, 2009-10-13 at 18:16 +, Chuck Short wrote: *** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 ** This bug has been marked a duplicate of bug 50430 NIS has problems starting before the network comes up Why has this bug been marked as a duplicate of 50430? 50430 talks about NIS (ypbind) not working properly on NetworkManager enabled systems. That should be fixed for a few releases now, and indeed I haven't seen it on my systems in a while. My suspicion is that the people who are still having trouble are really having problems with NetworkManager not detecting/reporting the network status of their systems properly (saying the network is up when it isn't or vice versa). This bug (213574) is about autofs not working properly on NetworkManager enabled systems. That is basically the same problem, but a completely different package (in fact that's my major complaint about NetworkManager: adding it to your system requires that you go around and hack on each network-aware service on your system, one at a time, to make them compatible with NetworkManager). I've not upgraded to Karmic but I've seen absolutely nothing that leads me to believe anyone has made any effort to enhance autofs, either the daemon itself (a la ypbind) or even just the init scripts, to be NM-aware. Until that happens this bug will not be fixed. What has to happen on a very abstract level is that you can't start autofs until all the services that it utilizes (based on /etc/nsswitch.conf for example) are running, if they are supposed to be started. It's hard because on many systems, /etc/nsswitch.conf lists nis or nisplus as a source for automount, and yet these services are not enabled. On other systems, automount data is taken from LDAP. Other places it comes from flat files. Etc. And remember, by running I don't just mean that the init script has completed. In the brave new world of NetworkManager, having the init script complete does NOT mean that the service is available. It just means that it may _become_ available, sometime later. autofs has to wait until these services are actually active, before it can start. In the old days, with a simple serialized boot process implying that once an init script was complete that service was available, this was simple. Now it's become very tricky indeed. -- Autofs fails to start with maps from NIS https://bugs.launchpad.net/bugs/213574 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 246322] Re: nis package must provide DHCP client scripts
After I filed this I realized there was no facility for updating dhclient.conf via dpkg scripting, so I also filed bug #246343 to have these fields added to the dhclient.conf request line by default. It won't hurt anything to have them requested there: if they're not available from the server then there's no problem; if they are available and the nis package is not installed (which it is not by default!) then no difference. As for extra complications, I don't know that I agree. The NTP package, for example, doesn't require extra setup to turn on this feature. The scripts are added to the dhclient exit hooks on package install without any confirmation from the user. We don't ask them whether they'd like to allow their DNS servers to be overridden or not. Like NTP, NIS is not installed by default: the user must explicitly install it. I honestly can't think of any reason why someone would NOT want to use the nis-domain and nis-server settings that are provided to them from their DHCP server. The only time a DHCP server would be configured to provide that information, after all, was if the admin knew it was needed. NIS is NOT something you find in your everyday internet cafe etc. I can see why this might be problematic based on the fact that it's potentially a change in behavior, but that's what Intrepid is for right? Many, many other behaviors are changed without warning on every release if Ubuntu. My opinion is that the default on package install should be to automatically accept DHCP settings, and if users want to disable this they can either (a) edit dhclient.conf and turn off the request entry, or (b) there can be some other facility via /etc/defaults or whatever that the NIS dhclient exit hooks look at to disable it. Note that the hook script would of course be written to preserve the existing /etc/yp.conf file (traditionally it would be renamed to /etc/yp.conf.dhcp) when obtaining a lease and put it back when releasing the lease, so we only override explicit user settings for the duration of the DHCP client connection, then they are put back. I'll point out that the enabled by default behavior is how other distros do this. -- nis package must provide DHCP client scripts https://bugs.launchpad.net/bugs/246322 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 90681] Re: resolv.conf overwritten using VPN/PPP etc...
I hit this too; my company uses Juniper's NetworkConnect and it adds its own DNS servers as the first ones to search to /etc/resolv.conf. I disabled the download of the DNS server info altogether which is obviously not optimal, but works OK for me because I've installed a Linux image on my Linksys router and enabled dnsmasq, so my local LAN DNS server is always my router, which never changes, not my upstream ISP. But, when I configured a laptop for a friend they have this problem in spades. To me, anything that watches for changes to /etc/resolv.conf and tries to change things back again is just not reliable enough. Ditto for having scripts depending on seeing a tun0 or ppp0 or whatever interface. I think the right answer HAS to be a smarter dhclient script. It's the only one that seems reliable and robust. An easy answer that will help most of the time was already suggested: if the hostname to be added to resolv.conf already exists, then don't change resolv.conf. This seems like something that is obviously correct and won't cause any problems. This works for me because my VPN solution leaves the original nameserver entry in /etc/resolv.conf, it's just put at the bottom. I suppose some people might have problems if their VPN solution completely replaces /etc/resolv.conf. That might require a more sophisticated solution. -- resolv.conf overwritten using VPN/PPP etc... https://bugs.launchpad.net/bugs/90681 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 215904] Re: [SRU] (ITS#5518) Assertion error in io.c:234: ber_flush2
The bug is in the libldap package. When you get a new version of that (which I believe is out now, even for the standard repositories) then all applications that use LDAP (including Evolution, xscreensaver, Apache, etc.) will use it and have the fix. There's no need for a new Apache package, because there's been no ABI change and so no need to rebuild Apache. It's the miracle of shared libraries!! :-) -- [SRU] (ITS#5518) Assertion error in io.c:234: ber_flush2 https://bugs.launchpad.net/bugs/215904 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 215904] Re: [SRU] (ITS#5518) Assertion error in io.c:234: ber_flush2
This is still in -proposed? I think it's pretty clear what this bug is and that it's fixed by the update; we've had a number of people testing it and reporting success already. Plus, if you look at the actual patch, it's pretty clear that it fixes the problem. IMHO this should get promoted out of -proposed and into the standard repo quickly. This is a crasher that impacts a wide range of software. What exactly is the criteria needed to approve the the promote? Maybe we need to figure out a way that this bug is really a security issue :-). Thanks! -- [SRU] (ITS#5518) Assertion error in io.c:234: ber_flush2 https://bugs.launchpad.net/bugs/215904 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 215904] Re: [SRU] (ITS#5518) Assertion error in io.c:234: ber_flush2
Sorry, I didn't realize people were waiting for me. I have no recipe for reliably reproducing the problem using Evolution so I can't be 100% sure that it's been fixed. However, I've been using the fix since Chuck posted his PPA version on 23 May, and -proposed version since it was uploaded, and I've never had this crash happen since. So, insofar as I can be, I'm sure this bug is crushed. Cheers! -- [SRU] (ITS#5518) Assertion error in io.c:234: ber_flush2 https://bugs.launchpad.net/bugs/215904 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 215904] Re: (ITS#5518) Assertion error in io.c:234: ber_flush2
I've loaded up these libraries to test the Evo Exchange crasher. Unfortunately there was no reliable way to reproduce it; you just had to do lots of work and eventually it would happen. However, I've added a debugging message to the code so that I'll know when I've hit a point where it SHOULD have happened, so I can see if it proceeds correctly in that situation or not. Also unfortunately my company is moving to a new building this weekend so the Exchange server is down at the moment (but should be up later tonight). -- (ITS#5518) Assertion error in io.c:234: ber_flush2 https://bugs.launchpad.net/bugs/215904 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 215904] Re: (ITS#5518) Assertion error in io.c:234: ber_flush2
I found this bug, I think. We're getting identical problems causing Evolution Exchange to crash. The problem is ldap is accessing memory after it's been freed. Here's the Gnome bug with lots of backtraces and some valgrind logs I used to figure it out: http://bugzilla.gnome.org/show_bug.cgi?id=512605 and here's the new bug I filed with openldap describing the issue: http://www.openldap.org/its/index.cgi/Incoming?id=5525;page=1;statetype=1 -- (ITS#5518) Assertion error in io.c:234: ber_flush2 https://bugs.launchpad.net/bugs/215904 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 231898] Re: evolution-exchange-storage SIGABRT
*** This bug is a duplicate of bug 215904 *** https://bugs.launchpad.net/bugs/215904 This is really a bug in openldap which is causing lots of ldap-based apps to fail. There is more info in ubuntu bug #215904 ** This bug has been marked a duplicate of bug 215904 (ITS#5518) Assertion error in io.c:234: ber_flush2 -- evolution-exchange-storage SIGABRT https://bugs.launchpad.net/bugs/231898 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu (via bug 215904). -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 215904] Re: (ITS#5518) Assertion error in io.c:234: ber_flush2
Marked Evolution Exchange bug as a duplicate. -- (ITS#5518) Assertion error in io.c:234: ber_flush2 https://bugs.launchpad.net/bugs/215904 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
