Things to check when logging stops
When AXS stops recording visits to your site, there are several possible reasons:
The file system no longer allows AXS to save to the "/axs/log.txt" file. This could be due to insufficient disk space, due to a user disk quota being exceeded, or file permissions being reset.
Or, the "ax.pl" logging script no longer functions. This could happen due to a Perl syntax error while editing the script, for example. Sometimes "ax.pl" fails even when "ax-admin.pl" continues to work.
Or, most commonly, the AXS system and files continue to work okay, but the tracking tags on your HTML pages are no longer present or are no longer working.
Follow these steps to isolate which of these problems you are facing. Note that if AXS is still logging some traffic, but not as much traffic as you expect, then the problem is almost certainly with your tracking tags.
Go to ax-admin and click the link "Instructions for Tagging".
Check the "Filesystem Test". Does it pass? If not, resolve that problem first. Failures may happen due to insufficient disk space on the server, a user disk quota that is exceeded, or a file permissions problem.
Scroll down to "Webmaster Logging Override". Are your visits being logged? Make sure that they are, so that you can test. You may need to go to ax-admin => Customize to disable webmaster logging overrides.
Click the "example link". Are you redirected to Yahoo?
If not, there is a problem with ax.pl. Resolve that first. You should see an error message instead of the redirect, and the error message will give clues on how to resolve the problem.
Return to ax-admin. Click "View in Database Format". Is your redirect to Yahoo listed at the top? If not, there is a problem with ax.pl. Resolve that first.
If your click-through to Yahoo worked and was logged, then the problem is with your AXS tags on your HTML pages, not with AXS itself.
"Things to check when logging stops" https://www.xav.com/scripts/axs/help/1005.html