• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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