Custom Query (21 matches)


Show under each result:

Results (1 - 3 of 21)

1 2 3 4 5 6 7
Ticket Resolution Summary Owner Reporter
#19 fixed bearmail - troubles with the responder Benjamin Linet Benjamin Linet

when we create a future auto-responder for a mail account the sieve file sym link is changed into a normal file which implies that the auto-responder will never be removed automatically

#2 fixed Upgrade open file limits in vserver context Lucas Bonnet Vincent Caron

A client reached a default of 256 open files in a vserver VM context. We can upgrade this limit to 1024 (done for this very client). This still looks a good number if we plan to maintain roughly 16 VMs per physical server. To be applied where suitable:

Other VMs will catch up later, no need to explicitly reboot them all now.

#3 fixed Vserver instances share a common interface and mess themselves up Lucas Bonnet Vincent Caron

Recently we discovered that the network device (and hence all networking support) was "disappearing" quite often in a vserer instance. An ifconfig -a would reveal no device at all.

This FAQ entry looks like a hint:

I suddenly wondered what was the exact meaning of the /etc/vservers/<name>/interfaces/0/dev parameter. I thought it was just a name for the virtual device in the vserver context. The documentation of this parameter is a one-liner.

Actually it looks like it's the name of a real interface in the host, which has the vserver's IP attached on the vserver instance startup (with ip addr add). Vserver is actually partitioning the network device on a per-IP basis. But the interface shown in the vserver is the host's one, not a "virtual one" such as in Xen.

Now in the host:

ziva:~# ip addr ls eth0
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:16:3e:40:12:18 brd ff:ff:ff:ff:ff:ff
    inet brd scope global eth0
    inet brd scope global eth0
    inet brd scope global secondary eth0
    inet brd scope global secondary eth0
    inet brd scope global secondary eth0
    inet brd scope global secondary eth0

What a mess. Some vserver instance got its IP attached as a primary one ( When this specific vserver is shutdown, all secondary addresses are dropped. First fix: we need to either:

  • make sure vserver IPs are always attached as secondary ones
  • or create a dummy interface per vserver.
  • or use the net.ipv4.conf.all.promote_secondaries sysctl trick from the FAQ

And in our specific Bearstech case, "eth0" (root server public interface) is definitively the wrong interface to alias. We should use eth2. Or more portable and prettier, rename eth2 as "eth-vrouter" and use that.

1 2 3 4 5 6 7
Note: See TracQuery for help on using queries.