Re: logrotate errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2004-07-01 at 09:51, Aaron Ross wrote:
> Process contexts:
> Current context:        root:sysadm_r:sysadm_t
> Init context:           system_u:system_r:kernel_t
> /sbin/mingetty          system_u:system_r:kernel_t
> /usr/sbin/sshd          system_u:system_r:kernel_t
> 
> File contexts:
> Controlling term:       root:object_r:devpts_t
> /etc/passwd             root:object_r:file_t
> /etc/shadow             root:object_r:file_t

This means that you haven't labeled your filesystems.  Run 'fixfiles
relabel' and reboot.

> And here is an example of the errors I'm seeing:
> 
> error: error getting file context /usr/local/apache/logs/access_log: No 
> data available

The file has no security context assigned, so logrotate is unable to get
the context of the log prior to rotation in order to preserve it.

-- 
Stephen Smalley <sds@xxxxxxxxxxxxxx>
National Security Agency


[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux