RPM Timeout issues.
-
What error does it give you when you just run yum update? There should be something about conflicting versions at the end. 0 -
Actually I think this is related to an issue with the CLN - we received the following communication from them about this: - customers cannot run yum commands on CloudLinux systems
- customers cannot register/unregister CL products
- customers have difficulties manage their CLN accounts (this shouldn't be related to your customers, though)
0 -
Apologies, I thought I had notifications turned on for this post. Thanks @cPanelLauren and @got.9520 This issue repeated itself a few nights ago. Same thing. It appears related to the quantity of updates; when I ran rpmup manually after it failed during upcp there were 350+ updates, the command completed successfully and upcp --force completed successfully afterwards. The previous failure contained 500+ updates. I'll stick my neck out here and say that the script is literally timing out midway through the update process because the timeout has been exceeded. There were no errors when I ran rpmup and upcp .... rpmup just took a fair bit of time to complete. Also, when upcp fails due to the rpmup timeout it holds the yum lock until the process is killed. 0 -
Have you tried just running yum update by itself? not rpmup. 0 -
Not yet. If and when it happens again I will. Thanks. 0 -
You can do that any time. You'll be able to quickly tell if your system is updated or not or if the updating system is broken with better diagnostic data if it is. 0
Please sign in to leave a comment.
Comments
6 comments