Digging some more, the testing iso had a bad app-network package which was in the updates-testing repo. I will have one more attempt at building the iso, but ultimately it is not totally necessary as the workaround we are using (a backgound update of app-edition and app-registration when you select the version of ClearOS during the first run wizard. We have app-edition require the new ca-certificates package, so the ca-certificates package gets updated then, before the main update and marketplace steps) works but does require us to keep a copy of ca-certificates in the rarely used clearos-infra repo.

Re: Yum update error

Ouch. You are miles behind. Try:

Re: Is this gona be a problem when i reboot after Auto kernel update?

You don't update your system very often! And you are still one kernel behind. Current is kernel-3.10.0-1160.42.2.el7.x86_64. When you next boot, it should boot off kernel-3.10.0-1160.41.1.el7.x86_64 so that should be OK. The issue is if you try selecting one of the 1062 kernels but these should be your third and fourth choice for booting.

You could try what it suggests:But I have never tried it. On the other hand, if you aren't worried about having the latest microcode package in those kernels, then don't bother. I probably wouldn't bother.

Re: Is this gona be a problem when i reboot after Auto kernel update?

You don't update your system very often! And you are still one kernel behind. Current is kernel-3.10.0-1160.42.2.el7.x86_64. When you next boot, it should boot off kernel-3.10.0-1160.41.1.el7.x86_64 so that should be OK. The issue is if you try selecting one of the 1062 kernels but these should be your third and fourth choice for booting.

You could try what it suggests:But I have never tried it. On the other hand, if you aren't worried about having the latest microcode package in those kernels, then don't bother. I probably wouldn't bother.

Re: Is this gona be a problem when i reboot after Auto kernel update?

You don't update your system very often! And you are still one kernel behind. Current is kernel-3.10.0-1160.42.2.el7.x86_64. When you next boot, it should boot off kernel-3.10.0-1160.41.1.el7.x86_64 so that should be OK. The issue is if you try selecting one of the 1062 kernels but these should be your third and fourth choice for booting.

You could try what it suggests:But I have never tried it. On the other hand, if you aren't worried about having the latest microcode package in those kernels, then don't bother. I probably wouldn't bother.

You don't update your system very often! And you are still one kernel behind. Current is kernel-3.10.0-1160.42.2.el7.x86_64. When you next boot, it should boot off kernel-3.10.0-1160.41.1.el7.x86_64 so that should be OK. The issue is if you try selecting one of the 1062 kernels but these should be your third and fourth choice for booting.

You could try what it suggests:But I have never tried it. On the other hand, if you aren't worried about having the latest microcode package in those kernels, then don't bother. I probably wouldn't bother.

What is the output of:

For the kmod-r8168 and kmod-r8169, I maintain them in ClearOS. For all the other kmod drivers, you have to install them from ElRepo. The reason I maintain the two is the ElRepo kmod-r8168 explicitly blacklists the r8169 drivers which seems pointless to me as their kmod-r8169 driver does not support the r8168 cards. If meant that, on my old server which had both cards, I was stuffed until I found a couple or workarounds. The easiest is to comment out the blacklisting in the r8168 driver and I now do this when I create the RPM. It does mean that, for safety, if you have an r8168 card you should install both drivers, in case you ever get an r8169 card. (And possibly the other way round but you rarely install the r8169 as, up to now, I have not heard of problems with the kernel version). The r8169 driver is unmodified.

Really what I should do is make each driver require the other, but I've never got that far.

And to revert, if you want to:And reboot.

and reboot.

On an RTL8111/8168/8411 system:and reboot.

The clearsyncd messages are probably a red herring. I have asked the devs before about thes messages. I get them like you, but at different intervals:I tried checking back on the last few and they did not tie back to any other normally logged messages. I do get two regular ones at 05:00 and 07:28. The 07:28 seems to tie back to a cron job which does a "/usr/sbin/clearcenter-checkin". The ones at 05:00 are not so obvious as there are about 7 cron jobs which fire then.