This ticket can be closed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2044034
Title:
/etc/security/limits.conf memlock changes have no effect
Status in pam package in
Looks like the problem was UsePAM=yes in /etc/ssh/sshd_config.
So system wide memlock is effected + ssh logins only effected if PAM is
enabled to set limits.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
This also fails... meaning... ulimit -l as root still shows 64...
*- memlock unlimited
root - memlock unlimited
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in
Public bug reported:
APT reports package as libpam-modules + launchpad says pam is the
closest package. Please change package name, if required.
Summary says it all.
Default of memlock seems to be 64 (which limits.conf suggests means
64k). Changing this setting seems to have no effect.
The
Public bug reported:
Notice the time spent inside lxd-containers.service + lxd.service which
require network + disk subsystems to work before they can work.
This behavior can be recreated by installing + configuring LXD, with no
containers.
Both lxd-containers.service + lxd.service should be
This bug has been hanging round for over a year now.
While packages seem to install when this diagnostic emits, users always
have questions about this.
Be great if someone could fix this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
root@net8-rmt:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.10
Release:15.10
Codename: wily
root@net8-rmt:~# uname -a
Linux net8-rmt.bizcooker.com 4.2.0-34-generic #39-Ubuntu SMP Thu Mar 10
22:13:01 UTC 2016
Still broken in ubuntu-15.10-wily + causes all manner of headaches
debugging.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1492837
Title:
iptables nat prerouting
Having bind use .d mechanism seems like the cleanest way to handle this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
The systemd facility changes sysvinit behavior considerably, especially
sending no SIGKILL after SIGTERM.
Suggested solution, send SIGKILL after timeout, following SIGTERM.
Primary difference is systemd defers forever to underlying processes,
rather than shooting them in the head
I see this bug is tagged xenial. Please post a fix which can be added to
Wily, to escape the long shudown delay.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
This is a very ugly bug.
Sometimes this causes reboots to hang for long periods. Just timed it on
a Wily system with all upgrades installed.
Takes 157 seconds, to shutdown system.
Above comments only mention 3.19 (Vivid) kernels. This problem persists
in Wily...
net4-dev# lsb_release -a
No LSB
Public bug reported:
Yet another horrible bug related to systemd which delays shutdowns by
minutes.
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1374759
surfaces this problem + the bug I'm reporting here is a separate issue.
Neither reboot or shutdown -r now work sensibly any
It appears - reboot -f - still works.
And this is a harsh way to reboot a system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1528655
Title:
Wily/15.10 - systemd
Still broken on Vivid as of Sept 26 2015.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1492837
Title:
iptables nat prerouting slight problem with adapter aliases
Public bug reported:
There seems to be a slight problem with iptables + adapter aliases.
Take the alias eth0:1 for example...
ifconfig eth0:1
eth0:1Link encap:Ethernet HWaddr 00:25:90:eb:cb:ae
inet addr:158.69.167.64 Bcast:158.69.255.255 Mask:255.255.0.0
UP
By "works" I mean packets forward correctly only when base adapter is
used (no :\d+) so aliases quietly drop packets.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1492837
Still broken in systemd 219.
If someone knows how to fix this, please update this ticket. Thanks.
rmt-net8# lxc-create --version
1.1.2
rmt-net8# lxcfs --version
FUSE library version: 2.9.2
fusermount version: 2.9.2
using FUSE kernel interface version 7.19
rmt-net8# psall | grep lxcfs
root
I had to remove both lines, in my case.
And this is likely a less than correct fix. I'm under the gun to get a
client machine I'm hosting setup to run many of their sites in LXC
containers, so time I invested looking at this fix was minimal.
Likely the entire stop function is best revisited, to
Just setting up a fresh Vivid LXC host machine + I was incorrect above.
There's no requirement for /etc/dnsmasq.conf to exist for lxc-net to
start correctly.
There is a requirement though for /etc/resolv.conf to reference at least
one valid name server.
--
You received this bug notification
Oh, I see...
I was using OOM as an example. I this case, it appears the missing
/etc/dnsmasq.conf file might be the culprit.
So first start of lxc-net, dnsmasq never starts.
After that, it will never start, unless a hard reboot is done.
--
You received this bug notification because you are a
IMHO, systemd seems to be the root of all evil.
touch /etc/dnsmasq.conf has no effect.
net4-dev# systemctl restart lxc-net
net4-dev# systemctl status lxc-net
● lxc-net.service - LXC network bridge setup
Loaded: loaded (/lib/systemd/system/lxc-net.service; enabled; vendor preset:
enabled)
Okay, a simple fix that seems to work (at least in my case), is to
comment out the first two guards in the stop function.
So...
#[ x$USE_LXC_BRIDGE = xtrue ] || { exit 0; }
#[ -f ${varrun}/network_up ] || { exit 0; }
Once these are skipped, the code seems to work.
--
You received this bug
Oh... and - touch /etc/dnsmasq.conf - is still required, so this is
another bug to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1452601
Title:
vivid container's
I've removed the patch tag + removed the patch file as LXC already has
this bug open + fix will likely come from there.
** Tags removed: patch
** Patch removed: Unified diff patch file
for
discussion about this bug
mkdir -p /var/log/drftools
/david-favor/tools/lxc-autostart-boothack
/var/log/drftools/lxc-autostart-boothack.log 21
** Attachment added: lxc-autostart-boothack
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458173/+attachment/4406621/+files/lxc-autostart
I believe this is a duplicate of bug 1240757.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1458063
Title:
Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time
Public bug reported:
net8-rmt# lxc-attach -n test -- bash -c 'id egrep ^root /etc/passwd echo
~ echo $HOME pwd'
uid=0(root) gid=0(root) groups=0(root)
root:x:0:0:root:/root:/bin/bash
/root
/root
/
Notice pwd show / instead of /root which is incorrect + causes all
manner of confusion when
This should be assigned to bsdtools as the package.
** Package changed: lxc (Ubuntu) = bootchart (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1458170
Title:
Vivid
Public bug reported:
Nothing shown via journalctl -k -b | grep bootchart after boot.
/var/log/bootchart does exist + is empty after boot.
net8-rmt# uname -a
Linux ns515383.ip-167-114-159.net 3.19.0-18-generic #18-Ubuntu SMP Tue May 19
18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
I'd have thought /etc/default/grub should have some directive about
bootchart + there is none.
Maybe this is the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1458170
Public bug reported:
The wall command should write a message to all users.
Issuing the command - wall foo - appears to dump dmesg to all users w/o
the message 'foo'.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
This does appear to relate to initial installs + some type of ordering
change, of how services start.
All other machines I manage had updates, rather than fresh installs +
all the updated machines work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Removed + Reinstalled...
Looks like all's well...
net8-rmt# apt-get install bootchart
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
bootchart
0 upgraded, 1 newly installed, 0 to remove and 0 not
This looks suspicious...
net8-rmt# service bootstart start
Failed to start bootstart.service: Unit bootstart.service failed to load: No
such file or directory.
net8-rmt# systemctl restart bootstart.service
Failed to restart bootstart.service: Unit bootstart.service failed to load: No
such file
Public bug reported:
In previous Ubuntu versions + current Ubuntu docs, boot time autostart
is accomplished by:
1) setting /etc/default/lxc LXC_AUTO=false
2) adding lxc.start.auto = 1 to config of containers to be started at
boot time
This no longer works.
___
net8-rmt# uname -a
Linux
lxc-autostart after boot works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1458173
Title:
Vivid + LXC autostart not working
Status in lxc package in Ubuntu:
New
Bug
Oh... Maybe the problem is lxcbr0 is up'ed before named starts.
Then if named listens on 0.0.0.0 makes sense it would glom onto the
lxcbr0 address too.
I'll modify named's config files + reboot + see if this fixes the
problem.
--
You received this bug notification because you are a member of
Public bug reported:
This is a clean Vivid install (rather than upgrade).
Maybe I munged something + for the life of me nothing comes to mind.
/var/log/syslog shows somehow bind is polluted with dnsmasq addresses?
All packages updated.
net8-rmt# lsb_release -a
No LSB modules are available.
Adding the following to /etc/named/named.conf.options seems to have
fixed this problem:
listen-on { 127.0.0.1; 167.114.159.29; };
This seems like a bug to me. Maybe switching to systemd created a subtle
change in order of network config + named + lxc-net start.
This is the first time I've had
40 matches
Mail list logo
