Hmmm, that's an old one. IIRC the real root cause was, that some files
possibly included via /usr/share/lxc/config/ubuntu.common.conf still
used lxc.cgroup.devices.* instead of lxc.cgroup2.devices.* (the machine
was upgraded from bionic to focal).
--
You received this bug notification because
Public bug reported:
If one starts dhcrelay with explicitly specifying the interfaces to
listen,it silently ignores these options and still listens on all
interfaces. This is neither what the man page says (it says, only if no
interface is given, it listen on all interfaces), nor what is needed.
So you suggest to break several hundred scripts written on/for standard
conforming platforms (i.e. not only for Linux) within the last 30 years
just because of bogus grub scripts? IMHO not a smart idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
FWIW: /usr/sbin/grub-probe is also posixly incorrect, e.g.:
# export POSIXLY_CORRECT=1
# /usr/sbin/grub-probe --device /dev/sda2 --target=partmap
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda2. Check
your device.map.
# unset POSIXLY_CORRECT
# /usr/sbin/grub-probe --device
The package is still broken (at least on focal) and outdated!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892372
Title:
oomd does not start
To manage notifications about this bug go to:
Public bug reported:
Since focal a casual unprivileged user cannot save the current X Server
Display Configuration, no matter which location is used. I.e. even for
e.g. /tmp/xorg.conf or /home/$LOGNAME/xorg.conf the user gets asked for
the root password.
This really stupid '"AUTHENTICATING FOR
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
lxc-stop -r -n $zone
Stops the container, but does not reboot it anymore, as in bionic.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
If one sets in /etc/default/grub (as e.g. desired by facebook oomd):
GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=1 swapaccount=1 ..."
lxc is not able to start any
There is no apport* installed on the machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905160
Title:
zfs-initramfs: zfs import rpool fails - too early
To manage notifications about this bug
** Attachment added: "debug output with Q fix"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1905160/+attachment/5436799/+files/xxxlong-patched.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
/usr/share/initramfs-tools/scripts/zfs::import_pool() tries to import
the root pool (in my case named rpool) before the related devices are
available, i.e. scsi scan has been finished.
I use the following Q workaround to fix it:
---
juliank: unset right before and restore after the call. It would not
screw up anything. The user does not know, what the script does (and
IIRC it didn't call zfs.mount in pre-focal versions). So the script has
to take care of what it does.
xnox: I do not think, that this fixed the problem. Just
Public bug reported:
If one has POSIXLY_CORRECT env var set (which is the case for all our
admin/operator accounts) and one calls /usr/sbin/update-grub or grub-
mkconfig ... it produces a /boot/grub/grub.cfg with a single entry 'UEFI
Firmware Settings' (fwsetup). So the after a reboot the OS is
Hmm, but https://github.com/jselbie/stunserver does not look like
stalled maintenance ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876541
Title:
stuntman-client is missing
To manage
Hmm, this includes stuntman-client? I do not care about stuntman-server,
because coturn seems to be sufficient, but having no proper CLI utility
is hard ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
focal does not provide a stuntman-client packages like in previous
releases (bionic, xenial). This is very bad because now one is not able
to test/use e.g. coturn or other STUN servers.
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status:
Łukasz Zemczak, yes, upgraded a machine from bionic to focal - same
problem. However, the patch looks not optimal but sufficient.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868892
Title:
Perhaps I should add, that this renders the machines un-bootable,
because several scripts require ksh93, e.g. udev scripts, which create
the device links for zpool related devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
An upgrade from bionic to focal as described on https://linuxconfig.org
/how-to-upgrade-ubuntu-to-20-04-lts-focal-fossa via do-release-upgrade
-d breaks the system, because ksh93 gets removed and the incompatible,
experimental ksh2020 gets installed.
Don't do that. ksh2020
Public bug reported:
If one needs to install libmysqlclient-dev (e.g. because python3-mysqldb
is too old/unusable), npm/nodejs get uninstalled, which breaks react
applications running on the server. If one in turn installs npm,
libmysqlclient-dev gets removed. That's a major bug/inconsistency
Hi Jeff,
hmm, didn't get notified by launchpad about your answer :(((. Anyway,
tried another machine with 4.15.0-91-generic and indeed, it seems to be
fixed.
Now the problem is, that our GPU machines are running 4.15.0-58-generic
and cannot be upgraded because all the nvidia stuff is very picky
Getting it all the time:
[Apr13 04:28] kino6_0: hw csum failure
[ +0.003777] CPU: 18 PID: 0 Comm: swapper/18 Tainted: P OE
4.15.0-58-generic #64-Ubuntu
[ +0.03] Hardware name: GIGABYTE G291-281-00/MG51-G21-00, BIOS R06
11/19/2019
[ +0.01] Call Trace:
[ +0.03]
[
Public bug reported:
If one creates e.g. /etc/systemd/network.cu and /etc/systemd/network.fc
and symlinks /etc/systemd/network to one of them, network setup will
fail on reboot, because /usr/share/initramfs-tools/hooks/udev does a
very poor job: it simply checks for a directory instead of the
kdump package is crap, because it is using a different image (initrd)
than update-initramfs creates, so /boot/initrd.img-* !=
/var/lib/kdump/initrd.img-* . Yes, they may have the same name, but not
the same content. What a hugh bullshit! So no wonder, why one has to
waste several hours to find
We use 'Linux kino6 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux' (Ubuntu 18.04.3 LTS) and see
all the time 'hw csum failure's:
[ +28.297139] kino6_0: hw csum failure
[ +0.003607] CPU: 12 PID: 0 Comm: swapper/12 Tainted: P O
Same here - it is a nightmare:
(Wed Mar 4 16:19:36 2020) [sssd[be[LDAP]]] [resolv_gethostbyname_done]
(0x0040): querying hosts database failed [5]: Input/output error
(Wed Mar 4 16:19:36 2020) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020):
Failed to resolve server 'ldap': Could not
Basically yes. When I do a 'dpkg -L libxen-dev|grep xenstat' I get:
/usr/include/xenstat.h
/usr/lib/x86_64-linux-gnu/pkgconfig/xenstat.pc
When doing a 'grep xenstat /usr/lib/x86_64-linux-gnu/pkgconfig/xenstat.pc' one
gets
Libs: -L${libdir} -lxenstat
Unfortunately, when I do 'dpkg -L
No, neither libxen-4.9 nor libxen-dev contains it. To confirm, just do a
dpkg -L libxen-dev libxen-4.9 |grep xenstat
One should see a libxenstat.so, but unfortunately this is not the case
...
** Changed in: xen (Ubuntu)
Status: Invalid => New
--
You received this bug notification
Public bug reported:
libxen-dev package contains /usr/include/xenstat.h but unfortunately the
related static lib and the dyn lib package libxen-4.9 doesn't contain it
either. Would be nice to add it at least to the libxen-4.9 so that one
does not need to install all the other huge bloat just to
Public bug reported:
# apt install lxc-templates
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
busybox-static cloud-image-utils debootstrap dirmngr distro-info genisoimage
gnupg gnupg-l10n
Public bug reported:
> + do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,263 kB]
Fetched 1,264 kB in 0s (0 B/s)
** Package changed: linux (Ubuntu) => libdbi-perl (Ubuntu)
** Changed in: libdbi-perl (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800861
Title:
Public bug reported:
/usr/lib/x86_64-linux-gnu/perl5/5.22/DBI.pm (xenial with latest updates) is
buggy.
To test, simply run:
---schnipp---
#!/usr/bin/perl
require DBI;
my $dbfile = "/tmp/notifications_sqlite.dat";
my $dbh = DBI->connect("dbi:SQLite:dbname=$dbfile",'','');
my $qu_attr =
Public bug reported:
The current ksh package (xenial and probably other releases as well)
have a pointless dependency to binfmt-support. It should be removed,
because a) it is not needed and b) because binfmt-support package is
useless in non-global containers (lxc). And c) it really sucks, if
Aha - using usually Solaris zones, which have no such distinctions...
Anyway, in this case: yes, all our linux containers are privileged, which seems
to be the default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmmm, not sure what "privileged container" means. Most machines are on xenial
now and use
lxc.aa_profile = lxc-container-default-cgns-with-mounting
if this is the question.
This way mounting manually as well as automatically via automount works,
but mounting something via the '-hosts' builtin
No, this is not an option. Also note, that this breaks a lot of
workflows without reason, because Ubuntu ssh client simply stops
working with a message like "~/.ssh/config line 3: Bad SSH2 cipher spec
'...'": it simply does not know such ciphers (does not ignore them). So
especially in
Yes, this (the missing entries) fixed the problem (used
'ldap_autofs_entry_value = automountInformation') as mentioned in the
URLs you gave.
Thanx a lot :) ,
jel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In bionic openssh client/server ships without blowfish-cbc, arcfour,
arcfour128, arcfour256 and cast128-cbc. Unfortunately they are required
for backward compatibility, especially for embedded devices, which do
not support other ciphers (e.g. Rittal Liquid Cooling Package for
Yes, correct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767886
Title:
sssd-ldap breaks automount on bionic
To manage notifications about this bug go to:
Public bug reported:
sssd in bionic (1.16.1) breaks automounting because it does neither
follow RFC 2307bis-02 nor obeys sssd.conf settings like:
ldap_schema = rfc2307
ldap_autofs_map_object_class = automountMap
ldap_autofs_map_name = automountMapName
ldap_autofs_entry_key = automountKey
On
Public bug reported:
xenial: Linux ares 4.4.0-78-generic #99-Ubuntu SMP Thu Apr 27 15:29:09
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
If one tries to install openjdk-9-source as well as openjdk-9-jdk, installation
breaks because a) both packages have a
Since xenial we have this very annoying behavior (unregister_netdevice:
waiting for lo to become free. Usage count = 1) as well, which in turn
makes a container reboot taking several minutes instead of seconds e.g.
on vivid (lxc-ls -f also hangs for that time). E.g.:
[ +10.244888]
This was on trusty/vivid/wiley and just tried on xenial with latest
updates: same thing:
diff -u sssd.conf.ok sssd.conf
--- sssd.conf.ok2017-09-27 04:41:37.686277498 +
+++ sssd.conf 2017-09-27 04:43:10.589649195 +
@@ -26,7 +26,7 @@
ssh_known_hosts_timeout = 180
Actually this is the problem: Users think, their system is up-to-date,
but it is not for sure because a site failed to respond. Therefore only
if _all_ sites answered the request properly, apt-get should return 0.
If not, it should return a specified return code, which lets the callee
know, that
The bug/subject here is, that apt-get doesn't return a proper exit code,
not, what else one could use to workaround the bug.
Saying, that update from one of all (i.e. 1+) sites is sufficient is
like going to fly with a jet, where one of two engines is already broken
before it starts. Making this
Public bug reported:
In earlier gnome-terminal versions one was able to hide gnome-terminal
menubar by default using ProfileSettings - General - Show Menubar. This
setting is not available anymore and thus there seems to be no way to
hide the menubar by default. This is extremly annoyingly.
Env
Public bug reported:
cinnamon-control-center (ccc) is missing dependencies to the packages
'gettext' as well as 'xdg-utils'. So e.g. if one has installed the
cinnamon-desktop-environment in a 'ubuntu-minimal' environment,
installing applets via the ccc's 'applet' settings "dialog" from online
It might be also a result of the bogus mount.zfs, which requires POSIX
incorrect arguments but honors POSIXLY_CORRECT env var!
Had a similar zfs mount order problem with a rpool/local/home/{A,B,C}
tree (was created using -p option) ...
--
You received this bug notification because you are a
Hmmm, IMHO 'Err:' and 'W: Failed to fetch' indicate, that it was not
able to update properly and thus the result of the operation is
unreliable. So its like "your connection is secured, but may be not". I
guess most people wouldn't do any financial transaction when reading
this ... ;-)
--
You
Please read carefully before answering: As already said (and the given
output clearly shows the problem beside being mentioned in the subject):
zfs screwed up the mount order and mounted rpool/VARSHARE/lxc _before_
rpool/VARSHARE. And when /var/share/lxc gets mounted, obviously
/var/share is not
Public bug reported:
I've the following zfs:
# zfs list -r rpool/VARSHARE
NAME USED AVAIL REFER MOUNTPOINT
rpool/VARSHARE 114K 165G30K /var/share
rpool/VARSHARE/lxc84K 165G19K /var/share/lxc
Public bug reported:
ksh does not depend on any binfmt-support, however such a bogus
dependency is declared in its metadata aka control file. This should be
removed.
One problem e.g. occurs in linux containers, where one does not want
binfmt-support, because useless and just causing problems: It
Public bug reported:
When running 'apt-get update' (e.g. on a container install post-install
script), apt-get return with exit code 0, even so it wasn't able to
"update" properly. E.g.:
+ apt-get update
Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving
AFAICS the problem is libmount/src/context_mount.c:exec_helper() which
is uses operands in a wrong/not posixly incorrect way. See also
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
mount from util-linux 2.27.1 (libmount 2.27.0: selinux, assert, debug)
Description:Ubuntu 16.04.2 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692109
Title:
mount is broken/misbehaving
Public bug reported:
"/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil
rpool/zones/bla /zones/bla"
fails, if env var POSIXLY_CORRECT is set, because it calls
"/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is obviously
a bug. Options should always come first
*** This bug is a duplicate of bug 1527727 ***
https://bugs.launchpad.net/bugs/1527727
No ETAs, when the backport is available for the LTS release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Wondering, whether there is an official repository, where one may look
into the source of the shipped version of the package. I found
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.9, but
even the grub2_2.02~beta2.orig.tar.xz is != to what is tagged as
grub-2.02-beta2 in the
BUG or not? At least I get mixed feelings, when I see, that the log
device gets passed to grub-probe! E.g.:
+ zpool status rpool
pool: rpool
state: ONLINE
scan: resilvered 547M in 0h0m with 0 errors on Thu May 18 03:49:08 2017
config:
NAME STATE READ WRITE CKSUM
BTW: Just encountered, that netinstall fails, when it tries to install
grub, because /sys seems not to be mounted to /target/sys:
# zpool status
The ZFS modules are not loaded.
Try running '/sbin/modprobe zfs' as root to load them.
After a mount --rbind /sys /target/sys :
# zpool status
Public bug reported:
Since on common platforms ureadahead solves nothing but causes a huge
amount of garbage/totally useless error messages, which makes it really
hard to extract the important messages from e.g. journalctl output, it
should be removed from ubuntu-minimal. If there are people,
It should not restrict import to hardcoded /dev and /dev/disk/by-id -
see https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1688890
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685528
Title:
** Patch added: "honor misc /dev dirs"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1688890/+attachment/4872753/+files/initramfs-zfs.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Right now 'zfs-initramfs', i.e. /usr/share/initramfs-tools/scripts/zfs
does not support any other directory than /dev for "zpool import ...".
Therefore even if a pool gets created from a different directory like
/dev, say /dev/disk/by-id or /dev/chassis/SYS on next reboot
Seems, that this package gets included via preseed:
tasksel tasksel/first multiselect minimal
d-i pkgsel/include string grub2 linux-crashdump openssh-server tcsh ksh gawk
vim sysstat lxc debootstrap libcap-ng-utils acpid at bc ethtool libxslt1.1
lxc-templates patch uidmap xz-utils acl iptables
~ # sed -i.orig -e '/^set/ a\set -x'
/target/var/lib/dpkg/info/kdump-tools.postinst
~ # tail -f /var/log/syslog
May 5 12:11:29 in-target: linux-crashdump depends on kdump-tools; however:
May 5 12:11:29 in-target: Package kdump-tools is not configured yet.
May 5 12:11:29 in-target:
May 5
Studied /etc/grub.d/10_linux a little bit deeper and found out, that the
'grub-mkrelpath /' is probably expected, but the way, how $rpool gets
determined is buggy (and in this case it results into an empty string).
Attaching a patch, which resolves the problem for me (just deduces it
from whatever
** Patch added: "grub-cfg.patch"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1688424/+attachment/4872219/+files/grub-cfg.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688424
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename: xenial
Not sure, why it is made that complicated. IMHO the only thing to know is the
name or ID of the pool, that contains the / dataset. Then initramfs
Public bug reported:
If zfs is used for boot, boot will fail because of bogus information returned by
/usr/bin/grub-mkrelpath. E.g. if the zfs dataset for / is rpool/ROOT/linux:
# /usr/bin/grub-mkrelpath /
/ROOT/linux@
This leads to a bogus /boot/grub/grub.cfg because /etc/grub.d/10_linux
Hi Christian,
Yepp, the patch looks good. Would be nice to get this integrated (or to
sync dmidecode with the current GNU version).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688162
Title:
BTW: the netcfg of the current netboot image (xenial) coredumps very
often, is absolutely unreliable now. Shuold be replaced by udhcpc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363681
Title:
Public bug reported:
Ubuntu version of dmidecode breaks several scripts because it prints
diagnostics messages to stdout instead of stderr.
E.g.: sudo /bin/ksh93
# /usr/sbin/dmidecode -s baseboard-manufacturer 2>/dev/null
Supermicro
Invalid entry length (16). Fixed up to 11.
The original
FWIW: Found another case, where grub2 fails:
May 3 15:37:28 in-target: grub-common is already the newest version
(2.02~beta2-36ubuntu3.9).
May 3 15:37:28 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not
upgraded.
May 3 15:37:28 main-menu[422]: (process:4764): grub-probe:
Public bug reported:
When installing Ubuntu xenial via netimage, installation fails because
of an error, when configuring the kdump-tools. /var/log/syslog says:
...
May 2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M
May 2 22:15:17 in-target: Setting up lxc-common
Done - see 1687664.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527727
Title:
grub-probe for zfs assumes all devices prefix with /dev, ignoring
/dev/disk/...
To manage notifications about
Public bug reported:
grub-probe /
fails with grub-probe: error: failed to get canonical path of
`/dev/HDD0p2'. This is simply because grub makes the wrong assumption,
that "zpool status $pool" lists the vdevs in use only with the '/dev/'
prefix stripped off. It probably assumes something like
Just encountered the same problem with xenial:
grub-probe: error: failed to get canonical path of `/dev/HDD0p2'
See also http://savannah.gnu.org/bugs/?50896
IMHO "zpool status -P $pool" should be used, everything else is a
kludge, which will fail sooner or later.
** Bug watch added: GNU
Public bug reported:
zfs modules as well as zfs-utils are not available in the current
netboot image and thus it is useless. Also partman does not contain the
related support even so an upstream repo seems to exits for a long time:
see https://anonscm.debian.org/cgit/d-i/partman-zfs.git
**
Yepp, tcsh_6.18.01-5ubuntu0.16.10.1_amd64.deb seems to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618803
Title:
tcsh crashed with SIGSEGV in __GI___rewinddir()
To manage notifications
Not sure, why launchpad shows 'Affects: unity' - I definitely selected
package 'dkms' ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638374
Title:
/usr/sbin/dkms: line 193: syntax error near
Public bug reported:
bash-4.3$ + dpkg --configure nvidia-367
Setting up nvidia-367 (367.57-0ubuntu3) ...
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia-367
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing
Public bug reported:
When a users having tcsh as its [login] shell presses tab key
(autocompletion), tcsh coredumps immediately, always:
admin.python ~ > gdb tcsh
GNU gdb (Ubuntu 7.11.90.20160906-0ubuntu1) 7.11.90.20160906-git
...
(gdb) run
Starting program: /local/home/admin/tcsh
admin.python
Today I upgraded our last utopic containers (~10) to vivid using do-
release-upgrade: Everywhere the same: after reboot systemd is the only
thing which is running in the container, but nothing else happens. It
doesn't start anything! So the only way to get the stuff fixed is to
manually attach to
Today I upgraded our last utopic containers (~10) to vivid using do-
release-upgrade: Everywhere the same: after reboot systemd is the only
thing which is running in the container, but nothing else happens. It
doesn't start anything! So the only way to get the stuff fixed is to
manually attach to
I'm running utopic with latest updates. Any container, which has systemd
running simply hangs, when /sbin/init gets started (no matter, whether
config has 'lxc.kmsg = 0' or not). Tried it previously with a trusty and
today with a vivid container. So wondering, whether there is a bugfix
available
I'm running utopic with latest updates. Any container, which has systemd
running simply hangs, when /sbin/init gets started (no matter, whether
config has 'lxc.kmsg = 0' or not). Tried it previously with a trusty and
today with a vivid container. So wondering, whether there is a bugfix
available
It appears, that something is still broken. Because systemd doesn't
work, I installed upstart + upstart-sysv (and uninstalled systemd-
sysv), but unfortunately sssd doesn't come up (has exactly the same
config, as in other 14.10 zones, where it works as expected). And
because sssd doesn't come
It appears, that something is still broken. Because systemd doesn't
work, I installed upstart + upstart-sysv (and uninstalled systemd-
sysv), but unfortunately sssd doesn't come up (has exactly the same
config, as in other 14.10 zones, where it works as expected). And
because sssd doesn't come
possible patch:
http://svn.apache.org/viewvc/subversion/trunk/subversion/bindings/swig/include/svn_types.swg?r1=1668617r2=1668618pathrev=1668618view=patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When trying to git svn fetch git-svn coredumps:
gdb perl core
GNU gdb (Ubuntu 7.8-1ubuntu4) 7.8.0.20141001-cvs
...
[New LWP 3503]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Core was generated by
Yepp, and that's IMHO a design flaw. E.g. if one wants to distribute the
load on iots storage, it might make sense, to distribute the zones of
several storage devices, e.g. zone1 on JBOD1, zone2 on JBOD2, etc
As said, the only thing, which lxc nees to track is a single config
directory which
Actually that's not the same at all, because $cgroup != $lxc_name . Your
workaround is absolutely user UNfriendly, i.e. still hard to read and
for casual users inconvinient, because one needs supply all that many
format options ...
Anyway, I agree, that these utils should support such things out
Actually that's not the same at all, because $cgroup != $lxc_name . Your
workaround is absolutely user UNfriendly, i.e. still hard to read and
for casual users inconvinient, because one needs supply all that many
format options ...
Anyway, I agree, that these utils should support such things out
Yepp, and that's IMHO a design flaw. E.g. if one wants to distribute the
load on iots storage, it might make sense, to distribute the zones of
several storage devices, e.g. zone1 on JBOD1, zone2 on JBOD2, etc
As said, the only thing, which lxc nees to track is a single config
directory which
Public bug reported:
When sss_obfuscate -d $section, it adds/replaces the corresponding
password /etc/sssd/sssd.conf, however it also removes valid entries,
which breaks sssd. E.g.:
--- /etc/sssd/sssd.conf.orig2015-03-10 05:28:29.959787539 +0100
+++ /etc/sssd/sssd.conf 2015-03-10
Public bug reported:
Right now lxc does a pretty poor job wrt. managing containers, i.e. one
needs to know, where containers have been installed to be able to
access/use/manage them (option -P dir) unless they've been installed in
the default location. Even if one knows the install path, it is
Public bug reported:
Container management/monitoring is currently a pain, because procps do
not support container, i.e. there is no way to tell the tools to
filter the output wrt. a certain zone or to add a column, which shows
the zone name a process belongs to.
E.g. for what is needed:
Public bug reported:
Container management/monitoring is currently a pain, because procps do
not support container, i.e. there is no way to tell the tools to
filter the output wrt. a certain zone or to add a column, which shows
the zone name a process belongs to.
E.g. for what is needed:
1 - 100 of 142 matches
Mail list logo
