[ale] RH9 Logwatch Errors / glibc stuff

Dow Hurst dhurst at kennesaw.edu
Mon Nov 17 10:21:05 EST 2003


I should clarify:

You must have booted from the install CD to get to rescue mode, however, 
what rpms do you remove?  Just glibc?  Or do you have to know all the 
updates that were applied and reinstall all of the original rpms?  Thanks,
Dow


Dow Hurst wrote:

> I've logged out and back in but haven't rebooted yet.  I need my 
> system running so haven't taken the chance.  I was hoping if there 
> really is a problem that RHN would show an update available.  Nothing 
> shows up when checking for updates other than it saying I'm uptodate.  
> I've let all the updates get applied as they appeared.  So the glibc 
> is updated on this machine.  I am not going to reboot until I know 
> what to do to fix it.  What is the normal procedure under RH9 to 
> recover from this situation?  Boot with the install CD?
> Dow
>
>
> Steve Nicholas wrote:
>
>> Hello Ale,
>> A two parter here.
>>
>> 1.  Installed RH9 from RH7.2 (install, not an upgrade).  Summary:  What
>> was broke in 7.2 appears to work, and things that worked in 7.2 are 
>> broke
>> in 9.0 :-(
>>
>> Logwatch returns the error message:
>>
>> Wrong configuration entry for "Service", if "All" selected, only "-" 
>> items
>> are allowed
>>
>> Worked in 7.2.  Looked at logwatch.org, linuxquestions.org, and google.
>> No luck.  Ditto for the man page and any FAQ I found.  Line 400 
>> appears to
>> be where logwatch.pl dies.  Running RH9 2.4.20-20.9.  RHs version is 
>> from
>> ~ 03/03, d/l'd latest version 5.0.1 (11/03 - rpm) and ran into the same
>> brick wall.  Any thoughts would be appreciated.
>>
>> 2. RH glibc updates:
>>
>> Danger Will Robinson Danger!!
>>
>> When I did the install, was diligent and d/l'd all patches and 
>> bugfixes -
>> including a glibc bugfix.  Box broke big time upon reboot.  I had to 
>> boot
>> off of cd into rescue mode, rm glibc, and reinstall the original and
>> reboot.  Read that it's not good to update glibc EXCEPT for security
>> issues.  Almost did this one until I started seeing msgs resembling 
>> what I
>> experienced the first time.
>>
>> For those who did the update, pls let the list know how things go 
>> when you
>> DO reboot...Inquiring minds want to know.  I may test it out, but not
>> until I get a few things sorted out and a good burn to a cd for backup.
>>
>> Hope #2 helps someone, hope someone can assist in #1.
>>
>> Steve
>>
>> =======================================================
>> | Steve Nicholas             |                        |
>> | Software Systems Engineer  |  A risk is not a risk  |
>> | Georgia State University   |  until it is taken.    |
>> | snicholas at gsu.edu          |                        |
>> | 404-651-1062               |  BBROYGBVGW            |
>> =======================================================
>>
>>
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> http://www.ale.org/mailman/listinfo/ale
>>
>>  
>>
>

-- 
__________________________________________________________
Dow Hurst                  Office: 770-499-3428            *
Systems Support Specialist    Fax: 770-423-6744            *
1000 Chastain Rd. Bldg. 12                                 *
Chemistry Department SC428  Email:   dhurst at kennesaw.edu   *
Kennesaw State University         Dow.Hurst at mindspring.com *
Kennesaw, GA 30144                                         *
************************************************************
This message (including any attachments) contains          *
confidential information intended for a specific individual*
and purpose, and is protected by law.  If you are not the  *
intended recipient, you should delete this message and are *
hereby notified that any disclosure, copying, distribution *
of this message, or the taking of any action based on it,  *
is strictly prohibited.                                    *
************************************************************




More information about the Ale mailing list