plesk 9.3 chrootsh logout problem with su from root

[mjail45]

Something that I noticed recently with plesk 9.3 under Ubuntu 8.04, is that when root uses su to switch to a chrooted user, the user login is successful the first time, but if I logout of that user and then try to "su - user" again, I get logged out automatically as soon as I type any key:

web01:~# su - gmaster
bash-3.2$ e
bash: e: command not found
bash-3.2$ exit
logout
web01:~# su - gmaster
bash-3.2$ elogout
web01:~#

In the example above, as root I su'ed to a chrooted user gmaster for the first time, and typed the letter e and hit enter. The results are normal (command not found).. Then I logged out, and then logged back in to that same user, and again typed the letter e, and right away I am logged out. It happens when any key is typed. Again, this only happens with root. Using su from another (non-chroot) account works fine.

This has been verified on two separate servers, both with plesk 9.3 and ubuntu 8.04.

I have another server with plesk 9.2 and centos 5, and it doesn't have this issue, so I copied the chrootsh binary from that server to one of the plesk 9.3 servers and now the su issue seems to have been solved, atleast temporarilly.

So, any idea when the chrootsh binary with plesk 9.3 will be fixed?

 

[IgorG]

Thank you for your detailed information. I have forwarded it to developers for the further investigation. I will update this thread with results as soon as I receive it.

 

[mjail45]

any new info

IgorG,

Have any new developments been made as far as this issue is concerned? I'd especially like to know if using the chrootsh binary from Plesk 9.2 is a safe alternative in the meantime (I've found no problems with it, but that doesn't necessarily mean it's safe).

Also, any other Plesk 9.3 users on Linux: please post your experiences with this issue, as it may prove useful to the developers. And keep in mind, this is a root su issue only; it doesn't affect other non-chroot users who use su, and it doesn't affect ssh logins in any way.

 

[mjail45]

any new info

IgorG,

Is there any news regarding this issue?

 

[IgorG]

IgorG,

Is there any news regarding this issue?

Problem still under developer's investigation.

 

[IgorG]

Developers have informed that they cant reproduce this problem.