[Touch-packages] [Bug 1956243] Re: Ping give socket error initially if IPv6 is disabled

[Andrew Welham]

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1956243

Title:
  Ping give socket  error initially if IPv6 is disabled

Status in iputils package in Ubuntu:
  New

Bug description:
  With IpV6 enabled everything works well. However if you disable ipv6 by 
editing /etc/default/grub with the following entry
  GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
   then when you ping there is an initial socket error 

  ping localhost
  ping: socket: Address family not supported by protocol
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms

  
  however ping -4 works

  ping -4 localhost
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms

  so it looks like ping is trying ipv6 first and not detecting that its
  disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: iputils-ping 3:20210202-1build1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Jan  3 17:42:07 2022
  InstallationDate: Installed on 2022-01-03 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211029)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1956243/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1956243] [NEW] Ping give socket error initially if IPv6 is disabled

[Andrew Welham]

Public bug reported:

With IpV6 enabled everything works well. However if you disable ipv6 by editing 
/etc/default/grub with the following entry
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
 then when you ping there is an initial socket error 

ping localhost
ping: socket: Address family not supported by protocol
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms


however ping -4 works

ping -4 localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms

so it looks like ping is trying ipv6 first and not detecting that its
disabled.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: iputils-ping 3:20210202-1build1
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Jan  3 17:42:07 2022
InstallationDate: Installed on 2022-01-03 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211029)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: iputils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1956243

Title:
  Ping give socket  error initially if IPv6 is disabled

Status in iputils package in Ubuntu:
  New

Bug description:
  With IpV6 enabled everything works well. However if you disable ipv6 by 
editing /etc/default/grub with the following entry
  GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
   then when you ping there is an initial socket error 

  ping localhost
  ping: socket: Address family not supported by protocol
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms

  
  however ping -4 works

  ping -4 localhost
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms

  so it looks like ping is trying ipv6 first and not detecting that its
  disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: iputils-ping 3:20210202-1build1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Jan  3 17:42:07 2022
  InstallationDate: Installed on 2022-01-03 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211029)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1956243/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

22 hours no issues
# systemctl status isc-dhcp-server
● isc-dhcp-server.service - ISC DHCP IPv4 server
 Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Sun 2020-08-16 09:43:12 BST; 22h ago
   Docs: man:dhcpd(8)
   Main PID: 730 (dhcpd)
  Tasks: 4 (limit: 9571)
 Memory: 10.9M
 CGroup: /system.slice/isc-dhcp-server.service
 └─730 dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode as follows:
     Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/
     Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/
  2) Run dhcpd as follows in both machine(s)

  # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4

  3) Leave the cluster running for a long (2h) period until the
  crash/race condition is reproduced.

  [REGRESSION POTENTIAL]

  * The fix will prevent the assertion to happen in the dispatch_send
  path, later versions of isch-dhcp upstream lack this logic and entirely 
removed the existence of this flag. Therefore, removing the need for this
  assertion at process_fd shouldn't be problematic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1872118/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

I managed to get it working last night, but the install was a bit of a mess. It 
did how ever run over night.
 
This morning i carried out the following
sudo apt install \
isc-dhcp-server \
libdns-export1109/focal-proposed \
libirs-export161/focal-proposed \
libisc-export1105/focal-proposed 

The versions are below,and i will leave this to run as a test

GW1
# dpkg -l | grep libdns-export1109
ii  libdns-export11091:9.11.16+dfsg-3~ubuntu1   
amd64Exported DNS Shared Library
# dpkg -l | grep libirs-export161
ii  libirs-export161 1:9.11.16+dfsg-3~ubuntu1   
amd64Exported IRS Shared Library
# dpkg -l | grep libisc-export1105
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64Exported ISC Shared Library
 

GW2

# dpkg -l | grep libdns-export1109
ii  libdns-export11091:9.11.16+dfsg-3~ubuntu1   
amd64Exported DNS Shared Library
# dpkg -l | grep libirs-export161
ii  libirs-export161 1:9.11.16+dfsg-3~ubuntu1   
amd64Exported IRS Shared Library
# dpkg -l | grep libisc-export1105
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64Exported ISC Shared Library

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode as follows:
     Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/
     Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/
  2) Run dhcpd as follows in both machine(s)

  # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4

  3) Leave the cluster running for a long (2h) period until the
 

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

Just tried this
apt-get -y remove isc-dhcp-server
apt-get -y remove libdns-export1109/focal-proposed
apt-get -y remove libirs-export161/focal-proposed
apt-get -y remove libisc-export1105/focal-proposed
apt-get -y install isc-dhcp-server
apt-get -y install libdns1109/focal-proposed
apt-get -y install libirs161/focal-proposed
apt-get -y install  libisc1105/focal-proposed


GW1
#  dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
#  dpkg -l | grep libdns
ii  libdns-export11001:9.11.3+dfsg-1ubuntu1.12  
amd64Exported DNS Shared Library
ii  libdns-export11091:9.11.16+dfsg-3~build1
amd64Exported DNS Shared Library
ii  libdns1109:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libirs
ii  libirs-export160 1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported IRS Shared Library
ii  libirs-export161 1:9.11.16+dfsg-3~build1
amd64Exported IRS Shared Library
ii  libirs161:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libisc
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~build1
amd64Exported ISC Shared Library
ii  libisc-export169:amd64   1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC Shared Library
ii  libisc1105:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64ISC Shared Library used by BIND
ii  libisccc161:amd641:9.11.16+dfsg-3~ubuntu1   
amd64Command Channel Library used by BIND
ii  libisccfg-export160  1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC CFG Shared Library
ii  libisccfg-export163  1:9.11.16+dfsg-3~build1
amd64Exported ISC CFG Shared Library
ii  libisccfg163:amd64   1:9.11.16+dfsg-3~ubuntu1   
amd64Config File Handling Library used by BIND


GW2
# dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
# dpkg -l | grep libdns
ii  libdns-export11001:9.11.3+dfsg-1ubuntu1.12  
amd64Exported DNS Shared Library
ii  libdns-export11091:9.11.16+dfsg-3~build1
amd64Exported DNS Shared Library
ii  libdns1109:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libirs
ii  libirs-export160 1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported IRS Shared Library
ii  libirs-export161 1:9.11.16+dfsg-3~build1
amd64Exported IRS Shared Library
ii  libirs161:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libisc
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~build1
amd64Exported ISC Shared Library
ii  libisc-export169:amd64   1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC Shared Library
ii  libisc1105:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64ISC Shared Library used by BIND
ii  libisccc161:amd641:9.11.16+dfsg-3~ubuntu1   
amd64Command Channel Library used by BIND
ii  libisccfg-export160  1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC CFG Shared Library
ii  libisccfg-export163  1:9.11.16+dfsg-3~build1
amd64Exported ISC CFG Shared Library
ii  libisccfg163:amd64   1:9.11.16+dfsg-3~ubuntu1   
amd64Config File Handling Library used by BIND


still not good

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a 

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

not looking good,

Aug 15 20:14:55 gw2-focal sh[741]: ../../../../lib/isc/unix/socket.c:4359: 
fatal error: select() failed: Bad file descriptor
Aug 15 20:14:55 gw2-focal systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Aug 15 20:14:55 gw2-focal systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'.

have the correct files been installed ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode as follows:
     Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/
     Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/
  2) Run dhcpd as follows in both machine(s)

  # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4

  3) Leave the cluster running for a long (2h) period until the
  crash/race condition is reproduced.

  [REGRESSION POTENTIAL]

  * The fix will prevent the assertion to happen in the dispatch_send
  path, later versions of isch-dhcp upstream lack this logic and entirely 
removed the existence of this flag. Therefore, removing the need for this
  assertion at process_fd shouldn't be problematic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1872118/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

Timo,
Just installed the updates I will let you know
I installed as follows 

apt-get install isc-dhcp-server

apt-get install libdns-export1109/focal-proposed
apt-get install libirs-export161/focal-proposed
apt-get install  libisc-export1105/focal-proposed


The installed version are
GW1
# dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
# dpkg -l | grep libdns-export1109
ii  libdns-export11091:9.11.16+dfsg-3~ubuntu1   
amd64Exported DNS Shared Library
# dpkg -l | grep libirs-export161
ii  libirs-export161 1:9.11.16+dfsg-3~ubuntu1   
amd64Exported IRS Shared Library
# dpkg -l | grep libisc-export1105
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64Exported ISC Shared Library
#


GW2
# dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
# dpkg -l | grep libdns-export1109
ii  libdns-export11091:9.11.16+dfsg-3~ubuntu1   
amd64Exported DNS Shared Library
# dpkg -l | grep libirs-export161
ii  libirs-export161 1:9.11.16+dfsg-3~build1
amd64Exported IRS Shared Library
# dpkg -l | grep libisc-export1105
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~build1
amd64Exported ISC Shared Library

Can you please confirm the correct versions are installed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Pretty sure its working now ;) been running 24 hours and over 2 million
requests. Thanks for  all the effort Jorge

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1872118/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Since i replaced the bad link , the patch appears to be working. been
running for 14 hours and over 1.2 Million requests both servers running
fine. Many thanks for all your effots.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1872118/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

looks like it may be fixed , been running about 5 hours about 400k
request and still alive. early signs are good, with the patch and my
dodgy link removed. Will leave running over night

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1872118/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

I think on of the links was wrong, just remade it. and going to test
again

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1872118/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Jorge, Here you go

andrew@gw2-focal:~$ ldd /usr/sbin/dhcpd | grep export
libirs-export.so.161 => /lib/x86_64-linux-gnu/libirs-export.so.161 
(0x00   
 007fa030e7b000)
libdns-export.so.1109 => /lib/x86_64-linux-gnu/libdns-export.so.1109 
(0x 
   7fa030c46000)
libisc-export.so.1105 => /lib/x86_64-linux-gnu/libisc-export.so.1105 
(0x 
   7fa030bcf000)
libisccfg-export.so.163 => 
/lib/x86_64-linux-gnu/libisccfg-export.so.163   
  
(0x7fa03098b000)
andrew@gw2-focal:~$ ldd /usr/sbin/dhcpd | grep export
libirs-export.so.161 => /lib/x86_64-linux-gnu/libirs-export.so.161 
(0x7fa9fbeaf000)
libdns-export.so.1109 => /lib/x86_64-linux-gnu/libdns-export.so.1109 
(0x7fa9fbc7a000)
libisc-export.so.1105 => /lib/x86_64-linux-gnu/libisc-export.so.1105 
(0x7fa9fbc03000)
libisccfg-export.so.163 => 
/lib/x86_64-linux-gnu/libisccfg-export.so.163 (0x7fa9fb9bf000)
andrew@gw2-focal:~$ dpkg -S /lib/x86_64-linux-gnu/libisc-export.so.1105
libisc-export1105:amd64: /lib/x86_64-linux-gnu/libisc-export.so.1105
andrew@gw2-focal:~$ apt-cache policy libisc-export1105  | grep -i ppa
  Installed: 1:9.11.16+dfsg-3~ppa1
  Candidate: 1:9.11.16+dfsg-3~ppa1
 *** 1:9.11.16+dfsg-3~ppa1 500
500 http://ppa.launchpad.net/niedbalski/fix-1872118/ubuntu focal/main 
amd64 Packages
andrew@gw2-focal:~$ ls -als  /lib/x86_64-linux-gnu/libirs-export.so.161

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Not sure if this helps i coped the coredump file to a test system install gdb
and got the following
# gdb /usr/sbin/dhcpd ./CoreDump
GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/dhcpd...
(No debugging symbols found in /usr/sbin/dhcpd)
[New LWP 63464]
[New LWP 63463]
[New LWP 63448]
[New LWP 63465]

warning: Unexpected size of section `.reg-xstate/63464' in core file.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dh'.
Program terminated with signal SIGABRT, Aborted.

warning: Unexpected size of section `.reg-xstate/63464' in core file.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7f0ed5c48700 (LWP 63464))]

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Yes i restarted isc-dhcp-server with systemctl restart isc-dhcp-server (
even tried a reboot once)


# dpkg -l | grep ppa1
ii  isc-dhcp-server  4.4.1-2.1ubuntu6~ppa1  
amd64ISC DHCP server for automatic IP address assignment
ii  libdns-export11091:9.11.16+dfsg-3~ppa1  
amd64Exported DNS Shared Library
ii  libirs-export161 1:9.11.16+dfsg-3~ppa1  
amd64Exported IRS Shared Library
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~ppa1  
amd64Exported ISC Shared Library
ii  libisccfg-export163  1:9.11.16+dfsg-3~ppa1  
amd64Exported ISC CFG Shared Library

# systemctl status isc-dhcp-server
● isc-dhcp-server.service - ISC DHCP IPv4 server
 Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Thu 2020-08-06 07:26:09 BST; 2min 39s ago
   Docs: man:dhcpd(8)
   Main PID: 42301 (dhcpd)
  Tasks: 4 (limit: 9569)
 Memory: 7.6M
 CGroup: /system.slice/isc-dhcp-server.service
 └─42301 dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf

Aug 06 07:28:47 gw2-focal dhcpd[42301]: Remove host declaration test or remove 
192.168.0.90
Aug 06 07:28:47 gw2-focal dhcpd[42301]: from the dynamic address pool for 
192.168.0.0/24
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.0.90 
(192.168.0.2) from MACREMOVED via ens3: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens13: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens12: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens11: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens10: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens9: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens8: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens3: ignored (not authoritative).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Last time in only did 
sudo apt install \
isc-dhcp-server=4.4.1-2.1ubuntu6~ppa1 \ sudo systemctl restart 
isc-dhcp-server

This time i ried as someone else had done.

sudo apt install \
isc-dhcp-server=4.4.1-2.1ubuntu6~ppa1 \
libdns-export1109=1:9.11.16+dfsg-3~ppa1 \
libirs-export161=1:9.11.16+dfsg-3~ppa1 \
libisc-export1105=1:9.11.16+dfsg-3~ppa1 && \


I've uploaded the full crash dump

** Attachment added: "_usr_sbin_dhcpd.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+attachment/5398988/+files/_usr_sbin_dhcpd.0.crash

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

My config files are


PRIMARY SERVER CONFIG


default-lease-time 600;
max-lease-time 7200;

failover peer "failover-partner" {
primary;
address 192.168.0.2;
port 519;
peer address 192.168.0.3;
peer port 521;
max-response-delay 60;
max-unacked-updates 10;
mclt 3600;
split 128;
load balance max seconds 3;
}

omapi-port 7911;
omapi-key omapi_key;

key omapi_key {
 algorithm hmac-md5;
 secret  REMOVED;
}

subnet 192.168.0.0 netmask 255.255.255.0 {
 option routers 192.168.0.1;
 option domain-name-servers 192.168.0.2, 192.168.0.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.0-dhcp-static-leases.conf";
# include"/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.0.6 192.168.0.254;
deny unknown-clients;
 }
}


subnet 192.168.1.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.1.1;
 option domain-name-servers 192.168.1.2, 192.168.1.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.1-dhcp-static-leases.conf";
# include"/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
 failover peer "failover-partner";
 range 192.168.1.6 192.168.1.254;
 deny unknown-clients;

 }
}

subnet 192.168.2.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.2.1;
 option domain-name-servers 192.168.2.2, 192.168.2.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.2-dhcp-static-leases.conf";
# include"/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.2.6 192.168.2.254;
deny unknown-clients;

 }
}

subnet 192.168.3.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.3.1;
 option domain-name-servers 192.168.3.2, 192.168.3.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.3-dhcp-static-leases.conf";
# include"/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.3.6 192.168.3.254;
deny unknown-clients;
 }
}

subnet 192.168.4.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.4.1;
 option domain-name-servers 192.168.4.2, 192.168.4.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.4-dhcp-static-leases.conf";
# include"/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.4.6 192.168.4.254;
deny unknown-clients;
 }
}

subnet 192.168.5.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.5.1;
 option domain-name-servers  192.168.5.2, 192.168.5.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.5-dhcp-static-leases.conf";
# include "/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.5.6 192.168.5.254;
deny unknown-clients;
 }
}

subnet 192.168.6.0 netmask 255.255.255.0 {
 allow unknown-clients;
 option routers 192.168.6.1;
 option domain-name-servers 192.168.6.2, 192.168.6.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers 212.23.6.6,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.6-dhcp-static-leases.conf";
# include "/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.6.6 192.168.6.254;
allow unknown-clients;
 }
}

subnet 192.168.7.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.7.1;
 option domain-name-servers  192.168.7.2, 192.168.7.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.7-dhcp-static-leases.conf";
# include "/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.7.6 192.168.7.254;
deny unknown-clients;
 }
}

subnet 192.168.8.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.8.1;
 option domain-name-servers 192.168.8.2, 192.168.8.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

isc-dhcp-server failed to start after that, a reboot fixed it and it appeared 
to stabilise. Then as a test i upgraded the primary server.
when the primary server came on line the secondary went off line and the 
stability of the environment went down fast. 
Remove the patched version and installed the version from 18.04 to be able to 
stay online

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1872118/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

also noticed this  APPARMOR is not happy now
Aug  4 09:37:37 gw2-focal kernel: [257023.493017] audit: type=1400 
audit(1596530257.080:51): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/63448/task/63463/comm" pid=63448 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 09:37:37 gw2-focal kernel: [257023.493726] audit: type=1400 
audit(1596530257.084:52): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/63448/task/63464/comm" pid=63448 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 09:37:37 gw2-focal kernel: [257023.494441] audit: type=1400 
audit(1596530257.084:53): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/63448/task/63465/comm" pid=63448 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 13:49:39 gw2-focal kernel: [272145.694002] audit: type=1400 
audit(1596545379.184:54): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/67792/task/67804/comm" pid=67792 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 13:49:39 gw2-focal kernel: [272145.694558] audit: type=1400 
audit(1596545379.184:55): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/67792/task/67805/comm" pid=67792 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 13:49:39 gw2-focal kernel: [272145.694837] audit: type=1400 
audit(1596545379.184:56): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/67792/task/67806/comm" pid=67792 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 15:20:30 gw2-focal kernel: [277597.307707] audit: type=1400 
audit(1596550830.760:57): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/69853/task/69865/comm" pid=69853 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 15:20:30 gw2-focal kernel: [277597.308533] audit: type=1400 
audit(1596550830.760:58): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/69853/task/69867/comm" pid=69853 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 15:20:30 gw2-focal kernel: [277597.309043] audit: type=1400 
audit(1596550830.760:59): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/69853/task/69868/comm" pid=69853 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 17:19:27 gw2-focal kernel: [284733.739418] audit: type=1400 
audit(1596557967.150:60): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/dhcpd" pid=73881 comm="apparmor_parser"

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

I've done the apt install on one of the failover server (Its the one
that mostly crashes)

Listing... Done
isc-dhcp-server/focal,now 4.4.1-2.1ubuntu6~ppa1 amd64 [installed]

still crashed


syslog shows
Aug  4 17:40:44 gw2-focal sh[74365]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Aug  4 17:40:44 gw2-focal sh[74365]: #0 0x7f2302a7fa4a in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #1 0x7f2302a7f980 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #2 0x7f2302abb7e1 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #3 0x7f2302862609 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #4 0x7f230299e103 in ??
Aug  4 17:40:44 gw2-focal systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Aug  4 17:40:44 gw2-focal systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'.


text part of crash shows

ProblemType: Crash
Architecture: amd64
Date: Tue Aug  4 17:44:17 2020
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/sbin/dhcpd
ExecutableTimestamp: 1596511208
ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
 Name:  dhcpd
 Umask: 0022
 State: D (disk sleep)
 Tgid:  74528
 Ngid:  0
 Pid:   74528
 PPid:  1
 TracerPid: 0
 Uid:   113 113 113 113
 Gid:   118 118 118 118
 FDSize:128
 Groups:
 NStgid:74528
 NSpid: 74528
 NSpgid:74528
 NSsid: 74528
 VmPeak:  235996 kB
 VmSize:  170540 kB
 VmLck:0 kB
 VmPin:0 kB
 VmHWM:12088 kB
 VmRSS:11904 kB
 RssAnon:   5784 kB
 RssFile:   6120 kB
 RssShmem: 0 kB
 VmData:   30568 kB
 VmStk:  132 kB
 VmExe:  592 kB
 VmLib: 5424 kB
 VmPTE:   88 kB
 VmSwap:   0 kB
 HugetlbPages: 0 kB
 CoreDumping:   1
 THP_enabled:   1
 Threads:   4
 SigQ:  0/31897
 SigPnd:
 ShdPnd:
 SigBlk:
 SigIgn:1000
 SigCgt:00018000
 CapInh:
 CapPrm:
 CapEff:
 CapBnd:003f
 CapAmb:
 NoNewPrivs:0
 Seccomp:   0
 Speculation_Store_Bypass:  thread vulnerable
 Cpus_allowed:  f
 Cpus_allowed_list: 0-3
 Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,,,0001
 Mems_allowed_list: 0
 voluntary_ctxt_switches:   22
 nonvoluntary_ctxt_switches:20
Signal: 6
Uname: Linux 5.4.0-42-generic x86_64
UserGroups: N/A
CoreDump: base64

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

error in the above description should have been 
I've done the apt install on one of SERVERS the failover server (Its the one 
that mostly crashes)

Listing... Done
isc-dhcp-server/focal,now 4.4.1-2.1ubuntu6~ppa1 amd64 [installed]

still crashed


syslog shows
Aug  4 17:40:44 gw2-focal sh[74365]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Aug  4 17:40:44 gw2-focal sh[74365]: #0 0x7f2302a7fa4a in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #1 0x7f2302a7f980 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #2 0x7f2302abb7e1 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #3 0x7f2302862609 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #4 0x7f230299e103 in ??
Aug  4 17:40:44 gw2-focal systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Aug  4 17:40:44 gw2-focal systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'.


text part of crash shows

ProblemType: Crash
Architecture: amd64
Date: Tue Aug  4 17:44:17 2020
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/sbin/dhcpd
ExecutableTimestamp: 1596511208
ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
 Name:  dhcpd
 Umask: 0022
 State: D (disk sleep)
 Tgid:  74528
 Ngid:  0
 Pid:   74528
 PPid:  1
 TracerPid: 0
 Uid:   113 113 113 113
 Gid:   118 118 118 118
 FDSize:128
 Groups:
 NStgid:74528
 NSpid: 74528
 NSpgid:74528
 NSsid: 74528
 VmPeak:  235996 kB
 VmSize:  170540 kB
 VmLck:0 kB
 VmPin:0 kB
 VmHWM:12088 kB
 VmRSS:11904 kB
 RssAnon:   5784 kB
 RssFile:   6120 kB
 RssShmem: 0 kB
 VmData:   30568 kB
 VmStk:  132 kB
 VmExe:  592 kB
 VmLib: 5424 kB
 VmPTE:   88 kB
 VmSwap:   0 kB
 HugetlbPages: 0 kB
 CoreDumping:   1
 THP_enabled:   1
 Threads:   4
 SigQ:  0/31897
 SigPnd:
 ShdPnd:
 SigBlk:
 SigIgn:1000
 SigCgt:00018000
 CapInh:
 CapPrm:
 CapEff:
 CapBnd:003f
 CapAmb:
 NoNewPrivs:0
 Seccomp:   0
 Speculation_Store_Bypass:  thread vulnerable
 Cpus_allowed:  f
 Cpus_allowed_list: 0-3
 Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,,,0001
 Mems_allowed_list: 0
 voluntary_ctxt_switches:   22
 nonvoluntary_ctxt_switches:20
Signal: 6
Uname: Linux 5.4.0-42-generic x86_64
UserGroups: N/A
CoreDump: base64

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

As my systems are pinned not to accept isc-dhcp-server upgrades, as I run the 
18.04 version as it works. I extracted the dhcpd file from your packages and 
dropped it in place.
It ran for about 5 hours with thousands of requests.
Then it crashed with 

Aug  4 13:13:29 gw2-focal sh[63448]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Aug  4 13:13:29 gw2-focal sh[63448]: #0 0x7f0ed6a02a4a in ??
Aug  4 13:13:29 gw2-focal sh[63448]: #1 0x7f0ed6a02980 in ??
Aug  4 13:13:29 gw2-focal sh[63448]: #2 0x7f0ed6a3e7e1 in ??
Aug  4 13:13:29 gw2-focal sh[63448]: #3 0x7f0ed67e5609 in ??
Aug  4 13:13:29 gw2-focal sh[63448]: #4 0x7f0ed6921103 in ??

In the syslog

The start of the crash (up to the base64 dump) is

ProblemType: Crash
Architecture: amd64
Date: Tue Aug  4 13:13:30 2020
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/sbin/dhcpd
ExecutableTimestamp: 1596530249
ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
 Name:  dhcpd
 Umask: 0022
 State: D (disk sleep)
 Tgid:  63448
 Ngid:  0
 Pid:   63448
 PPid:  1
 TracerPid: 0
 Uid:   113 113 113 113
 Gid:   118 118 118 118
 FDSize:128
 Groups:
 NStgid:63448
 NSpid: 63448
 NSpgid:63448
 NSsid: 63448
 VmPeak:  235996 kB
 VmSize:  170540 kB
 VmLck:0 kB
 VmPin:0 kB
 VmHWM:12468 kB
 VmRSS:12468 kB
 RssAnon:   6216 kB
 RssFile:   6252 kB
 RssShmem: 0 kB
 VmData:   30872 kB
 VmStk:  132 kB
 VmExe:  592 kB
 VmLib: 5424 kB
 VmPTE:   88 kB
 VmSwap:   0 kB
 HugetlbPages: 0 kB
 CoreDumping:   1
 THP_enabled:   1
 Threads:   4
 SigQ:  0/31897
 SigPnd:
 ShdPnd:
 SigBlk:
 SigIgn:1000
 SigCgt:00018000
 CapInh:
 CapPrm:
 CapEff:
 CapBnd:003f
 CapAmb:
 NoNewPrivs:0
 Seccomp:   0
 Speculation_Store_Bypass:  thread vulnerable
 Cpus_allowed:  f
 Cpus_allowed_list: 0-3
 Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,,,0001
 Mems_allowed_list: 0
 voluntary_ctxt_switches:   40
 nonvoluntary_ctxt_switches:19
Signal: 6
Uname: Linux 5.4.0-42-generic x86_64
UserGroups: N/A

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Tomek, Please remember I tried the version 4.4.2 as suggested and as you
say Ubuntu used 4.4.1, so it could be something to do with the 4.4.1
release or the ubuntu changes. Either way it looks like its not going to
be fixed. Given this how do you apply to have a ISC-DHCP_Server removed
form the Ubuntu bundle for no maintenance.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

tried it on a single server in the cluster and it looks like it better,
i.e it actually launches, however there is no -user or -group options,
with different directories and it must be started as root (with no
change of id_  to start, so not secure. I guess thee other changes are
added by ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Looking at the history around isc-dhcp, it appears if i read it properly that 
isc-dhcp sever for Ubuntu has been abandoned.
If this is the case should it even be in the focal build

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Thats what I did, but had a couple of outages, I had a choice of extending the 
lease time or downgrade. I did also try to disable apparmor, and dhcp gave an 
error (can't remember what though) and crashed I guess AppArmor just detected 
this and killed the process. So far about a week in ad every thing looks good.
The other option i guess (until they fix this) is to build the latest release 
from source. I did not do this due to no automatic patching

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

No response, I actually wondering if I logged the bug in the wrong
place. Anyone building a cluster of DHCP servers on Ubuntu 20.04 should
run into this. The above or no one is using Ubuntu for DHCP clusters ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

MM , Thanks I install the isc-dhcp-server from the Bionic-Security repository, 
and it appears to work.
For anyone else here is how to install an older version of the server,and then 
block updates to the focal version

PLEASE USE AT YOUR OWN RISK

#Backup your old config
sudo mkdir /etc/dhcp.20.04
sudo cp -r /etc/dhcp /etc/dhcp.20.04

#Remove your old isc-dhcp server
sudo apt remove isc-dhcp-server

#Add the old Bionic repository
add-apt-repository 'deb http://security.ubuntu.com/ubuntu bionic-security main'
sudo apt update

#Install isc-dhcp-server from the bionic-security repository
sudo apt-get install -t bionic-security/main isc-dhcp-server
sudo systemctl restart isc-dhcp-server


#Block upgrades of the package from the Focal Repository
edit /etc/apt/preferences.d/repo and add the following lines


Package: isc-dhcp-server
Pin: release a=bionic-security
Pin-Priority: 900

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Thats not a bad idea, they  It seems to be they are  ignoring the
critical issue. i.e you CAN@T RUN A PRODUCTION CLUSTER

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

See https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118
still no acknowledgement

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Focal:
  Fix Released

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

each server starts if the other is not running, but starting them
together caused this issue

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

[Andrew Welham]

Jane, Thanks, that interesting mine were from the use of KVM, although i
don't think i had it installed at the time (initially at least), as i
building the system. Although i can't be totally sure.

-- 
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/1860926

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Not SRU - N/A

  [scope]

  This is not reproducable on Eoan or Bionic; this is needed only for
  Focal.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 1650 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 1.6M
   CGroup: 

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

[Andrew Welham]

Sylvain, I also have mounts and had to do the same thing. I did notice
that the coundinit was getting in the way , so removed it

-- 
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/1860926

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Not SRU - N/A

  [scope]

  This is not reproducable on Eoan or Bionic; this is needed only for
  Focal.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 1650 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 1.6M
   CGroup: /system.slice/systemd-networkd.service
   └─1650 

[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

[Andrew Welham]

mm, see you have got tot he same stage as me after the changes removing
the rw to the some directories

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872106

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

[Andrew Welham]

I have some thing similar


I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked 
perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
This is being fixed by 

https://bugs.launchpad.net/bugs/1870729

However now one stops after a few hours with the following errors. One
can stay on line but not both.



Syslog shows 
Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??


nothing in kern.log


apport.log shows
ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 
6, core limit 0, dump mode 2
ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd 
(command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


/var/crash/_usr_sbin_dhcpd.0.crash shows

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 10 17:20:15 2020
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/sbin/dhcpd
ExecutableTimestamp: 1586210315
ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
 Name:  dhcpd
 Umask: 0022
 State: D (disk sleep)
 Tgid:  6828
 Ngid:  0
 Pid:   6828
 PPid:  1
 TracerPid: 0
 Uid:   113 113 113 113
 Gid:   118 118 118 118
 FDSize:128
 Groups:
 NStgid:6828
 NSpid: 6828
 NSpgid:6828
 NSsid: 6828
 VmPeak:  236244 kB
 VmSize:  170764 kB
 VmLck:0 kB
 VmPin:0 kB
 VmHWM:12064 kB
 VmRSS:12064 kB
 RssAnon:   5940 kB
 RssFile:   6124 kB
 RssShmem: 0 kB
 VmData:   30792 kB
 VmStk:  132 kB
 VmExe:  592 kB
 VmLib: 5424 kB
 VmPTE:   76 kB
 VmSwap:   0 kB
 HugetlbPages: 0 kB
 CoreDumping:   1
 THP_enabled:   1
 Threads:   4
 SigQ:  0/7609
 SigPnd:
 ShdPnd:
 SigBlk:
 SigIgn:1000
 SigCgt:00018000
 CapInh:
 CapPrm:
 CapEff:
 CapBnd:003f
 CapAmb:
 NoNewPrivs:0
 Seccomp:   0
 Speculation_Store_Bypass:  thread vulnerable
 Cpus_allowed:  3
 Cpus_allowed_list: 0-1
 Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,,,0001
 Mems_allowed_list: 0
 voluntary_ctxt_switches:   111
 nonvoluntary_ctxt_switches:144
Signal: 6
Uname: Linux 5.4.0-21-generic x86_64
UserGroups:


** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872106

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

[Andrew Welham]

please ignore this is fixed by https://bugs.launchpad.net/bugs/1870729,
but then the above happens

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872106

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872118] [NEW] DHCP Cluster crashes after a few hours

[Andrew Welham]

Public bug reported:


I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked 
perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
This is being fixed by 

https://bugs.launchpad.net/bugs/1870729

However now one stops after a few hours with the following errors. One
can stay on line but not both.


Syslog shows 
Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??


nothing in kern.log


apport.log shows
ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 
6, core limit 0, dump mode 2
ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd 
(command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


/var/crash/_usr_sbin_dhcpd.0.crash shows

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 10 17:20:15 2020
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/sbin/dhcpd
ExecutableTimestamp: 1586210315
ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
 Name:  dhcpd
 Umask: 0022
 State: D (disk sleep)
 Tgid:  6828
 Ngid:  0
 Pid:   6828
 PPid:  1
 TracerPid: 0
 Uid:   113 113 113 113
 Gid:   118 118 118 118
 FDSize:128
 Groups:
 NStgid:6828
 NSpid: 6828
 NSpgid:6828
 NSsid: 6828
 VmPeak:  236244 kB
 VmSize:  170764 kB
 VmLck:0 kB
 VmPin:0 kB
 VmHWM:12064 kB
 VmRSS:12064 kB
 RssAnon:   5940 kB
 RssFile:   6124 kB
 RssShmem: 0 kB
 VmData:   30792 kB
 VmStk:  132 kB
 VmExe:  592 kB
 VmLib: 5424 kB
 VmPTE:   76 kB
 VmSwap:   0 kB
 HugetlbPages: 0 kB
 CoreDumping:   1
 THP_enabled:   1
 Threads:   4
 SigQ:  0/7609
 SigPnd:
 ShdPnd:
 SigBlk:
 SigIgn:1000
 SigCgt:00018000
 CapInh:
 CapPrm:
 CapEff:
 CapBnd:003f
 CapAmb:
 NoNewPrivs:0
 Seccomp:   0
 Speculation_Store_Bypass:  thread vulnerable
 Cpus_allowed:  3
 Cpus_allowed_list: 0-1
 Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,,,0001
 Mems_allowed_list: 0
 voluntary_ctxt_switches:   111
 nonvoluntary_ctxt_switches:144
Signal: 6
Uname: Linux 5.4.0-21-generic x86_64
UserGroups:

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: 

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

ran for a few hours then crashed with

ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: called for pid 1900, signal 
6, core limit 0, dump mode 2
ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: not creating core for pid 
with dump mode of 2
ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: executable: /usr/sbin/dhcpd 
(command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: apport: report 
/var/crash/_usr_sbin_dhcpd.0.crash already exists and unseen, doing nothing to 
avoid disk usage DoS

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

dhcp-primary started to log the same errors so applied the same fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

FIXED

on the backup DHCP server I kept seeing

Apr 10 11:10:08 dhcp-backup kernel: [   86.045487] audit: type=1400 
audit(1586513408.708:44): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/1404/task/1417/comm" pid=1404 
comm="dhcpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Apr 10 11:10:08 dhcp-backup kernel: [   86.047925] audit: type=1400 
audit(1586513408.708:45): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/1404/task/1418/comm" pid=1404 
comm="dhcpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Apr 10 11:10:08 dhcp-backup kernel: [   86.048075] audit: type=1400 
audit(1586513408.708:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/1404/task/1419/comm" pid=1404 
comm="dhcpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

Changing 
/etc/apparmor.d/usr.sbin.dhcpd

 # owner @{PROC}/[0-9]*/task/[0-9]*/comm r,
  owner @{PROC}/[0-9]*/task/[0-9]*/comm rw,

then reloading the policy into the kernel with: sudo apparmor_parser -r
/etc/apparmor.d/usr.sbin.dhcpd

resolved the issue

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

Just checked a day later, only one kill on the primary dhcp server, 2nd
server will not start


** Changed in: isc-dhcp (Ubuntu)
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

incorrect statement above, since i have been bouncing the dhcp servers
to try to find a pattern, the primary dhcp server logged a single error
but continues to work

Apr  8 06:32:36 dhcp-primary systemd[1]: isc-dhcp-server.service: Main
process exited, code=killed, status=6/ABRT

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

I tried this.
If you stop the primary dhcp server
Start the backup (This time it works)
Restart the primary dhcp server
Secondary dhcp server fails with the error 

Apr  8 06:26:00 dhcp-backupl dhcpd[1360]: failover peer failover-partner: peer 
moves from communications-interrupted to normal
Apr  8 06:26:00 dhcp-backupl dhcpd[1360]: failover peer failover-partner: Both 
servers normal
Apr  8 06:26:00 dhcp-backupl sh[1360]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Apr  8 06:26:00 dhcp-backupl sh[1360]: #0 0x7fbe199fda4a in ??
Apr  8 06:26:00 dhcp-backupl sh[1360]: #1 0x7fbe199fd980 in ??
Apr  8 06:26:00 dhcp-backupl sh[1360]: #2 0x7fbe19a397e1 in ??
Apr  8 06:26:00 dhcp-backupl sh[1360]: #3 0x7fbe197e0609 in ??
Apr  8 06:26:00 dhcp-backupl sh[1360]: #4 0x7fbe1991c103 in ??
Apr  8 06:26:01 dhcp-backupl systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Apr  8 06:26:01 dhcp-backupl systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : 

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

The primary DHCP server is now fine, but the secondary won't start any more 
(although it did immediately after patching)
I now get the error
Apr  8 06:14:11 dhcp-backup dhcpd[1181]:
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: Sending on   
Socket/fallback/fallback-net
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: failover peer failover-partner: I move 
from normal to startup
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: Server starting service.
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: failover peer failover-partner: peer 
moves from normal to communications-interrupted
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: failover peer failover-partner: I move 
from startup to normal
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: balancing pool 5645d4679930 Internal  
total 250  free 125  backup 125  lts 0  max-own (+/-)25
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: balanced pool 5645d4679930 Internal  
total 250  free 125  backup 125  lts 0  max-misbal 38
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: balancing pool 5645d46e2cf0 Internal  
total 250  free 111  backup 139  lts 14  max-own (+/-)25
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: balanced pool 5645d46e2cf0 Internal  
total 250  free 111  backup 139  lts 14  max-misbal 38
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: failover peer failover-partner: peer 
moves from communications-interrupted to normal
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: failover peer failover-partner: Both 
servers normal
Apr  8 06:14:11 dhcp-backup sh[1181]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Apr  8 06:14:11 dhcp-backup sh[1181]: #0 0x7f0a52b25a4a in ??
Apr  8 06:14:11 dhcp-backup sh[1181]: #1 0x7f0a52b25980 in ??
Apr  8 06:14:11 dhcp-backup sh[1181]: #2 0x7f0a52b617e1 in ??
Apr  8 06:14:11 dhcp-backup sh[1181]: #3 0x7f0a52908609 in ??
Apr  8 06:14:11 dhcp-backup sh[1181]: #4 0x7f0a52a44103 in ??
Apr  8 06:14:12 dhcp-backup systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Apr  8 06:14:12 dhcp-backup systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 

[Touch-packages] [Bug 1870729] [NEW] DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

Public bug reported:

On Ubuntu 20.04 The idc-dhcp- server version is
isc-dhcp-server:
  Installed: (none)
  Candidate: 4.4.1-2.1ubuntu3
  Version table:
 4.4.1-2.1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages


The DHCP server is being regularly killed, when searching google the  bug looks 
very similar to an older bug regarding accessing a lease file, that was fixed 
year ago. As a temporary fix in systemd I have enabled a restart every time the 
main process fails. The error got worse when i start to run a pair of dhcp 
servers syncing state between each other


I regularly see the following in the syslog

Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart job, 
restart counter is at 3.
Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
Apr  4 00:05:00 gw sh[2049]: All rights reserved.
Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems Consortium.
Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: 

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

[Andrew Welham]

** Tags added: systemd-networkd

-- 
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/1860926

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  New

Bug description:
  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
version: 2
renderer: networkd
ethernets:
  enp4s0:
dhcp4: false
addresses: [192.168.0.4/24]
gateway4: 192.168.0.1
nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
version: 2
renderer: networkd
ethernets:
  enp4s0:
dhcp4: false
bridges:
  br0:
interfaces: [enp4s0]
dhcp4: no
addresses: [192.168.0.4/24]
gateway4: 192.168.0.1
nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  
  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
 Docs: man:systemd-networkd.service(8)
 Main PID: 979 (systemd-network)
   Status: "Processing requests..."
Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  
  systemctl restart systemd-networkd resolved the issue and a 

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
  TriggeredBy: ● systemd-networkd.socket
 Docs: man:systemd-networkd.service(8)
 Main PID: 1650 (systemd-network)
   Status: "Processing requests..."
Tasks: 1 (limit: 57662)
   Memory: 1.6M
   CGroup: /system.slice/systemd-networkd.service
   └─1650 /lib/systemd/systemd-networkd

  Jan 26 16:39:28 firebolt systemd[1]: Starting Network Service...
  Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: netdev ready
  Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: Gained IPv6LL
  Jan 26 16:39:28 firebolt systemd-networkd[1650]: Enumeration completed
  Jan 26 16:39:28 firebolt systemd[1]: Started Network Service.
  Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: netdev exists, using 
existing without changing its parameters
  Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: IPv6 successfully 
enabled


  a journalctl -u systemd-network produces

  Jan 26 16:36:28 firebolt systemd[1]: Starting Network Service...
  Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: netdev ready
  Jan 26 16:36:28 firebolt systemd-networkd[979]: Enumeration completed
  Jan 26 16:36:28 firebolt systemd-networkd[979]: wlp3s0: Interface name change 
detected, wlp3s0 has been renamed to wlan0.
  Jan 26 16:36:28 firebolt systemd[1]: Started Network Service.
  Jan 26 16:36:28 firebolt systemd-networkd[979]: wlan0: Interface name change 
detected, wlan0 has been renamed to wlp3s0.
  Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: rtnl: received neighbor 
message with invalid family, ignoring.
  Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: IPv6 successfully enabled
  Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: Link UP
  Jan 26 16:36:28 firebolt 

[Touch-packages] [Bug 1860926] [NEW] Ubuntu 20.04 Systemd fails to configure bridged network

[Andrew Welham]

Public bug reported:

Freshly installed Ubuntu 20.04 fully patched to days date with static IP
address works fine and survives a reboot

network:
  version: 2
  renderer: networkd
  ethernets:
enp4s0:
  dhcp4: false
  addresses: [192.168.0.4/24]
  gateway4: 192.168.0.1
  nameservers:
search: [mydomain]
addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

however when converted to a bridged network for kvm

network:
  version: 2
  renderer: networkd
  ethernets:
enp4s0:
  dhcp4: false
  bridges:
br0:
  interfaces: [enp4s0]
  dhcp4: no
  addresses: [192.168.0.4/24]
  gateway4: 192.168.0.1
  nameservers:
search: [mydomain]
addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

will not survive a reboot and required systemd-network to be restarted or
@reboot /usr/sbin/netplan apply
added to the crontab


after a reboot the network can not b eaccseed and a
systemctl status systemd-networkd produces

systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
TriggeredBy: ● systemd-networkd.socket
   Docs: man:systemd-networkd.service(8)
   Main PID: 979 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 57662)
 Memory: 4.1M
 CGroup: /system.slice/systemd-networkd.service
 └─979 /lib/systemd/systemd-networkd

Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received neighbor 
message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.


systemctl restart systemd-networkd resolved the issue and a 

systemctl status systemd-network producessystemd-networkd.service - Network 
Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
TriggeredBy: ● systemd-networkd.socket
   Docs: man:systemd-networkd.service(8)
   Main PID: 1650 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 57662)
 Memory: 1.6M
 CGroup: /system.slice/systemd-networkd.service
 └─1650 /lib/systemd/systemd-networkd

Jan 26 16:39:28 firebolt systemd[1]: Starting Network Service...
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: netdev ready
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: Gained IPv6LL
Jan 26 16:39:28 firebolt systemd-networkd[1650]: Enumeration completed
Jan 26 16:39:28 firebolt systemd[1]: Started Network Service.
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: netdev exists, using 
existing without changing its parameters
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: IPv6 successfully enabled


a journalctl -u systemd-network produces

Jan 26 16:36:28 firebolt systemd[1]: Starting Network Service...
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: netdev ready
Jan 26 16:36:28 firebolt systemd-networkd[979]: Enumeration completed
Jan 26 16:36:28 firebolt systemd-networkd[979]: wlp3s0: Interface name change 
detected, wlp3s0 has been renamed to wlan0.
Jan 26 16:36:28 firebolt systemd[1]: Started Network Service.
Jan 26 16:36:28 firebolt systemd-networkd[979]: wlan0: Interface name change 
detected, wlan0 has been renamed to wlp3s0.
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: rtnl: received neighbor 
message with invalid family, ignoring.
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: IPv6 successfully enabled
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: Link UP
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: Gained carrier
Jan 26 16:36:28 firebolt systemd-networkd[979]: enp4s0: rtnl: received neighbor 
message with invalid family, ignoring.
Jan 26 16:36:28 firebolt systemd-networkd[979]: enp4s0: rtnl: received neighbor 
message with invalid family, ignoring.
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: rtnl: received neighbor 
message with invalid family, ignoring.
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: Lost carrier
Jan 26 16:36:28 firebolt