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

WEB_Server_package parameter not defined in features list

Brujo

Silver Pleskian
Plesk Guru
Hi, after the upate yesterday from 8.6.0 to the lastest Version i have the following error now in the Plesk Controlpanel > Service Management:

WEB_Server_package parameter not defined in features list.
0: /usr/local/psa/admin/plib/common_func.php3:190
psaerror(string 'WEB_Server_package parameter not defined in features list.')
1: /usr/local/psa/admin/plib/class.WebServerManager.php:209
WebServerManager->getWebServerPackage()
2: /usr/local/psa/admin/plib/class.ServiceControl.php:88
ServiceControl->chkServiceObjects(string 'web')
3: /usr/local/psa/admin/plib/class.ServiceControl.php:261
ServiceControl->getServiceName(string 'web')
4: /usr/local/psa/admin/plib/class.RestartServForm.php:72
RestartServForm->assign(object of type ServiceControl)
5: /usr/local/psa/admin/htdocs/server/restart_services.php:38

no services are shown!

any hint?
Brujo
 
Are you sure Plesk upgrade was completed successfully?
Please, check Plesk package and database version:
# rpm -q psa
psa-8.6.0-cos4.build86080722.02
#
# cat /usr/local/psa/version
8.6.0 CentOS 4.2 86080822.20
#
# mysql -uadmin -p`cat /etc/psa/.psa.shadow ` psa -e "select * from misc where param='version'"
+---------+------+
| param | val |
+---------+------+
| version | 0860 |
+---------+------+
#
If everything shows version 8.6, that’s ok, it means Plesk was upgraded completely.
But if you will see duplicated Plesk package or previous Plesk database version shown, then you need to check updater log to determine the cause of Plesk upgrade failure:
# less /tmp/autoinstaller3.log
Also, in case it is a virtual server, make sure there are failed counters in /proc/user_beancounters
wich detects lack of system resources.
 
Back
Top