• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

GATE1 keeps going down, filter keeps reloading, apinger broken pipe

Scheduled Pinned Locked Moved General pfSense Questions
1 Posts 1 Posters 1.0k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • U
    UniCav
    last edited by Sep 10, 2012, 8:36 PM

    I've had a 2.0.1-RELEASE box running about a month. I have 2 WAN's and tried using load balancing but had too many issues with several secure sites so I disabled it. Recently I noticed a lot of delays on browsing, IRC kept bouncing, email would hang. Checked the logs and discovered that GATE1 kept showing as down. I was using the ISP's primary DNS on each WAN as the Alternative monitoring IP and had no problem pinging them but I deleted them so it would use the gateway IP, which I can also ping.  Initially I got a log error that it couldn't determine the status of the gateways so it declared them always up. I haven't had the network bounce since disabling the gateway monitoring.  I am still seeing some errors that keep coming up.

    Sep 10 14:30:09 apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
    Sep 10 14:30:09 apinger: Error while feeding rrdtool: Broken pipe
    Sep 10 14:29:15 php: : filter_generate_address: is not a valid source port.
    Sep 10 14:29:09 php: /interfaces.php: Creating rrd update script
    Sep 10 14:29:09 apinger: Starting Alarm Pinger, apinger(54287)
    Sep 10 14:29:09 check_reload_status: Reloading filter
    Sep 10 14:29:08 apinger: Exiting on signal 15.

    Notice apinger exits, then the filter reloads, then the "php: : filter_generate_address: is not a valid source port error" and then apinger rrdtool broken pipe and then apinger respawing too fast.  this is continually coming up.  I have looked through /tmp/rules.debug but don't really see anything that indicates a problem with a rule.  Any suggetions? Thanks in advance!

    1 Reply Last reply Reply Quote 0
    1 out of 1
    • First post
      1/1
      Last post
    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
      This community forum collects and processes your personal information.
      consent.not_received