group.of.nepali.translators team mailing list archive

[ChristianEhrhardt <1720109@xxxxxxxxxxxxxxxxxx>]

Note: since 5.7.3+dfsg-1.4 a native systemd file is used which uses type=simple and MAINPID tracking.
So >= Artful this is already fixed.

Setting the status to fixed, but adding a Xenial task as there the issue
still exists.

** Also affects: net-snmp (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: net-snmp (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: net-snmp (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: net-snmp (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1720109

Title:
  snmpd stop on host stops snmpd on LXD containers

Status in net-snmp package in Ubuntu:
  Fix Released
Status in net-snmp source package in Xenial:
  Triaged

Bug description:
  If you have ubuntu 16.04 containers running snmpd and you stop the
  snmpd on the LXD host system, it will also shut down all the snmpd
  instances on the containers (but will not restart them if you restart
  them on the LXD host) .. in fact, you even need to go back into the
  container, stop the snmpd before you can start it again.

  See log below, viepovzat17 is the LXD host, viezmaaat10 is the ubuntu
  container:

    driver: lxc
    driver_version: 2.0.8
    kernel: Linux
    kernel_architecture: x86_64
    kernel_version: 4.4.0-87-generic
    server: lxd
    server_pid: 4426
    server_version: "2.16"
    storage: zfs
    storage_version: 0.6.5.6-0ubuntu16

  root@viezmaaat10:~# /etc/init.d/snmpd start
  [ ok ] Starting snmpd (via systemctl): snmpd.service.
  root@viezmaaat10:~# ps -eaf | grep snmp
  snmp      1271     1  0 10:50 ?        00:00:00 /usr/sbin/snmpd -Lsd -Lf /dev/null -u snmp -g snmp -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid
  root      1291   757  0 10:50 ?        00:00:00 grep --color=auto snmp
  root@viezmaaat10:~#
  root@viezmaaat10:~# ps -eaf | grep snmp
  snmp      1271     1  0 10:50 ?        00:00:00 /usr/sbin/snmpd -Lsd -Lf /dev/null -u snmp -g snmp -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid
  root      1293   757  0 10:50 ?        00:00:00 grep --color=auto snmp
  root@viezmaaat10:~# exit

  root@viepovzat17:~# ps -eaf | grep snmp
  snmp     22757     1  0 10:45 ?        00:00:00 /usr/sbin/snmpd -Lsd -Lf /dev/null -u snmp -g snmp -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid
  100116   24118  5222  0 10:50 ?        00:00:00 /usr/sbin/snmpd -Lsd -Lf /dev/null -u snmp -g snmp -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid
  root     24153 21842  0 10:50 pts/1    00:00:00 grep --color=auto snmp
  root@viepovzat17:~# /etc/init.d/snmpd stop
  [ ok ] Stopping snmpd (via systemctl): snmpd.service.
  root@viepovzat17:~# ps -eaf | grep snmp
  root     24286 21842  0 10:50 pts/1    00:00:00 grep --color=auto snmp
  root@viepovzat17:~#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1720109/+subscriptions