1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

cron jobs and chroot shell are broken on 10.2

Discussion in 'Plesk 10.x for Linux Issues, Fixes, How-To' started by Hostasaurus.Com, Jun 30, 2011.

  1. Hostasaurus.Com

    Hostasaurus.Com Regular Pleskian

    30
    68%
    Joined:
    Oct 8, 2009
    Messages:
    465
    Likes Received:
    8
    So unless we give a customer a full /bin/bash shell, they can't log in at all using ssh and also can't set up cron jobs. In 10.2, if you try to ssh in when you have chroot shell set, you get this:

    Last login: Wed Jun 29 12:32:54 2011 from localhost.localdomain
    execv("/bin/bash") failed
    system error: No such file or directory


    And, in 10.2, customers' cron jobs are created with this in the crontab file:

    SHELL=/usr/local/psa/bin/chrootsh

    which causes any 'scheduled task' they create to fail with the same 'execv("/bin/bash") failed' error.
     
  2. breun

    breun Golden Pleskian

    29
     
    Joined:
    Jun 28, 2005
    Messages:
    1,647
    Likes Received:
    0
  3. Hostasaurus.Com

    Hostasaurus.Com Regular Pleskian

    30
    68%
    Joined:
    Oct 8, 2009
    Messages:
    465
    Likes Received:
    8
    The administrator guides that Parallels produces often show things as being possible when they aren't. I take it you haven't actually tried what the guide says since the command is not even in the right location for starters. If you do find the correct location and use it, the setting has absolutely no effect if the user is set to the chrootsh shell. The user needs to either have a Forbidden shell, or a full shell, and if they've been given a full shell, then you would not encounter the problem in the first place. So the problem comes back to being one of you can either deny customers SSH access, or deny them cron job access, since they can't have both unless you give them unrestricted access to the server.
     
  4. breun

    breun Golden Pleskian

    29
     
    Joined:
    Jun 28, 2005
    Messages:
    1,647
    Likes Received:
    0
    I reported the path error to the docs team. I hope the functionality gets fixed also.
     
Loading...