Red Hat Bugzilla – Bug 80496
up2date registration failures mailed every day
Last modified: 2007-04-18 12:49:19 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218 Description of problem: I tried to register my machine a few times before the Phoebe channel was set up in RHN. Since then, I've got messages in the mail every day, from LogWatch, containing the same errors. I suppose these will only go away when logrotate moves them to a separate file, if ever... Version-Release number of selected component (if applicable): How reproducible: Didn't try Steps to Reproduce: 1.Try to register a machine in an invalid channel 2.Read LogWatch e-mail every day Actual Results: Every day, it will say something like: ################### LogWatch 4.0.3 (10/14/02) #################### Processing Initiated: Fri Dec 27 04:02:02 2002 Date Range Processed: yesterday [...] --------------------- up2date Begin ------------------------ **Unmatched Entries** [Mon Dec 23 15:46:38 2002] up2date Error communicating with server. The message was: Error Message: Your account does not have access to any channels matching (release='8.0.92', arch='i686-redhat-linux') Error Class Code: 19 Error Class Info: Architecture and OS version combination is not supported. If you have a registration number, please register with it first at http://www.redhat.com/now and then try again. Explanation: An error has occurred while processing your request. If this problem persists please submit a bug report to rhn-help@redhat.com. If you choose to submit the bug report, please be sure to include details of what you were trying to do when this error occurred and details on how to reproduce this problem. [...] ---------------------- up2date End ------------------------- ###################### LogWatch End ######################### Expected Results: These messages should have been included only in the e-mail I got on Dec 24's morning. Additional info:
Can you try running 'chkconfig --level 135 rhnsd off' and seeing if that is the actual cause?
It isn't the cause. rhnsd has been enabled since I installed the new beta, and it hasn't generated any such messages. Now, that I've just tried to register the machines, hoping a RHN channel would have been set up, I get the messages from logwatch.
logwatch-4.3.1-2 does not contain the scripts that should go inside the /etc/log.d/scripts/logfiles/{autorpm,cron,up2date} directories. One job of these scripts is to apply to the logs a filter based on the date requested. The rpm should be updated to include the scripts and the this problem would be resolved. I have the same problem with the cron section of logwatch reports.
Created attachment 90609 [details] modification of logwatch.spec to include the missing scripts
logwatch 4.3.2 + your patch will be in rawhide, thanks.
Created attachment 95408 [details] Improved spec file patch to get all scripts/logfiles/* subdirectories The problem with the previous patch is the directory names are still hardcoded, even though the list now includes all current scripts/logfiles/* subdirectories. This will break if any new subdirectories are added in future source tarballs. A better approach is to borrow the loop that Kirk Bauer uses in his spec file, and use wildcards in the %files section. See my improved patch.
Thanks Gilles - that was just what was needed! Patch added after a long delay.
*** Bug 99438 has been marked as a duplicate of this bug. ***