Upstream bug referenced here is about cache storage failures during startup/reconfigure. Which seems a bit at odds with resolv.conf loading errors, although it may be a secondary bug result of the resolv.conf reconfigure action being successfully triggered very early after startup.
A stack trace is required to identify and confirm the code path leading to this crash. To be compared with the traces already available upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988802 Title: squid3 killed by ABRT signal. assertion failed: disk.cc377: "fd >= 0" To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/988802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
