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

Tomcat issue: no such file /etc/init.d/tomcat5

O

OlivierMaes

Guest
Hello,

I have a problem with tomcat.
When I remove a domain (from a account that was migrated from another server) I get this error:
Service is not available now, probably your plesk is misconfigured.
Contact your provider for details.
Internal plesk error occurd: tomcat failed --remove-service --vhost-name=domain.be


I go to Service Managment (plesk server administration), I see that tomcat isn't running, so I click start service.
than I get the error:
Service is not available now, probably your Plesk is misconfigured.
Contact your provider for details.
Internal Plesk error occured: Unable to manage service by thomcatmng: tomcatmng: No such file '/etc/init.d/tomcat5':
No such file or directory System error 2: No such file or Directory


Via SSH I get the same.

System:
Linux VPS, Virtuozzo
With Plesk 8.4, all component up-to-date
Plesk version: ps v8.4.0_build84080514.18os_centOS 5
OS: Linux 2.6.9-023stable046.2-enterprise

This server was a fresh install from the 1ste of august.
I already removed some domains, the last 2 I can't removed.
I migrated domains from different servers, but the 2 domains came from the same server and user. An other user domain from the same server I could delete without any trouble.

Someone who can help?

Many thanks!
 
You do not have tomcat support on that server and the domain was configured with tomcat support. You have 2 solutions:

1. Install tomcat support on the server.
2. Disable tomcat support on that domain (although in this case it might complain about the same thing :))
 
Back
Top