Direct access to kernel /proc/sys/net/ipv4/tcp_keepalive* not available in virtual containers
Open, 60Public

Description

When using the kolab binary in a virtual environment such as LXC, Python throws an exception for not having read access to /proc/sys/net/ipv4/tcp_keepalive_time. This is causing issues in pykolab/imap/__init__.py line 851.

pykolab-0.8.7-1.1.el7.kolab_wf.noarch

Reproduce: Run Kolab within an LXC container. (This exact environment is running on ProxmoxVE).

Details

Ticket Type
Task
cdp1337 created this task.Dec 14 2016, 7:06 PM

..... AND I have no good way to provide code... so Github it is!

https://github.com/cdp1337/pykolab/commit/76d97e82d17519f914d04ec7a6338831807227c8

Looks like the commit rP927dce48ba8566d20b08a8392943dc23b8aebcc5 broke this on LXC, and subsequently broke the build. (B7239)

Anyway, the branch /dev/cdp1337/T2049 on github has the fix and it's working now for me.

cdp1337 closed this task as Resolved.Dec 14 2016, 7:40 PM
cdp1337 reopened this task as Open.Dec 16 2016, 8:40 PM

(Actually, setting this to open until the upstream code gets fixed; may be a good idea) Resolved elsewhere, still a problem upstream.

Just updated to Kolab 16.0.1 Release 12.1.el7.kolab_wf that this is still an issue when running in an LXC host!

jph added a subscriber: jph.Sep 21 2017, 3:01 PM
jph added a comment.Sep 21 2017, 3:06 PM

If there is a patch for Winterfell could you please port this also to Kolab16?
I have a current Kolab16 installation in a Centos7 lxc container on an Ubuntu 16.04 host.
kolab lm is not working and there are no folders created for new users.

pasik added a subscriber: pasik.Nov 25 2017, 2:33 PM