# Troubleshooting This chapter provides tips and guidelines about troubleshooting problems related to `syslog-ng`. * As a general rule, first try to log the messages to a local file. Once this is working, you know that AxoSyslog is running correctly and receiving messages, and you can proceed to forwarding the messages to the server. * Always check the configuration files for any syntax errors on both the client and the server using the `syslog-ng --syntax-only` command. * If the AxoSyslog server does not receive the messages, verify that the IP addresses and ports are correct in your sources and destinations. Also, check that the client and the server uses the same protocol (a common error is to send logs on UDP, but configure the server to receive logs on TCP). If the problem persists, use `tcpdump` or a similar packet sniffer tool on the client to verify that the messages are sent correctly, and on the server to verify that it receives the messages. * To find message-routing problems, run AxoSyslog with the following command `syslog-ng -Fevd`. That way AxoSyslog will run in the foreground, and display debug messages about the messages that are processed. * If AxoSyslog is closing the connections for no apparent reason, be sure to check the log messages of `syslog-ng`. You may also want to run `syslog-ng` with the `--verbose` or `--debug` command-line options for more-detailed log messages. You can enable these messages without restarting `syslog-ng` using the `syslog-ng-ctl verbose --set=on` command. For details, see the [The syslog-ng.conf manual page](../docs/axosyslog-core/app-man-syslog-ng/syslog-ng.conf.5/index.md). * Build up encrypted connections step-by-step. First create a working, unencrypted (for example, TCP) connection, then add TLS encryption, and finally, client authentication if needed. * If you use the same driver and options in the destination of your AxoSyslog client and the source of your AxoSyslog server, everything should work as expected. Unfortunately, there are some other combinations, that may seem to work, but result in losing parts of the messages. For details on the working combinations, see [Things to consider when forwarding messages between AxoSyslog hosts](../docs/axosyslog-core/chapter-concepts/concepts-things-to-consider/index.md). * If you’re using [FilterX](../docs/axosyslog-core/filterx/index.md), see [Troubleshooting FilterX](../docs/axosyslog-core/filterx/filterx-troubleshooting/index.md) for specific tips. ## Support In case you need help with any of the AxoSyslog projects, or directly with `syslog-ng`, you have several ways to contact us: * Open a [GitHub issue in the AxoSyslog repository](). * Chat with us in the [syslog-ng or axosyslog channels of the Axoflow Discord server](). * Fill the [Axoflow contact form](). We also provide consulting and professional services for logging and observability related projects. [Contact us]() if you need our help! * * * [Possible causes of losing log messages](../docs/axosyslog-core/chapter-troubleshooting-syslog-ng/concepts-losing-messages/index.md) [Creating core files](../docs/axosyslog-core/chapter-troubleshooting-syslog-ng/syslog-ng-core-files/index.md) [Collecting debugging information with strace, truss, or tusc](../docs/axosyslog-core/chapter-troubleshooting-syslog-ng/syslog-ng-strace-truss-tusc/index.md) [Running a failure script](../docs/axosyslog-core/chapter-troubleshooting-syslog-ng/syslog-ng-failure-script/index.md) [Stopping the syslog-ng process](../docs/axosyslog-core/chapter-troubleshooting-syslog-ng/syslog-ng-stop/index.md) [Reporting bugs and finding help](../docs/axosyslog-core/chapter-troubleshooting-syslog-ng/report-bugs/index.md) [Recover data from orphaned diskbuffer files](../docs/axosyslog-core/chapter-troubleshooting-syslog-ng/diskbuffer-recovery/index.md) [Error messages](../docs/axosyslog-core/chapter-troubleshooting-syslog-ng/error-messages/index.md) [SELinux prevents using the execmem access on a process](../docs/axosyslog-core/chapter-troubleshooting-syslog-ng/troubleshooting-selinux-issue-creating-parsers/index.md) Last modified June 16, 2025: [Adds filterx troubleshooting section (b168cca)]()