CentOS

If you have access to the outside world, you can try testing against some other NTP server to see if the problem is with the NTP server in your network. Try for example ntpdate 92.243.6.5 . That server is mine and it should have correct time (see its entry on NTP Pool ). You can also use the -q opti...

Please refer to the Red Hat CVE database:
https://access.redhat.com/security/cve/cve-2016-10009
https://access.redhat.com/security/cve/cve-2016-6515

For both of those, RH has decided to not fix these issues for the time being, and consequently, CentOS openssh will not get fixed either.

That kernel is more than two years old. See if a newer kernel works better. Try yum update.

You will need to ask this from WHM. Fixing this the official CentOS way has a good chance of breaking your WHM installation, which you probably don't want.

Please run rpm -qif /lib64/libnetsnmptrapd.so.31 and report back the results.

Don't delete the CentOS .repo files, but instead, set enabled=0 for each repository listed in those .repo files.

Hi, TrevorH, thanks again, I found in my current setting (CentOS 6.9, by the way I want to go to CentOS 7 after this is resolved), There is no upgrade path from CentOS 6 to CentOS 7. If you want to use CentOS 7, the only supported way is to back up your data, clear your disk, install CentOS 7 and r...

Yeah, right. The funny thing is that the xinetd package does not provide an inetd binary. The binary in it is called xinetd. Also the /usr/local/bin path is suspicious. I'm sorry to say, but that inetd thing you have running is not a CentOS binary. It's likely someone's cpuminer (crypto currency min...

I ... have a hunch, but try ps -ef | grep inetd to see which inetd it is running.

I can't really comment on PXE, I haven't tested that, but I'll just note for the record and for further reference that it is not necessary to partition/format/empty the USB stick prior to dd'ing to it.