Kentico负载均衡环境下单节点Web Analytics文件堆积问题求助

Hey there, let's walk through the most likely causes for your Web Analytics files piling up on only one of your three load-balanced Kentico servers—this is usually a mix of configuration quirks or easy-to-miss permission details, not necessarily a bug.

First: Check Kentico's Built-In Analytics Configuration #

Kentico relies on scheduled tasks and core settings to manage and clean up those log files, so start here:

• Verify Scheduled Tasks: Head to the Kentico Admin → System → Scheduled tasks and look for two critical tasks:
  • Web analytics data processing: This task converts raw log files into usable analytics data.
  • Web analytics log cleanup: This task deletes processed log files based on your retention rules.
    Make sure these tasks are enabled, and check if they're set to run on all servers (or at least the problematic one). In load-balanced setups, tasks are sometimes configured to run only on a single "primary" server—if that primary isn't the one with the pile-up, unprocessed files will stick around indefinitely.
• Check Analytics Retention Settings: Go to Settings → On-line marketing → Web analytics and verify the Log file retention period value. If it's set to an unusually long duration, files will take far longer to get cleaned up. Also ensure Process log files is enabled here.
• Confirm Log Path Configuration: Double-check the CMSAnalyticsLogPath setting in your web.config (or via the Admin's Settings → System → Files). If this path points to a local folder (like ~App_Data\CMSModules\WebAnalytics) and your processing task only runs on one server, that server won't pick up log files from other servers unless you're using a shared network path for analytics logs.

Next: Dig Deeper into Permissions (Even If You Think They're Set) #

You mentioned granting full permissions to Network Service and IIS_IUSRS, but there are a few easy-to-overlook gotchas:

• File-Level Permissions: Check the actual files that are piling up, not just the parent folder. Sometimes folder permissions don't inherit to existing files, or new files might be created with different access rules. Right-click a log file → Properties → Security to confirm the two accounts have Modify and Delete access.
• Application Pool Identity: What identity is your Kentico application pool running under? If it's a custom service account (not Network Service/IIS_IUSRS), that account also needs full permissions to the analytics folder. This is a super common oversight!
• File Locking Issues: Is another process holding onto these log files? Antivirus scanners, backup tools, or monitoring software can lock files, preventing Kentico from deleting them. Use a tool like Process Explorer to check which process has the files open.

Finally: Load-Balancing Specific Checks #

Since you're running 3 load-balanced servers, this adds a unique layer of complexity:

• Configuration Sync: Is the problematic server's Kentico configuration fully synced with the other two? Sometimes a misconfigured web.config or setting (like the analytics log path or task triggers) on just one server can cause this. Compare the web.config files across all three servers to spot discrepancies.
• Shared Storage Setup: If you're using local paths for analytics logs on each server, the processing task on one server can't access logs from another. The fix here is to configure a shared network folder for all servers to write their analytics logs to, then point the processing task to that shared path. This way, all logs get processed and cleaned up centrally.

内容的提问来源于stack exchange，提问作者Vidhyardhi Gorrepati