This happened because your i386 version of the library and your amd64
version of the library are out of sync. I don't know why you have both
installed, but if you can uninstall one that you don't need, that can
help. Chances are good your mirror will be updated Soon Enough, and re-
running apt-get
Upstream Bug:
https://github.com/lxc/lxc/issues/340
Seems patches are floating around, no movement for a bit.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1339781
Title:
centos 7 nee
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1413028
Title:
package libnss3 2:3.17.1-0ubuntu0.14.04.2 failed to install/upgrade:
trying to over
Public bug reported:
Not sure what happened
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libnss3 2:3.17.1-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date:
The fix is in lxc git HEAD. It should show up in lxc 1.1 soon.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/140942
** Changed in: cinder
Milestone: kilo-2 => None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1313935
Title:
tenant is required for quota-update but not for quota-show
To manage
I would like to get an answer, whether to wait for new product versions
in Ubuntu 15.04 and which versions?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1411811
Title:
Please up
Peter,
I have created one PPA to be tested:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1412962
# add-apt-repository ppa:inaddy/lp1412962
# apt-get update
# apt-get install pacemaker
The right package version, for now, will be:
1.1.10+git20130802-1ubuntu2.3~lp1412962~1 (for Trusty)
And th
We are also seeing the problem with mailman. I would appreciate it if
someone could provide a workaround. Or perhaps a hint of where to look
for the code that needs fixing.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ub
Public bug reported:
It was brought to my attention that pacemaker could seg fault (stonith) on some
conditions. This problem
was brought to me when solving the following bug:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/
So you can check the problem here:
https://bugs.laun
** Attachment added: "Crash file (with core dump) used to analyze the problem"
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1412962/+attachment/4302557/+files/_usr_lib_pacemaker_stonithd.0.crash
** Changed in: pacemaker (Ubuntu)
Status: New => In Progress
--
You received t
Hello bugproxy, or anyone else affected,
Accepted librtas into utopic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/librtas/1.3.13-1~14.10
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Peter,
Since the bug you are reporting is related to "stonith", I'm separating
two cases:
LP: #1368737 -- Pacemaker (lrmd) can seg fault in Trusty and Utopic
after following message: Source ID XX was not found when attempting to
remove
And
LP: #1412962 -- Pacemaker (stonith) can seg fault in Tr
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1412887
Title:
unable to start lxc on ubuntu
To manage notifications about this bug go to:
https://bugs.laun
I just found one upstream commit fixing this:
##
commit 0326f05c9e26f39a394fa30830e31a76306f49c7
Author: Andrew Beekhof
Date: Thu Aug 7 13:49:24 2014 +1000
Fix: stonith-ng: Reset mainloop source IDs after removing them
diff --git a/lib/fencing/st_client.c b/lib/fencing/st_cli
Okay,
So the cherry-pick (for version
trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2, based on a upstream
commit) seems ok since it makes lrmd (services, services_linux) to avoid
repeating a timer when the source was already removed from glib main
loop context:
example:
+ if (op->opaque->rep
** Changed in: juju-core
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated /home/ub
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apr in Ubuntu.
https://bugs.launchpad.net/bugs/1412927
Title:
package libapr1:amd64 1.5.0-1 failed to install/upgrade: package
libapr1:amd64 is a
Bug may not be in the kernel package, but it seems very unlikely to be
in cgmanager, and more clueful people are likely to see it this way.
** Package changed: cgmanager (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notificati
Public bug reported:
problem
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libapr1:amd64 1.5.0-1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
AptdaemonVersion: 1.1.1-1ubuntu5.1
Architecture: amd6
Where did you get the custom kernel?
How exactly are you starting the container? What do you see when you
run
sudo lxc-checkconfig
? Please run 'lxc-start -n containername -l trace -o debug.out' and
attach 'debug.out'.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: Ne
I've had no problems with the 3.16 low latency kernel. From what I can
see I am not missing any required kernel config options, but can you
recommend a good source to describe exactly which kernel options are
required? Many thanks.
--
You received this bug notification because you are a member
Public bug reported:
The Debian packaging of Samba demoted the Recommends relationships to
libpam-winbind and libnss-winbind to Suggests after one Debian release:
samba (2:3.6.15-1) unstable; urgency=high
* Team upload.
* New upstream bugfix release. Closes: #707042
* Update VCS URL's for
USE THE COMMAND: "service freeradius stop". I looked through several
forums searching for how to kill freeradius on ubuntu. how to stop
freeradius. how to turn off freeradius. All because I was getting an
error that said freeradius port 1812 was in use. Spent a few hours
searching and found nothing
Hello bugproxy, or anyone else affected,
Accepted librtas into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/librtas/1.3.13-1~14.04
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
** Description changed:
Hi,
I've installed lxc on lubuntu utopic with a 3.18.3 lowlatency kernel,
and I can't get lxc to start. I'm getting the following errors in a
logfile:
lxc-start 1421773029.483 ERRORlxc_conf - conf.c:instanciate_veth:2817 -
failed to attach 'vethJCKW6M'
Public bug reported:
Hi,
I've installed lxc on lubuntu utopic with a 3.18.3 lowlatency kernel,
and I can't get lxc to start. I'm getting the following errors in a
logfile:
lxc-start 1421773029.483 ERRORlxc_conf - conf.c:instanciate_veth:2817 -
failed to attach 'vethJCKW6M' to the bridge 'l
Public bug reported:
The metadata server listens on 169.254.269.254 but not on any ipv6
address. Thus v6-only machines must be configured with a config-drive.
(There is no v6 address assigned to metadata, but it could easily listen
on the v4-in-v6 address ::169.254.169.254 in the same way.)
**
** Changed in: spamassassin (Ubuntu)
Assignee: (unassigned) => Kick In (kick-d)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1412830
Title:
[AHBL] spamassassin is returning fals
15:37 ScottK: can I have an opinion from you on bug 1412830 please?
sa-update or SRU?
15:37 bug 1412830 in spamassassin (Ubuntu) "[AHBL] spamassassin is
returning false positives by default" [Critical,Confirmed]
https://launchpad.net/bugs/1412830
15:37 Looking
15:38 rbasak: sa-update is disa
I believe that sa-update will update the rules correctly in
/var/lib/spamassassin, so after running this users should not be getting
a false positive. Please could someone confirm?
If this is true, I'm not sure whether the right thing to do is an SRU to
disable it for users who don't run sa-update
You have been subscribed to a public bug by Robie Basak (racb):
AHBL has discontinued their operations and is deliberetly marking all
checks as positive:
http://www.ahbl.org/content/last-notice-wildcarding-services-jan-1st
AHBL is enabled by default in SpamAssassin in at least 10.04, 12.04 and
1
** Changed in: nginx (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1194074
Title:
Default index.html blindly overwritten
To manage no
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: spamassassin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.n
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1412831
Title:
crm_mon crashed with SIGABRT in g_return_if_fail_warning()
To man
Public bug reported:
AHBL has discontinued their operations and is deliberetly marking all
checks as positive:
http://www.ahbl.org/content/last-notice-wildcarding-services-jan-1st
AHBL is enabled by default in SpamAssassin in at least 10.04, 12.04 and
14.04. This means that every mail gets 2 poi
This bug has been fixed on Vivid and I nominated it to be backported on
Trusty.
** Changed in: python-urllib3 (Ubuntu)
Status: New => Fix Released
** Changed in: python-urllib3 (Ubuntu Trusty)
Status: New => Triaged
--
You received this bug notification because you are a member of
** Also affects: python-urllib3 (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-urllib3 in Ubuntu.
https://bugs.launchpad.net/bugs/1412545
Title:
proxy isn't used aft
** Bug watch added: Debian Bug tracker #774464
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774464
** Also affects: nginx (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774464
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Hi Adam- Is this SRU appropriate to target for the 14.04.2 milestone?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1387594
Title:
init: symbol lookup error: /lib/powerpc64le-l
--- Comment From vsand...@in.ibm.com 2015-01-20 10:51 EDT---
*** Bug 120596 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.ne
I think we can close this now - juju status --format accepts a number of
new output formats (in addition to the default "yaml" and optional
"json"). Excerpt from juju status --help:
There are a number of ways to format the status output:
- {short|line|oneline}: List units and their subordinates.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi trialotto,
On 20/01/15 02:15, trialotto wrote:
> The documentation looks great.
Thanks!
> However, can you add the following (important) remarks to the
> documentation page:
>
> a) as from cloud-init 0.7.6, the option exists to create swap by
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Steve,
On 19/01/15 20:18, Stephen A. Zarkos wrote:
> In case customers are not familiar with the term "Custom Data" or
> how to use it, I would recommend linking to our documentation:
> http://azure.microsoft.com/en-us/documentation/articles/virtu
And here is the last core dump of my production system from today in the
morning, also core included.
** Attachment added: "_usr_lib_pacemaker_stonithd.0.crash"
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4302102/+files/_usr_lib_pacemaker_stonithd.0.crash
--
And this is the current cluster configuration of the testing
environment.
** Attachment added: "cib"
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4302101/+files/cib
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Here is the crash file from my virtual testing environment, including
core. I updated the nodes today with all current packages from trusty-
proposed. The core dump happened just after restarting the nodes after
the updates.
** Attachment added: "_usr_lib_pacemaker_stonithd.0.crash"
https://bu
47 matches
Mail list logo
