x2go-user

x2go-user@lists.x2go.org

3 participants
2322 discussions

HOWTO - install ubuntu & x2goserver inside inside LXC containers
by brian mullan 29 Aug '12

29 Aug '12

The following is a description of how to install Ubuntu & x2go server inside Linux Containers (LXC). All of the following was done on an Ubuntu 12.04 server installed inside LXC containers. These examples are only for a single container but you can either Clone the first container you create and make necessary changes regarding IP addresses (they will be different for each LXC container) or start from scratch and create each manually. If you are not familiar with LXC containers it is a very lightweight & therefore very fast (faster than vmware, kvm, xen etc) technology built into most modern Linux kernels and distributions from Ubuntu, Debian, Fedora etc. Note that LXC does not support installing windows into an LXC container. LXC allows you to provide complete isolation of one container from another by default. However, you can as an admin provide more or less isolation between containers and also between containers and the HOST computer OS. I will NOT go into how LXC works here as there is a lot of information on the web which can help you understand more if you do a google search for "lxc containers" or read some of the "references" I've put at the end of this email. Ubuntu 12.04 has made LXC very easy to use. Canonical has simplified many things to the extreme. Other linux distributions may/will differ on how you create, access etc LXC containers. But lets begin creating our first LXC container and then we will install Bonitasoft inside that container. *STEP 1* Assuming you are using Ubuntu 12.04 Desktop we will install LXC first the create our first container which we will call x2goserver1-lxc. In the following we are going to use an “ubuntu” lxc template. There are other “lxc templates” for debian, fedora, centos etc that you could use if you wanted to install one of those OS inside an LXC Container even if the host is Ubuntu NOTE: you can install any Linux OS into an LXC container the only major rule is that the Linux must use the same Kernel as the Host linux. * sudo apt-get install lxc* Next create the LXC container we are calling x2goserver1-lxc then start up that container: * * * sudo lxc-create -t ubuntu -n x2goserver1-lxc* * sudo lxc-start -n x2goserver1-lxc* The “create” command above will create a new container called "x2goserver1-lxc" and install ubuntu ... using the same version of Ubuntu as your host computer so it will install ubuntu 12.04 inside the LXC container named "x2goserver1-lxc" This will take some time as it downloads all the required files from the Ubuntu repositories and installs them to create a bootable Ubuntu 12.04 system. The “start” command above will actually start the LXC container called "x2goserver1-lxc" and its Ubuntu system and leave you at a terminal command prompt inside the LXC container. *Note:* that the command prompt will be different from a terminal on your HOST computer as you will now be *inside* the container and because we haven't added any additional user accounts yet the login USERID will be the default which is "ubuntu". The command prompt should look something like the following: *ubuntu@x2goserver1-lxc:~$* Create a User Accounts for the users that will be using this container: *sudo adduser user-name1* * etc.* *STEP 2* While logged into the container and at the terminal prompt install whatever other tools you usually use. In my case, because I wanted to see if x2go would work so I installed the ubuntu desktop and the x2go server components. Install the Ubuntu Desktop: *sudo apt-get install ubuntu-desktop* when this completes reboot Ubuntu in the LXC container: *sudo shutdown -r now* this will reboot ubuntu in the container so the desktop environment will be available. Login again and continue. Next install the x2go "server" side applications so I can later access the container using the x2goclient on my HOST PC. Next add the x2go repository: * sudo add-apt-repository ppa:x2go/stable* * sudo apt-get update* Install the x2go "server" side components: * sudo apt-get install x2goserver sudo apt-get install x2goserver-session* On your HOST computer install the x2go client: * sudo add-apt-repository ppa:x2go/stable sudo apt-get update sudo apt-get install x2goclient* *STEP 3* This step is important if you want to be able to access the LXC container from the host using SSH or whatever other tools you use. The genesis of this step is from Stephane Graber who has taught me alot about LXC from his blog. This step is: 1. performed outside of your linux container and must be done for the USER that will be accessing the x2goserver1-lxc. 2. will require that you know the container IP address. Each LXC container will have a different IP address even though they are all running on the same PC 3. is necessary to allow someone on the HOST computer to access a container using the container's name with something like SSH etc. for example in our case "ssh userID-on-x2goserver1@x2goserver1-lxc" will log the user-of-bos1-name into the container and leave them at a terminal prompt *Add the following to each users ~/.ssh/config file. Note you may have to create ~/.ssh/config if it doesn't yet exist and change the lxc-container IP address to the container that each user is assigned to work with.** * note: each of the following should be a single line entry Host *.lxc StrictHostKeyChecking no UserKnownHostsFile /dev/null ProxyCommand nc $(host $(echo %h | sed "s/\\\\.lxc//g") * my-lxc-container-ip-address* | tail -1 | awk '{print $NF}') %p Host *.libvirt StrictHostKeyChecking no UserKnownHostsFile /dev/null ProxyCommand nc $(host $(echo %h | sed "s/\\\\.libvirt//g") * my-host-ip-address* | tail -1 | awk '{print $NF}') %p >From now on you can access the x2goserver1-lxc container using either SSH or the x2go client *STEP 4* If you want to use x2go start the x2goclient, then on the HOST create a new x2go "session" and add info about what LXC container IP address you want to connect to, what desktop (unity, gnome etc) and what speed is the connection (change this by moving the slider to LAN since we want the fastest/no compression) and then save. Start the x2goclient session and log into the LXC container. From now on you can do everything as if you were on your HOST PC. Just remember you will be inside the LXC container so you are separated from your host and changes made will only be to the LXC container's Ubuntu. *PARTING THOUGHTS* The reason for doing all of this? Well there are several I can think of but I’ll just name a couple: 1. Linux is now available on ARM. ARM cpu’s don’t support h/w virtualization solutions like vmware, kvm, xen etc. but since LXC does NOT require h/w virtualization you can use LXC containers to provide different and isolated compute environments even on ARM computers. 2. LXC is much faster than vmware, kvm, xen because there is no h/w virtualization and because its part of the linux kernel each container can have as much or as little direct access to the HOST PC resources as you want to configure (read up about LXC CGROUPS). 3. Whereas Vmware, kvm, xen etc all require at least one dedicated cpu “core” for each virtual machine you can only run so many VMs concurrently on a system.. LXC does not have this restriction so with LXC there are many people running as many as 50-80 LXC containers on a single server although your mileage may vary depending on what each container has installed, how much CPU, memory etc is available. 4. Maybe you’d like to have multiple customers each with an x2goserver but isolated from each other without resorting to the expense of separate servers for each customer? 5. Web Servers often don’t really need dedicated servers or even dedicated Virtual Machines. LXC Containers works great for that purpose. Remember I said that LXC containers can be as isolated from each other and from the HOST as you want. They start totally isolated but we changed that a bit above so you could ssh or x2go into a container by adding the 2 statements to a users ~/.ssh/config file However, you can allow LXC containers to share a HOST file system/directory, or even a something like an SQL server running on the HOST (again read about LXC CGROUPS). I may have forgotten a step or mistyped something here and if so send me a note and I'll double check and make any addition/correction. Have fun... *References:* http://lxc.teegra.net/ http://www.ibm.com/developerworks/linux/library/l-lxc-containers/ http://www.stgraber.org/category/lxc/ Brian Mullan

2 1

X-Server cannot be started
by glpk xypron 25 Aug '12

25 Aug '12

Dear maintainer, when I try to start x2goclient on Windows I get an error message: X-Server lässt sich nicht starten. Bitte überprüfen Sie Ihre Installation. (X-server cannot be started, please, check your installation.) Reinstalling x2goclient did not solve the problem. Starting as administrator does not help either. Please, advice how find the root cause. Best regards Heinrich Schuchardt

2 2

Issue with keyboard layout settings / altGr key
by bigot julien 24 Aug '12

24 Aug '12

Hello, I'm lookings for help for configuring the keyboard layout in X2go sessions. I'm not sure i'm on the good mailing-list for that, please excuse me if i'm not. I'm using X2goserver 3.1.1.3 on a debian machine, and i connect from windows with X2goClient 3.99.2.2, on a lxde desktop session. By default, i'm connected with a french keyboard layout, so it's good, apparently, but the AltGr Key does not work, nor does the "ctrl+alt" combo supposed to behave the same way. It means i can't type letters such as " #, {, |, @ " ... So i tried to switch to us layout keyboard ( not the best solution, but at least, will reduce the need for an AltGr key ) , but i didn't managed to. I tried several way i found on the faq, on the mailing list, etc.. 1) In the session preference, on the client : the parameter keyboard layout / model is ignored, i'm still in french. 2) using setxkbmap in a terminal during the session : it returns an error # setxkbmap us >No protocol specified > Cannot open display ":51.0" 3) Putting "auto" in keyboard type session preference, then from the session, editing ~/.x2go/<session>/keyboard , then call x2gosetkeyboard. The command return no error, but makes no change. Any help on how to get the AltGr key to function properly, or, by default, any help on how to switch to the us keyboard will be greatly appreciated. Thanks in advance, Julien.

2 3

x2go installation: not tftp running
by ngainku chanceline 24 Aug '12

24 Aug '12

we try to install x2go but tftp is not running. the system use rlinetd but in the file /etc/rlinetd.conf no service is configured i use ubuntu 12.04 and install x2go as described in documentation before it was using /etc/inetd.conf is it the mistake and how to start tftp with rlinetd? i wonder is i am aloen with this problem michel

2 1

Re: [X2Go-User] x2go connecting timout with TCE
by Florian Müller 22 Aug '12

22 Aug '12

Hi Mike, this is the configuration of the desktop client: GNU nano 2.2.6 Datei: .x2goclient/sessions [20120813130507857] speed=2 pack=16m-jpeg quality=9 fstunnel=true export= iconvto=UTF-8 iconvfrom=ISO8859-1 useiconv=false fullscreen=false width=800 multidisp=false display=1 height=600 dpi=96 setdpi=false xinerama=false usekbd=true layout=de type=pc105/de sound=true soundsystem=pulse startsoundsystem=true soundtunnel=true defsndport=true sndport=4713 print=true name=Login icon=:icons/128x128/x2gosession.png host=x2go-server user= key= sshport=22 autologin=false krblogin=false rootless=false applications=WWWBROWSER, MAILCLIENT, OFFICE, TERMINAL, "gnome-session --session=gnome-fallback" command="gnome-session --session=gnome-fallback" rdpoptions= rdpserver= xdmcpserver=localhost and this is the configuration of the TCE-Environment(quite the same, because i copied the one of the client like descripted in the x2go-wiki): [20120813130507857] speed=2 pack=16m-jpeg quality=9 fstunnel=true export= iconvto=UTF-8 iconvfrom=ISO8859-1 useiconv=false fullscreen=true width=800 multidisp=false display=1 height=600 dpi=96 setdpi=false xinerama=false usekbd=true layout=de type=pc105/de sound=true soundsystem=pulse startsoundsystem=true soundtunnel=true defsndport=true sndport=4713 print=true name=Login icon=:icons/128x128/x2gosession.png host=x2go-server user= key= sshport=22 autologin=false krblogin=false rootless=true applications=WWWBROWSER, MAILCLIENT, OFFICE, TERMINAL command="gnome-session --session=gnome-fallback" rdpoptions= rdpserver= xdmcpserver=localhost Best Regards Flo

1 0

Re: [X2Go-User] x2go connecting timout with TCE
by christoffer krakou 21 Aug '12

21 Aug '12

On 16-08-2012 13:03, Florian Müller wrote: > Hi Mike, > > i'm sorry. you're right i gave you the packages on our TCE server, not > the pachages of chroot. Here are the right pachages: > > ii pinentry-x2go > 0.7.5.4-0~x2go1+squeeze~main~28~build1 Qt4-based PIN or pass-phrase > entry dialog for x2goclient > ii x2go-keyring > 2012.07.23+squeeze~main~17~build1 GnuPG keys of all X2Go > developers and the X2Go archive > ii x2gocdmanager > 1.0.1.8-0~x2go1+squeeze~main~321~build1 clientside daemon enabling > automatic CD-Rom mounting > ii x2goclient > 3.99.2.2-0~x2go1+squeeze~main~240~build1 X2Go Client application (Qt4) > ii x2gosmartcardrules > 1.0.1.8-0~x2go1+squeeze~main~321~build1 UDEV rules for smartcard readers > ii x2gothinclient > 1.0.1.8-0~x2go1+squeeze~main~321~build1 login daemon starting > x2goclient in displaymanager mode > ii x2gousbmount > 1.0.1.8-0~x2go1+squeeze~main~321~build1 clientside usb mass-storage > device mounting > > > Best Regards > Flo I am having the same problem with a recently installed TCE. The server-side packages are: ii x2goagent 2:3.5.0.14-0~247 X2Go agent ii x2goserver 3.1.1.3-0~571~pr X2Go server daemon scripts ii x2goserver-exten 3.1.1.3-0~571~pr X2Go server daemon scripts (extensions) and the tce packages are: ii pinentry-x2go 0.7.5.4-0~x2go1+squeeze~main~28~build1 Qt4-based PIN or pass-phrase entry dialog for x2goclient ii x2go-keyring 2011.12.07+squeeze~main~12~build1 GnuPG keys of X2go developers ii x2gocdmanager 1.0.1.6-0~x2go2+squeeze~main~306~build1 clientside daemon enabling automatic CD-Rom mounting ii x2goclient 3.99.2.1-0~x2go1+squeeze~main~229~build1 X2Go Client application (Qt4) ii x2gosmartcardrules 1.0.1.6-0~x2go2+squeeze~main~306~build1 UDEV rules for smartcard readers ii x2gothinclient 1.0.1.6-0~x2go2+squeeze~main~306~build1 login daemon starting x2goclient in displaymanager mode ii x2gousbmount 1.0.1.6-0~x2go2+squeeze~main~306~build1 clientside usb mass-storage device mounting If anyone has a solution, me and my customers would be eternally grateful, as we are currently wrestling with the exact same errors. I have a logfile from the server, i will attach it for good measure. Perhaps it will show something. It seems to just stop at the keyboard part Aug 16 12:00:35 ubuntu /usr/bin/x2golistsessions[11868]: x2golistsessions has been called with no option Aug 16 12:00:35 ubuntu /usr/bin/x2gostartagent: x2gostartagent called with options: fullscreen lan 16m-jpeg-9 unix-kde-depth_24 da pc105/da 0 D UNITY Aug 16 12:00:35 ubuntu /usr/bin/x2gostartagent: client announced itself as ,,78.156.108.245'' Aug 16 12:00:35 ubuntu /usr/bin/x2gosessionlimit[11890]: x2gosessionlimit has been called Aug 16 12:00:35 ubuntu /usr/bin/x2golistsessions[11893]: x2golistsessions has been called with options: --all-servers Aug 16 12:00:36 ubuntu /usr/lib/x2go/x2gogetdisplays[11907]: db_getdisplays called, server: ubuntu; return value: Aug 16 12:00:36 ubuntu /usr/lib/x2go/x2gogetports[11917]: db_getports called, server: ubuntu; return value: Aug 16 12:00:36 ubuntu /usr/lib/x2go/x2goinsertsession[11935]: db_insertsession called, session ID: christoffer-50-1345111236_stDUNITY_dp24, server: ubuntu, session ID: christoffer-50-1345111236_stDUNITY_dp24 Aug 16 12:00:37 ubuntu /usr/lib/x2go/x2goinsertport[11947]: db_insertport called, session ID: christoffer-50-1345111236_stDUNITY_dp24, server: ubuntu, SSH port: 30001 Aug 16 12:00:37 ubuntu /usr/lib/x2go/x2goinsertport[11959]: db_insertport called, session ID: christoffer-50-1345111236_stDUNITY_dp24, server: ubuntu, SSH port: 30002 Aug 16 12:00:37 ubuntu /usr/lib/x2go/x2goinsertport[11971]: db_insertport called, session ID: christoffer-50-1345111236_stDUNITY_dp24, server: ubuntu, SSH port: 30003 Aug 16 12:00:38 ubuntu /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Aug 16 12:00:38 ubuntu /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Aug 16 12:00:38 ubuntu /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: christoffer-50-1345111236_stDUNITY_dp24 pre-start Aug 16 12:00:38 ubuntu /usr/bin/x2gostartagent: successfully started X2Go agent session with ID christoffer-50-1345111236_stDUNITY_dp24 Aug 16 12:00:38 ubuntu /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Aug 16 12:00:38 ubuntu /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Aug 16 12:00:38 ubuntu /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: christoffer-50-1345111236_stDUNITY_dp24 post-start Aug 16 12:00:39 ubuntu /usr/lib/x2go/x2gocreatesession[12068]: db_createsession called, session ID: christoffer-50-1345111236_stDUNITY_dp24, cookie: 941b3e6300f822e9bbdf6834e29af749, client: 78.156.108.245, pid: 12021, graphics port: 30001, sound port: 30002, file sharing port: 30003 Aug 16 12:00:39 ubuntu /usr/bin/x2gostartagent: blocking creation of agent's keyboard file /home/christoffer/.x2go/C-christoffer-50-1345111236_stDUNITY_dp24/keyboard as requested by session startup command -- Venlig Hilsen / Best Regards Christoffer Krakou Fleten.net APS

1 0

x2go connecting timout with TCE
by Florian Müller 21 Aug '12

21 Aug '12

At the moment we are buildung up a x2go environment. It should contain TFTP-Boot, LDAP-Auth and Load Balancing. the tftp-boot is working (the login-client appears). But now i have following problem: It's not possible to connect so the server (from the syslinux image, which is booting over tftp). The Details of the login-page say following: Info: Proxy running in client mode with pid '1909' Session: Starting session at '...Date...Time...' Info: Connecting to remote hose 'localhost:31001'. ZeitüberschreitungInfo: Aborting the procedure due to signal '15'. Session: Session terminated at '...Date...Time...' I've found an old discussion of this, but there is no solution documented: http://comments.gmane.org/gmane.linux.terminal-server.x2go.user/539 It's weired because the desktop client is working perfectly. Can anybody help me? Thanks in advance. Best Regards Flo

2 2

x2go thinclient shutdown button crashed
by Mirco Rohloff 21 Aug '12

21 Aug '12

Hello, after the X2go Team integrated the Thinclient Shutdown Button funktion from the "x2gothinshutdown" packet to the normal x2goclient packet we have some problems with this switch. If you use the Thinclient some working hours you can not switch the client with the button off! Mostley if you work only a short time the button works well! Did anybody has the some problem or maybe a work around for this problem. Thanks Mirco Rohloff

1 0

x2go kubuntu 12.4
by Mirco Rohloff 19 Aug '12

19 Aug '12

Hello, i want to use Kubuntu 12.4 LTS with X2go. After any Login the Kdesktop restarts with folloing Krash Report. Has anybody a workaroung for this problem? Thanks Mirco Application: KWin (kwin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc671dfe780 (LWP 15661))] Thread 3 (Thread 0x7fc655994700 (LWP 15663)): #0 0x00007fc66ce0bee8 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #1 0x00007fc66ce0dd31 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007fc66cddac82 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x00007fc66cddaed7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007fc66ccd9fa7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007fc66cdba9ff in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007fc66ccdcfcb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007fc665f03e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x00007fc6716154bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x0000000000000000 in ?? () Thread 2 (Thread 0x7fc655193700 (LWP 15664)): #0 0x00007fc665f07d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fc66e0cb222 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x00007fc66e0cb259 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x00007fc665f03e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x00007fc6716154bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fc671dfe780 (LWP 15661)): [KCrash Handler] #6 0x00007fc6715a602c in free () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x00007fc66f057819 in XFree () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #8 0x00007fc66ebff2ee in XRRUpdateConfiguration () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2 #9 0x00007fc67194cc60 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #10 0x00007fc67193e4b8 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #11 0x00007fc66c1cdb85 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #12 0x00007fc66c1dcf98 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x00007fc66c207b3a in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #14 0x00007fc66cddac82 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #15 0x00007fc66cddaed7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #16 0x00007fc66cddff67 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #17 0x00007fc671940c36 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #18 0x00007fc67154476d in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #19 0x0000000000400661 in _start ()

1 0

x2gothinclient performance
by Michael Hierweck 19 Aug '12

19 Aug '12

Hi x2go users, I'm trying out x2go in thin client mode on more recent hardware (ZOTAC ZBOX, AMD E-350, 2 GB RAM). I experience both bad performance and high CPU load the client side, even worse than on my legacy Intel P III 1 GHz systems some time ago. Notable the x2goclient process consumes about 30% CPU time (one of tow cores) whenever a session is active - even a simple terminal (single application -> terminal) waiting for input. Which options are recommended for local (1 GBit LAN) usage? Thanks in advance. Any hints are appreciated. Michael Hierweck -- EDV-Serviceteam Annika & Michael Hierweck GbR Egerstraße 53, 44225 Dortmund (Germany) http://www.edv-serviceteam.net

3 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user