[FC3] Syslog issue

[Tim Wunder]

On 11/18/2004 11:08 AM, I believe that Net Llama! wrote:

> On Thu, 18 Nov 2004, Tim Wunder wrote:
> 
>>I've installed FC3 with XFS on an old AMD K6 with 284 MB RAM and an 80 GB
>>Seagate HDD. During the install, the installer froze when configuring GRUB.
>>It pegged the CPU at 99% for several hours before I gave up and rebooted the
>>system from the command line. The system did boot up OK, but syslog doesn't
>>seem to be running.
> 
> 
> That's a grub bug where it attempts to write directly to the block device
> instead of the filesystem layer.  This only happens with XFS.  The only
> known workaround is to make /boot something other than XFS.  I believe i
> read about a way of killing the hung process from the installer virtual
> console, and then manually writing grub to the MBR.  It worked for me
> once, but not other times.
> 

Ahh, I think I recall reading that somewhere. The system probly booted OK 
'cuz I did a reinstall using XFS after first installing ext3. Didn't know 
you could install FC3 with XFS at first. The GRUB from the first install was 
probly still there, and OK. (Only thing changed between installs was the 
filesystem type. Partition sizes and mount points remained the same.)

> 
>>All error messages are being displayed on the Console and nothing gets
>>written to /var/log/messages.
>>
>>When I execute:
>># service syslog restart
>>Shutting down kernel logger:                               [  OK  ]
>>Shutting down system logger:                               [FAILED]
>>Starting system logger: syslogd: error while loading shared libraries:
>>libc.so.6: cannot open shared object file: Permission denied
>>                                                            [FAILED]
>>Starting kernel logger:                                    [  OK  ]
>>
>># ll /lib/libc.so.6
>>lrwxrwxrwx  1 root root 13 Nov  7 20:07 /lib/libc.so.6 -> libc-2.3.3.so
>># ll /lib/libc-2.3.3.so
>>-rwxr-xr-x  1 root root 1402592 Oct 27 18:45 /lib/libc-2.3.3.so
>>
>>Doesn't seem to be a unix permissions issue.
>>
>>Any ideas? Could this be some sort of SELinux permission thing?
> 
> 
> maybe.  which policy did you select?
> 

# cat /etc/selinux/config
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing - SELinux security policy is enforced.
#       permissive - SELinux prints warnings instead of enforcing.
#       disabled - SELinux is fully disabled.
SELINUX=enforcing
# SELINUXTYPE= type of policy in use. Possible values are:
#       targeted - Only targeted network daemons are protected.
#       strict - Full SELinux protection.
SELINUXTYPE=targeted

Does any of that mean anything to you?
Guess I should read up on FC3's SELinux implementation. Got any pointers?

Thanks,
Tim