search

ministryofjustice / staff-device-dhcp-server

The ISC KEA server for serving DHCP requests (via a Docker image)
https://github.com/ministryofjustice/cloud-operations#dhcp--dns
MIT License
2 stars 3 forks source link

🐛 DHCP4_PACKET_PROCESS_STD_EXCEPTION #196

Open Gary-H9 opened 2 years ago

Gary-H9 commented 2 years ago

Describe the bug.

We are sporadically seeing the following error in logs: 

  |   | 2022-06-22 11:20:25.470 ERROR [kea-dhcp4.packets/114.139651171683128] DHCP4_PACKET_PROCESS_STD_EXCEPTION exception occurred during packet processing: Empty DUIDs are not allowed
  |   | 2022-06-22 11:20:21.724 ERROR [kea-dhcp4.packets/114.139651171683128] DHCP4_PACKET_PROCESS_STD_EXCEPTION exception occurred during packet processing: Empty DUIDs are not allowed
  |   | 2022-06-22 11:20:17.312 ERROR [kea-dhcp4.packets/114.139651166448440] DHCP4_PACKET_PROCESS_STD_EXCEPTION exception occurred during packet processing: Empty DUIDs are not allowed
  |   | 2022-06-22 11:20:09.300 ERROR [kea-dhcp4.packets/114.139651205913400] DHCP4_PACKET_PROCESS_STD_EXCEPTION exception occurred during packet processing: Empty DUIDs are not allowed
  |   | 2022-06-22 11:20:03.628 ERROR [kea-dhcp4.packets/114.139651171203896] DHCP4_PACKET_PROCESS_STD_EXCEPTION exception occurred during packet processing: Empty DUIDs are not allowed
  |   | 2022-06-22 09:33:50.237 ERROR [kea-dhcp4.packets/114.139651171060536] DHCP4_PACKET_PROCESS_STD_EXCEPTION exception occurred during packet processing: Empty DUIDs are not allowed

To Reproduce

Unable to reproduce, current theory is that this is a device on the network. When we next see the errors we are going to ask the networks team for a packet capture.

Expected Behaviour

No response

Environment

No response

Additional context

No response

github-actions[bot] commented 2 years ago

CNSA-51 created on Jira board and transitioned to Done

bagg3rs commented 1 year ago

Waiting on error to show up again

Gary-H9 commented 1 year ago

This behaviour occurred again yesterday, troubleshooting has reconvened.

mTouhid commented 1 year ago

if this happens again, contact Doultun

Gary-H9 commented 1 year ago

Alas, it happened again, we contacted the network team for a packet capture circa 9:30, by the time we reached agreement that one would be done at 16:15, we had missed the errors by 15 minutes. The packet capture process has been documented and shared with the network team in the event this occurs again.

Gary-H9 commented 1 year ago

Issue has re-appeared over the last week, I have emailed the KEA mailing list.