quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: liblockfile (Ubuntu Quantal)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
** No longer affects: lockfile-progs (Ubuntu)
** No longer affects: ntp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/941968
Title:
lockfile-create hangs inside lxc
@Sebastian,
what you are seeing is likely unrelated to this particular bug. However
if I simply do something like:
juju deploy --repository=~/myrepo local:precise/ovs-lxc
lxc-5678901234567890123456789012345678901
and very quickly
juju debug-log
then I see:
LXCError: lxc-start: node name ''
Never mind - simply doing
sudo hostname host567890123456789012345678901234567890
sudo apt-get install lxc
in precise reproduced this, giving me
* Starting NTP server ntpd
*** glibc detected *** lockfile-create: free(): invalid next size
(fast): 0x00d750a0 ***
--
You received this bug
@jamespage,
do you still see this bug?
** Changed in: ntp (Ubuntu)
Status: Expired = Confirmed
** Changed in: ntp (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
Note I get the same thing in a kvm-based cloud instance.
Marking this bug as not affecting lxc.
** No longer affects: lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/941968
I have reproduced this on precise and raring.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/941968
Title:
lockfile-create hangs inside lxc containers (potential buffer
overflow?)
** Also affects: lockfile-progs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/941968
Title:
lockfile-create hangs inside lxc
The problem is with string handling in liblockfile's
lockfile_create_save_tmplock(). I'll start work on getting a debdiff
prepared.
** Also affects: liblockfile (Ubuntu)
Importance: Undecided
Status: New
** Changed in: liblockfile (Ubuntu)
Assignee: (unassigned) = Tyler Hicks
** Changed in: lxc (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/941968
Title:
lockfile-create hangs inside lxc containers (potential
Sebastian,
I'm sorry, could you please give us more specifically the steps you
took? What was that username for - is that the logged-in username on
the host? is the environment the environment name in
.juju/environments.yaml, and service the name of the charm you invoked?
--
You received this
Sure. First, I ssh'd to project64198@deneb, a (metal) server of mine.
There prepared for local deployment:
sudo apt-get install python-software-properties
sudo add-apt-repository ppa:juju/pkgs
sudo apt-get update sudo apt-get install juju
sudo apt-get install lxc apt-cacher-ng libzookeeper-java
I accidentally reproduced this, using:
username project64198
environment democluster
service hbase-master
project64198-democluster-hbase-master-2 has 40 characters. After I
destroyed the environment and recreated under the name demo, everything
was running fine.
--
You received this bug
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ntp (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
Simply running lockfile-create, killing it quickly, and re-running it in
a container doesn't reproduce it for me. Can you please tell me which
juju charm to use to reproduce this? Can you still reproduce this
today?
** Changed in: lxc (Ubuntu)
Status: Confirmed = Incomplete
** Changed
*** This bug is a duplicate of bug 969299 ***
https://bugs.launchpad.net/bugs/969299
If I turn apparmour off, I can no longer effectively install through
juju if the package includes NTP. I'll work to reproduce with a minimal
environment.
--
You received this bug notification because you
*** This bug is a duplicate of bug 969299 ***
https://bugs.launchpad.net/bugs/969299
I'm the same has @breu. the juju charm I was using was making the
hostname of my system 40 characters. Reducing the charm name length
solved the problem. I think this bug should be re-opened and fixed in
I decided not to assign to jjohansen, only subscribe him :)
If noone else gets to the bottom of this before I clear some things off
my plate, I will see if I can get to the bottom of it. I would assign
myself to it, but dont' want to stop someone else from jumping in if
they have time.
--
You
Brue and davidpbritton,
could you please attach the charm you were using?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/941968
Title:
lockfile-create hangs inside lxc containers
*** This bug is a duplicate of bug 969299 ***
https://bugs.launchpad.net/bugs/969299
I played around with this a bit and derived that it is due to the length
of the hostname (at least in my case). With a hostname of length 40 I
can reproduce this error. Setting the hostname to = 37 produces
*** This bug is a duplicate of bug 969299 ***
https://bugs.launchpad.net/bugs/969299
I also do not believe that this bug is a duplicate and apparmor is only
the culprit in that it is finding a potential overflow somewhere in the
ntp code
--
You received this bug notification because you are
*** This bug is a duplicate of bug 925024 ***
https://bugs.launchpad.net/bugs/925024
** This bug has been marked a duplicate of bug 925024
apparmor makes it impossible to install postgresql-common on Precise
--
You received this bug notification because you are a member of Ubuntu
Server
*** This bug is a duplicate of bug 969299 ***
https://bugs.launchpad.net/bugs/969299
** This bug is no longer a duplicate of bug 925024
apparmor makes it impossible to install postgresql-common on Precise
** This bug has been marked a duplicate of bug 969299
apparmor prevents
** Tags added: rls-mgr-p-tracking
--
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/941968
Title:
lockfile-create hangs inside lxc containers
To manage notifications about this bug go
--
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/941968
Title:
lockfile-create hangs inside lxc containers
To manage notifications about this bug go to:
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
--
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/941968
Title:
lockfile-create hangs inside lxc containers
To manage
Thanks for submitting this bug, James.
I tried to reproduce it by simply installing ntp in two containers, but
failed.
However, my hunch is that it is due to bug 925024.
The fix for that bug had been queued in the precise kernel source, but
is not yet (I think) in the archive.
Could you
28 matches
Mail list logo
