** Changed in: keepalived (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644530
Title:
keepalived fails to restart cleanly due to the wrong systemd
** Description changed:
Because "PIDFile=" directive is missing in the systemd unit file,
keepalived sometimes fails to kill all old processes. The old processes
remain with old settings and cause unexpected behaviors. The detail of
this bug is described in this ticket in upstream:
https
I've provided the minimal reproducible example in Bug Description (sorry
for this late). Can you confirm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644530
Title:
keepalived fails to restart cle
Hi,
As I have pointed above, this problem is NOT solved! Even the newest
version of keepalived package (1.3.2) still lacks "PIDFile=" directive.
$ wget http://launchpadlibrarian.net/296728051/keepalived_1.3.2-1_amd64.deb
$ dpkg-deb --extract keepalived_1.3.2-1_amd64.deb keepalived
$ cat keepalive
** Description changed:
Because "PIDFile=" directive is missing in the systemd unit file,
keepalived sometimes fails to kill all old processes. The old processes
remain with old settings and cause unexpected behaviors. The detail of
this bug is described in this ticket in upstream:
https
Thank you for your comment!
> 1.2.24 is already in the coming Ubuntu relase, so that is fixed
there.
I'm afraid not. The issue still exists since the upstream continues to
use their own systemd unit file. I've created the same patch to the very
upstream:
https://github.com/formorer/pkg-keepaliv
Sorry, I repost my patch.
** Patch removed: "add PIDFile= directive in systemd unit file"
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1644530/+attachment/4782407/+files/fix-systemd-unit.patch
** Patch added: "add PIDFile= directive in systemd unit file"
https://bugs.launchpa
** Patch added: "fix-iscsid-startup.patch"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1640422/+attachment/4782415/+files/fix-iscsid-startup.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
This patch should fix the issue.
** Patch added: "add PIDFile= directive in systemd unit file"
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1644530/+attachment/4782407/+files/fix-systemd-unit.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
Because "PIDFile=" directive is missing in the systemd unit file,
keepalived sometimes fails to kill all old processes. The old processes
remain with old settings and cause unexpected behaviors. The detail of
this bug is described in this ticket in upstream:
https://github.com
Public bug reported:
iscsid automatically starts when an iscsi tool needs to access it. But
after the iscsid process started up with the default setting in
/etc/iscsid.conf, commands to control iscsid via systemd will fail since
the process is NOT under control of iscsid.service. The default is th
Thanks!
I've confirmed the problem is now fixed in trusty-proposed. The result
is below.
$ sudo apt-get install nsd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
nsd
0 upgraded, 1 newly installed, 0 to remo
Just in case when the upstream fix won't come down to trusty so quickly,
I resubmit this patch.
** Patch added: "Use upstream patch for Debian bug #743396"
https://bugs.launchpad.net/ubuntu/+source/nsd/+bug/1311886/+attachment/4269550/+files/move-debhelper-tag-at-end.patch
--
You received th
Sorry, I removed my patch.
As Hirotaka pointed out, the upstream fix seems what we want. Perfect.
** Patch removed: "Start nsd after setup is done"
https://bugs.launchpad.net/ubuntu/+source/nsd/+bug/1311886/+attachment/4269535/+files/fix-postinst-order.patch
** Tags removed: patch
--
You re
I create the "easy-fix" patch, which rado_p suggested.
The step "2. dpkg attempts to start the daemon." is automatically inserted into
the line with the word "#DEBHELPER#" by debhelper.
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/nsd/trusty-proposed/view/head:/debian/nsd.postinst#L
** Patch added: "udev-finish-rundir.patch"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1093731/+attachment/3467924/+files/udev-finish-rundir.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Description changed:
- I removed /etc/udev/rules.d/70-persistent-net.rules and rebooted the machine
in order to generate a new rules file, but couldn't get a complete
70-persistent-net.rules. A rule about eth0 was written in
/run/udev/tmp--70-persitent-net.rules and didn't merged onto
/etc/
Public bug reported:
I removed /etc/udev/rules.d/70-persistent-net.rules and rebooted the machine in
order to generate a new rules file, but couldn't get a complete
70-persistent-net.rules. A rule about eth0 was written in
/run/udev/tmp--70-persitent-net.rules and didn't merged onto
/etc/udev/
Currently installed VMWare with several Linux operating systems.
I came to the conclusion that the hub is causing all the problems with
the handshake. So this means you can have all the leafbots on the same
computer and the same operating system but the hubbot needs to be
somewhere else. For examp
I'm gonna try and install several virtual pcs and try getting it to run
from there. Will update on how it goes.
--
*** stack smashing detected ***: ./eggdrop terminated
https://bugs.launchpad.net/bugs/220327
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Would it help to have all the leafbots on one virtual machine and the
hubbot on another? Would this avoid the stack smashing?
--
*** stack smashing detected ***: ./eggdrop terminated
https://bugs.launchpad.net/bugs/220327
You received this bug notification because you are a member of Ubuntu
Bugs,
Problem is I've got about 4 or 5 bots all running on the same pc.
Normally this would be no problem but to virtualize all bots would mean
I need to install 4 or 5 virtual pc's running all linux... To keep this
all running would be one hell of a task. Isn't there another way I could
fix this?
--
*
Yes, I'm trying to run two eggdrop's at the same time on the same pc
with a botnet between the two bots. At first all goes well but after a
while the bot crashes unexpected.
--
*** stack smashing detected ***: ./eggdrop terminated
https://bugs.launchpad.net/bugs/220327
You received this bug notif
I've also experienced this behavior by my eggdrop installation. Using
Ubuntu 9.04 amd64.
--
*** stack smashing detected ***: ./eggdrop terminated
https://bugs.launchpad.net/bugs/220327
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
24 matches
Mail list logo
