Pfsense 2.1-release - Gateway aPinger broken?

BobDarnit

Can anyone specify if apinger has been fixed yet… or if there is a good work around? I've got two WANs, both static, and since upgrading to 2.1p1 it's needed the apinger service reset frequently. I've got multiple other devices at other locations, DHCP and Static that have had to reset the apinger since the 2.1 upgrades started.

Thanks for any help.

Bob

pubmsu

Hi Bob,

Please try the work around we used and got good result:

https://forum.pfsense.org/index.php?topic=78502.0

Thanks,
msu

saxd40

There's definitely still a problem in 2.1.4 and since 2.1.5 just released and I know that they are still trying to figure out the problem, I'm assuming it is still an issue in 2.1.5.

I have this problem on ONE pfSense box with a flakey T1 (yes, they DO exist, but apparently only in Detroit). I have never seen this on any other of my many pfSense installations.

They are aware of the issue and trying to figure it out. I'm in communication with them and have given them access to the ONE firewall where I have this problem.

In the meantime, I'm going to create a CRON job to restart apinger service at given intervals. BTW, this command will restart it:

/usr/local/sbin/pfSsh.php playback svc restart apinger

naras

Yes, it's still there, hope it will disappear in 2.2.

pubmsu

Please report it and discuss in the following 2.2 thread:

https://forum.pfsense.org/index.php?topic=78502

naras

@pubmsu:

Please report it and discuss in the following 2.2 thread:

https://forum.pfsense.org/index.php?topic=78502

I already did.

Supermule

I have this Cron job running every 5 minutes and for now it has been running no isssues.

pkill /usr/local/sbin/apinger -c /var/etc/apinger.conf

It seems some sort of buffer is filled on WAN DHCP interfaces and it begins to "suffer".

I havent got any issues on static WAN interfaces.

Derelict

I just had to disable gateway monitoring on a pfSense in a datacenter because apinger started seeing 6% loss no matter what was going on. Steady - every sample. 2.1.5 i386.

pubmsu

Please report it and discuss in the following 2.2 thread:

https://forum.pfsense.org/index.php?topic=78502

hmh

@krylou:

I`ve found temporary solution - restarting apinger every 5 minutes.

Open shell via putty

Go to /usr/local/www
and create file apinger.php with the following content:
require_once("/etc/inc/service-utils.inc");
require_once("/etc/inc/globals.inc");
require_once("/etc/inc/vslb.inc");
require_once("/etc/inc/gwlb.inc");

service_control_restart(apinger,restartservice)
?>

chmod 755 apinger.php

To run it manually you can just open http://pfsense/apinger.php

Then install cron package via pfsense UI and add new job:
*/5 * * * * /usr/local/bin/php /usr/local/www/apinger.php

Little extended script:


require_once("/etc/inc/service-utils.inc");
require_once("/etc/inc/globals.inc");
require_once("/etc/inc/gwlb.inc");

$counter = 0;
$a_gateways = return_gateways_array();
$gateways_status = array();
$gateways_status = return_gateways_status(true);

foreach ($a_gateways as $gname => $gateway) {
	if ($gateways_status[$gname]) {
		$str_data = $gateways_status[$gname]['delay'];
		$pos = substr($str_data,0,strpos($str_data, "ms"));
		if (floatval($pos) > 500 ) {
			$counter++;
			#print_r($counter ." - ". $pos ."\r\n");
		}	
	}	
}
if ($counter > 0) {
	service_control_restart(apinger,restartservice);
}
?>

@hmh:

Little extended script:


require_once("/etc/inc/service-utils.inc");
require_once("/etc/inc/globals.inc");
require_once("/etc/inc/gwlb.inc");

$counter = 0;
$a_gateways = return_gateways_array();
$gateways_status = array();
$gateways_status = return_gateways_status(true);

foreach ($a_gateways as $gname => $gateway) {
	if ($gateways_status[$gname]) {
		$str_data = $gateways_status[$gname]['delay'];
		$pos = substr($str_data,0,strpos($str_data, "ms"));
		if (floatval($pos) > 500 ) {
			$counter++;
			#print_r($counter ." - ". $pos ."\r\n");
		}	
	}	
}
if ($counter > 0) {
	service_control_restart(apinger,restartservice);
}
?>

What does this do ?

btw. This:

@krylou:

I`ve found temporary solution - restarting apinger every 5 minutes.

Open shell via putty

Go to /usr/local/www
and create file apinger.php with the following content:
require_once("/etc/inc/service-utils.inc");
require_once("/etc/inc/globals.inc");
require_once("/etc/inc/vslb.inc");
require_once("/etc/inc/gwlb.inc");

service_control_restart(apinger,restartservice)
?>

chmod 755 apinger.php

To run it manually you can just open http://pfsense/apinger.php

Then install cron package via pfsense UI and add new job:
*/5 * * * * /usr/local/bin/php /usr/local/www/apinger.php

and this :

@TechSavvySam:

In the meantime, I'm going to create a CRON job to restart apinger service at given intervals. BTW, this command will restart it:

/usr/local/sbin/pfSsh.php playback svc restart apinger

Both kill my RD Graphs. Is that just me ?

kamran

**Just disable NTPd time sync daemon.

apinger wil become stable.**

David_W

@kamran:

**Just disable NTPd time sync daemon.

apinger wil become stable.**

That might help if you're running pfSense in a VM, but the problems with apinger are nowhere near that simple to solve.

apinger has been replaced by dpinger in pfSense 2.3. Though 2.3 is still in beta, the core functionality is now very stable and it has a lot of worthwhile enhancements and fixes over 2.2.x.

Packages are still a mixed bag on 2.3 - some have been converted, some are available but haven't had a proper GUI conversion and others are not available at this point.

If you want to try 2.3, I strongly recommend backing up your configuration and making sure you have working 2.2.6 install media to hand before upgrading. That way, you can revert easily to 2.2.6 if necessary.