CentOS

Shouldn't be that considered as a bug then?

Hi, I am running an Ansible Playbook to deploy LAMP stack on CentOS in AWS. It is working perfectly when I am running it against local (Virtualbox VM) CentOS instance, but it is failing on Firewalld when I am deploying in on to CentOS (standard CentOS AMI) in AWS. The error I am experiencing in AWS:...

Yes, for some reason I had wrong permission set on authorized_keys file. Weird. Thanks for hint.

giulix63 wrote:Did you install the public key on the server? See #2 here.

Of course I've installed, it is not my first adventure with Linux, but I got used to this thing works out of the box in Slackware or Debian. Unfortunately I need one server based on CentOS.

gerald_clark wrote:Try "restorecon -r /home".

Yes, I tried before posted here.

I need CentOS to operate using password and keys. So I've added new user (nagios) and generated keys. File permissions are right: # ls -la /home/nagios/ total 16 drwx------. 3 nagios nagios 90 Mar 10 14:48 . drwxr-xr-x. 4 root root 33 Mar 10 14:47 .. -rw-------. 1 nagios nagios 76 Mar 10 14:52 .bash...

I've installed Centos Multiarch, and unfortunately all xfs partitions are in inode64 mode. How can I change it to inode32 or install centos with inode32 support by default?
I've tried remount it with -o inode32 option as well as modify fstab, but with no luck.

I have domain controller configured on Windows, and mixed Windows and Debian LDAP clients. I would like to configure Centos 7 as LDAP client in the same way as Debian desktops are, but for some reason Centos won't work. Debian /etc/krb5.conf: [libdefaults] default_realm = DOMAIN.COM krb4_config = /e...