• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

httpd update

mod_jk missing from psa-tomcat-configurator

This is a follow-up with details to better describe the problem and larger issue of repositories missing the required information to keep Plesk managed servers current.

I am currently running a CentOS 5 server with a 100 domains Plesk control panel and the Plesk Power Pack [at an extra charge] which includes Tomcat, SPAMAssassin and other features. Tomcat is a known non-compliant PCI package and the service accordingly has been disabled.

The server is updated exclusively by either the Plesk `Updater`icon or `Yum Update [command] [option]`. Only CentOS/Plesk underwritten mirror sites are used for all updates. I subscribe to the Plesk Control Panel and use authentic repositories because this is the best practice to keep my server PCI compliant.

Accordingly, when YUM UPDATE generates the error message: `mod_jk is needed by (installed) psa-tomcat-configurator`, it is clear that the current mirror site repositories do not include the needed `mod_jk` functionality to process over 150 CentOS 5 pending updates for Plesk v8.6.

This is a critical error and is exclusively a Plesk error because, as I understand it, `mod_jk` is only needed by Plesk`s ` psa-tomcat-configurator`.

Therefore, what is needed is a date when Parallels plans to populate the required repositories with the missing `mod_jk` functionality in order that my server, and everyone else`s server, stays compliant with future CentOS and Plesk updates and releases using generally available Plesk and CentOS repositories.
 
Back
Top