** Package changed: linux (Ubuntu) => samba (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1551175
Title:
"net join" to Active Directory may fail
To manage notifications
To workaround this add
shlib_directory = no
to your main.cf.
** Bug watch added: Debian Bug tracker #815047
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815047
** Also affects: postfix (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815047
Importance: Unknown
** Changed in: linux (Ubuntu Vivid)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
(Ubuntu Vivid)
Status: New => In Progress
** Changed in: linux (Ubuntu Vivid)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Wily)
Status: New => In Progress
** Changed in: linux (Ubuntu Wily)
Assignee: (unassigned) => Tim Gardn
** Package changed: linux (Ubuntu) => ethtool (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ethtool in Ubuntu.
https://bugs.launchpad.net/bugs/1533721
Title:
Ethtool didn't support link speed 25Gb 56Gb 100Gb 200Gb
To
Seems to me like we should close this issue as it doesn't seem like the
patch will be applied before Ubuntu 12.04 is end-of-life. What's the
correct status to mark an issue as "won't fix"?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
This is fixed in Xenial and Wily, doesnt seem critical enough to SRU
into vivid this late in its lifecycle.
** Changed in: python-tempest-lib (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Fix Committed
--
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/1499869
Title:
maas wily deployment to HP Proliant
Still this is a problem. It is a horrible bug and prevent us from using
network manager at all, which is highly inconvenient and nearly breaks
the whole system and causes many problems. PLEASE FIX THIS, or tell us
how to modify dnsmasq so that it uses the right dns server
--
You received this
This is an answer to some of the questions Seth asked
> In 1339770, in May 2015, it was mentioned that 1.18 was end-of-life and no
> further updates could be prepared for it. 1.18.0 was released just 13
> months earlier and 1.18.1 had been included in 14.04 LTS. Why was the 1.18
> infrastructure
Woah. I don't know where ethc6 came from. That should be eth1 not ethc6
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to radvd in Ubuntu.
https://bugs.launchpad.net/bugs/1450707
Title:
radvd advertises on wrong intereface
To manage
Public bug reported:
Running radvd 1:1.9.1-1.1ubuntu2 on Ubuntu 14.4 LTS amd64 with the
following config:
interface eth0
{
AdvSendAdvert on;
UnicastOnly on;
prefix 0:0:0:e0::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
Base6to4Interface ppp0;
};
};
interface ethc6
{
Yes, thanks for the link and thoughts. I'm currently investigating if I
can leave all the SA, amavis and clamav code out of my setup by using
the blacklist feature of postscreen*.
* http://www.postfix.org/postconf.5.html#postscreen_dnsbl_sites
--
You received this bug notification because you
This user switching is for reading per-user configurations only and I
think can be mitigated by making the per-user config world readable.
Furthermore from the README.spamd.gz you've mentioned If a fault is
found in spamd or spamassassin code, any third party linked-libraries or
imported perl
Public bug reported:
I was surprised that after following
https://help.ubuntu.com/14.04/serverguide/mail-filtering.html this
leaves me with the spamassassin daemon running as root.
This is not of the same standard compared with the secure defaults that
Postfix and Dovecot use. I think this
This ticket seems to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1232258
The #1232258 ticket suggests instead that symlinks be created to resolve
this problem. Unfortunately, simply changing the ${catalina.home}
settings in the catalina.properties file(s) to
After further analysis today, I realized my suggestion to correct the
configurations in catalina.properties to point at ${catalina.base}
instead of ${catalina.home} was WRONG.
The original suggestion of symlinks is a better solution, since the
location of ${catalina.base} may not always resolve
I ran into this bug today on Ubuntu Server 14.04.
I could be wrong, but I'm not sure this is an issue of missing symbolic
links, but rather a minor misconfiguration of catalina.properties on
Ubuntu 14.04. Specifically, the server.loader and shared.loader
settings are referencing CATALINA_HOME
Per my previous comment, this issue seems to be a possible duplicate of
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1308284
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
I tested the updated service scripts and indeed does also fix my boot
hang!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1417010
Title:
Reloading services can result in a deadlock
** Also affects: juju-core/1.21
Importance: Undecided
Status: New
** Changed in: juju-core
Milestone: 1.21-beta4 = 1.22
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
I don't have an easy way to repro, all this occurs fairly regularly on
our jenkins slave.
Ubuntu 14.04 LTS (GNU/Linux 3.13.0-29-generic x86_64)
juju version: 1.20.13-trusty-amd64
1 ppa installed: http://ppa.launchpad.net/juju/stable/ubuntu
$ dpkg -l | egrep -e (lxc|apparmor|cgmanager)
ii
I tried the patch from c#17 in a packstack install on fedora 21. After
dropping the old neutron database and rebuilding it, the migration now
works for me
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
Public bug reported:
I have just upgraded 2 of my machines from 14.04 to 14.10. Both have the
same error after the upgrade.
When the libvirt-bin service is started it crashes with the error:
2014-10-29 00:57:51.863+: 4809: info : libvirt version: 1.2.8, package:
1.2.8-0ubuntu11
2014-10-29
Filed https://tickets.puppetlabs.com/browse/FACT-709 upstream.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/1330120
Title:
facter doesn't handle can't open /proc/interrupts at
FWIW, Strato replied that the warnings were harmless (who would have
thought …), but I could rent a root server (just a 262.5 % increase in
costs :-)) to get rid of them and a true Ubuntu installation instead.
So taking this upstream is probably the sensible approach.
--
You received this bug
Problem still exists in Ubuntu 14.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1004494
Title:
Job not run message after any attempt to run a job using bconsole
To manage
I got the same trouble with my vanilla Ubuntu 14.04 installation.
Samba4 AD DC is not working properly after system reboot when ipv6 is enabled.
Snipped from /var/log/syslog:
Sep 3 12:05:08 ubuntu samba[986]: [2014/09/03 12:05:08.864745, 0]
)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
** Changed in: librtas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: librtas (Ubuntu Trusty)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Ubuntu
Server Team
Try this, it works for me:
apt-get install postfix/precise-proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1356843
Title:
ccs received early errors after openssl security
Precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1356843
Title:
ccs received early errors after openssl security update
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = John Johansen (jjohansen)
--
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/1357103
Title:
apparmor denied a golang build
Will appear in Ubuntu-3.16.0-7.12
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1342000
Title:
Tested on a precise lxc container I have:
it seems we could try with -L (or even better --console-log) and fall
back to -c (or --console) if that fails with exit code 1 (we could even
check the output for invalid option.
ubuntu@clean-precise:~$ lxc-start -n foo -L omg
lxc-start: invalid
** Also affects: openipmi (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: openipmi (Ubuntu Precise)
Status: New = In Progress
** Changed in: openipmi (Ubuntu Precise)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
--
You received this bug notification
** Changed in: openipmi (Ubuntu Precise)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1309860
Title:
missing ipmi module
To manage
Public bug reported:
On my rented Strato Linux virtual server, facter (and thus puppet)
throws a warning on each run:
| root@[redacted]:~# facter
| can't open /proc/interrupts at /usr/bin/lsdev line 15.
| [key = value pairs]
| root@[redacted]:~# puppet agent --test
| can't open /proc/interrupts
I found that the code was committed back in march to not mount the log
dir in the container.
My juju-precise-template lxc container had a line that include a mount
to /home/tim/.juju/local/log, which caused cgroups to complain when
logged in as my other local user.
Removing the juju-precise
Gah, I should read the entire description before changing things. This
was a different problem to me that had exactly the same error message.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
SRU Description:
openipmi won't start correctly because it does not detect that the ipmi
module is built into the kernel.
Patch Description: Detect that the module name exists within the kernel
namespace.
** Attachment added: Detect that a module is built into the kernel
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Summary changed:
- fails to start container with local provider with non-default LXC path
+ template container contains user log mount in error
--
You received this bug notification because you are a member
It seems to me that the bug isn't in the different container directory,
but the way that the log directory is mounted.
I have just hit this same problem locally, and I don't have a non-
default directory.
What I do have though is two different users locally.
When the juju conatiner template is
** Changed in: juju-core
Milestone: None = next-stable
--
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/1290920
Title:
fails to start container with local provider with non-default
I'm seeing exactly the same thing as #9.
LocationMatch /git/setup(\.git)?
AuthName Git repository: setup
AuthBasicAuthoritative Off
AuthBasicProvider pgsql
AuthType Basic
AuthUserFile /dev/null
require valid-user
Auth_PG_host XXX
Auth_PG_port XXX
Auth_PG_user XXX
Auth_PG_pwd
Whoops, forgot the CGI script component of the Apache config:
# Git HTTP Backend
SetEnv GIT_HTTP_EXPORT_ALL 1
SetEnv GIT_PROJECT_ROOT XXX
ScriptAlias /git /usr/lib/git-core/git-http-backend
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: keepalived (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: keepalived (Ubuntu Utopic)
Importance: High
Status: Invalid
** Also affects: linux (Ubuntu
** Changed in: linux (Ubuntu Trusty)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived doesn't load any ipv6
** Also affects: openipmi (Ubuntu Utopic)
Importance: Undecided
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Changed in: openipmi (Ubuntu Utopic)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: openipmi (Ubuntu Trusty)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1309860
Title:
missing ipmi module
To manage
James. I thought this might be the case, but if it is, it still doesn't
solve the original problem. My understanding is that Upstart scripts
require registration with initctl in order for the service commands to
work. This does not appear to be occurring during install, so the above
mentioned
I tried 3.2.0-27-generic and 3.11.0-18-generic from the precise repos.
Also a vanilla 3.10.18 and 3.10.28 based on the 3.2.0-27-generic config
file. I tried these ubuntu packages for qemu: saucy (1.5.0+dfsg-
3ubuntu5.3) and trusty (1.7.0+dfsg-3ubuntu5). Also the plain qemu from
Ciphers
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
HostKeyAlgorithms ssh-rsa,ssh-dss
KexAlgorithms diffie-hellman-group1-sha1
MACs hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160
In /etc/ssh/ssh_config resolve the issue. I would say this is not a
Was this removal intentional? I just assumed it was an omission since
it's setup process still exists in the package, and it's assumed to be
that way in the docs.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
Rather then removing the module handling code, how about wrapping it
with:
if ! grep ipmi_alloc_smi_msg /proc/kallsyms
then
...
fi
That way openipmi will continue to work with kernels where
ipmi_msghandler is still modular.
--
You received this bug notification because you are a member of
Please attach your patch and I'll see if it adheres to Ubuntu SRU
policy.
** Package changed: linux (Ubuntu Trusty) = openipmi (Ubuntu Trusty)
** Changed in: openipmi (Ubuntu Trusty)
Status: Invalid = In Progress
--
You received this bug notification because you are a member of Ubuntu
Just the diff please, e.g., 'diff -r -u original modified patch.txt'
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1309860
Title:
missing ipmi module
To manage notifications
Does not seem to be a kernel issue.
** Package changed: linux (Ubuntu) = lxc (Ubuntu)
--
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/1306916
Title:
cgroup-lite should be added as an
Critical is a stop the line type bug. No one is being assigned to it
right now, so it isn't Critical.
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Hi Serge,
You should be able to reproduce this with any iso from
http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/10.0/
Let me know if you need more information.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
That work around did not work for all the devices in my network sadly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1287222
Title:
openssh-client 6.5 regression bug with certain
This happens also with vanilla kernel, so its more an qemu-kvm bug then
kernel related
** Package changed: linux (Ubuntu) = qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to hv-kvp-daemon-init in Ubuntu.
https://bugs.launchpad.net/bugs/1298192
Title:
hyper-v: Unable to take backups of Generation 2 VMs
Can someone please test this?
lp:~thumper/juju-core/maas-no-restart-networking
I don't have a MAAS setup to hand, but according to the code above, this
*should* work.
Now we go
ifdown eth0
before messing with the network config, and
ifup eth0
ifup br0
after, and no 'restart
** Changed in: juju-core
Status: In Progress = Fix Released
** Changed in: juju-core
Milestone: 1.20.0 = 1.17.6
--
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/1276909
Marking as fix committed for trunk developers.
We should also make sure the build commands for the package are updated.
** Branch linked: lp:~thumper/juju-core/power-static-link-make
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
** Summary changed:
- openssh-client 6.5p1 regression bug with certain servers
+ openssh-client 6.5 (multiple releases) regression bug with certain servers
** Summary changed:
- openssh-client 6.5 (multiple releases) regression bug with certain servers
+ openssh-client 6.5 regression bug with
Public bug reported:
Previous working versions of SSH (6.2p2) work fine on certain host
machines as follows:
penSSH_6.2p2 Ubuntu-6, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Status: Triaged = In Progress
--
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
** Branch linked: lp:~thumper/juju-core/arm64-identification
--
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/1276909
Title:
error detecting hardware characteristics: unrecognised
I've made a branch out of the patches (well, manually did it). @dann can
I get you to give the diff a once over?
--
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/1276909
Title:
Public bug reported:
The recent update of spamassassin has broken the Ubuntu GNOME daily
builds.
Setting up sa-compile (3.4.0-1) ...
Running sa-compile (may take a long time)
In file included from /usr/lib/perl/5.18/CORE/perl.h:650:0,
from body_0.xs:2:
** Changed in: juju-core
Status: In Progress = Fix Committed
--
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/1271941
Title:
lxc container creation fails on trusty host
** Changed in: juju-core
Assignee: Tim Penhey (thumper) = Jesse Meek (waigani)
--
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/1271941
Title:
lxc container creation fails
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Status: Triaged = In Progress
--
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
thumper hallyn: has the autostart behaviour for lxc changed in trusty?
hallyn thumper: yes, stgraber's new autostart setup may be in now. certainly
in the ppa
stgraber hallyn: yep, it landed with beta2 last week
thumper hallyn: hmm... managed to break juju's behaviour
thumper hallyn: can you
Not sure if this is clear to everyone else so as a hint (I haven't
looked at the code for lxc) the IPv6 address shown gives a pretty good
indication that something is parsing an IPv6 address and then
representing the first 32 bits as an IPv4 address.
The specified ip address is 2607:f088:...
Public bug reported:
root@cps3:~/lxc# cat horizon-cps3.net.conf
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br18
lxc.network.name = eth0
lxc.network.hwaddr = 00:16:3e:00:02:70
lxc.network.ipv6 = 2607:f088:0:12::39
lxc.network.mtu = 9000
root@cps3:~/lxc# lxc-create -n
Sure thing, by start I assume you mean create since there is nothing
created yet. There are only three lines in the debug output, I'll just
paste it here:
root@cps3:~/lxc# lxc-create -n horizon-cps3 -f horizon-cps3.net.conf -t ubuntu
-l debug -o debug
lxc-create: No such file or directory -
Hello Stéphane,
I downloaded the packages manually, rebooted the node and the lxc
containers seem to have started nominally. Thanks for the info!
Serge,
Thanks again for the quick fix!
Cheers,
-Tim
** Tags removed: verification-needed
** Tags added: verification-done
--
You received
Thanks for the quick fix! Unfortunately, something else broke when I
pulled that package from the trusty repository. The lxc instance is
started but nothing runs. Starting it manually vs on boot produces the
same behavior and I only see these two lines when I start manually:
4init: console-setup
Public bug reported:
root@cps2-c1:/var/log/upstart# cat lxc.log
lxc-instance (os-api-cps2) start/running, process 2880
root@cps2-c1:/var/log/upstart# tail -f lxc-instance-os-api-cps2.log
lxc-start: failed to rename veth3ITMNG-eth0 : File exists
lxc-start: failed to setup netdev
lxc-start:
** Changed in: juju-core (Ubuntu Saucy)
Status: New = 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/1240709
Title:
local provider fails to start
To manage
** Branch linked: lp:~thumper/juju-core/maas-lxc-trunk
--
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/1246556
Title:
lxc containers broken with maas
To manage notifications
** Changed in: juju-core
Milestone: 1.15.0 = 1.15.1
** Changed in: juju-core
Status: In Progress = Fix Committed
--
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/1210054
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Milestone: None = 2.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
1.16 will also fix the local provider, which is broken on saucy with
1.14 due to changes in upstart and lxc.
--
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/1219879
Title:
[FFe]
** Changed in: juju-core
Status: New = Invalid
--
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/1204302
Title:
fails to bootstrap, returns error: no reachable servers
To
** Tags added: maas
** Summary changed:
- juju destroy-environment also destroys nodes that are not controlled by juju
+ [maas] juju destroy-environment also destroys nodes that are not controlled
by juju
** Changed in: juju
Importance: Undecided = High
--
You received this bug
I came across this same issue recently on Debian/Wheezy while trying to
enable Evolution's built-in spamassassin checking.
As noted at some length in the upstream Spamassassin issue, it's not
really a spamassassin issue at all (beyond quibbling over error message
helpfulness) and seems more to do
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Milestone: None = 1.15.0
** Branch linked: lp:~thumper/juju-core/lxc-stopping
--
You received this bug notification because
I've applied http://launchpad.net/ubuntu/+source/maas/1.2+bzr1373+dfsg-
0ubuntu1~12.04.2 from precise proposed into a fresh maas install and I
get the same error.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Public bug reported:
I noticed that my syslog file was empty, and some cursory googling
suggested that it may be libvirt.
I had a juju local environment set up which had some containers
autostarting. Destroying this environment, and making sure there were
no autostart containers, followed by a
I tried this on my Lenovo X120e with an AMD E-350 with no problem on a
3.11 kernel.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1201092
Title:
Cannot load kvm_amd module - (says
** Tags added: logging
--
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/1078213
Title:
juju-machine-agent.log/logs are not logrotated
To manage notifications about this bug go to:
Public bug reported:
On a new raring install I have added puppet (which brings in facter) but
puppet won't start:
# service puppet restart
* Restarting puppet agent
Sorry, I realized a few seconds after this went through that puppet was
broken by something else in my own environment.
--
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/1170801
Title:
failing.
I get this Socket read error. Why?
Server version: Apache/2.2.22 (Ubuntu)
(churchill is my latpop, accessing the system. )
( I also tried running sshd on and changing the proxytunnel config, same
result)
-
churchill:~ tim$ proxytunnel -E -p ec2.growthpath.com.au:443
I have requested help already via the forums, but didn't get an answer.
I guess it's an Apache problem because the error is a socket read error, but I
don't know enough to test this. I actually don't know what a socket read error
means. There one another reports of similar problems on RedHat,
*** This bug is a duplicate of bug 1016895 ***
https://bugs.launchpad.net/bugs/1016895
Tried the 3.5 kernel again and in the meantime Samba has been updated to
fix the bug causing this. So this is a dupe of lp#1016895
** This bug has been marked a duplicate of bug 1016895
smbd crashed
Public bug reported:
I've had a running 12.04 LTS system for several months now. I installed
the LTS Enablement Stack for 12.04.2 following the instructions at
https://wiki.ubuntu.com/Kernel/LTSEnablementStack. After doing this and
rebooting into the new kernel samba no longer works, every time I
1 - 100 of 241 matches
Mail list logo
