[Bug 1551175] Re: "net join" to Active Directory may fail
** 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1551175/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546788] Re: Fresh install of Postfix 3.0.3-1~build1 will not start with instance conflict error
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 Status: Unknown -- 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/1546788 Title: Fresh install of Postfix 3.0.3-1~build1 will not start with instance conflict error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1546788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1446906] Re: lxc container with postfix, permission denied on mailq
** 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. https://bugs.launchpad.net/bugs/1446906 Title: lxc container with postfix, permission denied on mailq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446906/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1446906] Re: lxc container with postfix, permission denied on mailq
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: linux (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 Gardner (timg-tpi) ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1446906 Title: lxc container with postfix, permission denied on mailq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446906/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1533721] Re: Ethtool didn't support link speed 25Gb 56Gb 100Gb 200Gb
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/1533721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1004204] Re: PostGIS does not properly escape data with PostgreSQL 9.1
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 to python-django in Ubuntu. https://bugs.launchpad.net/bugs/1004204 Title: PostGIS does not properly escape data with PostgreSQL 9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1004204/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1461573] Re: [SRU] trying to overwrite '/usr/bin/skip-tracker', which is also in package python-tempest-lib
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 to python-tempest-lib in Ubuntu. https://bugs.launchpad.net/bugs/1461573 Title: [SRU] trying to overwrite '/usr/bin/skip-tracker', which is also in package python-tempest-lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tempest-lib/+bug/1461573/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails
** 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 m400 arm64 server cartridge fails To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1499869/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
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 bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267393] Juju MIR resposne
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 torn down so shortly after including 1.18 in a release with > five-year support? I believe that this change was primarily brought about by the change from using bzr to git. The build and test infrastructure had to be re-tooled to make this work. > Have there been any similar changes in process that > would prevent or delay issuing an update to the currently supported > versions of juju already in the archive? We are unlikely to change from git. > It is currently impossible to upgrade from 14.04 LTS to 15.04 due to > incorrect version numbers. Has anyone else noticed this yet? When will > this be fixed? Are there any changes in process needed to ensure this > doesn't happen in the future? The older versions of Juju were not very good at handling unknown series. I have targeted a previously created bug to address this: https://bugs.launchpad.net/juju-core/+bug/1403689 There are work-arounds that have been used by IS to upgrade older environments. We do test a number of upgrade combinations, and I'm curious as to why you say it is impossible to upgrade? What exactly is the situation you are attempting? > Will the juju team be asking for an MRE? Is it anticipated that new series > (e.g., the 1.18 to 1.22 change) would be included as an MRE? What > processes are in place to test updates before including updates into the > archive? What processes are available to the security team to test > updates that we would prepare? There are CI tests around upgrading from older versions to the current tested release. I believe that one of these tests includes going from 1.18 to the current tested release. > I had more trouble reading the Juju code this review cycle than last > review cycle -- the Facade indirection mechanism makes code navigating > harder. I'm worried about it for a few reasons: > - Strings to reference method names are brittle and can't be checked at > compile time. What methods are in place to ensure that these aren't > typoed? There are unit tests in place that test both the client and server side of every call, and in addition to that there are full feature tests that make sure all the parts align. > - Generic args and return types defeat type checking. What ensures types > being returned or accepted have the desired properties? The specified unit and feature tests. > - Java has had significant problems with their Reflection mechanism, > probably dozens of issues per year. At what points of a process > lifetimes is the Facade mechanism dynamic? During the low level RPC call from the client to the API server. > Here's a few issues I found: > > - ./apiserver/apiserver.go logs passwords when tracing is enabled -- this > is fine IFF this is loudly documented somewhere obvious. Is it? It'd be > best to filter out passwords regardless. I have created a bug to address this more completely: https://bugs.launchpad.net/juju-core/+bug/1500298 > - Chown() doesn't quote the user or group In which cases is this really necessary? All the chowns that the Juju code base does is to either ubuntu, syslog or adm. Other chowns copy the uid/gid directly from the source. > - ./api/client.go WatchDebugLog() claims to read a line but looks like it > may read up to 4096 bytes -- is this correct? The first line returned in the WatchDebugLog is a serialized error, and only a serialized error. The size of the error is always less than 200 bytes, but 4k is a nice block size. Once this initial error has been returned, the websocket is used as a stream. > - significant number of TODO comments; is there a method in place to find > unowned comments and assign them somewhere? is there a process in place > to ensure they get revisited? I don't believe we have a formal process at this stage. New TODO comments are expected to have an associated bug, and a date. > - Which versions of the client work with which versions of the servers? > Where's that described? All clients from 1.18 on should work with any API server. This is the expected behaviour until at least Juju 2.0. > - ./api/keyupdater/authorisedkeys.go AuthorisedKeys(), > WatchAuthorisedKeys() expects exactly one authorized key, this seems > fragile I believe it expects one string, which may be multi-line, and each key is on a different line. > - Is -static-libgo still being used? No idea sorry. > I'm concerned with how previous issues have been handled -- the three > referenced bug reports have combined to represent the single most > expensive consequence I've personally seen and all were known issues five > months earlier. So I need reassurance that the Juju team will help the > security team maintain Juju in our supported re
[Bug 1450707] Re: radvd advertises on wrong intereface
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/1450707/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1450707] [NEW] radvd advertises on wrong intereface
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
{
AdvSendAdvert on;
UnicastOnly on;
prefix 0:0:0:e1::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
Base6to4Interface ppp0;
};
};
IPv6 is provided via 6to4 off ppp0 public IP. If both interfaces are
enabled, eth0 IPv6 advertisements are seen on eth1 network. forwarding
is enabled for ipv6. This causes clients to get both e0 and e1 flavor
addresses. They choose the e0 flavor while on eth1 network and no ipv6
networks can be reached.
disabling radvd config for eth0 causes eth1 systems to get connectivity,
but then no eth0 connected hosts have connectivity.
== ApportVersion =
2.14.1-0ubuntu3.10
== Architecture =
amd64
== Date =
Thu Apr 30 23:34:08 2015
== Dependencies =
adduser 3.113+nmu3ubuntu3
apt-utils 1.0.1ubuntu2.7
debconf 1.5.51ubuntu2
debconf-i18n 1.5.51ubuntu2
debianutils 4.4
dpkg 1.17.5ubuntu5.4
gcc-4.8-base 4.8.2-19ubuntu1
gcc-4.9-base 4.9.1-0ubuntu1
libacl1 2.2.52-1
libapt-inst1.5 1.0.1ubuntu2.7
libapt-pkg4.12 1.0.1ubuntu2.7
libattr1 1:2.4.47-1ubuntu1
libaudit-common 1:2.3.2-2ubuntu1
libaudit1 1:2.3.2-2ubuntu1
libbz2-1.0 1.0.6-5
libc6 2.19-0ubuntu6.6
libdaemon0 0.14-2ubuntu1
libdb5.3 5.3.28-3ubuntu3
libgcc1 1:4.9.1-0ubuntu1
liblocale-gettext-perl 1.05-7build3
liblzma5 5.1.1alpha+20120614-2ubuntu2
libpam-modules 1.1.8-1ubuntu2
libpam-modules-bin 1.1.8-1ubuntu2
libpam0g 1.1.8-1ubuntu2
libpcre3 1:8.31-2ubuntu2
libselinux1 2.2.2-1ubuntu0.1
libsemanage-common 2.2-1
libsemanage1 2.2-1
libsepol1 2.2-1ubuntu0.1
libstdc++6 4.8.2-19ubuntu1
libtext-charwidth-perl 0.04-7build3
libtext-iconv-perl 1.7-5build2
libtext-wrapi18n-perl 0.06-7
libustr-1.0-1 1.0.4-3ubuntu2
multiarch-support 2.19-0ubuntu6.6
passwd 1:4.1.5.1-1ubuntu9
perl-base 5.18.2-2ubuntu1
sensible-utils 0.0.9
tar 1.27.1-1
zlib1g 1:1.2.8.dfsg-1ubuntu1
== DistroRelease =
Ubuntu 14.04
== NonfreeKernelModules =
nvidia
== Package =
radvd 1:1.9.1-1.1ubuntu2
== PackageArchitecture =
amd64
== ProblemType =
Bug
== ProcEnviron =
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
== ProcVersionSignature =
Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
== SourcePackage =
radvd
== Tags =
trusty
== Uname =
Linux 3.13.0-49-generic x86_64
== UpgradeStatus =
Upgraded to trusty on 2014-05-11 (354 days ago)
** Affects: radvd (Ubuntu)
Importance: Undecided
Status: New
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/1450707/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1442087] Re: don't run as root by default
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 are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1442087 Title: don't run as root by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1442087/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1442087] Re: don't run as root by default
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 modules there is the potential for abuse of both the running uid of spamd, and the uid of the username supplied by spamc (and this could be any user)." I'm not sure how many LOC but there is quite a slew of extra code with all the plugins that ship with SA. I question if all this code is maintained with the same attention and security awareness as other parts of the mail stack. I know all other parts are not executed as root. Of course statistics wouldn't have hurt ;-). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1442087 Title: don't run as root by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1442087/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1442087] [NEW] don't run as root by default
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 undermines the whole setup and comes a bit unexpected. I would suggest to create a separate unprivileged user (maybe spamd?) for running spamd only and keep the user debian-spamd for updating the rules. ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1442087 Title: don't run as root by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1442087/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308284] Re: catalina.properties points to wrong location for shared libraries and classes
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 "${catalina.base}" won't
work in all scenarios.
A good example is when you use the "tomcat7-user" package to install
multiple instances of Tomcat under different user accounts. In this
scenario, ${catalina.base} would point at the Tomcat user account
installation (which would NOT include these various common directories
by default), while ${catalina.home} would still point at
/usr/share/tomcat7/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1308284
Title:
catalina.properties points to wrong location for shared libraries and
classes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1308284/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1232258] Re: tomcat7 installer fails to create symbolic links
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 to
/var/lib/tomcat7/.
A good example is when you use the "tomcat7-user" package to install
multiple instances of Tomcat under different user accounts. In this
scenario, ${catalina.base} would point at the Tomcat user account
installation (which would NOT include these various common directories),
while ${catalina.home} would still point at /usr/share/tomcat7/
So, all in all, the correct solution here seems to be what was initially
recommended. The tomcat7 package should automatically add these three
symlinks to /usr/share/tomcat7/:
sudo ln -s /var/lib/tomcat7/common/ common
sudo ln -s /var/lib/tomcat7/server/ server
sudo ln -s /var/lib/tomcat7/shared/ shared
As far as I'm aware those are the only symlinks that should be necessary
to resolve this issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1232258
Title:
tomcat7 installer fails to create symbolic links
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1232258/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1232258] Re: tomcat7 installer fails to create symbolic links
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. https://bugs.launchpad.net/bugs/1232258 Title: tomcat7 installer fails to create symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/serverguide/+bug/1232258/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1232258] Re: tomcat7 installer fails to create symbolic links
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 instead of CATALINA_BASE.
So, for example, on Ubuntu 12.04, the default
/var/lib/tomcat7/conf/catalina.properties sets these properties as the
following:
server.loader=/var/lib/tomcat7/server/classes,/var/lib/tomcat7/server/*.jar
shared.loader=/var/lib/tomcat7/shared/classes,/var/lib/tomcat7/shared/*.jar
However, on Ubuntu 14.04, the hardcoded "/var/lib/tomcat7/" paths have
been replaced with "${catalina.home}", so it looks like this:
server.loader=${catalina.home}/server/classes,${catalina.home}/server/*.jar
shared.loader=${catalina.home}/shared/classes,${catalina.home}/shared/*.jar
Unfortunately, "${catalina.home}" translates to "/usr/share/tomcat7"...
which is not the proper setting. As we know, these directories don't
exist under "/usr/share/tomcat7" (CATALINA_HOME)
The correct setting should be replacing those with ${catalina.base}, as
all the referenced directories do exist under "/var/lib/tomcat7"
(CATALINA_BASE). So, the correct settings seem to be:
server.loader=${catalina.base}/server/classes,${catalina.base}/server/*.jar
shared.loader=${catalina.base}/shared/classes,${catalina.base}/shared/*.jar
This same misconfiguration existing in both of these catalina.properties files:
* /var/lib/tomcat7/conf/catalina.properties
* /usr/share/tomcat7/skel/conf/catalina.properties (installed by the
tomcat7-user package)
Obviously, creating the symbolic links from these directories in
/var/lib/tomcat7/ to /usr/share/tomcat7/ would also be a possible
solution. But, it's different than how things were setup in Ubuntu
12.04, when the configurations in catalina.properties were just using
CATALINA_BASE directly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1232258
Title:
tomcat7 installer fails to create symbolic links
To manage notifications about this bug go to:
https://bugs.launchpad.net/serverguide/+bug/1232258/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1417010] Re: Reloading services can result in a deadlock under systemd
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 under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1417010/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1328958] Re: Local provider fails when an unrelated /home/ubuntu directory exists
** 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. https://bugs.launchpad.net/bugs/1328958 Title: Local provider fails when an unrelated /home/ubuntu directory exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1402005] Re: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response'
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 apparmor 2.8.95~2430-0ubuntu5 amd64User-space parser utility for AppArmor ii cgmanager0.24-0ubuntu7 amd64Central cgroup manager daemon ii dh-apparmor 2.8.95~2430-0ubuntu5.1 all AppArmor debhelper routines ii libapparmor-perl 2.8.95~2430-0ubuntu5 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5 amd64changehat AppArmor library ii libcgmanager0:amd64 0.24-0ubuntu6 amd64Central cgroup manager daemon (client library) ii liblxc1 1.0.3-0ubuntu3 amd64Linux Containers userspace tools (library) ii lxc 1.0.3-0ubuntu3 amd64Linux Containers userspace tools ii lxc-templates1.0.3-0ubuntu3 amd64Linux Containers userspace tools (templates) ii python3-lxc 1.0.3-0ubuntu3 amd64Linux Containers userspace tools (Python 3.x bindings) $ ps -ef | egrep -e "(cgproxy|cgmanager)" root 348 1 0 Nov03 ?00:07:44 /sbin/cgmanager --sigstop -m name=systemd jenkins 10661 9679 0 18:36 pts/14 00:00:00 egrep -e (cgproxy|cgmanager) There are many containers on this host and I'm not sure which one(s) are being used, but regardless of which I pick I get the same result: jenkins@charm-bundle-slave:/var/lib/juju/containers$ sudo lxc-start -P /var/lib/juju/containers -n juju-trusty-lxc-template -L -l trace -o outout lxc-start: Permission denied - Failed to make / rslave lxc-start: failed to setup rootfs for 'juju-trusty-lxc-template' lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'juju-trusty-lxc-template' Advice? -- 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/1402005 Title: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1402005/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384555] Re: SQL error during alembic.migration when populating Neutron database on MariaDB 10.0
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. https://bugs.launchpad.net/bugs/1384555 Title: SQL error during alembic.migration when populating Neutron database on MariaDB 10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1384555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1386949] [NEW] Libvirt crashes after startup "/var/run/libvirt/uml-guest: No space left on device" after upgrade from 14.04 to 14.10
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 00:57:51.863+: 4809: error : umlStateInitialize:561 : Failed to create inotify watch on /var/run/libvirt/uml-guest: No space left on device 2014-10-29 00:57:51.863+: 4809: error : virStateInitialize:749 : Initialization of UML state driver failed: Unknown problem df -i shows plenty of space in the directory Filesystem Inodes IUsed IFree IUse% Mounted on tmpfs 1021899527 10213721% /run ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Attachment added: "libvirtd.log" https://bugs.launchpad.net/bugs/1386949/+attachment/4247687/+files/libvirtd.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1386949 Title: Libvirt crashes after startup "/var/run/libvirt/uml-guest: No space left on device" after upgrade from 14.04 to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386949/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1330120] Re: facter doesn't handle "can't open /proc/interrupts at /usr/bin/lsdev line 15."
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 /usr/bin/lsdev line 15." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1330120/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1330120] Re: facter doesn't handle "can't open /proc/interrupts at /usr/bin/lsdev line 15."
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 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 /usr/bin/lsdev line 15." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1330120/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1004494] Re: "Job not run" message after any attempt to run a job using bconsole
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1004494/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1339434] Re: Samba4 get stuck after a server reboot, if IPv6 is enabled.
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] ../source4/cldap_server/cldap_server.c:134(cldapd_add_socket) Sep 3 12:05:08 ubuntu smbd[982]: You should start 'samba' instead, and it will control starting smbd if required Sep 3 12:05:08 ubuntu samba[986]: Failed to bind to ipv6::XX:XXX::XXX::::389 - NT_STATUS_ADDRESS_NOT_ASSOCIATED Sep 3 12:05:08 ubuntu samba[986]: [2014/09/03 12:05:08.877964, 0] ../source4/smbd/service_task.c:35(task_server_terminate) Sep 3 12:05:08 ubuntu samba[986]: task_server_terminate: [cldapd failed to setup interfaces] Is there a upstart signal which is emitted after a successful ipv6 interface configuration? Samba4 DC is working when I login into the system and restart the service via initctl. I hope this helps tlapawa@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.1 LTS Release:14.04 Codename: trusty -- 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/1339434 Title: Samba4 get stuck after a server reboot, if IPv6 is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1339434/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1359421] Re: Update librtas for LE support
** Also affects: librtas (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: librtas (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: librtas (Ubuntu Utopic) Status: New => Fix Committed ** Changed in: librtas (Ubuntu Utopic) 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, which is subscribed to librtas in Ubuntu. https://bugs.launchpad.net/bugs/1359421 Title: Update librtas for LE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librtas/+bug/1359421/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1357103] Re: apparmor denied a golang build inside a container
** 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 inside a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1357103/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1356843] Re: ccs received early errors after openssl security update
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: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1356843/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1356843] Re: ccs received early errors after openssl security update
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 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1356843/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1342000] Re: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw
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: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1348386] Re: lxc template fails to stop
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 option -- 'L' Usage: lxc-start --name=NAME -- COMMAND lxc-start start COMMAND in specified container NAME Options : -n, --name=NAME NAME for name of the container -d, --daemon daemonize the container -f, --rcfile=FILELoad configuration file FILE -c, --console=FILE Set the file output for the container console -C, --close-all-fds If any fds are inherited, close them If not specified, exit with failure instead Note: --daemon implies --close-all-fds -s, --define KEY=VAL Assign VAL to configuration variable KEY Common options : -o, --logfile=FILE Output log to FILE instead of stderr -l, --logpriority=LEVEL Set log priority to LEVEL -q, --quiet Don't produce any output -?, --help Give this help list --usage Give a short usage message Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options. See the lxc-start man page for further information. ubuntu@clean-precise:~$ echo $? 1 -- 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/1348386 Title: lxc template fails to stop To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1348386/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1309860] Re: missing ipmi module
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1309860] Re: missing ipmi module
** 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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1330120] [NEW] facter doesn't handle "can't open /proc/interrupts at /usr/bin/lsdev line 15."
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 at /usr/bin/lsdev line 15. | info: Caching catalog for [redacted].stratoserver.net | info: Applying configuration version '1402765937' | notice: Finished catalog run in 0.20 seconds | root@[redacted]:~# cat /etc/os-release | NAME="Ubuntu" | VERSION="12.04.4 LTS, Precise Pangolin" | ID=ubuntu | ID_LIKE=debian | PRETTY_NAME="Ubuntu precise (12.04.4 LTS)" | VERSION_ID="12.04" | root@[redacted]:~# facter --version | 1.6.5 | root@[redacted]:~# puppet --version | 2.7.11 | root@[redacted]:~# The warning (?) comes apparently from the call to lsdev in /usr/lib/ruby/1.8/facter/util/processor.rb and in fact none of the paths referred to in lsdev exist on the virtual server: | root@[redacted]:~# lsdev -Cc processor | can't open /proc/interrupts at /usr/bin/lsdev line 15. | root@[redacted]:~# ls -l /proc/dma /proc/ioports /proc/interrupts | ls: cannot access /proc/dma: No such file or directory | ls: cannot access /proc/ioports: No such file or directory | ls: cannot access /proc/interrupts: No such file or directory | root@[redacted]:~# ** Affects: facter (Ubuntu) Importance: Undecided Status: New -- 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 /usr/bin/lsdev line 15." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1330120/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1290920] Re: template container contains user log mount in error
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-template and getting juju to recreate it fixed the problem for me. My template container was created about a week before the code landed in trunk. @pitti, can I get you to take a look inside the config file for the lxc container to see if you have a similar problem? ** Changed in: juju-core Assignee: Tim Penhey (thumper) => (unassigned) ** Changed in: juju-core Importance: High => Low ** Changed in: juju-core Milestone: next-stable => None ** Summary changed: - template container contains user log mount in error + non-default lxc-dir breaks local provider -- 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: non-default lxc-dir breaks local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1290920] Re: non-default lxc-dir breaks local provider
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. https://bugs.launchpad.net/bugs/1290920 Title: non-default lxc-dir breaks local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1290920] Re: fails to start container with local provider with non-default LXC path
** 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 of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: template container contains user log mount in error To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1309860] Re: missing ipmi module
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" https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+attachment/4129032/+files/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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1290920] Re: fails to start container with local provider with non-default LXC path
** 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 LXC path To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1290920] Re: fails to start container with local provider with non-default LXC path
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 created, the log mount points are added. What this means is that other users on the same machine will not be able to mount the log directory as specified in the container lxc config file, and the cgroup setting will fail. One solution to this is to have a template container per user rather than a shared one. ** Tags added: local lxc regression ** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Status: New => Triaged ** Changed in: juju-core 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/1290920 Title: fails to start container with local provider with non-default LXC path To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1272857] Re: apache2 crashed with SIGSEGV in ()
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 subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1272857 Title: apache2 crashed with SIGSEGV in () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1272857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1272857] Re: apache2 crashed with SIGSEGV in ()
I'm seeing exactly the same thing as #9. 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 XXX Auth_PG_database XXX Auth_PG_encrypted on Auth_PG_hash_type MD5 Auth_PG_pwd_table "view_users, view_groups" Auth_PG_uid_field view_users.login Auth_PG_pwd_field view_users.hashed_password Auth_PG_pwd_whereclause "AND view_users.login = view_groups.login AND view_groups.group_name = 'XXX'" [Wed Jun 04 15:23:35.226264 2014] [core:notice] [pid 22392:tid 139964758747008] AH00051: child pid 27013 exit signal Aborted (6), possible coredump in /etc/apache2 *** Error in `/usr/sbin/apache2': free(): invalid pointer: 0x7f4bf4038c50 *** [Wed Jun 04 15:23:36.228084 2014] [core:notice] [pid 22392:tid 139964758747008] AH00051: child pid 27012 exit signal Aborted (6), possible coredump in /etc/apache2 *** Error in `/usr/sbin/apache2': free(): invalid pointer: 0x7f4bf4038c50 *** *** Error in `/usr/sbin/apache2': free(): invalid pointer: 0x7f4bf4038c50 *** -- 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/1272857 Title: apache2 crashed with SIGSEGV in () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1272857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers
** 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 virtual servers To manage notifications about this bug go to: https://bugs.launchpad.net/keepalived/+bug/1300739/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers
** 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 Utopic) Importance: High Assignee: Dave Chiluk (chiluk) Status: Confirmed ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Dave Chiluk (chiluk) ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: Fix Committed => In Progress ** Changed in: linux (Ubuntu Utopic) Status: Confirmed => 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 virtual servers To manage notifications about this bug go to: https://bugs.launchpad.net/keepalived/+bug/1300739/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1309860] Re: missing ipmi module
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1309860] Re: missing ipmi module
** 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 Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1309860 Title: missing ipmi module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1315188] Re: No init.d script included in icehouse ubuntu packaging
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 commands don't work. Appears to be the same for all OpenStack services. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1315188 Title: No init.d script included in icehouse ubuntu packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1315188/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287222] Re: openssh-client 6.5 regression bug with certain servers
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 bug. -- 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 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1287222/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
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 http://wiki.qemu-project.org/download/qemu-1.5.3.tar.bz2 I debugged this issue further. I got the freebsd Images from a friend. They are modified with MSFBSD(http://mfsbsd.vx.sk/). Plain FreeBSD is also working fine (sorry for the wrong information in the above messages). I notifed the responsible developer Martin Matuška and waiting for his reply. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1315188] Re: No init.d script included in icehouse ubuntu packaging
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. https://bugs.launchpad.net/bugs/1315188 Title: No init.d script included in icehouse ubuntu packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1315188/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1309860] Re: missing ipmi module
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 Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1309860 Title: missing ipmi module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1309860] Re: missing ipmi module
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1309860] Re: missing ipmi module
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 Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1309860 Title: missing ipmi module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1306916] Re: cgroup-lite should be added as an explicit dependency
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 explicit dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1306916/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1208430] Re: mongodb runs as root user
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. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287222] Re: openssh-client 6.5 regression bug with certain servers
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 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1287222/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
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 qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
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. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1299934] [NEW] package samba-common 2:3.6.3-2ubuntu2.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
Public bug reported: Release: 12.04 Package version: 2:3.6.3-2ubuntu2.10 Was installing updates via the update manager and it failed, prompting me to report this as a bug. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: samba-common 2:3.6.3-2ubuntu2.10 ProcVersionSignature: Ubuntu 3.8.0-37.53~precise1-generic 3.8.13.18 Uname: Linux 3.8.0-37-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Mar 30 18:53:20 2014 DuplicateSignature: package:samba-common:2:3.6.3-2ubuntu2.10:subprocess installed post-installation script returned error exit status 255 ErrorMessage: subprocess installed post-installation script returned error exit status 255 MarkForUpload: True NmbdLog: PackageArchitecture: all SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package samba-common 2:3.6.3-2ubuntu2.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) WindowsFailedConnect: Yes ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- 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/1299934 Title: package samba-common 2:3.6.3-2ubuntu2.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1299934/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1298192] Re: hyper-v: Unable to take backups of Generation 2 VMs
** Also affects: hv-kvp-daemon-init (Ubuntu Trusty) Importance: Undecided Status: Confirmed ** Package changed: hv-kvp-daemon-init (Ubuntu Trusty) => linux (Ubuntu Trusty) ** Changed in: linux (Ubuntu Trusty) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Trusty) 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1298192/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
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 networking' ** Branch linked: lp:~thumper/juju-core/maas-no-restart-networking -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1292353] Re: juju must install the libgo.so.5 library when required
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 Status: Triaged => 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/1292353 Title: juju must install the libgo.so.5 library when required To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1292353/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** 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 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287222] Re: openssh-client 6.5 (multiple releases) regression bug with certain servers
** 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 certain servers -- 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 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1287222/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287222] [NEW] openssh-client 6.5p1 regression bug with certain servers
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 hostname [IPAddress] port 22. debug1: Connection established. debug1: identity file /home/nelsot08/.ssh/identity type -1 debug1: identity file /home/nelsot08/.ssh/identity-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version Cisco-1.25 debug1: no match: Cisco-1.25 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2p2 Ubuntu-6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 24:75:76:a1:80:0e:6c:4e:a8:c4:a6:a9:d3:34:98:18 Warning: Permanently added 'hostname,IPAddress' (RSA) to the list of known hosts. debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received But in 6.5p1 the following bug occurs: OpenSSH_6.5, 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 hostname [IPAddress] port 22. debug1: Connection established. debug1: identity file /home/nelsot08/.ssh/identity type -1 debug1: identity file /home/nelsot08/.ssh/identity-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_rsa type 1 debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa type -1 debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1 debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/nelsot08/.ssh/id_ed25519 type -1 debug1: identity file /home/nelsot08/.ssh/id_ed25519-cert type -1 debug1: Remote protocol version 2.0, remote software version Cisco-1.25 debug1: no match: Cisco-1.25 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.5p1 Ubuntu-4 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Connection closed by IPAddress This is a regression and there are multiple references to this bug occurring previously: http://www.held.org.il/blog/2011/05/the-myterious-case-of-broken-ssh- client-connection-reset-by-peer/ ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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.5p1 regression bug with certain servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1287222/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** 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/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
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: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** 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 architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1283850] [NEW] Spamassassin update broke Ubuntu GNOME daily builds
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: /usr/include/x86_64-linux-gnu/sys/types.h:146:20: fatal error: stddef.h: No such file or directory #include ^ compilation terminated. make: *** [body_0.o] Error 1 command 'make >>/tmp/.spamassassin25191JqnsNXtmp/log' failed: exit 2 dpkg: error processing package sa-compile (--configure): subprocess installed post-installation script returned error exit status 25 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: spamassassin 3.4.0-1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 24 10:24:47 2014 InstallationDate: Installed on 2012-09-23 (518 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) PackageArchitecture: all SourcePackage: spamassassin UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: spamassassin (Ubuntu) Importance: Critical Status: New ** Tags: amd64 apport-bug trusty ** Changed in: spamassassin (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1283850 Title: Spamassassin update broke Ubuntu GNOME daily builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1283850/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
** 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 service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
** 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 on trusty host service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
hallyn: has the autostart behaviour for lxc changed in trusty? thumper: yes, stgraber's new autostart setup may be in now. certainly in the ppa hallyn: yep, it landed with beta2 last week hallyn: hmm... managed to break juju's behaviour hallyn: can you explain the change? juju uses autostart? thumper: yes, autostart settings are now upstream and use the container's config instead hallyn: yep, thumper: I believe I already told someone this morning wrt juju thumper: use "lxc.start.auto = 1" in the container config stgraber: don't expect us to talk to each other :-) stgraber: remind me, is there any attempt at auto-conversion for /etc/lxc/auto/ users? hallyn: yes, there's migration code, but it won't do them much good for new juju containers heh yah any container on the system at the time of the upgrade to beta2 should have been automatically converted (symlink removed, /etc/lxc/auto removed and lxc.start.auto = 1 added to the container config) stgraber: is this lxc going into the cloud archive? stgraber: for precise? is there a way we can work out if this is supported? thumper: maybe hallyn knows, I usually ignore the existence of that external archive entirely -*- thumper nods thumper: rule of thumb would be, if /etc/lxc/auto exists, use it, if not, use lxc.start.auto = 1 stgraber: that makes sense... should be able to handle that pretty easily -- 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 service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
** 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/bugs/1271941 Title: lxc container creation fails on trusty host service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1258304] Re: lxc-create fails on IPv6 address
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:... which we then split up into bytes: 26 07 f0 88 and then represent as base 10: root@cps3:~/lxc# printf "%d.%d.%d.%d\n" 0x26 0x07 0xf0 0x88 38.7.240.136 anything that looks like address=ip is probably suspect. -- 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/1258304 Title: lxc-create fails on IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1258304/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1258304] Re: lxc-create fails on IPv6 address
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 - invalid ipv6 address: 38.7.240.136 lxc-create: Error creating container horizon-cps3 root@cps3:~/lxc# cat debug lxc-create 1386289012.783 WARN lxc_log - lxc_log_init called with log already initialized lxc-create 1386289012.784 ERRORlxc_confile - No such file or directory - invalid ipv6 address: 38.7.240.136 lxc-create 1386289012.785 ERRORlxc_create - Error creating container horizon-cps3 -- 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/1258304 Title: lxc-create fails on IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1258304/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1258304] [NEW] lxc-create fails on IPv6 address
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 horizon-cps3 -f horizon-cps3.net.conf -t ubuntu
-B none
lxc-create: Failed to create backing store type none
lxc-create: Error creating backing store type none for horizon-cps3
lxc-create: Error creating container horizon-cps3
root@cps3:~/lxc# lxc-create -n horizon-cps3 -f horizon-cps3.net.conf -t ubuntu
lxc-create: No such file or directory - invalid ipv6 address: 38.7.240.136
lxc-create: Error creating container horizon-cps3
The same template (different IP/mac) worked on raring.
root@cps3:~/lxc# dpkg -l lxc | awk '/lxc/ {print $3}'
1.0.0~alpha1-0ubuntu14
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/1258304
Title:
lxc-create fails on IPv6 address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1258304/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251352] Re: lxc fails to start on boot but succeeds with a manual boot
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 this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1251352 Title: lxc fails to start on boot but succeeds with a manual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251352] Re: lxc fails to start on boot but succeeds with a manual boot
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: <4>init: console-setup main process (46) terminated with status 1 <30>systemd-udevd[58]: starting version 204 Furthermore, there are only two processes running, rsyslogd and (after a painful dist-upgrade inside the lxc root) systemd-udevd. Rolling back to 1.0.0~alpha1-0ubuntu13 allows me to start the instance again (albeit manually). -- 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/1251352 Title: lxc fails to start on boot but succeeds with a manual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251352] [NEW] lxc fails to start on boot but succeeds with a manual boot
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: failed to setup the network for 'os-api-cps2'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'os-api-cps2'
root@cps2-c1:/var/log/upstart# cat network-interface-veth3ITMNG.log
ifdown: interface veth3ITMNG not configured
root@cps2-c1:/var/log/upstart# cat /etc/lxc/auto/os-api-cps2
# Template used to create this container: ubuntu
# Template script checksum (SHA-1): 6f468a9a658112f6420fb39d2ab90a80fd43cd22
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br18
lxc.network.name = eth0
lxc.network.hwaddr = 00:16:3e:00:02:68
lxc.network.ipv6 = **
lxc.network.mtu = 9000
lxc.rootfs = /var/lib/lxc/os-api-cps2/rootfs
lxc.mount = /var/lib/lxc/os-api-cps2/fstab
lxc.pivotdir = lxc_putold
lxc.devttydir = lxc
lxc.tty = 4
lxc.pts = 1024
lxc.utsname = os-api-cps2
lxc.arch = amd64
lxc.cap.drop = sys_module mac_admin mac_override
# When using LXC with apparmor, uncomment the next line to run unconfined:
#lxc.aa_profile = unconfined
lxc.cgroup.devices.deny = a
# Allow any mknod (but not using the node)
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
#lxc.cgroup.devices.allow = c 4:0 rwm
#lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
#fuse
lxc.cgroup.devices.allow = c 10:229 rwm
#tun
lxc.cgroup.devices.allow = c 10:200 rwm
#full
lxc.cgroup.devices.allow = c 1:7 rwm
#hpet
lxc.cgroup.devices.allow = c 10:228 rwm
#kvm
lxc.cgroup.devices.allow = c 10:232 rwm
Running "service lxc restart" results in the same errors.
Running "lxc-start -d -n os-api-cps2" from the command line successfully
starts the instance.
root@cps2-c1:/var/log/upstart# dpkg -l | grep lxc
ii liblxc0 1.0.0~alpha1-0ubuntu13 amd64
Linux Containers userspace tools (library)
ii lxc 1.0.0~alpha1-0ubuntu13 amd64
Linux Containers userspace tools
ii lxc-templates 1.0.0~alpha1-0ubuntu13 all
Linux Containers userspace tools (templates)
ii lxctl 0.3.1+debian-3 all
Utility to manage LXC
ii python3-lxc 1.0.0~alpha1-0ubuntu13 amd64
Linux Containers userspace tools (Python 3.x bindings)
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/1251352
Title:
lxc fails to start on boot but succeeds with a manual boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1240709] Re: local provider fails to 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1240709/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1246556] Re: lxc containers broken with maas
** 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1246556/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1229275] Re: [maas] juju destroy-environment also destroys nodes that are not controlled by juju
** 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 to maas in Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: [maas] juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210054] Re: juju terminate-machine with local provider doesn't destroy machine
** 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 Title: juju terminate-machine with local provider doesn't destroy machine To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1210054/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1219879] Re: [FFe] juju-core 1.16 for Ubuntu 13.10
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] juju-core 1.16 for Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1219879/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1229275] Re: juju destroy-environment also destroys nodes that are not controlled by juju
** 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 notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: [maas] juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1204302] Re: fails to bootstrap, returns error: no reachable servers
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1204302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210054] Re: juju terminate-machine with local provider doesn't destroy machine
** 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 you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1210054 Title: juju terminate-machine with local provider doesn't destroy machine To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1210054/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1178826] Re: spamassassin broken error control on bad UNIX socket parameter
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 with a bad invokation of spamc by Evolution. As far as I was concerned, the fundamental issue was actually why wasn't Evolution using my perfectly good system spamd instead of creating per- user ones and trying to use some complicated socket mechanism to communicate with it. Anyway, I fixed that issue by a handful of mods to the sources to change upstream source's mentions of /usr/bin/spamd to the correct /usr/sbin/spamd (and also one mention of /usr/sbin/spamc to the correct /usr/bin/spamc but I'm not sure if that was important as Evolution seems to find spamc just fine anyway ) and now I have Evolution using my system spamd as expected just fine. More details at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724884 ** Bug watch added: Debian Bug tracker #724884 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724884 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1178826 Title: spamassassin broken error control on bad UNIX socket parameter To manage notifications about this bug go to: https://bugs.launchpad.net/spamassassin/+bug/1178826/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1204507] Re: MAAS rejects empty files
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. https://bugs.launchpad.net/bugs/1204507 Title: MAAS rejects empty files To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1204507/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1201092] Re: Cannot load kvm_amd module - (says disabled by bios)
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 disabled by bios) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1201092/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210431] [NEW] syslog stops logging when lxc containers autostart
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 reboot fixed this problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Fri Aug 9 09:06:45 2013 InstallationDate: Installed on 2012-04-26 (469 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-02-22 (168 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug raring -- 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/1210431 Title: syslog stops logging when lxc containers autostart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1210431/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078213] Re: juju-machine-agent.log/logs are not logrotated
** 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: https://bugs.launchpad.net/juju-core/+bug/1078213/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1170801] [NEW] puppet needs to use ruby1.8
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 /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- facter (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/puppet.rb:9:in `' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/puppet/application.rb:272:in `initialize' from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:60:in `new' from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:60:in `execute' from /usr/bin/puppet:4:in `' Looking at facter, it is apparent that it is only available under ruby1.8: % dpkg-query -L facter | grep -c ruby/1.8 83 % dpkg-query -L facter | grep -c ruby/1.9 0 However, /usr/bin/puppet is set to use ruby-1.9.1. Manually changing it to use ruby1.8 allows puppet to start. Additionally, puppet (<3.x) is known to only run on ruby <1.9.x. # lsb_release -rd Description:Ubuntu Raring Ringtail (development branch) Release:13.04 # apt-cache policy puppet facter ruby ruby1.8 ruby1.9.1 puppet: Installed: 2.7.18-4ubuntu1 Candidate: 2.7.18-4ubuntu1 Version table: *** 2.7.18-4ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status facter: Installed: 1.6.9-2ubuntu1 Candidate: 1.6.9-2ubuntu1 Version table: *** 1.6.9-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ruby: Installed: 4.9 Candidate: 4.9 Version table: *** 4.9 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ruby1.8: Installed: 1.8.7.358-7ubuntu1 Candidate: 1.8.7.358-7ubuntu1 Version table: *** 1.8.7.358-7ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ruby1.9.1: Installed: 1.9.3.194-8.1ubuntu1 Candidate: 1.9.3.194-8.1ubuntu1 Version table: *** 1.9.3.194-8.1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: puppet (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: puppet (Ubuntu) Status: New => Invalid -- 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: puppet needs to use ruby1.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1170801/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1170801] Re: puppet needs to use ruby1.8
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: puppet needs to use ruby1.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1170801/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1158141] Re: apache2 forward proxy socket read error
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, where fixes have involved SELinux tweaking, so maybe it is a security problem. If an expert in apache2 forward proxying can help give me some steps to eliminate apache2 that would be great. Because this is an important tool to bypass internet censorship and because apache2 and proxytunnel are common tools, I hope that someone can provide guidance. -- 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/1158141 Title: apache2 forward proxy socket read error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1158141/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1158141] [NEW] apache2 forward proxy socket read error
Public bug reported: I have an ubuntu 12.04 LTS server. I've set up proxy server on apache2, on port 443. The server serves SSL web pages, and I can ssh to the server from a remote shell. I can connect to ssh with a password. I've set up proxytunnel so I can ssh to it from anywhere. But it's 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 -d 127.0.0.1:22 -N -P tim -v Enter local proxy password for user tim: Build Type 1 NTLM Message : TlRMTVNTUAABAAeCCKIAAA== Local proxy ec2.growthpath.com.au resolves to 54.243.214.78 Connected to ec2.growthpath.com.au:443 (local proxy) Tunneling to 127.0.0.1:22 (destination) Communication with local proxy: -> CONNECT 127.0.0.1:22 HTTP/1.0 -> Proxy-Authorization: NTLM TlRMTVNTUAABAAeCCKIAAA== -> Proxy-Connection: Keep-Alive error: Socket read error. On the server, I have defined - ProxyRequests On AllowCONNECT 22 ProxyViaOn Order deny,allow Deny from all Order deny,allow Allow from all apachectl -t -D DUMP_MODULES /usr/sbin/apachectl: 87: ulimit: error setting limit (Operation not permitted) [Thu Mar 21 06:18:29 2013] [warn] NameVirtualHost *:80 has no VirtualHosts Loaded Modules: core_module (static) log_config_module (static) logio_module (static) mpm_worker_module (static) http_module (static) so_module (static) alias_module (shared) auth_basic_module (shared) authn_file_module (shared) authz_default_module (shared) authz_groupfile_module (shared) authz_host_module (shared) authz_user_module (shared) autoindex_module (shared) cgid_module (shared) deflate_module (shared) dir_module (shared) env_module (shared) expires_module (shared) headers_module (shared) mime_module (shared) negotiation_module (shared) proxy_module (shared) proxy_connect_module (shared) proxy_html_module (shared) proxy_http_module (shared) reqtimeout_module (shared) setenvif_module (shared) ssl_module (shared) status_module (shared) wsgi_module (shared) Syntax OK ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: apache2 -- 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/1158141 Title: apache2 forward proxy socket read error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1158141/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1155146] Re: samba segfaults when LTS enablement stack is installed
*** 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 with SIGABRT in dump_core()/setgroups being passed a -1 group is causing crashes. -- 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/1155146 Title: samba segfaults when LTS enablement stack is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1155146/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
