config sanity checker detected
I had working FreeNX 0.6.0 server from http://
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Shelby Cain
- Solved:
- Last query:
- Last reply:
Related bugs
Related FAQ:
None Link to a FAQ
Revision history for this message
![]() |
#2 |
In Ubuntu 7.04 I installed FreeNX like this:
1. Add repo in /etc/apt/
deb http://
deb-src http://
2. Add key: wget http://
3. sudo apt-get update
4. sudo aptitude install freenx
Done. It has work!
I have upgrade to 7.10. freenx process works, but I can`t connect to remote desktop.
Revision history for this message
![]() |
#3 |
In NX-client after stage "Established a display connection" I have an error.
Revision history for this message
![]() |
#4 |
I have this error message in client (when press "Details" in login window):
Info: Display running with pid '1676' and handler '0x50610'.
NXPROXY - Version 3.0.0
Copyright (C) 2001, 2007 NoMachine.
See http://
Info: Proxy running in client mode with pid '3728'.
Session: Starting session at 'Sun Oct 21 01:25:26 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/
Info: Using image cache parameters 1/1/65536KB.
Info: Using pack method '16m-rle-9' with session 'unix-gnome'.
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'.
Info: Forwarding multimedia connections to port '6000'.
Session: Session started at 'Sun Oct 21 01:25:26 2007'.
Info: Established X server connection.
Info: Using shared memory parameters 1/2048K.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.
Session: Session terminated at 'Sun Oct 21 01:25:29 2007'.
Revision history for this message
![]() |
#5 |
I had the exact problem. I just removed freenx and installed the free nxserver from NoMachine (yes, they have a free version now). Just download from http://
Revision history for this message
![]() |
#6 |
Simon, unfortunately free version of NX accepts only 2 users.
And I can`t run it correctly on upgraded system (NX server works only on clean Gutsy install but not on upgraded from Feisty to Gutsy)
Revision history for this message
![]() |
#7 |
Having the same issue on a Feisty upgraded to Gutsy:
Error: Connection with remote peer broken.
Revision history for this message
![]() |
#8 |
me too the same problem. I works in feisty after clean install gusty i can not connect to freenx server. is there any workaround? or a deb for the new freenx 0.7.1?
Revision history for this message
![]() |
#9 |
I tried to recompile it from the "source package" on the site:
Source (.dsc) nx_2.1.
Source (.tar.gz) nx_2.1.
Source (.diff.gz) nx_2.1.
and have the same problem - it doesn't work. The display with !M appeares and disappers in a moment. Here's what I have in nxclient log:
Info: Display running with pid '2992' and handler '0x4607f8'.
NXPROXY - Version 3.0.0
Copyright (C) 2001, 2007 NoMachine.
See http://
Info: Proxy running in client mode with pid '752'.
Session: Starting session at 'Wed Oct 24 14:23:16 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/
Info: Using image cache parameters 1/1/65536KB.
Info: Using pack method '16m-rle-9' with session 'unix-gnome'.
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'.
Session: Session started at 'Wed Oct 24 14:23:16 2007'.
Info: Established X server connection.
Info: Using shared memory parameters 1/2048K.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.
Session: Session terminated at 'Wed Oct 24 14:23:18 2007'.
Revision history for this message
![]() |
#10 |
I tried to recompile it from the "source package" on the site:
Source (.dsc) nx_2.1.
Source (.tar.gz) nx_2.1.
Source (.diff.gz) nx_2.1.
and have the same problem - it doesn't work. The display with !M appeares and disappers in a moment. Here's what I have in nxclient log:
Info: Display running with pid '2992' and handler '0x4607f8'.
NXPROXY - Version 3.0.0
Copyright (C) 2001, 2007 NoMachine.
See http://
Info: Proxy running in client mode with pid '752'.
Session: Starting session at 'Wed Oct 24 14:23:16 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/
Info: Using image cache parameters 1/1/65536KB.
Info: Using pack method '16m-rle-9' with session 'unix-gnome'.
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'.
Session: Session started at 'Wed Oct 24 14:23:16 2007'.
Info: Established X server connection.
Info: Using shared memory parameters 1/2048K.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.
Session: Session terminated at 'Wed Oct 24 14:23:18 2007'.
Revision history for this message
![]() |
#11 |
What about this:
https:/
Revision history for this message
![]() |
#12 |
> What about this:
> https:/
It works in Feisty, but not in Gutsy.
And there are no FreeNX repos for Gutsy.
Revision history for this message
![]() |
#13 |
Did you try changing feisty to gutsy in the repos ?
The wiki is not yet updated to gutsy.
Revision history for this message
![]() |
#14 |
FreeNX repos is not yet updated to gutsy to.
I tried clean install from Feisty repos — FreeNX didn`t work.
Revision history for this message
![]() |
#15 |
Seveas repos is still for feisty not for gutsy i have tried to force it install it in gusty but client can not connect. any workaround????
Revision history for this message
![]() |
#16 |
The free version of NX Server from NoMachine works fine on Gutsy system that is an upgraded Feisty.
We just use it for accessing our work machines from home, so the 2 user limit is not a problem.
Revision history for this message
![]() |
#17 |
Derek Buckley, did you have installed FreeNX on 7.04 before upgrade?
Revision history for this message
![]() |
#18 |
I did the following to get freenx working under Gutsy:
1) The nxsetup attempts to sanity check your config via nxloadconfig which fails because library names have changed:
Edit /usr/lib/
[ -z "$APPLICATION_
2) The font path in gutsy has changed so freenx can't find your install X fonts.
Edit /etc/nxserver/ and add (this is all one line with a space after "-fp"):
AGENT_EXTRA_
This gets freenx working well enough for me under Gutsy. However, this IS NOT a proper replacement for a working gutsy package. If you want to see one you need to politely ask the maintainers to create a proper package and update their gutsy repositories.
Revision history for this message
![]() |
#19 |
Thanks alyandon, that solved my question.
Revision history for this message
![]() |
#20 |
In my post above, in step #2, "Edit "/etc/nxserver"" should be "Edit "/etc/nxserver/
Revision history for this message
![]() |
#21 |
alyandon: I did the following to get freenx working under Gutsy:
1) The nxsetup attempts to sanity check your config via nxloadconfig which fails because library names have changed:
Edit /usr/lib/
[ -z "$APPLICATION_
2) The font path in gutsy has changed so freenx can't find your install X fonts.
Edit /etc/nxserver/ and add (this is all one line with a space after "-fp"):
AGENT_EXTRA_
This gets freenx working well enough for me under Gutsy. However, this IS NOT a proper replacement for a working gutsy package. If you want to see one you need to politely ask the maintainers to create a proper package and update their gutsy repositories.
=======
Still got errors after following this help. However, I finally find it out.
There's one space in "$A PPLICATION_
Thank you very much for your very useful help. ^^ .
Love Ubuntu and FreeNX ^^
Revision history for this message
![]() |
#22 |
Yeah, that's definitely some sort of copy/paste issue. Sorry about that.
Revision history for this message
![]() |
#23 |
alyandon, you are a gentleman and a scholar! I was so not looking forward to debugging that. Thanks for doing it for me. :-)
Revision history for this message
![]() |
#24 |
Hello anyone had this error:
----> Testing your nxserver configuration ...
Warning: Could not find nxdesktop in /usr/lib/nx. RDP sessions won't work.
Warning: Could not find nxviewer in /usr/lib/nx. VNC sessions won't work.
Warning: Invalid value "COMMAND_
Users will not be able to request a KDE session.
Warning: Invalid value "COMMAND_
Users will not be able to request a Gnome session.
Warning: Invalid value "COMMAND_
Users will not be able to request a CDE session.
Warning: Invalid value "COMMAND_
Warning: Invalid value "COMMAND_
Warnings occured during config check.
To enable these features please correct the configuration file.
<---- done
I had to change some libraries to libraryname.2 because I had them in second version.
I can't connect to server. I can login but after login nxwindow shows for 1 second and dissapers. I thinks it's beacuse of this:
Warning: Invalid value "COMMAND_
Users will not be able to request a Gnome session.
Log from nxsetup
$> sudo nxsetup
------> You did select no action.
FreeNX guesses that you want to _install_ the server.
Type "y" to abort the installation at this point in time.
"N" is the default and continues installation.
Use "/usr/sbin/nxsetup --help" to get more detailed help hints.
Do you want to abort now? [y/N]
------> It is recommended that you use the NoMachine key for
easier setup. If you answer "y", FreeNX creates a custom
KeyPair and expects you to setup your clients manually.
"N" is default and uses the NoMachine key for installation.
Do you want to use your own custom KeyPair? [y/N]
Setting up /etc/nxserver ...done
Setting up /var/lib/
Setting up /var/log/
Setting up known_hosts and authorized_keys2 ...done
Setting up permissions ...done
----> Testing your nxserver configuration ...
Warning: Could not find nxdesktop in /usr/lib/nx. RDP sessions won't work.
Warning: Could not find nxviewer in /usr/lib/nx. VNC sessions won't work.
Warning: Invalid value "COMMAND_
Users will not be able to request a KDE session.
Warning: Invalid value "COMMAND_
Users will not be able to request a Gnome session.
Warning: Invalid value "COMMAND_
Users will not be able to request a CDE session.
Warning: Invalid value "COMMAND_
Warning: Invalid value "COMMAND_
Warnings occured during config check.
To enable these features please correct the configuration file.
<---- done
----> Testing your nxserver connection ...
HELLO NXSERVER - Version 1.5.0-60 OS (GPL)
NX> 105 quit
Quit
NX> 999 Bye
<--- done
Ok, nxserver is ready.
PAM authentication enabled:
All users will be able to login with their normal passwords.
PAM authentication will be done through SSH.
Please ensure that SSHD on localhost accepts password authentication.
You can change this behaviour in the /etc/nxserver/
Have Fun!
Revision history for this message
![]() |
#25 |
I can't edit my message so I write here:
Maybe it's problem because I use nxclient 3.0.0 with nxserver 2.1.0 log from error files in .nx dir:
Loop: WARNING! Connected to remote NXPROXY version 3.0.0 with local version 2.1.0.
Proxy: WARNING! Handling data for finishing FD#6 channel ID#1.
Proxy: WARNING! Handling data for finishing FD#6 channel ID#1.
and log from session:
NXAGENT - Version 2.1.0
Copyright (C) 2001, 2006 NoMachine.
See http://
Info: Agent running with pid '11018'.
Session: Starting session at 'Mon Nov 5 21:52:57 2007'.
Info: Proxy running in server mode with pid '11018'.
Info: Waiting for connection from '127.0.0.1' on port '5000'.
Info: Accepted connection from '127.0.0.1' with port '60116'.
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://
Info: Synchronizing local and remote caches.
Info: Handshaking with remote proxy completed.
Info: Using wan link parameters 768/24/1/0.
Info: Using agent parameters 5000/50/0/0.
Info: Using cache parameters 4/4194304/
Info: Using image streaming parameters 50/128/
Info: Using image cache parameters 1/1/65536KB.
Info: Using pack method '16m-jpeg-9' with session 'unix-gnome'.
Info: Using ZLIB data compression 1/1/32.
Info: Not using ZLIB stream compression.
Info: Using cache file '/home/
Info: Established X client connection.
Info: Using shared memory parameters 1/1/1/4096K.
Info: Detected window manager running.
Info: Not using local device configuration changes.
Info: Using alpha channel in render extension.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
nxagentRedirect
Session: Session started at 'Mon Nov 5 21:52:58 2007'.
AUDIT: Mon Nov 5 21:52:58 2007: 11018 nxagent: client 1 rejected from local host
AUDIT: Mon Nov 5 21:52:58 2007: 11018 nxagent: client 2 rejected from local host
Session: Terminating session at 'Mon Nov 5 21:52:58 2007'.
Info: End of NX transport requested by agent.
Info: Watchdog running with pid '11038'.
Info: Waiting the watchdog process to complete.
Info: Shutting down the NX transport.
Session: Session terminated at 'Mon Nov 5 21:53:08 2007'.
Revision history for this message
![]() |
#26 |
IIRC, you have to use the NX 1.5 or 2.x client when connecting to a freenx server.
Revision history for this message
![]() |
#27 |
FWIW - I did the font fix (*only*), and that was sufficient to get me back on the air.
Conditions:
Fiesty upgraded to gutsy
FreeNX fiesty repository enabled.
FreeNX removed, then replaced via synaptic.
/etc/nxserver/
Whalla - it worked (for me...)
Revision history for this message
![]() |
#28 |
Hi,
I've got same problem : "Connection with remote peer broken.".
After that I tried to figure out reading your conversations and found a solution (for me):
my configuration:
Updated from 6.10 to 7.10 Gutsy Ubuntu.
Free NXServer and NxClient instead of FreeNX.
I only commented the line of AGENT_EXTRA_OPTIONS = "-fp /usr/share/
It worked.
Regards,
Revision history for this message
![]() |
#29 |
I solved the font-problem after my upgrade from Feisty to Gutsy with following commands:
cd /usr/share/X11
sudo ln -s ../fonts/X11 fonts
It's just another way of solving the same problem.