Tired of seeing the Xinetd error message repeating every 15 minutes? Learn the real cause and fix it permanently without confusion. Our Live Support Team is always here to help you.
Why the Xinetd Error Message Keeps Repeating Every 15 Minutes
If you’ve noticed the Xinetd error message repeating every 15 minutes, you’re not alone. Many pfSense users run into this repetitive log entry that pops up every quarter-hour, leaving them wondering what’s really happening behind the scenes.
At its core, this issue usually traces back to the filter sync process. The message you’re seeing comes from xinetd activating a service on port 6969, which is tied to the TFTP proxy. Even when TFTP proxy looks disabled, it might still wake up due to a configuration quirk in pfSense. Let’s look deeper into how this happens and how to stop it for good.
An Overview
What Xinetd Really Does
The xinetd daemon acts as a TCP wrapped super service. It manages access to several network services such as FTP, IMAP, and Telnet, while offering extended options for:
- Access control
- Detailed logging
- Port binding and redirection
- Resource and connection control
When a client attempts to reach a service under xinetd’s control, the daemon checks TCP wrapper access rules, validates permissions, and then spawns the correct service process. Once active, it steps aside and lets the client communicate directly with the server.
Why the Xinetd Error Message Keeps Appearing
The Xinetd error message repeating every 15 minutes usually means something is trying to restart or reconfigure services repeatedly. There are a few reasons this can happen:
1. TFTP Proxy Issue
The service on UDP port 6969 is linked to the TFTP proxy. Even when it’s disabled, a bug in certain pfSense versions can cause it to log activity every 15 minutes during sync.
2. File Permission or Ownership Errors
Wrong file permissions or ownership on configuration or executable files may prevent xinetd from starting certain services properly.
3. Firewall or Networking Misconfiguration
A faulty firewall or binding issue can block xinetd from opening its required ports, making it retry periodically.
4. Broken xinetd Configuration File
Any syntax or service definition errors inside /etc/xinetd.d/ can also lead to these constant log entries.
Interestingly, this repetitive error also links to a cron job that runs the command:
/etc/rc.filter_configure_syncThis command syncs pfSense firewall rules and triggers xinetd to reload services like TFTP every 15 minutes.
Stop Xinetd Errors for Good!
How to Stop the Xinetd Error Message Repeating Every 15 Minutes
Let’s go straight to the practical part.
1. Check and Disable the TFTP Proxy
- Go to System > Advanced.
- Under the Firewall & NAT tab, locate TFTP Proxy settings.
- Deselect all interfaces.
- Click Save.
- Check the xinetd log again to confirm if the repeated messages are gone.
It’s worth noting that unchecking the interfaces stops xinetd from binding to ports but doesn’t completely kill the service. pfSense developers have confirmed this behavior as a minor bug.
2. Review xinetd Configuration Files
- Open /etc/xinetd.d/ and inspect files for syntax errors.
- Ensure the command path defined in /etc/xinetd.d/xxx is correct.
- If unnecessary, remove the file:
rm /etc/xinetd.d/xxx- Then restart xinetd for changes to take effect:
service xinetd restartWhen It’s Safe to Ignore
In some cases, the Xinetd error message repeating every 15 minutes isn’t harmful. It may simply log during scheduled filter reloads or firewall rule updates. If you have schedule-based rules enabled, pfSense reconfigures the filter every 15 minutes, triggering that log each time. So, while it’s spammy, it’s not dangerous.
Conclusion
The Xinetd error message repeating every 15 minutes often looks more serious than it is. It mostly comes down to pfSense’s filter synchronization and TFTP proxy handling. Start by disabling the TFTP proxy, double-check your configuration files, and ensure there’s no corrupt xinetd entry. If nothing changes, upgrading to the latest pfSense build usually resolves it.
This isn’t a system-breaking issue, but if clean logs matter to you, a few minutes of tweaking can stop that annoying message once and for all.
