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

chroot sftp stopped working today

ultracaffeinated

New Pleskian
Plesk 12.0.18, no yum updates, just stopped working. System accounts work, plesk created accounts with their shell set to /bin/bash (chrooted) fail. I'm getting this error in /var/log/messages:
Code:
Feb 25 01:08:31 ip-XXX-XXX-XXX-XXX systemd: Created slice user-10002.slice.
Feb 25 01:08:31 ip-XXX-XXX-XXX-XXX systemd: Starting user-10002.slice.
Feb 25 01:08:31 ip-XXX-XXX-XXX-XXX systemd-logind: New session 904 of user ftplogin.
Feb 25 01:08:31 ip-XXX-XXX-XXX-XXX systemd: Started Session 904 of user ftplogin.
Feb 25 01:08:31 ip-XXX-XXX-XXX-XXX systemd: Starting Session 904 of user ftplogin.
Feb 25 01:08:31 ip-XXX-XXX-XXX-XXX plesk-chrootsh[30686]: execv("/bin/bash") failed
Feb 25 01:08:31 ip-XXX-XXX-XXX-XXX plesk-chrootsh[30686]: system error: Permission denied
Feb 25 01:08:31 ip-XXX-XXX-XXX-XXX systemd-logind: Removed session 904.
Feb 25 01:08:31 ip-XXX-XXX-XXX-XXX systemd: Removed slice user-10002.slice.
Feb 25 01:08:31 ip-XXX-XXX-XXX-XXX systemd: Stopping user-10002.slice.
I've run the plesk repair tool and rebuilt all the configs with httpdmng. I've also followed these directions: http://kb.odin.com/en/125519 to no avail (they do get rid of the PAM faulty module message but don't restore chroot. Any other ideas? CentOS 7 with SELlinux set to permissive for now.
 
Last edited:
I adjusted the subscription to have a different shell, synced them all, then ran the bootstrapper repair:

/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh repair

Then I switched it back to /bin/bash (chrooted), synced, and it started working. Running the bootstrapper repair originally did nothing.
 
Back
Top