[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Jailkit-users] /usr/sbin/jk_chrootsh No such file or directory

From: Dan Rossi
Subject: Re: [Jailkit-users] /usr/sbin/jk_chrootsh No such file or directory
Date: Thu, 20 Dec 2007 23:52:16 +1100

Ok i upgrade ssh just in case it was that, and its removed that problem now. However I started to get this error now in auth.log.

Dec 20 23:44:08 host sshd[27005]: pam_env(ssh:setcred): Unable to open env file: /etc/default/locale: No such file or directory

However this was locking me out.

So i touched that file to remove that error however its still locking out the user, I get the console welcome message

iElectro:~ danielr$ ssh address@hidden
address@hidden's password:
Linux host 2.6.22-14-server #1 SMP Sun Oct 14 22:09:15 GMT 2007 x86_64

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.
No mail.
Last login:
Connection to host.com closed.
iElectro:~ danielr$

Now error logging.

On 18/12/2007, at 9:25 AM, Olivier Sessink wrote:

Dan Rossi wrote:
Is there any kind of solution to my issue, everything seems so easy so
far to actually setup the chroot it just wont login. I also mentioned
that a similar issue was happening with the ssh chroot patch, but i
reverted ssh back to the package now.

I'm trying to get a clue. Normally what I would do is log on to the
system as root, and tail all logfiles:

`tail -f /var/log/messages /var/log/daemon.log /var/log/auth.log

then I would start the second login with user 'testuser' See if anything
is appended to any of the logfiles that could give a clue.

So far from your replies it seems that none of the jailkit programs is
actually started because the first thing jk_chrootsh does is send some
messages to your syslog server. However, one of your messages
contradicts with this conclusion: "When i copy it over to the chroot
directory the error goes away". This suggests that the problem is in
your chroot jail and jk_chrootsh is running fine, trying to jail the
user and failing. But again: when failing you would get logging why it
fails, and you don't get any logging.

Do you have logging in the jail enabled and running (either with syslog
or with jk_socketd) ??

A more obscure thing that could be the issue is if you're using SELinux or AppArmor or another access control system, and this system interferes..

Hope this helps.


Jailkit-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]