On Thu, Oct 13, 2016 at 07:21:33AM +0000, Duje Drazin wrote:
> Hi all,
>
>
>
> I have configured following:
>
>
>
> qlogin_command telnet
>
> qlogin_daemon /usr/sbin/in.telnetd
>
> rlogin_command /usr/bin/ssh -X
>
> rlogin_daemon /usr/sbin/sshd -i
>
> rsh_command /usr/bin/ssh -X
>
> rsh_daemon /usr/sbin/sshd -i
>
>
>
>
>
> but with this configuration on qrsh I have following error:
>
>
>
> 1654 23344 main R E A D I N G J O B ! ! ! ! ! ! ! ! ! !
> !
>
> 1655 23344 main
> ============================================
>
> 1656 23344 main random polling set to 5
>
> 1657 23344 140545581356800 --> sge_gettext_() {
>
> 1658 23344 140545581356800 -->
> sge_get_message_id_output_implementation() {
>
> 1659 23344 140545581356800 <--
> sge_get_message_id_output_implementation() ../libs/uti/sge_language.c 582
> }
>
> 1660 23344 140545581356800 <-- sge_gettext_()
> ../libs/uti/sge_language.c 730 }
>
> 1661 23344 140545581356800 --> sge_gettext__() {
>
> 1662 23344 140545581356800 sge_gettext() called without valid
> gettext function pointer!
>
> 1663 23344 140545581356800 <-- sge_gettext__()
> ../libs/uti/sge_language.c 781 }
>
> 1664 23344 140545581356800 --> sge_htable_resize() {
>
> 1665 23344 140545581356800 <-- sge_htable_resize()
> ../libs/uti/sge_htable.c 204 }
>
> 1666 23344 main --> wait_for_qrsh_socket() {
>
> 1667 23344 main accepted client connection, fd = 3
>
> 1668 23344 main <-- wait_for_qrsh_socket() ../clients/qsh/qsh.c
> 404 }
>
> 1669 23344 main --> get_client_server_context() {
>
> 1670 23344 main --> read_from_qrsh_socket() {
>
> 1671 23344 main <-- read_from_qrsh_socket()
> ../clients/qsh/qsh.c 461 }
>
> 1672 23344 main qlogin_starter sent: 137
>
>
>
> When I manually execute ssh toward servers everithing works fine, so I
> would like to understand which unix command are executed in background of
> command qrsh?There's a diagram of the process which qrsh uses below. The commands you specified replace rsh, rshd and rlogind in the diagrams. http://arc.liv.ac.uk/repos/hg/sge/source/clients/qrsh/qrsh.html Check the nodes involved for a firewall/packet filter as for qrsh to work various things need to listen and accept connections on dynamically assigned ports rather than just port 22 like normal ssh. William > > > > > > > > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users
signature.asc
Description: Digital signature
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
