PEAR channel restoration
a few days ago, I attempted to install an pear package via SSH shell. later did not work and is removed. But did not realize that the cpanel pear module is changed pointing to the different channel.
I did edit the pear.conf via the shell command
#pear config-set default_channel pear.php.net
did not correct the cpanel (is stuck on seeing pear.horde.org list of modules)
How do i restore this channel back to pear.php.net?
Roy
-
Hello :) You can try removing the cached data from the /tmp/pear/ directory and then running the following commands: /usr/local/cpanel/bin/updatepear /usr/local/cpanel/scripts/fix_pear_registry
Let us know if this helps. Thank you.0 -
We've run into the same thing after clicking 'Reinstall' on a PEAR module. Both the PEAR and PECL extensions/applications lists disappeared from the Module Installers page. Attempts to correct include the steps above and steps found in other forum posts: # /usr/local/cpanel/3rdparty/bin/pecl list (no packages installed from channel pecl.php.net) # /usr/local/cpanel/3rdparty/bin/pecl install Nothing to install
# /usr/local/cpanel/bin/updatepear config-set succeeded config-set succeeded config-set succeeded config-set succeeded # /usr/local/cpanel/scripts/fix_pear_registry (snipped 167 lines) There are 167 installed PEAR RPMs. Of those packages, 162 already existed in the PEAR registry, 1 did not, and 4 did not contain an XML file. Of the 1 package not listed in the registry, the system successfully added 0, and failed to add 1.
We've also recompiled AE3, forced upcp, rebooted, increased cPanel max process memory; still no PEAR or PECL extensions/applications showing. This is a bizarre issue. Anything else we can try?0 -
We've also recompiled AE3, forced upcp, rebooted, increased cPanel max process memory; still no PEAR or PECL extensions/applications showing. This is a bizarre issue. Anything else we can try?
Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you.0 -
Update: tkt 7712421 Apache was rebuilt again, which apparently corrected whatever it was that wasn't working when it got rebuilt the first time. At any rate, issue is corrected. 0 -
I'm happy to see the issue is now resolved. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
5 comments