Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This is the sort of thing that would be best fixed upstream - it's
probably best not to make distro-specific changes in this area. Have you
considered testing for this problem in the original upstream release and
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please can you arrange to get us a full backtrace, including debugging
symbols? Instructions at:
https://help.ubuntu.com/community/ReportingBugs#Reporting_an_application_crash
Once done, please change the bug
Note: clamav does appear to have debug symbol ddebs at ddebs.ubuntu.com.
** Changed in: clamav (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
keepalived is already packaged, but I can see that upstream version
1.2.7 is available. Ubuntu and Debian have 1.2.2; 1.2.6 is available in
experimental.
Please specify which upstream release you are requesting,
*** This bug is a duplicate of bug 1182552 ***
https://bugs.launchpad.net/bugs/1182552
Thanks for posting the stacktrace, but this trace does not contain
symbolic information. Did you have the clamav ddebs installed at the
time you generated the stacktrace? See
** Changed in: maas (Ubuntu)
Status: New = Triaged
** Changed in: maas (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1182980
Title:
** Changed in: maas (Ubuntu)
Status: New = Triaged
** Changed in: maas (Ubuntu)
Importance: Undecided = Medium
** Changed in: maas (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas
** Changed in: cinder (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1182689
Title:
cinder needs a hard version requirement on
** Changed in: maas (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1182459
Title:
clean up root.tar.gz and fast path installer files
To
** Changed in: maas (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1181265
Title:
acquire followed quickly by start may not start system
To
** Changed in: maas (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1181334
Title:
i386 required to install amd64
To manage notifications
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Changed in: juju (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1175958
Title:
New peer relations not created when upgrading charms
To
** Changed in: maas (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1172336
Title:
MAAS server reference to AvahiBoot wiki page that does not
** Changed in: maas (Ubuntu)
Importance: Undecided = Medium
** Summary changed:
- Package install hangs if LC_ALL is not set
+ Package install hangs if LC_ALL set to a locale that is not configured
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: maas-enlist (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/1131296
Title:
maas-enlist uses a wrong url when enlisting
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I have reproduced the behaviour you describe on 5.4.9-4ubuntu2.
According to the documentation, the salt provided for Blowfish must be:
22 characters from the alphabet ./0-9A-Za-z
See:
Debian/Ubuntu may use a different implementation perhaps, such as the
system one. But what you have is a question rather than a bug - perhaps
try askubuntu.com?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
The facter merge I prepared in bug 1173265 appears to fix this. Just
awaiting sponsorship.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1182613
Title:
puppet completely broken on
** Changed in: juju (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1183508
Title:
A command to scale-down a service safely.
To manage
*** This bug is a duplicate of bug 1134036 ***
https://bugs.launchpad.net/bugs/1134036
I think this is precisely the same issue and has the same root cause as
bug 1134036 - caused by ssh-ing into a server that does not have a
locale setting that you use locally configured on the server. I'll
When I ssh in to a Precise or Saucy server using:
LC_ALL=en_DK.UTF-8 ssh server
I get the message:
WARNING! Your environment specifies an invalid locale.
This can affect your user experience significantly, including the
ability to manage packages. You may install the locales by running:
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, so I'm marking this bug as Invalid.
Specifically, the MySQL configuration file /etc/mysql/my.cnf is missing
on your system, so MySQL cannot be expected to work properly.
You can find pointers
*** This bug is a duplicate of bug 1182746 ***
https://bugs.launchpad.net/bugs/1182746
** Changed in: dnsjava (Ubuntu)
Status: New = Triaged
** Changed in: dnsjava (Ubuntu)
Importance: Undecided = High
** This bug has been marked a duplicate of bug 1182746
FTBFS: requires
*** This bug is a duplicate of bug 999766 ***
https://bugs.launchpad.net/bugs/999766
** This bug has been marked a duplicate of bug 999766
MySQL 5.5 not compiled with native AIO
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If this is indeed a local configuration problem, you can find pointers
to
From log:
Setting up samba-common (2:3.6.3-2ubuntu2.6) ...
Use of uninitialized value $_[1] in join or string at
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, GEN0 line 14.
Use of uninitialized value $val in substitution (s///) at
/usr/share/perl5/Debconf/Format/822.pm line 83, GEN7 line
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If this is indeed a local configuration problem, you can find pointers
to
From log:
useradd: cannot lock /etc/passwd; try again later.
adduser: `/usr/sbin/useradd -d /srv/ftp -g ftp -s /bin/false -u 148 ftp'
returned error code 1. Exiting.
dpkg: error processing vsftpd (--configure):
subprocess installed post-installation script returned error exit status 1
--
You
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, so I'm marking this bug as Invalid.
Specifically, it looks like you have a /etc/passwd.lock lockfile left
over from a previous problem.
You can find pointers to get help for this sort of
Sorry, there isn't enough here to warrant considering this a bug in
exim4.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
** Changed in: exim4 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, so I'm marking this bug as Invalid.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
You should also try with the latest version of
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please could you post steps to reproduce this problem on a 13.04 system?
Is it possible to recreate the problem on a single system by installing
an LDAP server locally, and then pointing nsswitch to it?
**
Jens,
Thanks for your reply.
I'm looking for specific instructions to reproduce this on a 13.04
system so that I (or another developer) can then investigate further. I
suggested a local LDAP server to make it easier for developers to look
into the problem.
If you don't understand why I'm asking
Fixed with facter 1.7.0-1ubuntu1 now in Saucy.
** Changed in: puppet (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1182613
Title:
Thanks for following this up with upstream. Marking Invalid in line with
upstream's decision.
** Changed in: asterisk (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
@Julian
Do you have a ~/.cloud-locale-test.skip file present? If not, do you see
a /etc/profile.d/Z99-cloud-locale-test.sh file? The warning is provided
by cloud-init; I wonder what version provides it, and if we need to SRU
it? What version of cloud-init do you have?
I think the root cause is:
I've started a discussion thread at: https://lists.ubuntu.com/archives
/ubuntu-devel/2013-June/037195.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1134036
Title:
Failure
The Debian package has now synced to Saucy, so I presume this is fixed
in Saucy now, too.
** Changed in: siege (Ubuntu)
Status: Triaged = Fix Released
** Tags removed: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Blueprint changed by Robie Basak:
Work items changed:
Work items:
[andreserl] write dep-8 test for heartbeat/corosync/pacemaker: TODO
[andreserl] write dep-8 test for tftpd-hpa: TODO
[gandelman-a] write dep-8 test for haproxy: TODO
[gandelman-a] write dep-8 tests puppet + facter: TODO
From log:
Setting up samba-common (2:3.6.3-2ubuntu2.6) ...
Installing new version of config file /etc/dhcp3/dhclient-enter-hooks.d/samba
...
frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
dpkg: error processing samba-common (--configure):
subprocess installed
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If this is indeed a local configuration problem, you can find pointers
to
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I have reproduced this warning. But so that the bug importance can be
set correctly, can you provide steps to reproduce a specific problem
with the operation of php5-gd, please?
Thanks!
** Changed in: php5
Thanks Michael!
** Changed in: freeradius (Ubuntu)
Status: New = Triaged
** Changed in: freeradius (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in Ubuntu.
Thanks Ondřej. I see that Debian sid is on 5.5.0~rc2+dfsg-2 now, so we
should just merge this.
** Tags added: upgrade-software-version
** Changed in: php5 (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
17:48 slangasek rbasak: why should you have to maintain a delta for an
upstart
job now? These should all be upstreamable to Debian
17:49 rbasak slangasek: I was asking in response to review a debdiff to
introduce
an upstart job in our delta, to override an
I asked in #ubuntu-dev just now if we want to convert daemons in universe to
upstart when there's no particular
other reason, and the answer was yes, we do.
Have you forgotten to source /etc/default/freeradius to pick up any
FREERADIUS_OPTIONS settings?
Apart from that it lgtm, assuming it's
Following discussion in that thread and on IRC, we have a compromised,
explained in bug 969462. The postgres package will ignore the
environmental locale and use /etc/default/locale or /etc/environment or
fall back to C. This should fix the issue.
In case the workaround isn't clear, it is:
Thanks. Saucy is now on 2.1.25.dfsg1-7, so marking Fix Released.
If you need a fix for an existing stable release, please comment with a
justification against https://wiki.ubuntu.com/StableReleaseUpdates#When
and complete steps 1 through 4 in
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
Is walinuxagent modifying /etc/ssh/sshd_config? I don't think it's
allowed to do that. See Debian policy 10.7.4:
http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Perhaps it needs ClientAliveInterval because underlying connection
tracking in Azure breaks the connection otherwise? Just speculating
here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, so I'm marking this bug as Invalid.
Specifically, the package supplies /etc/init.d/mysql, but it is not
present on your system.
You can find pointers to get help for this sort of problem here:
Thanks Ondřej!
** Summary changed:
- package php5-ldap 5.4.6-1ubuntu1.2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
+ php5{en,dis}mod are too picky on removed files or changed symlinks
** Changed in: php5 (Ubuntu)
Status: New =
Note that zombie has a specific meaning that doesn't apply here.
** Summary changed:
- Facter bug causes puppet to become a zombie
+ Facter bug causes puppet to freeze
** Summary changed:
- Facter bug causes puppet to freeze
+ Facter bug causes puppet to hang
--
You received this bug
@Chris Abbey
Thanks for pointing this out. I can't seem to find any corresponding
commit related to a fix in 1.7.0 though. I'm looking at
https://github.com/puppetlabs/facter/commits/1.7.1/lib/facter/memory.rb
for example - given that the original pull request
If this is fixed in Saucy, it should be Fix Released and have a Precise
task added. I set this to Confirmed for now so we don't lose it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
Thinking about it, adding log rotation would just start rotating an
already large file. I don't see regression potential except where
existing users are already managing the log file in some other way
(perhaps as a result of it not having log rotation previously?)
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Fixing this in Precise would need to go through the SRU procedure
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure and comply with
SRU policy (https://wiki.ubuntu.com/StableReleaseUpdates#When).
I'm not
*** This bug is a duplicate of bug 1190154 ***
https://bugs.launchpad.net/bugs/1190154
This has since been fixed.
** Changed in: php5 (Ubuntu)
Status: Won't Fix = New
** This bug has been marked a duplicate of bug 1190154
php5-fpm does not rotate logs
--
You received this bug
OK, then in that case, let's leave it. Marking as Fix Released, as I've
verified that /etc/logrotate.d/php5-fpm is provided by php5-fpm in
Saucy.
** Summary changed:
- please backport the missing logrotage file for the php5-fpm package
+ php5-fpm does not rotate logs
** Changed in: php5
We'll also need this fixed in Saucy before we can commence an SRU. What
is the fix needed in Saucy? Just memory.rb? The same patch? Or
processor.rb as well?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
@Shane
Could you please confirm the patch that you're using on memory.rb, and
confirm that this fixes the problem for you?
I've also been seeing 'puppet apply' hanging via cron, but never figured
out if this was the issue or if this patch fixed it. I've been working
around it with a timeout.
If
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, so I'm marking this bug as Invalid.
Specifically, /etc/php5/mods-available/xmlrpc.ini is supplied by the
package but it is removed on your system.
You can find pointers to get help for this
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
It looks like your tftp system account has had an expiry date set, which
From log:
Paramétrage de tftpd-hpa (5.0-11ubuntu2.1) ...
Votre compte a expiré. Contactez votre administrateur système
chfn : échec de la méthode d'authentification PAM
adduser: `/usr/bin/chfn -f tftp daemon tftp' a retourné le code d'erreur 1.
Abandon.
dpkg : erreur de traitement de tftpd-hpa
From log:
Setting up php5-xmlrpc (5.4.9-4ubuntu2.1) ...
Not replacing deleted config file /etc/php5/mods-available/xmlrpc.ini
ERROR: /etc/php5/mods-available/xmlrpc.ini does not exist
dpkg: error processing php5-xmlrpc (--configure):
subprocess installed post-installation script returned error
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, so I'm marking this bug as Invalid.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
If you believe that this is really a bug, then you
From log:
Setting up apache2-mpm-prefork (2.2.22-6ubuntu5) ...
egrep: /etc/apache2/mods-enabled/*.load: No such file or directory
* Starting web server apache2 Syntax error on line 189 of
/etc/apache2/apache2.conf:
Invalid command 'Order', perhaps misspelled or defined by a module not included
Thank you for your report. I've asked a member of the security team to
clarify.
** Summary changed:
- No security release provided for CVE-2013-3567
+ No security release provided in Lucid for CVE-2013-3567
** Information type changed from Public to Public Security
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I've just checked the Debian net-snmp source, and it looks like this bug
applies equally there. So it would be best fixed in Debian, and then
Ubuntu will pick it up on the next merge. In any case, I'd prefer to
Thank you for your report.
Since this looks like local disk corruption or a hardware problem,
rather than a bug in Ubuntu, I'm marking this bug as Invalid.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
If you believe that this is really
Please set the bug status back to New once you've replied. Thanks!
** Changed in: clamav (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
** Changed in: augeas (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to augeas in Ubuntu.
https://bugs.launchpad.net/bugs/1193176
Title:
augeas-lenses package lacking support in
://github.com/puppetlabs/facter/pull/174 and had no explanation for
why they were put in either. So I think it's safe to backport all of the
patch to Precise. I'll do this next week.
** Changed in: facter (Ubuntu Precise)
Assignee: (unassigned) = Robie Basak (racb)
--
You received this bug
I've reported this upstream, since I don't see that this bug will get
fixed any other way:
https://sourceforge.net/tracker/?func=detailaid=3614595group_id=29880atid=397597
I'm dubious about calling this a security vulnerability. I can see your
logic, but this bug's root cause is the fundamental
(this appears fixed in Saucy, so just the Precise SRU needed)
** Description changed:
+ [Impact]
+
+ puppet apply hangs about 20% of the time on affected servers. This
+ affects users using puppet without a puppetmaster. The normal use case
+ is to make puppet apply run regularly. This causes
** Description changed:
[Impact]
puppet apply hangs about 20% of the time on affected servers. This
affects users using puppet without a puppetmaster. The normal use case
is to make puppet apply run regularly. This causes hung puppet
processes to build up, eventually exhausting
Public bug reported:
lxc 0.9.0-0ubuntu3.3
Running lxc-create -t ubuntu-cloud -n test -- -i test creates a Lucid
container. I expected it to be Raring (when on Raring).
Indeed, on Precise, I believe that you'd get a Precise container.
The culprit appears to be
** Description changed:
lxc 0.9.0-0ubuntu3.3
Running lxc-create -t ubuntu-cloud -n test -- -i test creates a Lucid
- container. I expected it to be Raring.
+ container. I expected it to be Raring (when on Raring).
Indeed, on Precise, I believe that you'd get a Precise container.
Public bug reported:
If I run:
sudo lxc-create -t ubuntu-cloud -n wip -- -r saucy -i foobar -s
daily
then the created container still uses a random instance id. grepping for
foobar /etc and /var/lib/cloud gives me nothing.
Expected result:
/var/lib/cloud/data/instance-id should be foobar.
Public bug reported:
On a fresh Saucy cloud image, apt-get install puppetmaster-passenger
fails. Log attached.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: puppetmaster-passenger 3.2.2-1
ProcVersionSignature: User Name 3.9.0-6.14-generic 3.9.6
Uname: Linux 3.9.0-6-generic x86_64
Looks like this is because Debian has apache2 2.4.4-6 and Ubuntu is
still on 2.2.22-6ubuntu5. Debian has moved to /etc/apache2/sites-
enabled/puppetmaster.conf, whereas Ubuntu's apache2 still requires
/etc/apache2/sites-enabled/puppetmaster.
--
You received this bug notification because you are
Turns out we have apache2 2.4 in saucy-proposed, but is currently
blocked from being migrated because it breaks other packages. When this
is complete, it should work again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in
Public bug reported:
A script cannot call lxc-start-ephemeral and get a named container in a
reliable, race-free way.
Having the caller specify a name directly is racy, since the name could
have been taken in between checking that it doesn't exist already and
calling lxc-start-ephemeral.
On Fri, Jul 05, 2013 at 12:01:08PM -, Serge Hallyn wrote:
Practically speaking, have you actually created the container name with
mktemp (i.e. mktemp -u -t lxc-XX | sed 's@/tmp/@@') and gotten name
clashes?
No, but eyebrows were raised on my approach of generating a random name
on code
I've made some suggestions here:
https://lists.ubuntu.com/archives/ubuntu-server/2013-July/006675.html
Reading cyco's comment, I suppose another route would be to get Simon's
plugin into nagios-plugins-contrib?
--
You received this bug notification because you are a member of Ubuntu
Server
I've just hit this. C is a valid LANG, AFAIK.
--
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/1166841
Title:
lxc-create fails if LANG is not valid
To manage notifications about this
Public bug reported:
When lxc-create fails (eg. due to bug 1166841), then it leaves
/run/lock/subsys/lxc-ubuntu lying around. A subsequent attempt to run
lxc-create again causes it to hang while it waits on this lockfile.
Workaround: remove the lockfile by hand.
Steps to reproduce:
1. sudo
Why is en_US being hardcoded? Isn't C valid on its own? locale-gen C
doesn't make sense, but shouldn't the system work without it?
--
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/1166841
From log:
Preparing to replace apache2-utils 2.2.22-6ubuntu5 (using
.../apache2-utils_2.4.4-6ubuntu2_amd64.deb) ...
Unpacking replacement apache2-utils ...
dpkg: error processing
/var/cache/apt/archives/apache2-utils_2.4.4-6ubuntu2_amd64.deb (--unpack):
trying to overwrite
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Note that you shouldn't have saucy-proposed enabled, as package upgrades
to saucy-proposed are expected to break. Please see
https://lists.ubuntu.com/archives/ubuntu-devel/2013-July/037451.html and
the surrounding
$ sudo lsof /var/lock/subsys/lxc-ubuntu
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
udevd 6564 root 200w REG 0,170 598420 /run/lock/subsys/lxc-ubuntu
$ sudo LANG=C strace -fo /tmp/strace.log lxc-create -n saucy -t ubuntu
-- -r saucy -d
lxc-create: No config file
Sorry, armhf if that wasn't clear. highbank.
Linux c15 3.8.0-23-generic #34-Ubuntu SMP Wed May 29 20:34:45 UTC 2013
armv7l armv7l armv7l GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: apache2 (Ubuntu Saucy)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1199318
Title:
package apache2-utils 2.2.22-6ubuntu5
What I have so far: everything except point 6 in the plan above.
Problems:
1) libvirt creates an AppArmor profile for console.fifo and not
console.fifo.{in,out}.
Other things to check:
1) Console logging gets resumed correctly on restart.
2) Correct management of live migration.
3) Correct
Thank you for your report. This package failure looks like being caused
by a corrupted file system. Please start the Memory check from the
boot menu. If that runs successfully, please start the desktop cd. Hold
right-shift key after the bios checks to get to the grub menu and run
Check disc for
Eduardo,
Do you know how you have ended up with libaio:i386 version 0.3.104-1
installed? The current supported versions are:
libaio1 | 0.3.106-8ubuntu1 | hardy | amd64, hppa, i386, ia64, lpia,
powerpc, sparc
libaio1 | 0.3.107-3ubuntu2 | lucid | amd64, armel, i386, ia64,
This looks like it is specific to your openldap configuration. Still,
the maintainer script should be able to cope with a customised
installation.
** Changed in: openldap (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server
301 - 400 of 12224 matches
Mail list logo
