Bug 64392
| Summary: | dns_cache missing, preventing webalizer from running | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Chris Ricker <chris.ricker> |
| Component: | webalizer | Assignee: | Than Ngo <than> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | carl, mike |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-05-10 17:31:07 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Chris Ricker
2002-05-03 14:59:00 UTC
It seems to run on my system, but I do receive the error as stated above. Do an ls -l of /var/www/html/usage and you'll see the date/time changes to the time it was last run. It's fixed in 2.01_10-5. Does this fix includes some cron entries which would run 'webazolver' from time to time? dns_cache does not seem to be very useful when it is stale. Also a resolution notice could include this tidbit that it is enough to run 'webazolver' to create the required dns_cache.db or it can be commented out in /etc/webalizer.conf file. Both actions do not require switching to rawhide stuff. That information can be found in 'man webalizer' but in a somewhat obscure form. I've installed webalizer-2.01_10-9 and I'm still getting the daily message "Error: Unable to open DNS cache file /var/lib/webalizer/dns_cache.db" Everything works correctly, but I'd prefer to not get that message. Than, can you tell us what you did to fix it in 2.01_10-5? i have made the changes in /etc/webalizer.conf. It could be that you still have the old config file on your system after upgrade process. Please check it again. An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2002-254.html |