• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Wordpress installations not recognized

TRESLabs

New Pleskian
All Wordpress installations were recognized but they are not selectable and all have a parse error:

PHP Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING, expecting T_STRING in /usr/share/plesk-wp-cli/php/wp-cli.php(18) eval()'d code on line 89

{err_code";0,"err_message":/n<h1> Error establishing database connection . . .

See the attached jpeg for the complete error message.

All the sites are working okay so we know the databases are accessible and working. We have the latest version of Plesk 12 with micro updates done daily. This is a plain installation with no mods to the system files or software. This is hosted at 1and1.com; our other server at Rackspace found the WP installations without any problems.

Any suggestions would be much appreciated.

Component name Component version
awstats 7.3-14050621.parallels
bind 9.8.2-0.23.rc1.el6_5.1
courier-imap 4.15-cos6.build1200140617.18
fail2ban 0.8.13-14052018
health-monitor 12.0.18-cos6.build1200140526.11
httpd 2.2.15-31.el6.centos
mailman 2.1.12-18.el6
mod_bw 0.92-14060421
mod_perl 2.0.4-11.el6_5
mod_python 3.3.1-14.el6.1
modsecurity 2.8.0-24.el6.art
mysql 5.1.73-3.el6_5
perl-Apache-ASP 2.61-1.el6.rf
php 5.3.3-27.el6_5
phpmyadmin 4.2.5-cos6.build1200140702.16
phppgadmin 5.1-cos6.build1200140423.17
PPSitebuilder 12.0.5-14043013
psa 12.0.18-cos6.build1200140606.15
psa-api-rpc 12.0.18-cos6.build1200140606.15
psa-autoinstaller 3.16.20-140624.15
psa-backup-manager 12.0.18-cos6.build1200140606.15
psa-horde 5.1.6-cos6.build1200140526.11
psa-imp 6.1.7-cos6.build1200140526.11
psa-kav8 8.0.3-0.14061710
psa-logrotate 3.7-cos6.build110120606.19
psa-migration-manager 12.0.18-cos6.build1200140606.15
psa-mod-fcgid-configurator 2.3.9-14033111
psa-proftpd 1.3.5-cos6.build1200140529.18
psa-qmail 1.03-cos6.build1200140526.11
psa-qmail-rblsmtpd 0.88-cos6.build120140331.11
psa-spamassassin 12.0.18-cos6.build1200140606.15
psa-turba 4.1.4-cos6.build1200140526.11
samba 3.6.9-169.el6_5
spamassassin 3.3.1-3.el6
webalizer 2.21_02-3.3.el6
 

Attachments

  • Screen Shot 2014-08-02 at 5.56.30 PM.png
    Screen Shot 2014-08-02 at 5.56.30 PM.png
    98.4 KB · Views: 21
Similar issue for me, it happen in wp manually imported while in wp seted up from plesk everything works fine.
Alarm is:

PHP Fatal error: Call to undefined function add_filter() in /usr/share/plesk-wp-cli/php/wp-cli.php(18) : eval()'d code on line 92
 
Hello guys, the WP CLI Project uses code from your wordpress installation, maybe the issue comes from there.
Which WP versions you are trying to import? And the filesystem permissions are also okay?

Greetings
K.
 
The absurd thing is that wp is updated and the site is running. Issue affect sometimes entire server with CPU overload
 
@TRESLabs
Your PHP configuration for cli (shells etc..) contains errors, it will work if you either reinstall or correct your imagick php extension or deactivate.
 
The new Plesk feature for wordpress is not configured to deal with all ( optional ) additional plugins, which might be coded in another way, than wordpress suggested. The wordpress installation ( and it's modifications ) might still be fully functional, but the Plesk wordpress feature still could not be able to read optional, specific config-files that your installation of wordpress might contain. Keep in mind, that some plugins are coded by hobby programmers and therefore often have unsual code, which might be working in wordpress, but the new Plesk wordpress feature might not be able to verify specific unsual code. Plesk itself is mostly not the issue when it comes to strange behaviours on your webserver with wordpress installations, it's mostly some strange code in optional, additional plugings wich cause the errors and missbehaviour.

A good way to investigate problems is to read apache and ngingx access and error-logs, because they point out the potential problems. If you are unsure about where to find the logs, just visit: Parallels Plesk Panel for Linux services logs and configuration files ( KB : 111283 )


KazimirM is right, when he suggests to check the ImageMagick PHP - extension as well, because the extension might be missing, or not being updated for the actual PHP - version on your server ( another reason to investigate errors in your access and error - logs regarding to this ^^ ).
 
As suggested, you might want to add "ImageMagick", because the errors contain, that this extension can't be found.

If I read your posts rights, you are on Centos, so your command to install ImageMagick would be "yum install ImageMagick ImageMagick-devel" If your system tells you, that this is already installed, you really have to investigate the error logs, to give us some more details.
 
Back
Top