Bug #8921
closed
dpinger without .pid files.?. 'pending' status
0%
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..)
Updated by Pi Ba about 6 years ago
Added some logging:
Sep 20 19:42:05 php-fpm 318 /rc.newwanip: CALL sigkillbypid( /var/run/dpinger_OPT2_DHCP~100.64.240.50~8.8.4.4.pid ) [ simplestacktrace2(..) - /etc/inc/util.inc:69 sigkillbypid(..) - /etc/inc/util.inc:32 killbypid(..) - /etc/inc/gwlb.inc:85 stop_dpinger(..) - /etc/inc/gwlb.inc:301 setup_gateways_monitor(..) - /etc/rc.newwanip:195 ] Sep 20 19:42:05 php-fpm 318 /rc.newwanip: CALL sigkillbypid( /var/run/dpinger_WAN_DHCP~100.64.143.98~8.8.8.8.pid ) [ simplestacktrace2(..) - /etc/inc/util.inc:69 sigkillbypid(..) - /etc/inc/util.inc:32 killbypid(..) - /etc/inc/gwlb.inc:85 stop_dpinger(..) - /etc/inc/gwlb.inc:301 setup_gateways_monitor(..) - /etc/rc.newwanip:195 ] Sep 20 19:42:05 php-fpm 318 /rc.newwanip: CALL sigkillbypid( /var/run/dpinger_WAN_DHCP~100.64.143.98~8.8.8.8.pid ) [ simplestacktrace2(..) - /etc/inc/util.inc:69 sigkillbypid(..) - /etc/inc/util.inc:32 killbypid(..) - /etc/inc/gwlb.inc:85 stop_dpinger(..) - /etc/inc/gwlb.inc:166 start_dpinger(..) - /etc/inc/gwlb.inc:309 setup_gateways_monitor(..) - /etc/rc.newwanip:195 ] Sep 20 19:42:05 php-fpm 318 /rc.newwanip: CALL start DPINGER( 8.8.8.8 ) [ simplestacktrace(..) - /etc/inc/gwlb.inc:181 start_dpinger(..) - /etc/inc/gwlb.inc:309 setup_gateways_monitor(..) - /etc/rc.newwanip:195 ] 0 Sep 20 19:42:05 php-fpm 318 /rc.newwanip: CALL sigkillbypid( /var/run/dpinger_OPT2_DHCP~100.64.240.50~8.8.4.4.pid ) [ simplestacktrace2(..) - /etc/inc/util.inc:69 sigkillbypid(..) - /etc/inc/util.inc:32 killbypid(..) - /etc/inc/gwlb.inc:85 stop_dpinger(..) - /etc/inc/gwlb.inc:166 start_dpinger(..) - /etc/inc/gwlb.inc:309 setup_gateways_monitor(..) - /etc/rc.newwanip:195 ] Sep 20 19:42:05 php-fpm 318 /rc.newwanip: CALL start DPINGER( 8.8.4.4 ) [ simplestacktrace(..) - /etc/inc/gwlb.inc:181 start_dpinger(..) - /etc/inc/gwlb.inc:309 setup_gateways_monitor(..) - /etc/rc.newwanip:195 ] 0
And it looks like dpinger is being killed and immediately started again, i suspect the old process is still 'shutting down'.. And deletes the pid file as a final step, while actually the new dpinger was already running..
Updated by Pi Ba about 6 years ago
This seems to fix it: https://github.com/pfsense/pfsense/pull/3987
Updated by Anonymous about 6 years ago
- Target version changed from 2.4.4-GS to 2.4.4-p1
Updated by Steve Wheeler about 6 years ago
I'm unable to replicate this is 2.4.4. I configured 3 WANs, all DHCP with one that fails to find a server. Only that WAN shows as pending after rebooting.
This looks like a timing issue though so might be hardware dependent.