Educate Me on Remote Desktops - Page 2 - AVS Forum | Home Theater Discussions And Reviews
Forum Jump: 
Reply
 
Thread Tools
post #31 of 200 Old 05-01-2010, 08:05 AM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
I guess I didn't know what I was looking at in my previous post. Those two commands that you gave me worked! I can log in!!!

Thank you, tux, as always, for your help.
shane2943 is offline  
Sponsored Links
Advertisement
 
post #32 of 200 Old 05-01-2010, 08:40 AM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
Ok, once I was able to ssh, I tried to access NX again and instead of getting the "could not connect" message, I got "authentication failed." This is progress!

So I added the user 'shane' to the nxserver:
Code:
[root@localhost shane]# nxserver --useradd shane
NX> 801 User: shane uses SSHD authentication.
NX> 900 Adding public key for user: shane to the authorized keys file.
NX> 716 Public key added to: /home/shane/.ssh/authorized_keys2.
NX> 900 Verifying public key authentication for NX user: shane.
NX> 900 Public key authentication succeeded.
NX> 301 User: shane enabled in the NX user DB.
NX> 999 Bye.
But I'm still not able to get in. Same authentication failed message.

Here's a couple screenshots of what I'm getting on the Macbook:

shane2943 is offline  
post #33 of 200 Old 05-01-2010, 02:32 PM
AVS Forum Special Member
 
tux99's Avatar
 
Join Date: Jan 2005
Location: Europe
Posts: 1,515
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 11
As I said I have no clue about NX, so can't promise anything, but if provide the output of:
tail -30 /var/log/messages
right after a failed login attempt there might me an indication that will help solve the issue in it.

/var/log/messages is the primary log file of any Linux box, so when you have problems that's always a good place to look for error messages that might help solve an issue.

My Linux news / reviews / tips+tricks / downloads web site: http://www.linuxtech.net/
tux99 is offline  
 
post #34 of 200 Old 05-01-2010, 03:18 PM
 
mythmaster's Avatar
 
Join Date: Mar 2008
Location: 255.255.255.255
Posts: 2,107
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
You might need to copy the SSH key over to the mac. It's really been a while since I've used NX, but it seems like a good idea to generate one. http://serverfault.com/questions/641...efault-ssh-key
mythmaster is offline  
post #35 of 200 Old 05-01-2010, 08:09 PM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
Ugh. I think I screwed something up. When I run "nxserver --install," I get this:
Code:
[root@localhost shane]# nxserver --install
NX> 701 Updating: server at: Sat May 01 21:58:11 2010.
NX> 701 Autodetected system: mandrake.
NX> 701 Update log is: /usr/NX/var/log/update.
NX> 701 Checking NX server configuration using /usr/NX/etc/server.cfg file.
NX> 723 Cannot start NX statistics:
NX> 709 NX statistics are disabled for this server.
NX> 701 WARNING: Error when trying to connect to NX server, error is:
NX> 701 WARNING: nxsetup cannot validate the sanity of the current installation:
NX> 701 WARNING: the current system or NX configuration could be broken.
NX> 701 WARNING: If difficulties arise (for example sessions cannot be started),
NX> 701 WARNING: it is advisable that you try to uninstall the NX server and the
NX> 701 WARNING: NX client packages then install them again.
NX> 701 WARNING: Search also the NoMachine Knowledge Base at the URL below:
NX> 701 WARNING: http://www.nomachine.com/kb
NX> 701 WARNING: for common errors encountered when performing a software update
NX> 701 WARNING: and the related hints on how to solve them..
NX> 701 Update of NX server has been completed with warnings
NX> 701 Please review the update log for details.
NX> 701 Bye.
When I try to login to the server via the Macbook's NX client, I get this in /var/log/messages on the HTPC:
Code:
May  1 20:19:13 localhost sshd[24685]: User nx not allowed because shell /usr/bin/nxserver does not exist
I tried to uninstall the nxserver using the uninstall command and it ran. I reinstalled with the same result. I uninstalled the nxserver package using the package manager and then reinstalled it with the same result.

Dang it.
shane2943 is offline  
post #36 of 200 Old 05-01-2010, 08:54 PM
AVS Forum Special Member
 
tux99's Avatar
 
Join Date: Jan 2005
Location: Europe
Posts: 1,515
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 11
Can you tell us exactly which NX server package you are currently using?

My Linux news / reviews / tips+tricks / downloads web site: http://www.linuxtech.net/
tux99 is offline  
post #37 of 200 Old 05-02-2010, 09:26 AM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
The freenx that is in the Mandriva repos.
Code:
[root@localhost shane]# nxserver --version
NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
[root@localhost shane]#
Here's more info. In case y'all need it:
Code:
[root@localhost shane]# nxloadconfig --check
Warning: Could not find nxdesktop in /usr/bin. RDP sessions won't work.
Warning: Could not find nxviewer in /usr/bin. VNC sessions won't work.
Warning: Invalid value "APPLICATION_LIBRARY_PRELOAD=/usr/lib/libX11.so.6.2:/usr/lib/libXext.so.6.4:/usr/lib/libXcomp.so:/usr/lib/libXcompext.so:/usr/lib/libXrender.so.1.2". /usr/lib/libX11.so.6.2 could not be found. Users will not be able to run a single application in non-rootless mode.
Warning: "/usr/lib/cups/backend/nxipp" is not executable.
         Users will not be able to enable printing.
Warning: Invalid value "CUPS_ETC=/etc/cups/"
         Users will not be able to enable printing.
Warning: Invalid value "COMMAND_START_GNOME=gnome-session"
         Users will not be able to request a Gnome session.
Warning: Invalid value "COMMAND_START_CDE=cdwm"
         Users will not be able to request a CDE session.
Warning: Invalid value "COMMAND_SMBMOUNT=smbmount". You'll not be able to use SAMBA. 
Warning: Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be able to use SAMBA.
Warning: Invalid cupsd version of "/usr/sbin/cupsd". Need version 1.2.
         Users will not be able to enable printing.

  Warnings occured during config check.
  To enable these features please correct the configuration file.
I don't see anything coming up in /var/log/messages when I try to login from the client anymore since the last reboot.

Here's the config file:
Code:
# 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@nomachine.com and nxdevelopers@nomachine.com):
#
#           http://www.nomachine.com/mailinglists.php
#
# The FreeNX (freenx-knx@kde.org) list is here:
#
#           https://mail.kde.org/mailman/listinfo/freenx-knx
#
# SVN: $Id: node.conf.sample 580 2008-08-22 00:44:43Z 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="0"

# 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"

# If ENABLE_SLAVE_MODE="1" the user will be just logged in _once_ and the 
# communication is done via nxnode slave mode.
#
# This is useful for one time passwords or to have less traffic in utmp 
# and wtmp.
#
# Also session startup times are much faster in slave mode. This is true especially 
# if many printers or shares have to be added.
#
# For this to work the binary nxserver-helper has to be installed in 
# PATH_BIN.
#
ENABLE_SLAVE_MODE="1"

# If ENABLE_LOG_FAILED_LOGINS="1" then failed login attempts are logged to the system
# auth.log.
#
# This is useful in combination with tools like fail2ban.
#
# The default is to log failed login attemps via syslog (3).
#
#ENABLE_LOG_FAILED_LOGINS="1"

#########################################################################
# 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=""

# This enables the mirroring of running sessions via VNC feature.
# 
# Session is marked as resumable and type is vnc-mirrored.
# 
#ENABLE_MIRROR_VIA_VNC=1

# This enables the sharing of :0 via VNC feature.
# 
# Session is marked as resumable and type is vnc-local.
# 
# Note: You need to have the rights to access the display
#       else it does not work.
#
#ENABLE_DESKTOP_SHARING=1

#
# General shadowing / mirroring notes:
#
# By default shadowing is only allowed for the same user.
#
# If nxserver finds nxshadowacl binary, it asks it, for which users 
# the permission is granted.
# 
# nxshadowacl 
# 
# Exit code:
#
# 0 -> Save cookie in session file for other users
# 1 -> Do not save cookie
#
# Check if user is allowed to be shadowed by admin user.
#
# nxshadowacl  
# 
# Exit code:
#
# 0 -> Yes, allow shadowing and add to list
# 1 -> No, don't allow shadowing
# 

#
# When using NX 3.0 shadowing, this enables asking the user whether
# he authorizes another user to shadow his session
#
# 0: No authorization request will be presented,
#    and the session will be shadowed as if the user had approved.
# 1: (default) Ask for authorization
#
#ENABLE_SESSION_SHADOWING_AUTHORIZATION=1

# Allow session shadowing in interactive mode:
#
# 1: The shadowing user can interact with the shadowed session.
#
# 0: The shadowed session is view-only. No interaction with the
#    shadowed session is possible.
#
#ENABLE_INTERACTIVE_SESSION_SHADOWING=1

#
# Enable or disable clipboard:
#
# client:  The content copied on the client can be pasted inside the
#            NX session.
#
# server: The content copied inside the NX session can be pasted
#             on the client.
#
# both:    The copy&paste operations are allowed both between the
#             client and the NX session and vice-versa.
#
# none:   The copy&paste operations between the client and the NX
#            session are never allowed.
#
#ENABLE_CLIPBOARD="both"


#
# Enable or disable the pulldown dialog, which provides a graphical
# way to suspend or terminate the rootless session:
#
# 1: Enabled. The pulldown menu is shown when the mouse pointer
#     moves near the middle of the top boundary of a window and
#     allows the user to suspend or terminate the session by means
#     of an icon-click.
#
# 0: Disabled. The ctrl+alt+T key combination has to be issued
#     to get the dialog for suspending or terminating the session.
#
#ENABLE_PULLDOWN_MENU="1"


# The option USE_PROCESSOR_TASKSET is for setting the CPU affinity of all
# nx related processes.
#
# Note: To have for example startkde run on even another core, just specify:
#
# COMMAND_STARTKDE="taskset -c 2 -- startkde"
#
# FreeNX runs this option like: $COMMAND_TASKSET -cp "$USE_PROCESSOR_TASKSET" $$
# 
# So with $USE_PROCESSOR_TASKSET set to 3,4 it would balance the tasks to cores
# 3 and 4.
#
# If this option is empty, no balance to cores is done.
#
#USE_PROCESSOR_TASKSET=""

# If you set ENABLE_ADVANCED_SESSION_CONTROL="1" you can start a new application in an already
# running rootless session by using "add " as session name.
#
# Note: The client will return a message on that.
#
#ENABLE_ADVANCED_SESSION_CONTROL="0"

# If you set ENABLE_SHOW_RUNNING_SESSIONS="0" then nxserver will only show
# suspended sessions and you will not be able to resume or terminate a running 
# session.
#
#ENABLE_SHOW_RUNNING_SESSIONS="1"

#########################################################################
# 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

# 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

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

# 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"
#
# For "load" you need a script called nxcheckload in PATH_BIN.
# 
# A sample script, which you can change to your needs it shipped with
# FreeNX under the name nxcheckload.sample.

#LOAD_BALANCE_ALGORITHM="random"

# 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 socket into it.
#
# If you additionally enable ENABLE_KDE_CUPS_DYNAMIC it will set the 
# Host entry to the script nxcups-gethost, which dynamically tries all 
# possible entries to find the current printing host.
#
# The order is: CUPS_SERVER (env var), ~/.cups/client.conf, $KDE_PRINTRC,
#               $CUPS_DEFAULT_SOCK, localhost
#
# So this option is most useful with ENABLE_CUPS_SERVER_EXPORT="1".
# 
# $KDE_PRINTRC is automatically calculated if its not set.

#ENABLE_KDE_CUPS="0"
#ENABLE_KDE_CUPS_DYNAMIC="0"
#KDE_PRINTRC="$KDEHOME/share/config/kdeprintrc"

# FreeNX with ENABLE_CUPS_SERVER_EXPORT="1" will automatically
# export the environment variable CUPS_SERVER.

#ENABLE_CUPS_SERVER_EXPORT="1"

# FreeNX with ENABLE_CUPS_SEAMLESS will automatically try to download the 
# necessary ppds from the client.
# 
# As the forwarding is just active as soon as nxagent is started,
# we need a small delay of $CUPS_SEAMLESS_DELAY.
#
# Note: You need to use a patched cupsd on client side.

#ENABLE_CUPS_SEAMLESS="0"
#CUPS_SEAMLESS_DELAY="10"

# FreeNX with ENABLE_FOOMATIC will integrate the foomatic db to the list
# of available ppd drivers via the $COMMAND_FOOMATIC command.

#ENABLE_FOOMATIC="1"
#COMMAND_FOOMATIC="/usr/lib/cups/driver/foomatic-ppdfile"

# CUPS_BACKEND and CUPS_ETC are the corresponding paths of your CUPS 
# installation.

#CUPS_BACKEND="/usr/lib/cups/backend"
#CUPS_IPP_BACKEND="$CUPS_BACKEND/nxipp"
#CUPS_DEFAULT_SOCK="/var/run/cups/cups.sock"
#CUPS_ETC="/etc/cups"

# SAMBA_MOUNT_SHARE_PROTOCOL is a key to configure the supported 
# protocols for mounting shares.
#
# This key can be set to the following values:
#
# both, either SMB and CIFS protocol are supported, this is the default value.
# smbfs, only SMB protocol is supported.
# cifs, only CIFS protocol is supported.
# none, no network file-sharing protocol is supported.

#SAMBA_MOUNT_SHARE_PROTOCOL="both"

# FreeNX with ENABLE_SAMBA_PRELOAD="1" will automatically setup
# port 445 and 139 and forward them to the used samba port.
#
# This enables samba browsing to the local subnet in for example 
# konqueror.
#
#ENABLE_SAMBA_PRELOAD="0"

# FreeNX with ENABLE_SOURCE_BASH_PROFILE="1" will source the users ~/.bash_profile
# before application startup as we are kind of a login shell.
#
# With this key this behaviour can be enabled (default) or disabled.
# 
#ENABLE_SOURCE_BASH_PROFILE="1"

#########################################################################
# 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/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 command name
# 'mount.cifs'.
#COMMAND_SMBMOUNT_CIFS=/sbin/mount.cifs

# The key that contains the name of the complete path of command name
# 'umount.cifs'.
#COMMAND_SMBUMOUNT_CIFS=/sbin/umount.cifs

# 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="openssl md5"

# The key that contains the name of the complete path of the 'rdesktop' command.
#COMMAND_RDESKTOP=rdesktop

# The key that contains the name of the complete path of the 'vncviewer' command.
#COMMAND_VNCVIEWER=vncviewer

# The key that contains the name of the complete path of the 'vncpasswd' command.
# By default the builtin nxpasswd is used.
#COMMAND_VNCPASSWD="$PATH_BIN/nxpasswd"

# The key that contains the name of the complete path of the 'x11vnc' command.
#COMMAND_X11VNC=x11vnc

# The key that contains the name of the complete path of the 'taskset' command.
#COMMAND_TASKSET=taskset

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

# When you installed an old 1.5.0 NX Backend, set this to 1.
ENABLE_1_5_0_BACKEND="0"

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

# 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="1"
#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="-nolisten tcp"

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

# 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=""

# In case you want to use an external 'rdesktop' command
# set this to "1".
# 
# If nxdesktop cannot be found this is set automatically to "1".
#ENABLE_EXTERNAL_NXDESKTOP="0"

# This configuration variable determines if 'rdesktop' command should be run with -k keyboard option
# or if the keyboard should be autodetected.
#
#ENABLE_EXTERNAL_NXDESKTOP_KEYBOARD="1"

# In case you want to use an external 'nxviewer' command
# set this to "1".
# 
# If nxviewer cannot be found this is set automatically to "1".
#ENABLE_EXTERNAL_NXVIEWER="0"
ENABLE_2_0_0_BACKEND="1"
ENABLE_ROOTLESS_MODE="1"
[root@localhost shane]#
I've tried setting the authentication mode to just the SSH option and that doesn't work. According to the freenx setup page on Mandriva's site, I could set the authentication method to passdb and then add the user and a password so I did that and still can't get it. According to the freenx wiki, I cannot set more than one of the 3 options (ssh, passdb, userdb) to "1" at a time. It seems as though the client is trying to login as user "nx" instead of the username I am specifying and the authentication is failing.

I can ssh into the HTPC fine. matter of fact, that's how I'm getting most of this done since I don't want to burn up the projectors lamps sooner than I have to. Since I rebooted the HTPC, I have to use ssh until I login to it.
shane2943 is offline  
post #38 of 200 Old 05-02-2010, 03:00 PM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
I think this might be an sshd issue. The NX Client on my macbook tries to authenticate as user 'nx' for some reason as can be seen here:


I then edited the /ect/ssh/sshd_config file and added the "AllowUsers nx" clause to it like is explained in this article:
http://www.faqs.org/docs/securing/chap15sec122.html

Still no dice though and now I can't ssh in from the macbook (probably because I left the user "shane" out from that edit).

Ugh. Why is this not working for me?

I even tried uninstalling freenx the best I could and trashing the config files and such so that I could start over fresh and reinstalled freenx on the Mandriva box. I set it up according to this article:
http://wiki.mandriva.com/en/Freenx

Still can't connect. Same error on the Macbook.
shane2943 is offline  
post #39 of 200 Old 05-02-2010, 03:38 PM
 
mythmaster's Avatar
 
Join Date: Mar 2008
Location: 255.255.255.255
Posts: 2,107
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Look into the SSH keys, shane: http://ubuntuforums.org/showthread.php?t=724800

This guide should be more relevant to you, also: http://wiki.centos.org/HowTos/FreeNX
mythmaster is offline  
post #40 of 200 Old 05-02-2010, 06:04 PM
AVS Forum Special Member
 
tux99's Avatar
 
Join Date: Jan 2005
Location: Europe
Posts: 1,515
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 11
First remove that "AllowUsers nx" from the sshd config and make sure you can log onto the HTPC as shane via ssh again.

Do you actually have a user 'nx' on your HTPC?

grep nx /etc/passwd will show you if a user 'nx' exists.

Then I think you need to focus more also on the NX client config on your macbook.
I'm really just guessing here since I have no experience with NX.

Edit: removed crap suggestions, see posts below for correct procedure.

My Linux news / reviews / tips+tricks / downloads web site: http://www.linuxtech.net/
tux99 is offline  
post #41 of 200 Old 05-02-2010, 06:35 PM
AVS Forum Special Member
 
tux99's Avatar
 
Join Date: Jan 2005
Location: Europe
Posts: 1,515
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 11
I just installed freenx (the package from the Mandriva repos) on my Mandriva 2010.0 HTPC.
At the end of the package installation there is an info pop-up that says the following:

Quote:
After installing this package, an nx user is created (this is a system user, do not try to log in as him), with a home located at /var/lib/nxserver/nxhome. His password is a random 32-character password.
Your user must install the key located at: /var/lib/nxserver/nxhome/.ssh/client.id_dsa.key to log in.
For knx, put it in: /usr/share/knx/ with world-readable right. For nomachine.com Nx client for windows put it in : C:\\Program Files\\NX Client for Windows\\share
You user will now be able to log in using their username and password provided you have ssh logins enabled for them

Did you read this and copy the key from /var/lib/nxserver/nxhome/.ssh/client.id_dsa.key to your macbook client?

My Linux news / reviews / tips+tricks / downloads web site: http://www.linuxtech.net/
tux99 is offline  
post #42 of 200 Old 05-02-2010, 07:33 PM
AVS Forum Special Member
 
tux99's Avatar
 
Join Date: Jan 2005
Location: Europe
Posts: 1,515
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 11
Ok I got it working.
you don't need to do any changes of the default sshd or freenx config on your server (the HTPC).

All you need to do is copy and paste the content of that key file from the server (/var/lib/nxserver/nxhome/.ssh/client.id_dsa.key) into the related config file of your NX client on the macbook.

I don't have a mac so I don't know where that's kept on a mac, but the nomachine NX client for Linux keeps the key in the following file:

/home//.nx/config/.nxs

where is your user name on the client machine (for example your macbook) and is in this case the hostname of your HTPC.

Inside the .nxs is a config key called:



replace any existing key (xxxxxx) in this config key with the content of the file /var/lib/nxserver/nxhome/.ssh/client.id_dsa.key from your server.
That's all!

My Linux news / reviews / tips+tricks / downloads web site: http://www.linuxtech.net/
tux99 is offline  
post #43 of 200 Old 05-03-2010, 07:12 PM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
I did the things in the link that Mythmaster posted about the ssh keys. Currently, I can't ssh in anymore. I just don't understand enough.

And, my wonderful Comcrap internet isn't working so I can't give y'all a rundown on what I've done so far so we can get ssh working again. Once it's back up, I'll give y'all a command-by-command history on what I did to mess this up worse.

I do want to thank you tux, mythmaster, and the rest who have contributed to help! I always try to make sure I thank those who gave time, knowledge, etc to help me. You guys make this place great.
shane2943 is offline  
post #44 of 200 Old 05-03-2010, 07:32 PM
AVS Forum Special Member
 
tux99's Avatar
 
Join Date: Jan 2005
Location: Europe
Posts: 1,515
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 11
Quote:
Originally Posted by shane2943 View Post

I did the things in the link that Mythmaster posted about the ssh keys. Currently, I can't ssh in anymore. I just don't understand enough.

And, my wonderful Comcrap internet isn't working so I can't give y'all a rundown on what I've done so far so we can get ssh working again. Once it's back up, I'll give y'all a command-by-command history on what I did to mess this up worse.

I do want to thank you tux, mythmaster, and the rest who have contributed to help! I always try to make sure I thank those who gave time, knowledge, etc to help me. You guys make this place great.

Please read my last post again, as I said I got NX working, you don't need to do any change of the sshd config or of the freenx config on the HTPC.

To clean the current mess just uninstall all openssh and the freenx packages, clean out any left-over config files in /etc/ssh and .nx/ and .ssh/ in your home directory and then reinstall these packages again.

Then follow the procedure I mentioned in my last post, try it on your Mint laptop first, once it works there then try NX on your macbook (the config might be different there).

Just as a side note, whenever you edit a config file (especially system-wide config files under /etc) it is always prudent to make a backup copy of the original file first (just make a copy ending with -BAK in the same directory) so you can easily restore it if your changes turn out to be bad.

My Linux news / reviews / tips+tricks / downloads web site: http://www.linuxtech.net/
tux99 is offline  
post #45 of 200 Old 05-03-2010, 08:18 PM
 
mythmaster's Avatar
 
Join Date: Mar 2008
Location: 255.255.255.255
Posts: 2,107
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
^^^ THIS

Plus, don't feel bad -- SSH keys are totally confusing. I didn't think that I had to do anything with them last time, but maybe I'm wrong. I used to smoke alot of pot, and I wouldn't even remember my own name if it wasn't printed on my driver's license.

You should be able to follow tux's instructions and get it working, though.

If you can't find where the key goes in the mac, then I think that you can still paste it into the NX client dialog there (per the guide that I posted earlier). You should only have to do that once, and it will be saved.

All of these security measures, while frustrating, are quite important, and you can feel confident that no one can break into your system and transfer CP or threats to the President or steal credit card numbers, etc. and have the finger pointed at you. It really is worth the effort.
mythmaster is offline  
post #46 of 200 Old 05-04-2010, 05:20 AM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
Quote:
Originally Posted by tux99 View Post

To clean the current mess just uninstall all openssh and the freenx packages, clean out any left-over config files in /etc/ssh and .nx/ and .ssh/ in your home directory and then reinstall these packages again.

That's all I have to do to clean this up? SWEET! I can do that! I haven't had a chance to try what you instructed previously but I will and wanted to, but then I discovered I messed up SSH. I will do this tonight (hopefully). Thanks!

Quote:
Originally Posted by mythmaster View Post

^^^ THIS

Plus, don't feel bad -- SSH keys are totally confusing. I didn't think that I had to do anything with them last time, but maybe I'm wrong. I used to smoke alot of pot, and I wouldn't even remember my own name if it wasn't printed on my driver's license.

You should be able to follow tux's instructions and get it working, though.

If you can't find where the key goes in the mac, then I think that you can still paste it into the NX client dialog there (per the guide that I posted earlier). You should only have to do that once, and it will be saved.

All of these security measures, while frustrating, are quite important, and you can feel confident that no one can break into your system and transfer CP or threats to the President or steal credit card numbers, etc. and have the finger pointed at you. It really is worth the effort.

Yea, as much as I dislike P-BO, I definitely don't want to threaten him (or have anyone else threaten him on my behalf). O_O
shane2943 is offline  
post #47 of 200 Old 05-04-2010, 05:28 PM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
OMG IT'S WORKING!!!!..........sorta....

I can connect now! But I don't stay connected. I see the desktop of the server for about 5 seconds and then it vanishes and I get this error:


I've googled that error and received inconclusive results. Gonna try the client on the Mint lappy and see if it works there. if so, I'm happy using that one. As long as ONE of the laptops can connect without issue, I'm happy.
shane2943 is offline  
post #48 of 200 Old 05-06-2010, 07:45 AM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
Looks like the client on the Mint laptop is doing the same exact same thing. This might be a server issue. I haven't dug into it too far but according to the messages on the server (/var/log/messages) ssh is just killing the connection for some reason.

Gonna hopefully dig more into it tonight.
shane2943 is offline  
post #49 of 200 Old 05-06-2010, 08:56 AM
AVS Forum Special Member
 
tux99's Avatar
 
Join Date: Jan 2005
Location: Europe
Posts: 1,515
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 11
Quote:
Originally Posted by shane2943 View Post

Looks like the client on the Mint laptop is doing the same exact same thing. This might be a server issue. I haven't dug into it too far but according to the messages on the server (/var/log/messages) ssh is just killing the connection for some reason.

Gonna hopefully dig more into it tonight.

Posting the log messages here would be useful!

My Linux news / reviews / tips+tricks / downloads web site: http://www.linuxtech.net/
tux99 is offline  
post #50 of 200 Old 05-06-2010, 10:25 AM
 
mythmaster's Avatar
 
Join Date: Mar 2008
Location: 255.255.255.255
Posts: 2,107
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by shane2943 View Post

Looks like the client on the Mint laptop is doing the same exact same thing. This might be a server issue. I haven't dug into it too far but according to the messages on the server (/var/log/messages) ssh is just killing the connection for some reason.

Gonna hopefully dig more into it tonight.

I've never had that problem, but check through the log files to see if they indicate why the connection is being shut down. Make sure that logging is enabled in freenx -- there's an option in node.conf:
Quote:


You need to enable logging in /etc/nxserver/node.conf
NX_LOGFILE sets the path to the log file, with default being
/var/log/nxserver.log
NX_LOG_LEVEL sets log level between 0 (default, none) and 7 (max)

I think that SSH logs to /var/log/secure, but check /etc/syslog.conf to be sure.

And, of course, look in /var/log/messages
mythmaster is offline  
post #51 of 200 Old 05-06-2010, 10:44 AM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
Quote:
Originally Posted by tux99 View Post

Posting the log messages here would be useful!

Will do it tonight.

Quote:
Originally Posted by mythmaster View Post

I've never had that problem, but check through the log files to see if they indicate why the connection is being shut down. Make sure that logging is enabled in freenx -- there's an option in node.conf:

I think that SSH logs to /var/log/secure, but check /etc/syslog.conf to be sure.

And, of course, look in /var/log/messages

Thanks! I'll post all that up later tonight.

Thanks, guys for bearing with me (and having patience).
shane2943 is offline  
post #52 of 200 Old 05-06-2010, 03:40 PM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
Ok, I set the log level all the way up to get the most info. FreeNX is currently logging everything. Here is what i get from the server start all the way to when the client trying to connect gets kicked off:
Code:
-- NX SERVER START:  - ORIG_COMMAND=
-- NX SERVER START:  - ORIG_COMMAND=
Info: Using fds #4 and #3 for communication with nxnode.
HELLO NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 105 hello NXCLIENT - Version 3.2.0
NX> 134 Accepted protocol: 3.2.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: shane
NX> 102 Password: 
Info: Auth method: ssh shane@127.0.0.1's password:
NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 716 Slave mode started successfully.
nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
nxnode_reader: NX> 716 finished
nxnode_reader: NX> 1001 Bye.

NX> 103 Welcome to: localhost.localdomain user: shane
NX> 105 listsession --user="shane" --status="suspended,running" --geometry="1280x800x32+render" --type="unix-kde"
NX> 127 Sessions list of user 'shane' for reconnect:

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


NX> 148 Server capacity: not reached for user: shane
NX> 105 startsession  --link="lan" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="HTPC" --type="unix-kde" --geometry="1024x768+128+0" --client="macosx" --keyboard="query" --screeninfo="1024x768x32+render" 

&link=lan&backingstore=1&encryption=1&cache=16M&images=64M&shmem=1&shpix=1&strict=0&composite=1&media=0&session=HTPC&type=unix-kde&geometry=1024x768+128+0&client=macosx&keyboard=query&screeninfo=1024x768x32+render&clientproto=3.2.0&user=shane&userip=10.10.69.208&uniqueid=B58E9A28157CA99822984DD6B714E778&display=1002&host=127.0.0.1 
nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
server_nxnode_echo: NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
nxnode_reader: NX> 700 Session id: localhost.localdomain-1002-B58E9A28157CA99822984DD6B714E778
nxnode_reader: NX> 705 Session display: 1002
nxnode_reader: NX> 703 Session type: unix-kde
nxnode_reader: NX> 701 Proxy cookie: 001120c3b743e6c4ce3243f411671ceb
nxnode_reader: NX> 702 Proxy IP: 127.0.0.1
nxnode_reader: NX> 706 Agent cookie: 001120c3b743e6c4ce3243f411671ceb
nxnode_reader: NX> 704 Session cache: unix-kde
nxnode_reader: NX> 707 SSL tunneling: 1
NX> 700 Session id: localhost.localdomain-1002-B58E9A28157CA99822984DD6B714E778
NX> 705 Session display: 1002
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 001120c3b743e6c4ce3243f411671ceb
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 001120c3b743e6c4ce3243f411671ceb
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 1
server_nxnode_echo: NX> 700 Session id: localhost.localdomain-1002-B58E9A28157CA99822984DD6B714E778
server_nxnode_echo: NX> 705 Session display: 1002
server_nxnode_echo: NX> 703 Session type: unix-kde
server_nxnode_echo: NX> 701 Proxy cookie: 001120c3b743e6c4ce3243f411671ceb
server_nxnode_echo: NX> 702 Proxy IP: 127.0.0.1
server_nxnode_echo: NX> 706 Agent cookie: 001120c3b743e6c4ce3243f411671ceb
server_nxnode_echo: NX> 704 Session cache: unix-kde
server_nxnode_echo: NX> 707 SSL tunneling: 1
nxnode_reader: NX> 1009 Session status: starting
NX> 1009 Session status: starting
server_nxnode_echo: NX> 1009 Session status: starting
nxnode_reader: NX> 710 Session status: running
nxnode_reader: NX> 1002 Commit
nxnode_reader: NX> 1006 Session status: running
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 B58E9A28157CA99822984DD6B714E778 Running
NX> 105 server_nxnode_echo: NX> 1006 Session status: running
bye
Bye
NX> 999 Bye
Info: Closing connection to slave with pid 5492.
nxnode_reader: 1001 Bye.
1001 Bye.
nxnode_reader: NX> 1001 Bye.
NX> 1001 Bye.
server_nxnode_echo: NX> 1001 Bye.
Info: Closing connection to slave with pid 5492.
[root@localhost shane]#
Here is a segment of the system messages I fond interesting:
Code:
May  6 17:10:02 localhost sshd[16958]: Accepted publickey for nx from 10.10.69.208 port 50285 ssh2
May  6 17:10:04 localhost sshd[17109]: Accepted password for shane from 127.0.0.1 port 36542 ssh2
May  6 17:10:26 localhost klogd: nxagent[17605]: segfault at 10 ip 08072564 sp bfdff900 error 4 in nxagent[8048000+49d000]
May  6 17:10:26 localhost sshd[17111]: Received disconnect from 127.0.0.1: 11: disconnected by user
The nxagent segment fault appears 3 times in the syslog:
Code:
May  6 17:10:26 localhost klogd: nxagent[17605]: segfault at 10 ip 08072564 sp bfdff900 error 4 in nxagent[8048000+49d000]
May  6 17:13:59 localhost klogd: nxagent[26286]: segfault at 10 ip 08072564 sp bfd9af30 error 4 in nxagent[8048000+49d000]
May  6 17:19:28 localhost klogd: nxagent[6003]: segfault at 10 ip 08072564 sp bfddba50 error 4 in nxagent[8048000+49d000]
So it looks as though something with nxagent is causing it.

I googled the error and found this:
https://qa.mandriva.com/show_bug.cgi?id=54074

Doesn't look like any solutions have been found. I likely need to remove freenx and install NX Free (as in beer....whatever that means). Gonna try that tonight. Hopefully I can figure it out!
shane2943 is offline  
post #53 of 200 Old 05-06-2010, 04:04 PM
 
mythmaster's Avatar
 
Join Date: Mar 2008
Location: 255.255.255.255
Posts: 2,107
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by shane2943 View Post

I likely need to remove freenx and install NX

Yeah, if it's segfaulting then something is definitely wrong. Did you install it from the package manager or did you download it? (Well, I don't see a Mandriva-specific download on the freenx download page).

Assuming that you and tux are running the same version, I don't know what could be causing yours to segfault. If the NX version crashes, too, then we have some serious troubleshooting to do.

EDIT: You are apparently not alone: http://www.linuxquestions.org/questi...08-1-a-665380/

EDIT2: Also, http://lists.mandriva.com/bugs/2010-03/msg03511.php
mythmaster is offline  
post #54 of 200 Old 05-06-2010, 04:04 PM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
Crud. It appears NXserver won't install properly because user 'nx' is already on the system. I installed it using urpmi but some of the files are missing and I can't start the server:
Code:
[root@localhost setup]# nxserver --restart
NX> 595 ERROR: Initialization failed: Can't open file: /usr/NX/etc/server.cfg.
NX> 595 ERROR: No such file or directory. Please try to fix the problem by
NX> 595 ERROR: running /usr/NX/scripts/setup/nxserver --install.
[root@localhost setup]#
and when I try to run the install command:
Code:
[root@localhost setup]# nxserver --install
NX> 704 ERROR: Cannot add user: nx.
NX> 704 ERROR: User: nx already exists.
NX> 704 To fix the problem, you may try to completely uninstall NX
NX> 704 Server and install it from scratch. If this is not enough,
NX> 704 please delete the nx user by using the system commands and
NX> 704 proceed with a new installation of NX Server.
[root@localhost setup]#
How can I get Mandriva setup so I can clean install NX? Removing user 'nx' and all that.
shane2943 is offline  
post #55 of 200 Old 05-06-2010, 04:25 PM
 
mythmaster's Avatar
 
Join Date: Mar 2008
Location: 255.255.255.255
Posts: 2,107
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
In case you didn't, read the edits in my previous post.

Anyway, try this (it's for Ubuntu but should work similarly in Mandriva)
mythmaster is offline  
post #56 of 200 Old 05-07-2010, 01:50 AM
AVS Forum Special Member
 
tux99's Avatar
 
Join Date: Jan 2005
Location: Europe
Posts: 1,515
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 11
Shane when you (re-)install the freenx package on Mandriva, you don't need to do anything else, do not run 'nxserver --install', since that's all taken care of during package installation (including startup scripts so that it starts at boot).

I would suggest you do the following as root in a terminal to reinstall everything cleanly:

uninstall all freenx packages:
rpm -e nxproxy freenx nxagent libnxX11_0

check if any nomachine.com packages are still on your box:
rpm -qa|grep -e nxserver -e nxnode -e nxclient

remove those too if found:
rpm -e nxserver nxnode nxclient

remove nx user:
userdel nx

delete directory:
rm -rf /var/lib/nxserver

delete nx config in your user dir:
rm -rf /home/shane/.nx

reinstall freenx:
urpmi freenx

then copy the key from your HTPC (/var/lib/nxserver/nxhome/.ssh/client.id_dsa.key) to your client (Mint laptop or macbook) as previously described (see post #42). This is needed again since due to reinstallation the key has been regenerated.

After that start your nomachine client and try to connect to your HTPC, it should work fine (at least it does here for me with my Mandriva 2010.0 HTPC). I just tested this reinstall procedure on my HTPC and it worked fine.

If you still have disconnect problems, try to disable the firewall completely to see if the problem is caused by the firewall (in MCC > "Security" > "Set up your personal firewall" select "Everything (no firewall)" then click "OK").
I don't have the firewall active on my HTPC since I consider it a useless nuisance on a Linux HTPC with no local data and on a private LAN, so that could be the difference between our systems why it works for me and not for you.


Edit to add:
I just thought something else that could be the cause of your problems. Did you originally install the nxserver from nomachine.com? Maybe that package (or config files from it) are still on your HTPC messing up the Mandriva freenx install?
I have added two more steps to check and remove them to the procedure above (I hope you installed them as rpm not as tar ball!)

My Linux news / reviews / tips+tricks / downloads web site: http://www.linuxtech.net/
tux99 is offline  
post #57 of 200 Old 05-07-2010, 11:12 AM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
Quote:
Originally Posted by mythmaster View Post

In case you didn't, read the edits in my previous post.

Anyway, try this (it's for Ubuntu but should work similarly in Mandriva)

I think I posted at the same time as you so I missed you last post. I went back a reread it. Good info! Thanks, myth. As always.

Quote:
Originally Posted by tux99 View Post

Shane when you (re-)install the freenx package on Mandriva, you don't need to do anything else, do not run 'nxserver --install', since that's all taken care of during package installation (including startup scripts so that it starts at boot).

I would suggest you do the following as root in a terminal to reinstall everything cleanly:

uninstall all freenx packages:
rpm -e nxproxy freenx nxagent libnxX11_0

check if any nomachine.com packages are still on your box:
rpm -qa|grep -e nxserver -e nxnode -e nxclient

remove those too if found:
rpm -e nxserver nxnode nxclient

remove nx user:
userdel nx

delete directory:
rm -rf /var/lib/nxserver

delete nx config in your user dir:
rm -rf /home/shane/.nx

reinstall freenx:
urpmi freenx

then copy the key from your HTPC (/var/lib/nxserver/nxhome/.ssh/client.id_dsa.key) to your client (Mint laptop or macbook) as previously described (see post #42). This is needed again since due to reinstallation the key has been regenerated.

After that start your nomachine client and try to connect to your HTPC, it should work fine (at least it does here for me with my Mandriva 2010.0 HTPC). I just tested this reinstall procedure on my HTPC and it worked fine.

If you still have disconnect problems, try to disable the firewall completely to see if the problem is caused by the firewall (in MCC > "Security" > "Set up your personal firewall" select "Everything (no firewall)" then click "OK").
I don't have the firewall active on my HTPC since I consider it a useless nuisance on a Linux HTPC with no local data and on a private LAN, so that could be the difference between our systems why it works for me and not for you.


Edit to add:
I just thought something else that could be the cause of your problems. Did you originally install the nxserver from nomachine.com? Maybe that package (or config files from it) are still on your HTPC messing up the Mandriva freenx install?
I have added two more steps to check and remove them to the procedure above (I hope you installed them as rpm not as tar ball!)

I will try to reinstall freeNX later using the instructions you have posted. I have installed everything so far using rpms. That includes the NX Free and freeNX packages. I will post my results. Thanks, Tux!
shane2943 is offline  
post #58 of 200 Old 05-07-2010, 06:28 PM - Thread Starter
Advanced Member
 
shane2943's Avatar
 
Join Date: Mar 2009
Posts: 775
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 10
Ok, I did the procedures exactly as you posted them, Tux and the same problem still occurring with nxagent segfaulting and killing the display.

I think maybe my only option at this point is to install NX from nomachine. I will wait for y'alls advice before I go further.

shane2943 is offline  
post #59 of 200 Old 05-07-2010, 06:48 PM
 
mythmaster's Avatar
 
Join Date: Mar 2008
Location: 255.255.255.255
Posts: 2,107
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by shane2943 View Post

Ok, I did the procedures exactly as you posted them, Tux and the same problem still occurring with nxagent segfaulting and killing the display.

I think maybe my only option at this point is to install NX from nomachine. I will wait for y'alls advice before I go further.


It's worth a shot

TBH though I don't know why it segfaults for you and not tux. Maybe something hardware-related. If NX segfaults too you may be SOL. But we'll see if we can pinpoint what's going on.
mythmaster is offline  
post #60 of 200 Old 05-08-2010, 01:39 AM
AVS Forum Special Member
 
tux99's Avatar
 
Join Date: Jan 2005
Location: Europe
Posts: 1,515
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 11
Quote:
Originally Posted by shane2943 View Post

Ok, I did the procedures exactly as you posted them, Tux and the same problem still occurring with nxagent segfaulting and killing the display.

Hmmm, it looks like you are maybe hitting that same bug that mythmaster linked to earlier. What you could try is see if it depends on some specific setting of your user, since in the bug report they mention it works as a different user:
https://qa.mandriva.com/show_bug.cgi?id=54074#c1

Try create a new user (as root run the following):

useradd testuser

passwd testuser
(enter a password for the new user twice when prompted)

Then try to connect as this new user instead of 'shane'.

Please also post the output of the following command:
cat /etc/sysconfig/compositing-*

Quote:
Originally Posted by shane2943 View Post

I think maybe my only option at this point is to install NX from nomachine. I will wait for y'alls advice before I go further.


If you have the same problem as reported by other users in the bugreport and in the linuxquestions.org thread linked by mythmaster then installing NX from nomachine will most likely not help since they mention they have it with nomachine's NX too. It rather appears to be related to some desktop config setting, so if it works for you with the testuser then it should just be a matter to find out what KDE settings you changed as shane user, and try changing them back to default one by one until you find the one that makes NX crash.

My Linux news / reviews / tips+tricks / downloads web site: http://www.linuxtech.net/
tux99 is offline  
Sponsored Links
Advertisement
 
Reply HTPC - Linux Chat

Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off