https://www.rackaid.com/helpdesk/index.php?...kbarticleid=148
A quick rundown for those who don't feel like making an external visit:
QUOTE
On some RHEL 3.9 boxes an update to Plesk 8.3 results in a GLIBC errror:
If plesk does not start try:
/usr/local/psa/admin/sbin/httpsd configtest
if you get:
/usr/local/psa/admin/sbin/httpsd: /usr/lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/ ...
Then:
rm /usr/lib/libgcc_s.so.1
cd /usr/lib
ln -s ../../lib/libgcc_s_plesk.so.1
This is a bug in the plesk upater not linking the correct lib.
If plesk does not start try:
/usr/local/psa/admin/sbin/httpsd configtest
if you get:
/usr/local/psa/admin/sbin/httpsd: /usr/lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/ ...
Then:
rm /usr/lib/libgcc_s.so.1
cd /usr/lib
ln -s ../../lib/libgcc_s_plesk.so.1
This is a bug in the plesk upater not linking the correct lib.
Firstly, a huge THANK YOU to whoever figured that out and posted it over there.
For that matter, how does one figure that out?! Maybe I was on the right path since the google search terms which finally found their fix on day 3 was "plesk libgcc_s.so.1". Still, to discover what was wrong AND the solution too... impressive! I'm wide open for feedback on troubleshooting strategies!
Secondly, why did I have to find the answer where I did? This drove me nuts for a few days as I searched Parallels' forum and knowledge base for clues, why could I find nothing? Do they even know about it? If so, why wouldn't they do everything in their power to let us end-users know about it too (so we can fix it ASAP) especially when they already have a reputation for buggy updates/releases. Ugh, the mind boggles.
Welp, hopefully this'll save some other "Planeteers" a few grey hairs.
