[INFO-109] Dhcp client not running - restarted

Hello Monkey74,

Thank you for reaching out to the community, is your appliance deployed in HA or standalone mode ?

Can you share the output of the following:

# ps aux | grep dhcp
# cat /var/log/selfmon.log
# cat /var/mdw-debug.log
# version 
# rpm -qa | grep dhcp
# cat /var/mdw/scripts/dhcpd

Vivek,

Thank you very much for your reply. Please see the output of the commands below:

# ps aux | grep dhcp

root      7269  0.0  0.0   9460   976 ?        Ss   Aug04   0:31 /usr/sbin/dhcpd -cf /etc/dhcpd.conf eth6 eth0

root     27967  0.0  0.0   5672   748 pts/0    S+   19:23   0:00 grep dhcp

# cat /var/log/selfmon.log
2022:08:24-18:45:25 fw01 selfmonng[4008]: I check Failed increment afc_running counter 1 - 3

# cat /var/mdw-debug.log
cat: /var/mdw-debug.log: No such file or director

# version 
Current software version...: 9.711005

Hardware type..............: Software Appliance

Installation image.........: 9.351-3.1

# rpm -qa | grep dhcp
ep-chroot-dhcpc-9.70-14.gde59063.rb5

dhcp-chroot-server-4.4.1-3.g629f991.rb5

ep-chroot-dhcps-9.70-15.ge43a374.rb6

dhcp-chroot-client-4.4.1-3.g629f991.rb5

# cat /var/mdw/scripts/dhcpd

bash: cat /var/mdw/scripts/dhcpd: No such file or directory

Additionally, the below was gathered from one of the DHCP events. I believe this happened with the ISP so, not sure if the issue is on that side.

2022:08:22-12:51:48 app dhclient: DHCPREQUEST for x.x.x.x on eth7 to 255.255.255.255 port 67

2022:08:22-12:51:50 app dhclient: DHCPREQUEST for x.x.x.x on eth7 to 255.255.255.255 port 67

2022:08:22-12:51:50 app dhclient: DHCPACK of x.x.x.x from x.x.230.1

2022:08:22-12:51:50 app dhclient: Killed old client process

2022:08:22-12:51:52 app dhclient: DHCPREQUEST for x.x.x.x on eth7 to 255.255.255.255 port 67

2022:08:22-12:51:53 app dhclient: DHCPREQUEST for x.x.x.x on eth7 to 255.255.255.255 port 67

2022:08:22-12:51:53 app dhclient: DHCPACK of x.x.x.x from x.x.230.1

2022:08:22-12:51:54 app dhclient: bound to x.x.x.x -- renewal in 3229 seconds.

2022:08:22-12:51:55 app ntpd[12580]: Listen normally on 7 eth7 x.x.x.x:123

2022:08:22-12:51:55 app ntpd[12580]: new interface(s) found: waking up resolver

2022:08:22-12:52:12 app dns-resolver[4442]: DNS server failed to contact!

2022:08:22-12:52:12 app dns-resolver[4442]: Updating REF_DefaultSophosUTMSupportHost :: hub.apu.sophos.com

2022:08:22-12:52:13 app dns-resolver[4442]: DNS server failed to contact!

2022:08:22-12:53:13 app dns-resolver[4442]: DNS server failed to contact!

2022:08:22-12:53:13 app dns-resolver[4442]: Updating REF_DefaultLetsEncryptApiServer :: acme-v02.api.letsencrypt.org

2022:08:22-12:53:14 app dns-resolver[4442]: DNS server failed to contact!

2022:08:22-12:54:14 app dns-resolver[4442]: DNS server failed to contact!

2022:08:22-12:55:01 app /usr/sbin/cron[29322]: (root) CMD (   /usr/local/bin/reporter/system-reporter.pl)

2022:08:22-12:55:14 app dns-resolver[4442]: DNS server failed to contact!

Thanks for the help!

Error: DNS server failed to contact!
--------------------------------------------------
By any chance the eth7 interface was unplugged ? Or went down due to any power outage situation? How often it happens ?

Error: DNS server failed to contact!
--------------------------------------------------
By any chance the eth7 interface was unplugged ? Or went down due to any power outage situation? How often it happens ?

Hi, Vivek,

No, the Ethernet was not unplugged nor had a power outage. In fact, 

It does not happened very often, I can recall two or three times in the last month or two.