Okay, I've written up a short README.Debian describing the necessary
changes to /etc/default/lxc-net and the dnsmasq config file. I don't
remember what steps are necessary to make the domain names accessible,
though, and I'd like to include those steps in the readme.
Do I have to restart the
No, installed clamav as part of amavis.
update of signatures happens via freshclam.
I circumvent this by reinstalling libclamav6. But I doubt that
installing this library regularly after every upgrade should be a
solution.
usually happens after an update of clamav or the kernel.
I also
Sorry Serge, I didn't see the first reply. I made a mistake pasting the (4),
the four was missing the
127.0.1.1 hostname
--
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/1447160
I'm quite new to apt and ppa.
https://launchpad.net/~maas-maintainers/+archive/ubuntu/stable still has old
version. Could someone, please, tell me how do I install this new update with
apt in 14.04?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
ii dlm 4.0.1-0ubuntu1
amd64DLM - Distributed lock manager binaries
. /etc/rc.d/init.d/functions
# ls -l /etc/rc.d/init.d/functions
ls: cannot access /etc/rc.d/init.d/functions: No such file or directory
Public bug reported:
Having deployed vivid-kilo-proposed with openstack-charm-testing, I'm initially
unable to launch instances, because ovs-vsctl errors out:
ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed
(Protocol error)
Restarting openvswitch-switch resolves the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pacemaker (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
I've been trying to capture a log of the failure when running lxc-attach
and it seems to cause just enough delay to get by the race. Also, it
does not always occur, but more time than not, the error happens leading
more credence to this being a race. I've attached the config I use for
the
Actually, running sudo unity8-lxc-setup has a start/wait/attach
sequence that is causing failures. Another way I try to reproduce after
the whole container is setup is to create a little script with the
following:
lxc-start -n unity8-lxc
lxc-wait -t 5 -s RUNNING -n unity8-lxc
lxc-attach -n
I have certified juju 1.20.1 in trusty proposed is compatible with juju agent
streams and with the ecosystem of tools in trusty. I verified:
* The binary archs in proposed work with the archs in agent streams.
* Juju is suitable for local testing and charm development
* juju-deployer can deployed
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
Hello Chuck, or anyone else affected,
Accepted nova into utopic-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/nova/1:2014.2.3-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
You have been subscribed to a public bug by Robie Basak (racb):
Hello,
When dlm_controld requests the fencing of a node, the node is fenced but
dlm_controld is not notified of the fence result.
All the informations are reported on pacemaker mailing-list
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Is there an upstream release that fixes this issue, please, and if so,
which version?
To fix the packages in Trusty, please follow the steps documented at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure -
I assume that bin/unity8-lxc-compositor is the script you are using. But
how does it get run? Do I just install that package in a container to
reproduce this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Thanks Curtis! Adding 'verification-done' tag based on your comments.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
There was a typo in the message #8 from Curtis. Juju 1.22.1 has been certified
not 1.20.1.
sinzui strikov, oops, yes, I do mean *1.22.1*
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Are there any plans to update this package in https://launchpad.net
/~maas-maintainers/+archive/ubuntu/stable for 14.04?
--
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/1446878
Title:
Public bug reported:
neutron-plugin-linuxbridge-agent service cannot start due to missing executable
so initscripts exits silently with code 0.
There is a name inconsistency between filesystem and initscript.
In /etc/init/neutron-plugin-linuxbridge-agent.conf path to daemon is
Related question on Ask Ubuntu:
How to fix a “Software caused connection abort” error in Ubuntu 14.04?
https://askubuntu.com/q/450206/232993
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
** 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/1384279
Title:
Enhancement Request Version and program data About
To
2.1.1-1ubuntu1~vivid2 uploaded. I'll upload 2.1.1-1ubuntu1 to wily in a
few minutes.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1450642
Title:
seccomp missing many new
Hi Serge,
This does not happen when doing this by hand, only in a script. And I
can't seem to reproduce on a container created using a template. So
far, I've only been able to reproduce this when creating the container
using the procedure in lp:unity8-preview-lxc. This is a project that
was
Change abandoned by Mike Perez (thin...@gmail.com) on branch: master
Review: https://review.openstack.org/143575
Reason: No activity for over a month.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
[Expired for golang (Ubuntu) because there has been no activity for 60
days.]
** Changed in: golang (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
Hello Gregory, or anyone else affected,
Accepted spice into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/spice/0.12.4-0nocelt2ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
26 matches
Mail list logo
