• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk 8.3.0 on Debian 4.0 / 4.1 with GCC 4.2

P

Paebbels

Guest
Hi,

we build a Debain 4.0 System with Plesk 8.3.0 => this was working fine
after this we wanted to switch to Debian 4.1 but there is a big problem and I dont mean the unsupported System by Plesk :)

lenny wants to use gcc 4.2 and new libstdc++6, libc ans so on
but the internal apache for the control-panel - an old 1.3.33 - requires old libs ...

so we are searching for a good way to build a new httpsd für plesk with gcc 4.2

I'm NOT willing to use PHP 5.2.0 instad of 5.2.5 with abount 500 bugs und near 50 security holes, because a damn httpsd is using old libs !
 
Is there nobody who can help me?
I'm surely not the only one who wants to use Plesk with new and bug-free software!
 
# file /usr/local/psa/admin/bin/httpsd
/usr/local/psa/admin/bin/httpsd: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped

you see that problem:) "dynamically linked"

i guess symlinking old files to ones with new indeces will be a dirty hack to it. actually what you are trying to do is kind of brain surgery made through rectum:)
 
Back
Top