caroseuk
- Total activity 31
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 7
Comments
Recent activity by caroseuk-
Hi Michael, thanks. For anyone else who may have the same issue, we had someone from support log in and do some troubleshooting. From cPanel's perspective there was an issue with resolving the maj...
-
Hi all, With the recent announcement of new critical PHP vulnerabilities (namely PHPMailer - CVE-2016-10033). Is there anything particular needing to be carried out on WHM servers to keep them saf...
-
Hi Michael, We ended up doing the upcp --force command and updated to version 60 build 28. Had a few issues with old tailwatchd process running but we killed it and WHM started the newer process. ...
-
Thanks Michael, we will register with the support portal now.
-
Hi Michael, Output below: cat /usr/local/cpanel/version 11.54.0.15 arch x86_64 We haven't tried running upcp with --force. Will this break anything? This is a production server.
-
Simply running that command will only fix the issue until the next time the cPanel Update job runs (~24 hours). At which time, it will remove the rpm again and replace it with the one in the EPEL r...
-
Correct, it solves it for my case. However for other users facing the same issue then it needs to be addressed. Otherwise cPanel Users need to disable the EPEL repo. Which isn't really an option ...
-
I agree, this is just a short term fix. Ideally you would only include the updates for packages you have installed from EPEL. So for me "blacklisting" everything apart from redis/fail2ban woul...
-
I personally think keeping it in the epel.repo exclude is better... as the cPanel scripts amend the yum.conf file every time it prepares to run. So it might remove your manually added p0f entry. I...
-
I would try excluding it from the epel.repo file as that is where the conflicting rpm is based. That should tell yum to not replace the cpanel p0f rpm with the one found in epel. Just an idea ;)