• 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.

7.5.3 Problems

M

MikeParsons

Guest
I tried the updater to go from 7.5.2 to the new 7.5.3 on what is basically a new install, and after it failed tried the commandline as advised in another post here.

After a couple of goes it finally ran to completion

Now I get

Syntax error on line 213 of /usr/local/psa/admin/conf/httpsd.conf:
Cannot load /usr/local/psa/admin/libexec/mod_info.so into server: /usr/local/psa
/admin/libexec/mod_info.so: undefined symbol: top_module
/usr/local/psa/admin/bin/httpsdctl start: httpd could not be started
Starting Plesk: [FAILED]

The sites seem to be working on the server but I can't log into Plesk as its not running.

If I re-run the update it tells me its already at current version and exits

How do I force an update to mod_info.so or is the error actually something else.

At the moment I'm stumped
 
My suggestion is to back up your /usr/local/psa/admin/conf/httpsd.conf and then edit it.

# cp /usr/local/psa/admin/conf/httpsd.conf /usr/local/psa/admin/conf/httpsd.conf.bak

Do a search for "mod_info" in the httpsd.conf file, and comment out the two (?) lines that load it (AddModule and LoadModule). Then try to restart PSA and see how it goes.
 
Sort of worked

Redhat 9.0, PSA 7.5, MySQL 4.0

I had this same problem, and that was exactly what I did (you also have to comment out the addModule mod_info.so line in /usr/local/psa/admin/conf/httpsd.conf)

the startup script returns an OK, but I still can't login to the psa web server.
 
OK, what does the admin server error log say?

( tail /usr/local/psa/admin/logs/httpsd_error_log ) -- or wherever that log is on your system.. the above location is for freebsd.
 
httpsd_error_log doesnt say anything because the dameon is never started.
 
Hello there.

I already upgrade to the last version.. but now; i get the same error on the PSA restart command.

Someone can contact to plesk or try to get the solution to fix it?

Thank you in advanced!
 
cool... i fixed!

just run:

rpm -Uhv /root/psa/PSA_7.5.3/rpm_FedoraCore_2/base/psa-7.5.3-fc2.build75050506.13.i586.rpm --force


:D
 
Back
Top