*** This bug is a duplicate of bug 941968 ***
https://bugs.launchpad.net/bugs/941968
** This bug has been marked a duplicate of bug 941968
lockfile-create hangs inside lxc containers (potential buffer overflow?)
--
You received this bug notification because you are a member of Ubuntu
Bugs
This bug had me stymied for far too long. When using juju, hostnames
can get quite long. For instance, I have instances with names like
"juju-nick-testopenstack-lhr01-instance-24", and ntp in precise will
just hang on installation and prevent juju from even installing the
charm. This can be a ra
I can confirm this too. I wonder if it's somewhat related to bug 941968
Apparently in our case (we use puppet to provision the server),
/etc/init.d/ntp start gets stuck (maybe because lockfile-create
segfaults?) while the package postinstall script is run, so puppet gets
stuck too while provisioni
I can confirm I too experience this issue with a host name that is
longer than 36 chars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971314
Title:
1:4.2.6.p3+dfsg-1ubuntu3 on Precise generates a me
Some further investigation:
---
Hostname length | Result
---
0-35| ok
36-37 | invalid next size
38-39 | memory corruption
40-47 | invalid next size
>47 | untested
--
Actually, on closer inspection, the error I saw was 'invalid next size',
not 'memory corruption'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971314
Title:
1:4.2.6.p3+dfsg-1ubuntu3 on Precise gene
This bug appears to be linked to hostnames greater than 36 character in
length:
--
root@ip-10-53-101-13:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"
root@ip-10-53-101-13:~# hostname 0123456789012345678901234
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ntp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971314
Title:
1:4.2.6
** Changed in: ntp (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971314
Title:
1:4.2.6.p3+dfsg-1ubuntu3 on Precise generates a memory corruption
To manage n
** Changed in: ntp (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971314
Title:
1:4.2.6.p3+dfsg-1ubuntu3 on Precise generates a memory corruption
To manage
Thank you James for your help and be assured that i will use ubuntu-bug
the next time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971314
Title:
1:4.2.6.p3+dfsg-1ubuntu3 on Precise generates a mem
apport information
** Tags added: apport-collected precise
** Description changed:
ntp, from the package ntp-1:4.2.6.p3+dfsg-1ubuntu3 on Precise with KDE,
generates the following error when restarted on the command line with
the command "sudo service ntp restart"
rapc@rapc-HP-Compaq-
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 971314
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the
13 matches
Mail list logo
