[Bug 312336] Re: Pound unable to start after reboot - Cannot create path for poundctl.socket
I confirm this bug on Oneiric server, 64 bit. The patch above helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/312336 Title: Pound unable to start after reboot - Cannot create path for poundctl.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pound/+bug/312336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312336] Re: Pound unable to start after reboot - Cannot create path for poundctl.socket
Still happens on Oneiric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/312336 Title: Pound unable to start after reboot - Cannot create path for poundctl.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pound/+bug/312336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312336] Re: Pound unable to start after reboot - Cannot create path for poundctl.socket
This just affected me on Ubuntu 10.04. I worked around it by running mkdir /var/run/pound. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/312336 Title: Pound unable to start after reboot - Cannot create path for poundctl.socket -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312336] Re: Pound unable to start after reboot - Cannot create path for poundctl.socket
** Changed in: pound (Ubuntu) Status: Incomplete = Fix Released -- 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
[Bug 312336] Re: Pound unable to start after reboot - Cannot create path for poundctl.socket
I can confirm this is still happening in Karmic (9.10 64-bit). -- 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
[Bug 312336] Re: Pound unable to start after reboot - Cannot create path for poundctl.socket
Yes, I can also confirm it is still happening on Karmic as well. I have personally fixed it by applying the attached patch on the init script /etc/init.d/pound ** Attachment added: Patch for /etc/init.d/pound . Makes sure the directory /var/run/pound exists before starting the pound daemon. http://launchpadlibrarian.net/36472333/pound.patch -- 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
[Bug 312336] Re: Pound unable to start after reboot - Cannot create path for poundctl.socket
It's still happening in current Jaunty. The problem is that while the deb package creates the /var/run/pound directory on install, /var/run is a tmpfs ramdisk so the pound directory disappears on restart. The best solution would probably be to have the init script create the directory on startup if it doesn't already exist. -- 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
Re: [Bug 312336] Re: Pound unable to start after reboot - Cannot create path for poundctl.socket
Yes the issue still exists in both Jaunty and Karmic (Alpha 2). On Sat, Jul 18, 2009 at 5:51 AM, Martin Meredithmez.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
[Bug 312336] Re: Pound unable to start after reboot - Cannot create path for poundctl.socket
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 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
