Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail open terminal #122

Closed
ntvsx193 opened this issue Aug 22, 2013 · 5 comments
Closed

Fail open terminal #122

ntvsx193 opened this issue Aug 22, 2013 · 5 comments

Comments

@ntvsx193
Copy link

Screenshot

@ntvsx193
Copy link
Author

My system:
Debian GNU/Linux 7.1 (wheezy)
"uname -a": Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux

@Eugeny
Copy link
Member

Eugeny commented Aug 22, 2013

Please include your /etc/ajenti/config.json contents

@ntvsx193
Copy link
Author

{
"users": {
"root": {
"configs": {
"ajenti.plugins.fm.fm.FileManager": "{"root": "/"}",
"ajenti.plugins.terminal.main.Terminals": "{"shell": "sh -c $SHELL"}"
},
"password": "........................................................",
"permissions": []
}
},
"bind": {
"host": "0.0.0.0",
"port": 8000
},
"authentication": true,
"ssl": {
"enable": true,
"certificate_path": "/etc/ajenti/ajenti.pem"
},
"enable_feedback": true,
"installation_id": 305
}

@ntvsx193
Copy link
Author

На втором сервере с такой же системой терминал работает.
Этот сервер vds, на виртуализации Xen.

@Eugeny
Copy link
Member

Eugeny commented Aug 23, 2013

Замените sh -c $SHELL на sh -c $SHELL || sh (в новых билдах это сделано в конфиге по умолчанию). У вас не установлен $SHELL для запускающихся сервисов.

@Eugeny Eugeny closed this as completed Aug 23, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants