Xinetd error message repeating every 15 minutes - HELP

kesawi

I have this same issue as well since upgrading from 2.2.6 to 2.3.1 (and now 2.3.2).

Gateways are up
Happens whether monitoring is disabled or enabled.
Happens whether state killing on gateway failure is disabled or enabled

t00th

I'm in the same boat. Not using TFTP, but this reload happens often and resets my IPSEC tunnel as well…

markn62

Anyone else have a cron entry; 0,15,30,45;;;;;root;/etc/rc.filter_configure.sync ? This appears to be causing it for me. Can this cron entry be removed without causing other issues? How often should the filter be resync'd?

jimp

That cron entry would be from having scheduled rules (or at least having schedules defined). If you are not using scheduled rules, you can removed it. The filter will sync when config changes are applied or from automated events like gateway failures/recovery.

kesawi

So if you need the filters to resync, how do you stop the log spam from occurring? I've followed all of the advice provided.

jimp

At the moment, you don't. There isn't a way in xinetd to stop it from being so chatty.

kesawi

What about stopping the underlying service that appears to be causing it to be chatty (i.e. the TFTP service)?

markn62

Although I also have no interfaces selected I find a service entry in /var/etc/xinetd.conf, see attached. So I rem'd it out.

image.png_thumb

markn62

Now I only get log entries "check_reload_status" "syncing firewall" every 15 minutes without readjusting service 6969-udp. I'll reduce the cron frequency as well.

markn62

Well that didn't last long. Some other file removed the #rem from xinetd.conf. Jimp, can you say how the service gets entered into the file so TFTP proxy can be rem'd out permanently?

jimp

FYI I just pushed a fix for this for all of the next release branches. If no interfaces are selected for TFTP proxy and reflection is not set to NAT+Proxy, the daemon will not attempt to run.

johnpoz

Yeah ;) Thanks JimP

doktornotor

@jimp:

FYI I just pushed a fix for this for all of the next release branches. If no interfaces are selected for TFTP proxy and reflection is not set to NAT+Proxy, the daemon will not attempt to run.

rebytr

Will this fix be in the 2.4 release?

jimp

2.4, 2.3.3, and 2.3.2_2, it's in all the branches. Whichever one we put out next will have it.

TomT

Hi

2.3.2-RELEASE-p1 (amd64)

I've just noticed I'm getting this as well.
No Interfaces selected in 'TFTP Proxy'.

Is there anything I can do manually until the next release is available ?

Thanks

doktornotor

Yeah, you can manually upgrade to 2.3.3-rc.

skeating

Any idea when 2.3.2.2 will come out?

jimp

There won't be a 2.3.2_2, 2.3.3 is coming out shortly. Probably early next week, release images are building now and then we have to beat it up with testing for a couple days.

edener

@kesawi:

I have this same issue as well since upgrading from 2.2.6 to 2.3.1 (and now 2.3.2).

Gateways are up

Happens whether monitoring is disabled or enabled.

Happens whether state killing on gateway failure is disabled or enabled

I have the same issue as above although i use the most recently stable version. I'm a newcomer of pfsense. I have to say the help docs are not good. For example, I cant even find a sample or demo to help set up flow control of my network which is so easy in other cheap routers. Pfsense is professional but not user friend. Who can show me how to set a rule to block MACs or bind MACs to a fixed IP?