This bug was fixed in the package keepalived - 1:1.2.24-1ubuntu0.16.04.1~cloud0
---
keepalived (1:1.2.24-1ubuntu0.16.04.1~cloud0) trusty-mitaka; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
keepalived (1:1.2.24-1ubuntu0.16.04.1) xenial; urgency=medium
The verification of the Stable Release Update for keepalived has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update s
The verification of the Stable Release Update for keepalived has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update s
This bug was fixed in the package keepalived - 1:1.2.24-1ubuntu0.16.04.1~cloud0
---
keepalived (1:1.2.24-1ubuntu0.16.04.1~cloud0) trusty-mitaka; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
keepalived (1:1.2.24-1ubuntu0.16.04.1) xenial; urgency=medium
The verification of the Stable Release Update for keepalived has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update s
This bug was fixed in the package keepalived - 1:1.3.9-1ubuntu0.18.04.1~cloud0
---
keepalived (1:1.3.9-1ubuntu0.18.04.1~cloud0) xenial-queens; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
keepalived (1:1.3.9-1ubuntu0.18.04.1) bionic; urgency=medium
.
* d/p/f
I believe that since you changed the location of the config file,
changing the systemd service file is just a continuation of your local
configuration. Simon's tip in comment #1 was spot on, as was your
investigation of the config setting that needed changing.
Regarding the regression aspect of th
Thanks for the update, Chris. Larry, does this update help your case as
well?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1783343
Title:
package sa-compile 3.4.1-8build1 failed t
I believe your problem could be related to bug #1731502, which happens
when there is no network up and running yet by the time samba starts. It
only waits so long. The usual case is a desktop machine or laptop that
only connects to the network after a user logs in, like a wifi network.
Is that your
** Changed in: openldap (Ubuntu)
Status: In Progress => Incomplete
** Changed in: openldap (Ubuntu)
Assignee: Howard Chu (hyc) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpa
marking as fix released in the devel task, since the fix is in cosmic.
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Released
** Changed in: openssh (Ubuntu)
Assignee: Karl (kstenerud) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
** Changed in: openssh (Ubuntu Xenial)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1771340
Title:
sshd failed on config reload
To manage notifications ab
*** This bug is a duplicate of bug 1731502 ***
https://bugs.launchpad.net/bugs/1731502
Ok, thanks for getting back to us. I'll mark this as a duplicate of that
bug then.
** This bug has been marked a duplicate of bug 1731502
nmbd starts fine with no interfaces, but doesn't notify systemd t
13 matches
Mail list logo
