Xinetd error message repeating every 15 minutes - HELP

jimp

It is most likely from the filter sync. That message is from xinetd that is activating for one service on port 6969, which would be the TFTP proxy. Deselect all interfaces on System > Advanced, Firewall & NAT tab in the TFTP Proxy list, then save, and it should deactivate that service.

rebytr

I'm seeing the same spam in my system log. I tried the suggestion, but that didn't resolve it. I didn't have any interfaces selected under the TFTP Proxy section when I checked. Tried selecting all my interfaces, then saved it, then deselected them, then saved again. But messages still appear every 15 min.

Jun 10 21:00:00	xinetd	23343	Reconfigured: new=0 old=1 dropped=0 (services)
Jun 10 21:00:00	xinetd	23343	readjusting service 6969-udp
Jun 10 21:00:00	xinetd	23343	Swapping defaults
Jun 10 21:00:00	xinetd	23343	Starting reconfiguration

georgeman

It's indeed the TFTP proxy. Unchecking all the interfaces just prevents binding I guess, but does not stop the service. I think that it was cmb who confirmed on some thread that this was "sort of" a bug

router_wang

@jimp:

It is most likely from the filter sync. That message is from xinetd that is activating for one service on port 6969, which would be the TFTP proxy. Deselect all interfaces on System > Advanced, Firewall & NAT tab in the TFTP Proxy list, then save, and it should deactivate that service.

I'm not using TFTP proxy and this is happening quite frequently and disturbing traffic when it happens.

cmb

@router_wang:

I'm not using TFTP proxy and this is happening quite frequently and disturbing traffic when it happens.

It's absolutely not disturbing traffic, it's nothing but log spam.

Whatever is triggering the filter reload is the source of the "disturbing traffic", but it's probably that you're having ISP issues.

router_wang

@cmb:

@router_wang:

I'm not using TFTP proxy and this is happening quite frequently and disturbing traffic when it happens.

It's absolutely not disturbing traffic, it's nothing but log spam.

Whatever is triggering the filter reload is the source of the "disturbing traffic", but it's probably that you're having ISP issues.

Across internal networks.

jimp

If you have a gateway showing as "down", and state killing on gateway failure enabled, then it would reset the states each time the filter reloads.

So fix the down gateway, disable monitoring for it, or unset the state killing on gateway failure option.

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.