Project

General

Profile

Actions
Copy link

Bug #8921

closed

dpinger without .pid files.?. 'pending' status

Added by Pi Ba over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Gateway Monitoring
Target version:
2.4.4-p1
Start date:
09/19/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4
Affected Architecture:
All

Description

Using 2.4.4-RC (amd64) built on Tue Sep 18 17:52:29 EDT 2018

I've installed a new pfSense VM with 3 wan interfaces assigned by DHCP.
The second wan interface, does not get a reply from the dhcp server on that network.
After a reboot the machine all 3 gateways remain in 'pending' state..

Looking with htop there are 2 dpinger processes, both are supposed to write their .pid file in /var/run/. But for some reason neither did, or it was deleted.?.. Not sure yet.. will try and find out more tomorrow. dpingers are reporting their status when questioned by "socat stdio /var/run/dpinger_OPT2_DHCP~100.64.240.50~8.8.4.4.sock".. so not sure yet what went wrong there, it seemed to me this could be troublesome for some people though, so i decided to report today, investigate further tomorrow.. (i'm confident its 'supposed' to work though..)

Actions
Copy link

Also available in: Atom PDF