Simo
Go ahead an propose the patch you are thinking on.
Best!
On Monday, June 29, 2015, Simo Punnonen simo.punno...@f-secure.com
wrote:
is the lo_name which gets stored in the loop_info structure actually
required to be an actual file path or is it enough to be an arbitrary
string
cat /proc/self/cgroup
10:cpuset:/system.slice/lsh-server.service
9:memory:/system.slice/lsh-server.service
8:freezer:/system.slice/lsh-server.service
7:blkio:/system.slice/lsh-server.service
6:hugetlb:/system.slice/lsh-server.service
5:perf_event:/system.slice/lsh-server.service
is the lo_name which gets stored in the loop_info structure actually
required to be an actual file path or is it enough to be an arbitrary
string identifier?
If it doesn't have to be a file path, could it be for instance a sha1
hash of the provided path? That fits into 40 chars and is relatively
Hand-built packages from:
https://launchpad.net/~monotek/+archive/ubuntu/qemu-glusterfs-3.6?field.series_filter=trusty
** Attachment added: hand-built packages
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1464278/+attachment/4421909/+files/list_hand-built_packages
--
You received
I still don't get the point about lsh - I mean what's the difference
with openssh? Are there some specific step by ssh server with regards to
user session setup necessary? Or some specific system-wide configuration
required somewhere?
--
You received this bug notification because you are a
** Package changed: ubuntu = libvirt (Ubuntu)
--
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/1468247
Title:
Libvirt patches needed for 15.04 ppc64le
To manage notifications about
Thanks for the example config.
The client will encode the identity as FQDN and the server is forced to
encode it as keyid (the content will be the same but the type is
different). So there won't be a match. Looking at the screenshot I'm not
sure how to configure a FQDN in the pfSense GUI, perhaps
list all packages.
** Attachment added: list_all_packages
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1464278/+attachment/4421887/+files/list_all_packages
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
5.5 superceded in = Vivid = Won't Fix. Fixed in 5.6. Could be SRU'd if
bundled in with some other updates, so no objection to bug tasks for
specific stable releases.
** Changed in: mysql-5.5 (Ubuntu)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a
** Branch linked: lp:~cloudware/ubuntu/vivid/cloud-init/vivid-wip
** Branch linked: lp:~cloudware/ubuntu/trusty/cloud-init/trusty-wip
** Branch linked: lp:~cloudware/ubuntu/precise/cloud-init/precise-wip
--
You received this bug notification because you are a member of Ubuntu
Server Team,
From kvm_pc_setup_irq_routing() function, we can see that 15 routes from
PIC and 23 routes from IOAPIC are added into irq route table, but only
23 irq(gsi) are reserved. This leads to irq route table has been full
but there are still tens of free gsi. So the retry part of
kvm_irqchip_get_virq()
This is the diff from 1.22.5 to 1.22.6
http://pastebin.ubuntu.com/11793455/
--
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/1469744
Title:
[needs-packaging] 1.22.6 is not packaged
Hi Robie.
I opened a new bug to track the specific request of placing 1.22.6 into
trusty. I have prepared a new source package branch using the trusty
1.22.5 branch I proposed for bug 1462001.
We can see src/github.com/juju/txn changed; review the change for
copyright issues. The only change is
Public bug reported:
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Stable Fix]
[sinzui] Prepare source
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 1465935
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and
is lsh somehow not triggering pam_systemd?
--
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/1467611
Title:
unprivileged lxc containers broken
To manage notifications about this bug go
I already fixed this. Make the following changes on the
/etc/init.d/samba
-- Change /etc/init.d/ on every line on the file with sudo service
-- Move the line 24 to line 26, above ;;
Your file must look like the attachment (more or less).
** Attachment added: Patch
** 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 maas in Ubuntu.
https://bugs.launchpad.net/bugs/1273197
Title:
maas-cluster-controller does not update pserv.yaml
How does this triggering happens normally? I mean should ssh server call
something specific explicitly?
--
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/1467611
Title:
unprivileged lxc
This issue has been verified to work both on upgrade and fresh install,
and has been QA'd. Marking verification-done.
--
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/1387859
Title:
This issue has been verified to work both on upgrade and fresh install,
and has been QA'd. Marking verification-done.
** 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
** Description changed:
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Stable Fix]
-
This issue has been verified to work both on upgrade and fresh install,
and has been QA'd. Marking verification-done.
** 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
This issue has been verified to work both on upgrade and fresh install,
and has been QA'd. Marking verification-done.
** 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
** 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 maas in Ubuntu.
https://bugs.launchpad.net/bugs/1387859
Title:
When MAAS has too many leases, and lease parsing
This issue has been verified to work both on upgrade and fresh install,
and has been QA'd. Marking verification-done.
** 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
This issue has been verified to work both on upgrade and fresh install,
and has been QA'd. Marking verification-done.
** 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
This issue has been verified to work both on upgrade and fresh install,
and has been QA'd. Marking verification-done.
** 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
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
--
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/1469744
Title:
[needs-packaging] 1.22.6 is
Thanks, workaround posted to lxc-devel mailing list.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1468611
Title:
dnsmasq fails to start in lxc-net
To manage notifications about
You have been subscribed to a public bug:
virsh edit domain
fails with the following error :
# virsh edit 7
error: XML document failed to validate against schema: Unable to validate doc
against /usr/share/libvirt/schemas/domain.rng
Extra element os in interleave
Element domain failed to validate
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read How to report bugs effectively
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to uvtool in Ubuntu.
https://bugs.launchpad.net/bugs/1459748
Title:
libvirt.libvirtError: internal error:
Public bug reported:
1. % lsb_release -rd
Description:Ubuntu Wily Werewolf (development branch)
Release:15.10
2. % apt-cache policy libvirt-bin
libvirt-bin:
Installed: 1.2.15-0ubuntu4
Candidate: 1.2.15-0ubuntu4
Version table:
*** 1.2.15-0ubuntu4 0
500
** Also affects: python-oslo.log (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1385295
Title:
use_syslog=True does not log to
Have you be able to reproduce this issue on a wily host? What about a
different guest? Or is only RHEL6.3 affected?
--
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/1465935
Title:
It appears that the latest version of the patch is here:
http://lists.gnu.org/archive/html/qemu-devel/2015-01/msg00822.html
However, this hasn't yet be accepted upstream. The most recent
discussion requires the submitter to respond to the maintainers
questions here:
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
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/1465935
Title:
kvm_irqchip_commit_routes: Assertion `ret ==
cat /proc/self/cgroups
cat: /proc/self/cgroups: No such file or directory
Hmm.. what ssh server have to do with this?
** Changed in: systemd (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
If i understand correctly, the fix is to compare only the first 63 chars
of the path.
With kpartx the precise file path matters in resolving the correct loop
device, the suggested solution has the following consequence:
Assuming all loop devices are available, these commands succeed and
mount
This feature has been disabled due to the security risks of using arguments
with NRPE.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756479
** Bug watch added: Debian Bug tracker #756479
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756479
--
You received this bug notification
So that seems to be an artifact of using lsh-server? After ssh'ing in,
please copypaste the output of cat /proc/self/cgroups
** Changed in: systemd (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
@Curtis, we are seeing this with juju 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/1316272
Title:
juju destroy-environment =256 nodes fails
To manage notifications about
I meant /proc/self/cgroup, sorry.
what ssh server have to do with this?
Because your process is in /system.slice/lsh-server.service, which your
user cannot access.
** Changed in: systemd (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nagios-plugins (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
Also seeing this same issue with Ubuntu 14.04 LTS on a Dell XPS 13
Developer's Edition.
--
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/997927
Title:
NM reports VPN service
[Expired for mysql-5.6 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-5.6 (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
The root users .ssh/known_hosts is also getting polluted by 'juju run',
which is causing subsequent 'juju run' commands to fail when IP
addresses are recycled.
I'm also seeing IP addresses recycled much more often, especially with
the local provider which now reuses them immediately.
** Changed
I think this is dependent on security bug #892552
--
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/802117
Title:
juju ssh/scp/run commands cause spurious key errors
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: neutron (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
http://lists.gnu.org/archive/html/qemu-devel/2015-01/msg00822.html
Seems that the latest version code has answered maintainers questions.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Ryan,
Our Hypervisors are running in the internal network which can't access to
Launchpad,
# apport-collect 1465935
ERROR: connecting to Launchpad failed: [Errno 110] Connection timed out
We saw this qemu crash on 18 Hypervisor nodes. So far all our
hypervisors are ubuntu 12.04,
53 matches
Mail list logo
