[FreeNX-kNX] nx-client terminates on linux but works on windows

William Hoburg Howil at gmx.net
Fri Sep 21 08:16:21 UTC 2007


Hi everyone,

i'm using an freenx-server 0.7.0 with NXSERVER - Version 1.5.0-70 on
redhat EL5 (64bit). I can connect with a windows xp nomachine nx-client (version
3.0.0-78) without problems. but when i try  to connect from a linux (i
tried fedora core7, ubuntu 7.04, ubuntu 7.10) with the same client
version i cannot get the connection established correct.
the (linux client ) shows:
# Established the display connection
and afterwards it says:
# Session sulfur failed

ssh authentication for nx user on the server looks good and also a X-connection over ssh works as it should.

i listed all logs below... details of the client logs from the server
(and agent) as well as the node.conf

An other problem is that when i start a gnome session (till now from
windows xp) i get an error after starting up the session which says that
there were problems starting the gnome setting daemon
(GNOME-Einstellungsdämon) 'Failed to connect to
socket /tmp/dbus-XD8cbfwRqy: Verbindungsaufbau abgelehnt' what leads to
problems setting up a correct keyboard layout.

Does anyone know what that means resp. what i can do?

thx a lot in advance
howil

ps.: i changed the user name into hort*****


In the Details i found, what looks good for me until Terminating
session:

#NXPROXY - Version 3.0.0
#
#Copyright (C) 2001, 2007 NoMachine.
#See http://www.nomachine.com/ for more information.

#Info: Proxy running in client mode with pid '9409'.
#Session: Starting session at 'Fri Sep 21 09:30:06 2007'.
#Warning: Connected to remote version 2.1.0 with local version 3.0.0.
#Info: Connection with remote proxy completed.
#Info: Using LAN link parameters 1536/24/1/0.
#Info: Using image streaming parameters 50/128/1024KB/6144/768.
#Info: Using image cache parameters 1/1/65536KB.
#Info: Using pack method '16m-rle-9' with session 'unix-kde'.
#Info: Not using NX delta compression.
#Info: Not using ZLIB data compression.
#Info: Not using ZLIB stream compression.
#Info: Not using a persistent cache.
#Info: Forwarding X11 connections to display ':0.0'.
#Session: Session started at 'Fri Sep 21 09:30:06 2007'.
#Info: Established X server connection.
#Info: Using shared memory parameters 1/2048K.
#Session: Terminating session at 'Fri Sep 21 09:31:07 2007'.
#Info: Waiting the cleanup timeout to complete.
#Warning: Parent process appears to be dead. Exiting watchdog.



in the nxserver.log i found :


-- NX SERVER START: -c /usr/libexec/nx/nxserver - ORIG_COMMAND=
HELLO NXSERVER - Version 1.5.0-70 OS (GPL)
NX> 105 hello NXCLIENT - Version 1.5.0
NX> 134 Accepted protocol: 1.5.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: hort*****
NX> 102 Password: 
Info: Auth method: passdb 
NX> 103 Welcome to: sulfur user: hort*****
NX> 105 listsession --user="hort*****" --status="suspended,running"
--geometry="1400x1050x24+render" --type="unix-kde"
NX> 127 Sessions list of user 'hort*****' for reconnect:

Display Type             Session ID                       Options  Depth
Screen         Status      Session Name
------- ---------------- -------------------------------- -------- -----
-------------- ----------- ------------------------------


NX> 148 Server capacity: not reached for user: hort*****
NX> 105 startsession  --link="lan" --backingstore="1" --encryption="1"
--cache="16M" --images="64M" --media="0" --session="sulfur"
--type="unix-kde" --geometry="1400x1000" --kbtype="pc105/de"
--screeninfo="1400x1000x24+render" 

&link=lan&backingstore=1&encryption=1&cache=16M&images=64M&media=0&session=sulfur&type=unix-kde&geometry=1400x1000&kbtype=pc105/de&screeninfo=1400x1000x24+render&clientproto=1.5.0&user=hort*****&userip=192.168.100.65&uniqueid=FB2031B4D4C5C743F38A7118C48DC2FB&display=1000&host=127.0.0.1 
NX> 1000 NXNODE - Version 1.5.0-70 OS (GPL)
server_nxnode_echo: NX> 1000 NXNODE - Version 1.5.0-70 OS (GPL)
NX> 700 Session id: sulfur-1000-FB2031B4D4C5C743F38A7118C48DC2FB
NX> 705 Session display: 1000
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 1777d022d8b2ca4714d15e43ad61c259
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 1777d022d8b2ca4714d15e43ad61c259
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 1
server_nxnode_echo: NX> 700 Session id:
sulfur-1000-FB2031B4D4C5C743F38A7118C48DC2FB
server_nxnode_echo: NX> 705 Session display: 1000
server_nxnode_echo: NX> 703 Session type: unix-kde
server_nxnode_echo: NX> 701 Proxy cookie:
1777d022d8b2ca4714d15e43ad61c259
server_nxnode_echo: NX> 702 Proxy IP: 127.0.0.1
server_nxnode_echo: NX> 706 Agent cookie:
1777d022d8b2ca4714d15e43ad61c259
server_nxnode_echo: NX> 704 Session cache: unix-kde
server_nxnode_echo: NX> 707 SSL tunneling: 1
NX> 1009 Session status: starting
server_nxnode_echo: NX> 1009 Session status: starting
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
server_nxnode_echo: NX> 710 Session status: running
server_nxnode_echo: NX> 1002 Commit
session_status FB2031B4D4C5C743F38A7118C48DC2FB Running
NX> 105 server_nxnode_echo: NX> 1006 Session status: running
bye
Bye
NX> 999 Bye
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
SESSION_LOG_CLEAN=0 in node.conf and investigate
"/a/ursus/hort*****/.nx/F-C-sulfur-1000-FB2031B4D4C5C743F38A7118C48DC2FB/session". You might also want to try: ssh -X myserver; /usr/libexec/nx/nxnode --agent to test the basic functionality. Session log follows:
server_nxnode_echo: NX> 596 Session startup failed.
NX> 596 Session startup failed.
server_nxnode_echo: NX> 1004 Error: NX Agent exited with exit status 1.
To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate
"/a/ursus/hort*****/.nx/F-C-sulfur-1000-FB2031B4D4C5C743F38A7118C48DC2FB/session". You might also want to try: ssh -X myserver; /usr/libexec/nx/nxnode --agent to test the basic functionality. Session log follows:
NX> 1006 Session status: closed
session_close FB2031B4D4C5C743F38A7118C48DC2FB
server_nxnode_echo: NX> 1006 Session status: closed



/a/ursus/hort*****/.nx/F-C-sulfur-1000-FB2031B4D4C5C743F38A7118C48DC2FB/session looks like:

NXAGENT - Version 2.1.0

Copyright (C) 2001, 2006 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Agent running with pid '27560'.
Session: Starting session at 'Fri Sep 21 09:45:03 2007'.
Info: Proxy running in server mode with pid '27560'.
Info: Waiting for connection from '127.0.0.1' on port '5000'.
Info: Accepted connection from '127.0.0.1' with port '35346'.
Info: Connection with remote proxy established.
Warning: Connected to remote NXPROXY version 3.0.0 with local version
2.1.0.
Warning: Consider checking http://www.nomachine.com/ for updates.
Info: Synchronizing local and remote caches.
Info: Handshaking with remote proxy completed.
Info: Using lan link parameters 1536/24/1/0.
Info: Using agent parameters 5000/50/0/0.
Info: Using image streaming parameters 50/128/1024KB/6144/768.
Info: Using image cache parameters 1/1/65536KB.
Info: Using pack method '16m-rle-9' with session 'unix-kde'.
Info: Not using NX delta compression.
Info: Not using ZLIB data compression.
Info: Not using ZLIB stream compression.
Info: Not using persistent cache.
Info: Established X client connection.
Info: Using shared memory parameters 1/1/1/2048K.
Info: Detected window manager running.
Info: Not using local device configuration changes.
Info: Using alpha channel in render extension.
xsetroot:  unable to open display 'unix:1000'
xset:  unable to open display "unix:1000"
xset:  unable to open display "unix:1000"
xsetroot:  unable to open display 'unix:1000'
startkde: Starting up...
ksplash: cannot connect to X server unix:1000
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kded: cannot connect to X server unix:1000
DCOP aborting call from 'anonymous-27679' to 'kded'
kcminit_startup: cannot connect to X server unix:1000
ksmserver: cannot connect to X server unix:1000
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
startkde: Done.


the node.conf looks like:

# node.conf
#
# This file is provided by FreeNX. It should be placed either into
# /etc/nxserver/node.conf (FreeNX style) or /usr/NX/etc/node.conf
# (NoMachine NX style).
#
# It is mostly compatible with NoMachine node.conf. The most important
# difference is that no spaces are allowed when assigning values (eg
# "A=value" is allowed, "A = value" is NOT).
#
# This file is sourced by bash, so you can do some fancy stuff here if
you
# want to, but be aware that it is sourced 3 times per connection. If
you
# want autostart stuff, set NODE_AUTOSTART instead!
#
#
# You surely are aware that FreeNX is based on the fantastic results
that
# the hard work by NoMachine.com has achieved. NoMachine.com released
the
# core NX libraries under the GPL. The installation of these libs are
the
# precondition for all FreeNX scripts to work. If you are installing
this
# software with the help of one of the package management tools of your
# Linux distribution, you can assume that this dependency is taken care
of
# by the tool.
#
# You have questions about the inner workings of the NX technology?
#
# Then you are recommended to first check out the rich and very detailed
# NoMachine documentation and their online Knowledge Base at
#
#           http://www.nomachine.com/kb/
#
# Other sources of information are the NoMachine mailing lists
# (nxusers at nomachine.com and nxdevelopers at nomachine.com):
#
#           http://www.nomachine.com/mailinglists.php
#
# The FreeNX (freenx-knx at kde.org) list is here:
#
#           https://mail.kde.org/mailman/listinfo/freenx-knx
#
# SVN: $Id: node.conf.sample 226 2006-07-04 23:38:10Z fabianx $

#########################################################################
# General FreeNX directives
#########################################################################

# The host name which is used by NX server. It's should be used if it's
# different than the default hostname (as returned by `hostname`)
#SERVER_NAME="$(hostname)"

# The port number where local 'sshd' is listening.
#SSHD_PORT=22

#########################################################################
# Authentication / Security directives
#########################################################################

# Authentication directives

# This adds the usermode to the possible authentication methods
# Usermode means that a user can start the nxserver as his shell
# and connect directly to the right server via a custom client.
#ENABLE_USERMODE_AUTHENTICATION="0"

# This adds the passdb to the possible authentication methods
#ENABLE_PASSDB_AUTHENTICATION="1"

# This adds SSH to the possible authentication methods. For it to work
sshd
# must be set up at localhost accepting password authentication.
#ENABLE_SSH_AUTHENTICATION="1"

# This adds SU to the possible authentication methods. For it to work
the
# "nx" user must be in the wheel (RedHat, Fedora) or the users group
(SUSE)
# and the user logging in must have a valid shell that accepts the -c
# parameter.
#ENABLE_SU_AUTHENTICATION="0"

# Require all users to be in the passdb, regardless of authentication
method
#ENABLE_USER_DB="0"


# If enabled forces the user to use encryption. This will bail out
# if the user does not have encryption enabled.
#ENABLE_FORCE_ENCRYPTION="0"

# Refuse the NX client connection if SSHD does not export the
# SSH_CONNECTION and SSH_CLIENT variables in the environment
# passed to the NX server.
# 1: Will check the remote IP and will not accept the
#    connection if it can't be determined.
# 0: Will accept the connection even if the remote IP
#    is not provided.
#SSHD_CHECK_IP="0"

#########################################################################
# Restriction directives
#########################################################################

# The base display number from which sessions are started.
#DISPLAY_BASE=1000

# The maximum number of contemporary sessions that can be run on FreeNX
#SESSION_LIMIT=200

# The maximum number of contemporary sessions that a single user can run
# on FreeNX. Defaults to the value of SESSION_LIMIT.
#SESSION_USER_LIMIT=200

# The number of displays reserved for sessions, it has to be greater or
equal
# to the maximum number of contemporary sessions that a server can run.
#DISPLAY_LIMIT=200


# User for which sessions should be persistent. Either the keyword "all"
or a
# comma-separated list of usernames or groups in the @groupname syntax.
#ENABLE_PERSISTENT_SESSION="all"

# Users and groups for whom persistent sessions should be disabled.
# Especially useful if ENABLE_PERSISTENT_SESSION="all"
#DISABLE_PERSISTENT_SESSION=""


#########################################################################
# Logging directives
#########################################################################

# This directives controls the verbosity of the server-wide log.
# 0: No Logging
# 1: Errors
# 2: Warnings
# 3: Important information
# 4: Server - Client communication
# 5: Information
# 6: Debugging information
# 7: stderror of some applications
#NX_LOG_LEVEL=0
NX_LOG_LEVEL=7

# By setting this to 0 the nxserver might be a bit faster, but passwords
can be found in the log files.
#NX_LOG_SECURE=1

# Before turning logging on, please make sure that NX_LOGFILE is
# writeable for the "nx" user
#NX_LOGFILE=/var/log/nxserver.log
NX_LOGFILE=/var/log/nxserver.log

# This directive controls if the temporary session directory
# ($HOME/.nx/C-<hostname>-<display>-<session_id>) should be kept after a
# session has ended. A successfully terminated session will be saved as
# T-C-<hostname>-<display>-<session_id> while a failed session will be
saved
# as F-C-<hostname>-<display>-<session_id>.
# The default is to cleanup the directories.
SESSION_LOG_CLEAN=0

# Amount of seconds nxserver is to keep session history. The default of
2592000
# is equivalent to 30 days. If this is 0 no session history will be kept
# and a negative value denotes infinity.
#SESSION_HISTORY=2592000


#########################################################################
# Forwarding directives
#########################################################################

# FreeNX with ENABLE_SERVER_FORWARD="1" will automatically forward all
# connections to the host specified in SERVER_FORWARD_HOST with the
# secret key SERVER_FORWARD_KEY.
#
# This allows to have a "chain" of NX Servers. Note that you will need
to
# use "SSL encryption" for all connections.

#ENABLE_SERVER_FORWARD="0"
#SERVER_FORWARD_HOST=""
#SERVER_FORWARD_PORT=22
#SERVER_FORWARD_KEY="/usr/NX/share/client.id_dsa.key"


# FreeNX with ENABLE_NOMACHINE_FORWARD_PORT="1" will automatically
forward all
# connections to the commercial NoMachine nxserver installed on the same
# machine, which go in by port NOMACHINE_FORWARD_PORT. This feature is
introduced
# to enable the usage of FreeNX and NoMachine NX side by side on the
same machine
# without conflicts.
#
# Note: You need to let SSHD listen to several ports to make use of this
#       directive.

#ENABLE_NOMACHINE_FORWARD_PORT="0"
#NOMACHINE_FORWARD_PORT="22"

#NOMACHINE_SERVER="/usr/NX/bin/nxserver"
#NOMACHINE_NX_HOME_DIR="/usr/NX/home/nx"

# LOAD BALANCING
# ==============
#
# To do load balancing setup some hosts in LOAD_BALANCE_SERVERS and
# make:
#
#   - either sure that all incoming connections are sent to the master
#     server by using forwarding directives on the "slave" servers.
#
#   - or share the session database space via NFS between the servers.
#     (not recommended at the moment as race conditions for DISPLAYs can
#      occur)
#

#LOAD_BALANCE_SERVERS=""

# The following load_balance_algorithms are available at the moment:
#
# "load", "round-robin", "random"
#

#LOAD_BALANCE_ALGORITHM="load"

# By setting ENABLE_LOADBALANCE="1" you can let users choose their
# preferred host, while being forwarded to another server. Of course
# this is just a preference. The loadbalancing algorithm can completely
# choose to ignore the users choice.

#ENABLE_LOAD_BALANCE_PREFERENCE="0"

#########################################################################
# Services directives
#########################################################################

# FreeNX with ENABLE_ESD_PRELOAD="1" will automatically try to setup
# the sound with the help of the esd media helper.
#
# Currently ESD will be used just by the Windows NX Client.
#
# Be sure that $ESD_BIN_PRELOAD is in your path, does exist and work
# before enabling this directive.

#ENABLE_ESD_PRELOAD="0"
#ESD_BIN_PRELOAD="esddsp"

# FreeNX with ENABLE_ARTSD_PRELOAD="1" will automatically try to setup
# the sound with the help of the artsd media helper.
#
# Currently ARTSD will be used just by the Linux NX Client.
#
# Be sure that $ARTSD_BIN_PRELOAD is in your path, does exist and work
# before enabling this directive.

#ENABLE_ARTSD_PRELOAD="0"
#ARTSD_BIN_PRELOAD="artsdsp"

# FreeNX with ENABLE_KDE_CUPS="1" will automatically write
# $KDE_PRINTRC and put the current used port into it.
# $KDE_PRINTRC is automatically calculated if its not set.

#ENABLE_KDE_CUPS="0"
#KDE_PRINTRC="$KDEHOME/share/config/kdeprintrc"
#CUPS_ETC="/etc/cups"

#########################################################################
# Path directives
#########################################################################

# USER_FAKE_HOME is the base directory for the .nx directory. Use this
# parameter instead of the users home directory if $HOME is on a NFS
share.
# Note that this directory must be unique for every user! To accomplish
this
# it is recommended to include $USER in the path.
#USER_FAKE_HOME=$HOME

# Add the nx libraries to LD_LIBRARY_PATH before starting nx agents.
# WARNING: This will NOT (and should not) affect applications. ONLY
Disable
# this if the nx libraries are in a standard system path (such
as /usr/lib)!
#SET_LD_LIBRARY_PATH="1"


# The command binary for the default window manager. If set it is run
when a
# 'unix-custom' session is requested by the NX Client and an application
# to run is specified. It defaults to empty (ie no WM is run).
# If KILL_DEFAULT_X_WM is set the WM is terminated after the started
# application finishes. Else FreeNX will wait for the WM to complete.
#DEFAULT_X_WM=""
#KILL_DEFAULT_X_WM="1"

# When a 'unix-default' session is requested by the client the user's X
startup
# script will be run if pressent and executable, otherwise the default X
# session will be run.
# Depending on distribution USER_X_STARTUP_SCRIPT might
be .Xclients, .xinitrc
# and .Xsession
# Depending on distribution DEFAULT_X_SESSION might
be /etc/X11/xdm/Xsession,
# /etc/X11/Sessions/Xsession or /etc/X11/xinit/xinitrc
#USER_X_STARTUP_SCRIPT=.Xclients
#DEFAULT_X_SESSION=/etc/X11/xdm/Xsession

# The key that contains the name of the script that starts a KDE
session.
# It's run when a 'unix-kde' session is requested by the client.
#COMMAND_START_KDE=startkde

# The key that contains the name of the script that starts a gnome
session.
# It's run when a 'unix-gnome' session is requested by the client.
#COMMAND_START_GNOME=gnome-session

# The key that contains the name of the script that starts a CDE
session.
# It's run when a 'unix-cde' session is requested by the client.
#COMMAND_START_CDE=cdwm

# The key that contains the name of the complete path of command name
# 'xterm'. It is run when a unix "xterm" session is requested by the
# client.
#COMMAND_XTERM=xterm

# The key that contains the name of the complete path of command name
# 'xauth'.
#COMMAND_XAUTH=/usr/X11R6/bin/xauth

# The key that contains the name of the complete path of command name
# 'smbmount'.
#COMMAND_SMBMOUNT=smbmount

# The key that contains the name of the complete path of command name
# 'smbumount'.
#COMMAND_SMBUMOUNT=smbumount

# The key that contains the name of the complete path of the 'netcat'
command.
#COMMAND_NETCAT=netcat

# The key that contains the name of the complete path of the 'ssh' and
# 'ssh-keygen' command.
#COMMAND_SSH=ssh
#COMMAND_SSH_KEYGEN=ssh-keygen

# The key that contains the name of the complete path of the 'cupsd'
command.
#COMMAND_CUPSD=/usr/sbin/cupsd

# The tool to generate md5sums with
#COMMAND_MD5SUM=md5sum

#########################################################################
# Misc directives
#########################################################################

# When you installed a 2.0.0 NX Backend, set this to 1.
#ENABLE_2_0_0_BACKEND="0"
ENABLE_2_0_0_BACKEND="1"
ENABLE_1_5_0_BACKEND="1"

# When set to 1 this will automatically resume started sessions
#ENABLE_AUTORECONNECT="1"

# When set to 1 this will automatically resume started sessions
# but only if an older client version is used
#ENABLE_AUTORECONNECT_BEFORE_140="1"

# When set to 1 exports NXUSERIP / NXSESSIONID in nxnode
#EXPORT_USERIP="0"
#EXPORT_SESSIONID="1"

# This can be set to any executable, which is started after session
startup
# like: $NODE_AUTOSTART {start|restore}
#NODE_AUTOSTART=""

# When set to 1 will start nxagent in rootless mode.
#ENABLE_ROOTLESS_MODE="1"

# If enabled writes entries via the COMMAND_SESSREG program
# into utmp/wtmp/lastlog database.
# Note: You have to make sure that you add the nx user to the
#       utmp or tty group or how its called on your system
#       before this directive works.
#ENABLE_USESSION="0"
#COMMAND_SESSREG="sessreg"

# Extra options sent to the different nx agents. See !M documentation
# for examples of useful parameters.
#AGENT_EXTRA_OPTIONS_RFB=""
#AGENT_EXTRA_OPTIONS_RDP=""
AGENT_EXTRA_OPTIONS_X=""

# The number of seconds we wait for the nxagent to start before
# deciding startup has failed
AGENT_STARTUP_TIMEOUT="60"
###AGENT_STARTUP_TIMEOUT="10"

# The font server the agent will use. If set to "" no font server is
used.
# For this to do any good, the client has to have the same font server
set
# in /etc/X11/XF86Config
#AGENT_FONT_SERVER=""

# Disable or enable use of 'tcp nodelay' on proxy. Old versions of Linux
# kernels have problems using this option on sockets that will cause a
loss
# of TCP connections. This option is not set by default to allow clients
to
# specify whether to enable or disable TCP nodelay. Setting this option
to
# the value of "0" NX proxy avoids using 'tcp nodelay' but it will cause
a
# loss of interaction in sessions.
#PROXY_TCP_NODELAY=""


# Extra options to nxproxy. See !M documentation for useful parameters.
#PROXY_EXTRA_OPTIONS=""













-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger



More information about the FreeNX-kNX mailing list