• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Autoinstaller kills xinetd

LarsenD

Regular Pleskian
This happens in around 30% of the cases when I run CLI autoinstaller to update/install/remove packages.

Code:
Patches were installed successfully.
The changes were applied successfully.
Synchronizing the Debian APT package index files...

# pgrep -lf xinetd || service xinetd start
Starting internet superserver: xinetd.

# pgrep -lf xinetd || service xinetd start
849 /usr/sbin/xinetd -pidfile /var/run/xinetd.pid -stayalive

As you can see, after the autoinstaller finishes, xinetd is not running and has to be started again.
 
To see a more detailed log, you could use over the command line:

export PLESK_INSTALLER_DEBUG=yes
/usr/local/psa/admin/bin/autoinstaller ....
This will force a more detailled output on the screen, as well in the corresponding autoinstaller - log - file for this instance. You can now investigate what caused the issue, that xinetd couldn't be restarted during or after the completed autoinstaller process.
 
Back
Top