Skip to main content

Reconfiguring Everything

LupineDream
I've determined by the errors in I am getting in PECL module installer:
WARNING: "pecl/PDO" is deprecated in favor of "channel://
That I am yet again going to need to redo everything. I've been up for nearly 48 hours straight trying to resolve these compiler issues (no sleep). It all boils down to drupal installation: The first issue was an unserialize token() problem, which was resolved by changing some EasyApache4 and MultiPHP configurations. The second issue I had was attempting to build pecl modules by hand, which failed because cpanel threw the errors I listed above, so I went and built them and of course they refuse to work with cPanel and EasyApache4. yum and rpm just straight up throws up when you try and inject your own binaries on a VPS. The third issue is I must use cpanel because my web provider's control panel depends on its functionality. I have been through drupal configuration, linux build guides, discovering certain things I could and could not do with cPanel and drupal seems to be one of them because of complex MySQL modules failing to build. cPanel's toolchain is just nuked. The fourth issue was restored it all with a (I thought) fresh install, tried reconfiguring httpd manually in ssh,spent half a day yesterday with pre and post vhost conf, php.ini and MultiPHP. And now am having mySQL database problems when attempting to install drupal. (needs modules that refuse to load because not built and refuse build) The last issue, I'm not paid for this. What are the instructions for completely restoring everything back to complete stock for my server and in fully working order as far as cpanel/whm and configuring it to work with drupal? I will not post my current configs, because I want a fresh and fully-functional cPanel. Not one that refuses to work without a load of backend tweaks. ----- current machine state ---- CentOS 6.9 x86_64 Bluehost VPS /opt/cpanel Some residual junk in /usr I'm sure needs cleaned, including non-symlinked custom php binaries and a pear that half-works (phpize doesn't) Not enitrely sure what perfect state yum or rpm is in, I've rebuilt the rpm database numerous times. php -V works at root pear doesn't at root phpize not at all in cpanel or root drupal install throwing up about modules i cannot build. (configured on subdomain, works until accessing the mySQL database portion of setup). Confirmed rewrite rules are working. ------------------------------- I mean, really, the support representative told me to "figure it out" and refused to open a ticket for these issues (Bluehost web provider yesterday evening). I pretty much learned how to admin in 48 hours, its mind-numbing.

Comments

4 comments

Date Votes
  • Infopro
    What are the instructions for completely restoring everything back to complete stock for my server and in fully working order as far as cpanel/whm and configuring it to work with drupal?

    There are none. Properly cleaning up a server you made a mess of without knowing what you were doing is up to you, short of wiping the entire server and re-installing the OS and cPanel. Installing Drupal should be a painless task and it should run on a default cPanel setup without changing anything. I'm not sure why you're having so many issues, your very long post doesn't provide us with enough clues to assist you.
    0
  • LupineDream
    There are none. Properly cleaning up a server you made a mess of without knowing what you were doing is up to you, short of wiping the entire server and re-installing the OS and cPanel. Installing Drupal should be a painless task and it should run on a default cPanel setup without changing anything. I'm not sure why you're having so many issues, your very long post doesn't provide us with enough clues to assist you.

    I had to go through 3 support representatives today. (First two where beligerant until I explained to the third I'd done repairs on a completely broken re-image and they where surprised I had gotten it to work) They'd found nothing wrong aside these pecl issues, so my issue was submitted to the backend team there for processing. In context I have to say I was initially shipped a VPS without a working DNS Zone editor, subdomain editor, Apache server, or functional control panel due to a datacenter installation script problem (they tried two re-images, first two where unsuccessful, they'd purchased new servers inTexas and I was informed I was one of 3 accounts ), these where before I even configged and logged into root or activated sudo. I'm sorry for the misinterpretation I provided in the original post. It's in biligerancy, because manually doing repiars like these without autorepair scripts is very time consuming. So I would say repairing cpanel to a point (manually) to where I could actually use the features the web provider was supposidly selling me is a time consuming feat. And so far has been successful. I had to add the rpm for the cpanel production feed in, thats how broken it was. Dsiscovered after fresh re-image rpm was broken too, fixed that. I'll refine this question to: how to repair the compliers integrated into cpanel for module builds, since my horrid re-image shipped without them or in a misconfigured state. Would simply symlinking my CentOS compilers directly to the cpanel mount resolve the build problems? Those where the ones that worked to get Easyapache and php70 somewhat functional. I'm noticing as well that which php returns /usr/share/bin/php, which isn't symlinked. The script they'd used put easyapache in that /opt/cpanel partition, and its cache and system files in /var/cpanel partition. I didn't see manual configs for partition locations in WHM, if they are there let me know, that might solve the issue re-attaching all of them into one. (virtually)
    0
  • Anoop P Alias
    Drupal should just work fine. What is the exact error you get ? apache error_log and per directory error_log file contents? I think the need to restore everything to stock is something you feel you need; but is not required in real
    0
  • LupineDream
    Drupal should just work fine. What is the exact error you get ? apache error_log and per directory error_log file contents? I think the need to restore everything to stock is something you feel you need; but is not required in real

    They've marked my further explanation moderator approval. But I gave some extensive details on what actually happened. I'm having the backend team there re-merge and re-symlink things. It was due to a re-image installation script error on their backend. It may be handled with in the next few days (I hope). I had done a lot of manual repair to get things (sort of) working.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post