Just remove the tc.log File and afterwards the mariadb.service will start.
sudo: unable to load /usr/lib64/libsss_sudo.so: /usr/lib64/libsss_sudo.so: cannot open shared object file: No such file or directory
Reason: ? Maybe due an Update it got broken.
Solution: yum -y install libsss_sudo
Have you ever had such a problem?
# reboot bash: /sbin/reboot: Input/output error # shutdown -r now bash: /sbin/shutdown: Input/output error
Obviously, there is a problem with your drive. These commands are failing because the kernel is unable to load the /sbin/reboot and /sbin/shutdown binaries from the disk so that it can execute them.
At least you could try thisecho 1 > /proc/sys/kernel/sysrq
and then talk direct to the kernelecho b > /proc/sysrq-trigger
on the foreman server I had to run:
puppet cert clean client-certname
on the client
rm -rf /var/lib/puppet/ssl
puppet agent -td --server=<foremanservername>
To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certificate.
On the master:
puppet cert clean <fqdn-hostname>
On the agent:
1a. On most platforms: find /var/lib/puppet/ssl -name <fqdn-hostname>.pem -delete
1b. On Windows: del "\var\lib\puppet\ssl\certs\<fqdn-hostname>.pem" /f
2. puppet agent -t
Easy as this
virsh setmem <vmdomname> 4096M --live --config