Yes the issue still exists in both Jaunty and Karmic (Alpha 2).
On Sat, Jul 18, 2009 at 5:51 AM, Martin Meredith<mez.ubu...@gmail.com> wrote: > Is this still happening in Jaunty/Karmic? > > ** Changed in: pound (Ubuntu) > Status: New => Incomplete > > -- > Pound unable to start after reboot - Cannot create path for poundctl.socket > https://bugs.launchpad.net/bugs/312336 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “pound” package in Ubuntu: Incomplete > > Bug description: > Binary package hint: pound > > Once configured, Pound was able to start and run successfully post install > but after reboot it fails to start. > > $ tail /var/log/syslog | grep pound > Dec 29 17:01:20 ubuntu pound: Control "/var/run/pound/poundctl.socket" bind: > No such file or directory > > I've confirmed this on 32 and 64bit versions of Intrepid server. > > I've been able to workaround by changing the poundctl control socket location > in pound.cfg > > Control "/var/run/poundctl.socket" > -- Pound unable to start after reboot - Cannot create path for poundctl.socket https://bugs.launchpad.net/bugs/312336 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
