[X2go-dev] install : at least 4 mistakes in pdf de.insstallation.x2go.pdf and a install script

[Paul van der Vlis]

kamerun at immerda.ch schreef:
> hello,

Hello Michael,

> at least and after many test, we are able to install x2go
>
> installation date monday 3.8.2009
>
> installation on machine with debian 5 and lxde (ths same result with a
> debian 5 machine with gnome)
> 
> we have done the installtion many times on different machines with the
> same bad result
> 
> we can start client and everything is ok

You tell you can start the client and everything is OK.
Do you mean that you use a client booting via PXE, like in LTSP ?

It would be nice to know what manual you use. Is this this German
manual?  http://www.x2go.org/fileadmin/doc/de.installation.x2go.pdf

> after the installation, when reboot,
> *big problem:*
> 
> when booting stop in statd (NFS) and follow after ~ 1 minutes
> after stop y postgres : long message CEST FATAL could not create any
> TCP/IP sokets
> after more than 1 minute continue
> stop again by statd wait long and finish until login

Looks-like there is something wrong with NFS. Maybe give us your
/etc/exports file. With this file you configure NFS.

This is in my /etc/exports (except for some commented lines):
/opt/x2gothinclient 192.168.0.0/24(ro,async,no_root_squash)

> after login
> nfs does not work
> atftp is running
> dhcp is running but the file /etc/default/dhcp3-server is overwritten

What is in it?  I have this:
INTERFACES="eth0"

> nfs cannot start, postgres has mistakes and it takes very long time to boot
> it comes to login and we can login, but no postgres and nfs is running.
> i try to start nfs
> but it fails, so logically the client cannot start
> 
> and the machine by shutdown the machine don't shutdown properly
> 
> we try to start nfs and posstgres manually, but it fails: no socket
> 
> 
> i wonder if somebody else has the same situation

No. I have also problems, but they are completely different. starting
the machine, NFS en Postgresql is no problem. And the client bootes, but
I get an error in the boot-process.

> *installation:
> *
> from my humble opinion there are at least 4 mistakes in the pdf
> de.installation.x2go.pdf

Ah. OK.

> #echo "192.168.1.1 x2goserver.planetexpress.de x2goserver" >>/opt/
> x2gothinclient/etc/hosts

I have also seen that the manual uses sometime 192.168.0.x and sometimes
192.168.1.x. And that is wrong in my opinion.

> -- 
> 
> label linux
> kernel vmlinuz
> append root=/dev/nfs nfsroot=192.168.1.1:/opt/x2gothinclient ro
> initrd=initrd.img ip=dhcp
> 
> -- 
> 
> option domain-name "planetexpress.de";
> option domain-name-servers 192.168.1.1;
> # x2go thin client range/group
> subnet 192.168.0.0 netmask 255.255.255.0 {
> range 192.168.0.100 192.168.0.199;
> filename "/pxelinux.0";
> next-server 192.168.0.250;
> }

This is wrong because you use both 192.168.0.x and 192.168.1.x.
Use all the time the same network.

> when i put the dhcp-server on 192.168.0..250 and change the ip
> 192.168.1.1 to 192.168.0.250, it works. it is for me a mistake first not
> to say on which ip address the dhcp server must be set, that it works
> the description of de.installation.x2go.pdf. anyway with the 192.168.1.1
> i could not install an x2go.

I think the manual has been made for people who know a lot about
networking. It describes the installation of X2go, but not good the
network-configuration.

> there is another mistake :
> 
> # cd /usr/lib/X2go/scrip
> # ./x2gocreatebase.sh
> 
> X2go directory does not exist, it exist x2go directory

Correct.

> (i don't know, but i was thinking that before it was existing)
> 
> 
> question: when i want to close a client, it comes back to login it can
> just switch off, is it normal?

This is normal.

> a good news is that lxde is working well, i prefer the light lxde than kde.
> thanks

I am using Gnome, but I understand that you like the light LXDE.

I will advice you to get first X2go working without the PXE boot client.
You can also install a client on a normal PC.
Does this work?
Please don't use LDAP for the first tests.
You can even install the client and the server on the same machine, and
then connect to localhost. This is what I do for testing.

With regards,
Paul van der Vlis.




-- 
http://www.vandervlis.nl/