This happens when you re-create or mess with
/var/log/secure file. This will break file permissions, especially if SELinux is enabled.
Do the following:
/var/log/secure is owned by
$ sudo chown root:root /var/log/secure
Make sure the permission is set to
$ sudo chmod 600 /var/log/secure
If SELinux is enabled, you can temporarily disable while troubleshooting your issue
$ sudo setenforce 0
If you decide to keep SELinux enabled, make sure the file has the following context:
$ ls -lZh /var/log/secure
To manipulate SELinux on the fly (copy context from an existing known working):
$ sudo chcon --reference /var/log/dmesg /var/log/secure
To manipulate SELinux context permanently, use the semanage command instead.