Automatic nightly YUM updates with yum-cron

shall I create a normal cron yum update y ??

---

 

I got a notification at my Pushover : Failed to check for updates with the following error message: failed to build transcation: uw-imap devel 2007....x86_64 requires libc client..
and when I ran the below command, I got nothing.

Code:

grep yum.cron /var/log/cron | tail -10

is there any errors ?

 

Overnight yum-cron updated to the following openssl packages on CentOS 7:

Code:

openssl x86_64 1:1.0.2k-16.el7_6.1 updates 493 k
openssl-devel x86_64 1:1.0.2k-16.el7_6.1 updates 1.5 M
openssl-libs x86_64 1:1.0.2k-16.el7_6.1 updates 1.2 M

Is this Ok, do I need to somehow get back to 1.1.1b or do these packages have nothing to do with the nginx/php compilation process?

I've excluded MariaDB upgrades by altering the exclude line in /etc/yum.conf:

Code:

exclude=*.i386 *.i586 *.i686 nginx* php* mysql* MariaDB*

Wondering if I should do the same with openssl or any other packages (as not able to use --disableplugin=priorities --enablerepo=remi)?

 

Sorry going back to the exclude situation I didn't edit yum.conf, I added to the base section of /etc/yum/yum-cron.conf:

Code:

[base]
exclude=*.i386 *.i586 *.i686 nginx* php* mysql* MariaDB*

Is this also not advisable?

 

Forgive my noob question, I am furiously reading all the documentation I can find on centmin but there are some basic questions I can't really find an answer for.
If I missed the answer from the docs I deeply apologise.

It is my understanding that I can safely schedule nightly yum update with no problems. What I don't understand is, since centmin carefully pick and choose specific versions of each package to optimise them, is there any risk yum will update one of the packages breaking the optimisations or worse, breaking the carefully tuned working connections between them?

Again, I hope I am not wasting anybody's time..

using centmin mod 123.09beta01

 

Huh, I had no idea it does that. I noticed it seem to be building a few packages manually, occasionally when running centmin, but I didn't give it much thought. I suppose even if a system package was installed, the ones built by centmin should be in a path with higher priority anyway.

The only packages I excluded from yum-cron are all of ImageMagick packages, cause centmin has a separate installer script which also includes building the php extension, that you can also add to your cronjob.

I've had mine setup that way for a few years already, with no issues worth mentioning, but still take it with a grain of salt (especially the bits about the packages possibly being installed into path with higher priority or whatever).