Thanks much, I did not have jk_socketd running (it was already configured and it's run in the past, but ...?) After starting it, I do get jk_lsh logging:
jk_chrootsh[25593]: now entering jail /usr/local/chroot_jail for user CSUSER (1002)
jk_lsh[25593]: jk_lsh version 2.10, started jk_lsh[25593]: the requested executable rsync is not found jk_lsh[25593]: executing command 'rsync --server -e.Ls . /home/CSUSER' for user CSUSER (1002) jk_lsh[25593]: WARNING: running rsync failed for user CSUSER (1002): Unknown error 4294967295
jk_lsh[25593]: WARNING: check the permissions and libraries for rsync
I am able to run the rsync executable 'by hand' using chroot command on the command line: chroot /usr/local/chroot_jail rsync ...etc...
Is this not a representative test for running it under jk_lsh?
Is there a good way to narrow the problem to a more specific cause?
The rsync executable file is in /usr/local/chroot_jail/usr/bin with perms 755; the dir and its parents are 755. All are owned by root:root.