EasyApache4 provision
having a bit of a head scratch. Is this a CloudLinux issue of cPanel?
running CL7 with EA4 on a WHM 56.0 (build 24). packages install fine via yum, but when trying to install them via EA4 this is what I am getting:
any help appreciated...
Provision process started.
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4787, in install
mypkgs = self.pkgSack.returnPackages(patterns=pats,
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1079, in
pkgSack = property(fget=lambda self: self._getSacks(),
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 784, in _getSacks
self.repos.populateSack(which=repos)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 344, in populateSack
self.doSetup()
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 158, in doSetup
self.ayum.plugins.run('postreposetup')
File "/usr/lib/python2.7/site-packages/yum/plugins.py", line 188, in run
func(conduitcls(self, self.base, conf, **kwargs))
File "/usr/lib/yum-plugins/fastestmirror.py", line 202, in postreposetup_hook
all_urls = FastestMirror(all_urls).get_mirrorlist()
File "/usr/lib/yum-plugins/fastestmirror.py", line 369, in get_mirrorlist
self._poll_mirrors()
File "/usr/lib/yum-plugins/fastestmirror.py", line 413, in _poll_mirrors
pollThread.start()
File "/usr/lib64/python2.7/threading.py", line 746, in start
_start_new_thread(self.__bootstrap, ())
thread.error: can't start new thread
yum exited 256
Provision process finished.any help appreciated...
-
Hi, Can you throw in a support ticket on this? This is something I haven't seen before. It sounds like Yum can't get the memory it needs to start a new thread, but it's odd. There's a link in my signature to throw in a ticket. Thanks! 0 -
done, ticket #7577723 0 -
It"s more likely a YUM plugin issue. For me it was the "fastestmirror" plugin that caused the provision error on a VM with 4 GB RAM. Please try to reduce the "maxthreads" value from 15 to 5 and try again. File to edit: /etc/yum/pluginconf.d/fastestmirror.conf 0 -
done, ticket #7577723
To update, the issue was addressed by rebuilding the RPM database. Thank you.0
Please sign in to leave a comment.
Comments
4 comments