IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 6 April 2016   (all times are UTC)

02:06GodFather has left IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com, Ping timeout: 264 seconds)
04:55quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: :wq)
04:56quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
05:27alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
05:35alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
05:49vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
05:54ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:34alkisg is now known as alkisg_away
07:00kjackal has left IRC (kjackal!~kjackal@2a02:587:3101:3500:c8ce:bb65:49a7:ffca, Ping timeout: 246 seconds)
07:00kjackal_ has left IRC (kjackal_!~kjackal@2a02:587:3101:3500:c8ce:bb65:49a7:ffca, Ping timeout: 246 seconds)
07:28mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:30semo163 has joined IRC (semo163!58c8d653@gateway/web/freenode/ip.88.200.214.83)
07:32
<semo163>
hello there . Cannot find out why thin clients freeze about 2 hours after startup. Ubuntu 14.04 ltsp x64 ltsp5 pnp server and clients
07:33
nbd server client version is 3.7
07:37alkisg_away is now known as alkisg
07:37
<alkisg>
semo163: are they freezing only inside the user session or also when they're in ldm?
07:37
<semo163>
It doesn't matter if some one is doing something or not. Client just freezes. Only hard reset button helps
07:37
I use auto login in lts.conf
07:39
after restart of diskless client in gets nbd root and starts session after autologin
07:39
user may use firefox as ltsp-localapps firefox or just libreoffice it doesnt matter wat hi uses
07:40
on server i installed lubuntu environment
07:42
already tried to change net.ipv4.tcp_keepalive_probes=50 as was suggested
07:42
<alkisg>
Try without logging in
07:42
<semo163>
ok
07:42
<alkisg>
This will minimize the issue to only nbd + networking issues, not to ssh timeouts etc
07:43
I have clients here with 14.04 that work for days without problems
07:43
So it's not a general issue that affects all installations ec
07:43
etc
07:43
<semo163>
You mean disable autologin and just wait for disconnect ?
07:43
<sebd>
semo163: I know a place where the firewall silently disconnects my ssh sessions after a while. Security measure I guess.
07:43
<alkisg>
Yes
07:43
<semo163>
there is no firewall on server
07:43
<alkisg>
semo163: you can also put SCREEN_02=shell in lts.conf, to get a shell instead of ldm
07:43
That will make it easier to see if the client hanged or not, to see kernel panics etc
07:44
<semo163>
ok
07:44
thank you alkisg
07:44
<alkisg>
np
07:45
<semo163>
as a last resort today after work will try nbd from upstream (3.17 I guess) 16.04 release
07:46
something tells me that it nbd client issue
07:47
sebd: iptables are flushed no firewall (ufw or so is installed on server)
07:48
sebd: not installed I mean
07:49
<sebd>
ok semo163 and nothing active between server and clients ?
07:51
<semo163>
sebd: no they are in small lan... no firewall . switch can not be an issue because ping from ather PC to LTSP server goes well
07:53
<alkisg>
Your dhcp server doesn't have 2 hours lease time and assign the expired IP to another client, does it?
07:53
The default tcp timeout is 2h 11 minutes, but it shouldn't affect nbd connections with the usual keepalive etc.
07:54
<semo163>
will check dhcp. thanks for such a thouhgt
07:56
nbd client uses usual (after installation params) /sbin/nbd-client 192.168.1.18 -N /opt/ltsp/amd64 /dev/nbd0 -swap -persist
07:58
/sbin/nbd-client 192.168.1.18 /dev/nbd9 -N /opt/ltsp/amd64
08:02
default-lease-time 6000;
08:04
all clients have different hw (all have about 1Gb of RAM just no HD on em) but behave the same way
08:05
thera are 4 as yet but I will add more after resolve this
08:20
<alkisg>
(10:58:23 πμ) semo163: /sbin/nbd-client 192.168.1.18 /dev/nbd9 -N /opt/ltsp/amd64 ==> that should only be a temporary mount for 1 second
08:21
Btw, do you have the greek schools ppa in your sources?
08:21
!greek-schools-ppa
08:21
<ltsp>
greek-schools-ppa: https://launchpad.net/~ts.sch.gr/+archive/ppa/ supports LTS Ubuntu releases with newer LTSP versions, bug fixes etc
08:55
<semo163>
yes i've got greek schook in ppa ltsp5 was installed with this ppa
08:56
actually on client i've got ps aux|grep nbd /sbin/nbd-client 192.168.1.18 -N /opt/ltsp/amd64 /dev/nbd0 -swap -persist 2 records and one record /sbin/nbd-client 192.168.1.18 /dev/nbd9 -N /opt/ltsp/amd64
08:57
at all run time of thin client
08:59
meanwhile nbdstat on server says this client got only one nbd connection
09:00
actually nbd is lsof which says nbd-serve 8412 nbd 6u IPv4 1391882 0t0 TCP ltsp.csm.local:nbd->baksheeva.csm.local:39580 (ESTABLISHED)
09:04
<alkisg>
If nbd-client stays around after the connection was closed, it sounds like a bug. That wouldn't be the one affecting you though.
09:19alkisg is now known as alkisg_away
10:46izzle121 has left IRC (izzle121!~izzle121@2601:193:c200:1d00:52e5:49ff:fec0:534b)
10:48GodFather has joined IRC (GodFather!~rcc@96.92.43.9)
11:36kjackal has joined IRC (kjackal!~kjackal@ppp-2-86-52-112.home.otenet.gr)
11:48GodFather has left IRC (GodFather!~rcc@96.92.43.9, Remote host closed the connection)
11:49Faith has joined IRC (Faith!~paty_@unaffiliated/faith)
11:53GodFather has joined IRC (GodFather!~rcc@96.92.43.9)
12:07GodFather has left IRC (GodFather!~rcc@96.92.43.9, Remote host closed the connection)
12:07GodFather has joined IRC (GodFather!~rcc@96.92.43.9)
12:16GodFather has left IRC (GodFather!~rcc@96.92.43.9, Ping timeout: 260 seconds)
12:19gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
13:13PeperPots has left IRC (PeperPots!sid1218@gateway/web/irccloud.com/x-aodyqbphqxbtjpxm, Remote host closed the connection)
13:14semo163_ has joined IRC (semo163_!5345b224@gateway/web/freenode/ip.83.69.178.36)
13:15PeperPots has joined IRC (PeperPots!sid1218@gateway/web/irccloud.com/x-urvywrmqrgvbrqce)
13:48
<semo163_>
alkisg: installed nbd from upstream ubuntu (16.04), so far so good (no freezes as yet). On client there's only one nbd-client process now @sbin/nbd-client 192.168.1.18 -N /opt/ltsp/amd64 /dev/nbd0 -swap -persist -systemd-mark
13:55
could someone please show out of ps -aux|grep nbd from ubuntu ltsp5 pnp diskless client command
13:55
and ps aux|grep ssh as well
13:56ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
14:03alkisg_away is now known as alkisg
14:03
<alkisg>
semo163_, so you think that nbd-client from 14.04 is broken?
14:05
# ps aux|grep nbd
14:05
root 287 1.4 0.0 2208 56 ? Ss 17:04 0:00 @sbin/nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0 -swap -persist systemd-mark
14:05
root 291 1.0 0.0 0 0 ? S< 17:04 0:00 [nbd0]
14:05
root 602 0.0 0.0 2208 96 ? Ss 17:04 0:00 nbd-client 192.168.67.1 -N swap /dev/nbd1 -swap
14:05
root 605 0.0 0.0 0 0 ? S< 17:04 0:00 [nbd1]
14:05
root 2860 0.0 0.0 2208 76 ? S 17:05 0:00 nbd-client 192.168.67.1 /dev/nbd9 -N /opt/ltsp/i386
14:07
# ps aux|grep ssh
14:07
root 2962 0.3 3.4 7724 5068 pts/2 Ss+ 17:05 0:00 ssh -Y -t -M -S /var/run/ldm_socket_2816_server -o NumberOfPasswordPrompts=1 -o ConnectTimeout=10 -l ltsp -o Ciphers=arcfour128,aes128-ctr server echo LTSPROCKS; exec /bin/sh -
14:07
root 3034 0.0 3.1 7724 4632 tty7 S 17:05 0:00 ssh -x -a -oClearAllForwardings=yes -oControlPath=/var/run/ldm_socket_2816_server -2 server -s sftp
14:07
root 3035 0.0 0.1 31216 216 ? Ssl 17:05 0:00 sshfs -o disable_hardlink,allow_other,nonempty,ControlPath=/var/run/ldm_socket_2816_server server:/home/ltsp /home/ltsp
14:07
root 3043 0.0 3.2 7724 4700 tty7 S 17:05 0:00 ssh -x -a -oClearAllForwardings=yes -oControlPath=/var/run/ldm_socket_2816_server -2 server -s sftp
14:07
<semo163_>
not sure as yet will see if thin clients stay connected overnight
14:08
<alkisg>
semo163_, did you do the "test if clients hang at ldm" part?
14:08
Did they hang there?
14:08
<semo163_>
doing it now
14:08
<alkisg>
But with a different nbd-client, so you won't know for sure...
14:09
<semo163_>
I've upgraded nbd so cannot tell you about prev version
14:09
<alkisg>
Right
14:09
<semo163_>
now monitoring console of one of them
14:10
one I rebooted with SCREEN_02=shell without autologin
14:13
it still get ltsp welcome login screen ... I left 07 screen as is without logining in it and switched to 02 then tail -fn30 /var/log/syslog
14:14
not sure if it's right way to isolate LDM or not...
14:16
<alkisg>
LDM or not doesn't matter, it's sshfs or nbd that matters, and since you haven't logged in you're only using nbd
14:17
Although a weird mix of old nbd-server, new nbd-client etc
14:18
<semo163_>
ok. no mix i've installed new nbd client and server from 16.04 and rebuild image with ltsp-update-image --cleanup /
14:19
after 2 clients were booted with new version of nbd client. One with autologin second without login
14:20
in 30 min first results :-)
14:21
usually they hangs after 2hours aprx.
14:23mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
15:06
<semo163_>
alkisg: freezed client with just nbd session (without LDM)
15:07
syslog on both parts (server and client) shows nothing unusual (no client disconnect or so...)
15:08
strange, but with LDM (second client) is still running
15:17
second one also freezed -(
15:22
could someone send output from /ets/ssh/ssh_config sshd_config
15:28
no need it. This is nbd for sure. But how to debug it ?
16:09gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
16:13vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
16:25Mowens_ has joined IRC (Mowens_!4395c282@gateway/web/freenode/ip.67.149.194.130)
16:29robb_nl has joined IRC (robb_nl!~robb_nl@ip-83-134-22-244.dsl.scarlet.be)
16:29
<Mowens_>
Hello - reading up on LTSP - looks like you have to PXE your clients to get it's OS-- is there an alternative solution that can easily be used over the WAN?
16:33
<Hyperbyte>
Mowens_, hi.
16:33
The whole idea behind LTSP is having clients without a harddisk. Clients without a harddisk need to get their software from somewhere.
16:33
You could install Ubuntu on a USB stick I guess?
16:34
But what you're doing now, is kind of like going to a butcher and asking for vegetables. ;-)
16:34
LTSP clients have no OS themselves. They get it from the server, via the network.
16:35
Or maybe I'm totally misunderstanding the question?
16:36Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
16:36
<Hyperbyte>
Are you just looking for a way to provide remote desktops over the internet?
16:44
<Mowens_>
Ahhh i got ya.
16:45
Yes, long explanation coming. :)
16:45GodFather has joined IRC (GodFather!~rcc@96.92.43.9)
16:52
<Hyperbyte>
Check out x2go if you just want remote desktops from a central server over the internet
16:56
<Mowens_>
Yes, I am looking for a way to provide remote desktops over the internet. I was looking at this all wrong. I come from an extensive background in Citrix and windows terminal server, and currently exploring the linux alternatives for my employer. The ultimate end goal is to create the ability to provide a desktop to any user's device. (phone, tablet, laptop, desktop, thin client, or other) from anywhere. It looks like X2go has a good
16:56
yours appears to run much thinner, and I like that. :)
16:58
I have a x2go POC and I like that, I just wanted to give you guys a good try incase I missed something in the documentation
17:05GodFather has left IRC (GodFather!~rcc@96.92.43.9, Ping timeout: 248 seconds)
17:11
<Hyperbyte>
You can combine LTSP and x2go
17:11
I do that at one of the companies I work for too. LTSP for the local thin clients, x2go for the remote offices.
17:23
<Mowens_>
excellent. ty
17:29dtcrshr has left IRC (dtcrshr!~datacrush@unaffiliated/datacrusher, Quit: Saindo)
17:30bradyj has joined IRC (bradyj!49cb7058@gateway/web/freenode/ip.73.203.112.88)
17:32
<bradyj>
I have just installed LTSP with Lubuntu 14.04, everything went smooth, however I am unable to login to the thin client.
17:35darkend has joined IRC (darkend!c837bdad@gateway/web/freenode/ip.200.55.189.173)
17:36
<darkend>
hy
17:40darkend has left IRC (darkend!c837bdad@gateway/web/freenode/ip.200.55.189.173, Quit: Page closed)
17:42bradyj has left IRC (bradyj!49cb7058@gateway/web/freenode/ip.73.203.112.88, Ping timeout: 250 seconds)
17:44semo163_ has left IRC (semo163_!5345b224@gateway/web/freenode/ip.83.69.178.36, Ping timeout: 250 seconds)
17:48
<Hyperbyte>
mhm
17:49darkend has joined IRC (darkend!c837bdac@gateway/web/freenode/ip.200.55.189.172)
17:50
<darkend>
I install and configure the server and later create de image.
17:50
hy. i have a little problem with a ltsp server in debian wheezy.
17:51
but the client say that not found de pxe.0 file.
17:54
<vagrantc>
if it's a new install, i wouldn't recommend wheezy
17:55
though it's probably just a misconfiguration with dhcp
17:56
darkend: https://wiki.debian.org/LTSP/Howto
17:57
<darkend>
the ltsp server no have a dhcp server inside.
17:57
well the dhcp server is an dedicated server
17:58
<vagrantc>
ok, then configure your dhcp server to tell it to boot from the ltsp server.
17:58
or use proxydhcp
17:58
<darkend>
the cliente can see the dhcp server but can´t see the client image
17:58
<vagrantc>
!proxydhcp | echo darkend
17:58
<ltsp>
darkend proxydhcp: A proxy DHCP server is defined by the PXE specification as a server which sends auxiliary boot information to clients, like the boot filename, tftp server or rootpath, but leaves the task of IP leasing to the normal DHCP server. More info: https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP
18:00
<quinox>
we also use a diff. DHCP server that we configured to send a client to the LTSP server, works fine
18:00
<darkend>
in first instance, i install it on ubuntu 14.04 like a --fat-client and work very well.
18:00
<quinox>
/etc/dnsmasq.conf: dhcp-boot=/srv/tftp/ltsp/amd64/pxelinux.0,duivenkracht,10.50.0.8
18:00
<darkend>
now my boss order me tha change to debian and create de image like thin client and don´t work.
18:06robb_nl has left IRC (robb_nl!~robb_nl@ip-83-134-22-244.dsl.scarlet.be, Remote host closed the connection)
18:13Mowens_ has left IRC (Mowens_!4395c282@gateway/web/freenode/ip.67.149.194.130, Ping timeout: 250 seconds)
18:15sutula has left IRC (sutula!~sutula@207-118-162-223.dyn.centurytel.net, Ping timeout: 276 seconds)
18:17
<vagrantc>
darkend: try ltsp-config dnsmasq
18:17
darkend: but why are you running wheezy?
18:17sutula has joined IRC (sutula!~sutula@207-118-151-30.dyn.centurytel.net)
18:18
<vagrantc>
darkend: current debian stable release jessie is already almost a year old
18:25gravetech has joined IRC (gravetech!433ac2c2@gateway/web/freenode/ip.67.58.194.194)
18:26
<gravetech>
I was hoping someone could help with a question about LDM_XSESSION in the lts.conf?
18:29
I'm attempting to follow the instructions here: http://ubuntuforums.org/showthread.php?t=2177959
18:29
The problem is I am not using xfce and I can't seem to get the client to login with the LDM_XSESSION script in place
18:31lbssousa has joined IRC (lbssousa!~laercio@177.143.31.126)
18:32GodFather has joined IRC (GodFather!~rcc@2600:1007:b02d:772f:b1f8:cba0:93c1:3786)
18:32
<darkend>
@vagrantc: I use wheezy because is that i have. i´m in Cuba and the access to repos are very difficult
18:43
<alkisg>
gravetech: I think it would be better to ask what you need from scratch, not "help me on this forum post"
18:43
I don't agree with the way this forum post handles ltsp, there are much better ways to do what he's trying to do
18:47
<gravetech>
@alkisg sounds good let me start over!
18:48
So I am attempting to setup an LTSP server to assist with some computer-based training that we have starting here at my work. Currently we have three Ubuntu 14.04 boxes with Guest Sessions enabled that wipe out anything they do after they log-out. I am looking for similar functionality from LTSP
18:49
I'd like it if they could log-in as a guest and then when they log out (or log in the next time) wipe their settings back to a template
18:49
I am trying to do this with some spare computers that are PXE booting
18:49
The long-term goal is to run it with RPi3's
18:51
<vagrantc>
darkend: ah, that's difficult. wheezy should be able to do what you're needing
18:52
gravetech: there are some posts on ltsp-discuss@lists.sourceforge.net that do exactly that ...
18:52* vagrantc also likes using libpam-mount to mount a tmpfs homedir on login
18:52
<vagrantc>
especially with fat clients
18:53* vagrantc had been meaning to integrate that directly into ltsp for some time now but never got it set up
18:56
<darkend>
How a can have many users in a --fat-client???
18:56
other cuestion.
18:57
<vagrantc>
one for each terminal
18:57
anyways, good luck folks, gotta head out
18:57* vagrantc waves
18:57vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
18:57
<darkend>
i create two users and only mcan acces with the user with i create the client image.
19:00
ok i will try again. bye
19:00darkend has left IRC (darkend!c837bdac@gateway/web/freenode/ip.200.55.189.172, Quit: Page closed)
19:00
<alkisg>
gravetech: ok, i'll give you 3 tutorials
19:00
!ltsp-pnp
19:00
<ltsp>
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
19:01
<alkisg>
This is to get ltsp up and running with the spare boxes
19:01
!raspberrypi
19:01
<ltsp>
raspberrypi: (#1) Ubuntu/LTSP on Pi 2: https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi, or (#2) Debian/LTSP (with raspbian chroot) on Pi: http://cascadia.debian.net/trenza/Documentation/raspberrypi-ltsp-howto/, or (#3) unofficial Ubuntu/LTSP (with raspbian chroot) on Pi: http://pinet.org.uk/
19:01
<alkisg>
#1 is for when you get the rpi3's
19:02
And for the guest sessions, it's one script, let me locate the url..
19:03
<gravetech>
I think I found your post on the mail archives @alkisg
19:03
You create a /opt/ltsp/i386/usr/share/ldm/rc.d/S00-guest-sessions
19:04
<alkisg>
https://sourceforge.net/p/ltsp/mailman/message/27814821/
19:04
Right
19:05
gravetech: note though that with the ltsp-pnp tutorial, there's no chroot, so you put it in /usr/share/ldm/rc.d/S00-guest-sessions
19:05
<gravetech>
Ok perfect, just one more question: do I still need to have multiple accounts (one for each client connecting)?
19:05
Thanks, that would have tripped me up!
19:05
<alkisg>
With this how-to, yes, because their home is on the server and it needs to be on a different path,
19:05
<gravetech>
OK I thought so. Thank you!
19:06
<alkisg>
but it's possible to have only one guest account, e.g. "ltsp", with /home mounted from the server,
19:06
via nbd, or from the tmpfs in ram
19:06
You're welcome
19:06
<gravetech>
I'll take a look in to that
19:11
<semo163>
is there any way to execute command from ubuntu ltsp 5 pnp server to the client (let say shutdown -r now what I need)
19:12
<alkisg>
!epoptes | echo semo163:
19:12
<ltsp>
semo163: epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org
19:12
<alkisg>
semo163: short tutorial: sudo apt-get install epoptes; sudo ltsp-update-image -c /
19:15
<semo163>
alkisg: thank you, but I'll have to do it next day (I left the place already -( )
19:15
no way esle but epoptes ?
19:16
<alkisg>
I don't understand the problem
19:16
You want to install a software but you left and you are looking for another software?
19:16
How will that help?
19:16
If you have ssh to the server, you can install whatever you want... if not... no
19:16
<semo163>
no I mean I'm far away from client now
19:17
<alkisg>
Is the client logged in?
19:17
<semo163>
i can login to server
19:17
but after installation I need to reboot client
19:17
i can not do it
19:17
now
19:17
<alkisg>
Is the client logged in?
19:17
<semo163>
yes they are loged in
19:17
<alkisg>
Are they thin clients or fat?
19:17
<semo163>
thin
19:18
<alkisg>
You can do it with epoptes then
19:18
<semo163>
diskless
19:18
login to ltsp server (lubuntu session runs on server)
19:19
ok will try to install now
19:19
<alkisg>
install epoptes, `su` to the user accounts, and run /usr/share/epoptes-client/get-display to get access to their displays, and /usr/share/epoptes-client/endsession --reboot to reboot the thin clients
19:20
<semo163>
thank you very much . will try
19:20
<alkisg>
do run ltsp-update-image -c / as well so that you can control them graphically after the first reboot
19:20
<semo163>
ok
19:23
<alkisg>
semo163: note that you said "yes they are thin, diskless". But ltsp fat clients are also diskless.
19:24
If you're using ltsp-pnp, by default clients with >400 mb ram are fat clients
19:24
They run the desktop session locally, not on the server
19:24
In that case you can't use the method I said
19:25
In that case you'll have to update the image and wait for them to logout, because the new image will make them reboot at ldm
19:26
<semo163>
alkisg: no they run desktop session on server for sure
19:27
dispite they all have 1Gb of RAM
19:28
<alkisg>
semo163: that's not the default though, so you must have specified that in lts.conf, by LTSP_FATCLIENT=False
19:28
You can run ps aux and check if you see the user processes on the server
19:28
All of them running gnome-session etc
19:29
<semo163>
ps says they all run on server now
19:30
<alkisg>
*not gnome-session, lxde-session or whatever its name is
19:30
If you see one lxde-session for each user, they're thin
19:32
<semo163>
yes
19:33
I did /usr/share/epoptes-client/get-display DISPLAY=192.168.1.41:7
19:33
then /usr/share/epoptes-client/endsession --reboot I don't know how to reboot in this environment
19:33
output from server
19:34
i guess i have to deleay till morning -(
19:34
<alkisg>
export $(/usr/share/epoptes-client/get-display)
19:34
/usr/share/epoptes-client/endsession --reboot
19:35
<semo163>
I did and got this "I don't know how to reboot in this environment"
19:35
this is output from ltsp server
19:35
<alkisg>
Did you run the export command?
19:36
Is that Lubuntu 14.04?
19:36
<semo163>
yes
19:36
<alkisg>
What's the output of this? echo $DISPLAY
19:36
<semo163>
managed to reboot by prefixing SUDO
19:37
<alkisg>
...reboot the server?!
19:37
<semo163>
F....k yes it was server.... Lost all clients now for sure
19:37
<alkisg>
You don't want sudo there
19:39
Yes unfortunately the xorg, ssh, nbd connections are lost, you can't access them after server reboot unless you had panic=xxx in the kernel cmdline
19:39
<semo163>
If i had known then that i know now .... (pearl jam i guess) :-)
19:40
5 zombie processes (they are)
19:40
but stations are pinging
19:41
<alkisg>
The kernel on the clients is running, but he'll never get its "disk" back (nbd)
19:41
So it cannot longer even find the reboot command
19:42
<semo163>
no processes of them
19:47
alkisg: All right thank you veeeeery much indeed. Tomorrow will find out further
19:48
<alkisg>
You're welcome
19:49
<semo163>
how to logout here who knows ?
19:49
from chat i mean
19:50
<gravetech>
usually a /quit
19:50
<semo163>
thanks
19:50semo163 has left IRC (semo163!58c8d653@gateway/web/freenode/ip.88.200.214.83, )
19:52
<metaf5>
So I am able to get a root shell in my "shell" screen script, but my ldm screen script fails to log in. I *cannot* su to user "test" from my shell because of a missing passwd entry. Is this missing passwd entry also the reason that I can't login via LDM?
19:52
If that's likely, could someone tell me what part of the LTSP process is supposed to sync the passwd file so I can un-break my configuration?
19:53
<maldridge>
LDM checks logins against the server, so you shouldn't have issues there, but its possible that you need to grant that user exemptions to password policies
19:54
<metaf5>
On the server's auth.log I see that the "test" user successfully authenticates with SSH, and then it recieves a client-disconnect.
19:55
What do you mean grant exemptions?
19:57
<maldridge>
like if your user needed a kerberos tgt to access resources, your script wouldn't be able to grant that
19:58
if you don't already know you have security constraints being enforced on that user, you probably don't
20:00
<metaf5>
Ah, okay. Yeah, nothing like that.
20:02
<maldridge>
there is an lts.conf directive you can use to set the password, but I do not recall it, I believe it is related to this thouhg (one moment while I try to remember how to invoke the bot)
20:02
!ltsp SCREEN_02
20:02
<ltsp>
Error: "ltsp" is not a valid command.
20:02
<maldridge>
!SCREEN_02
20:02
<ltsp>
SCREEN_02: To get a root shell on an Ubuntu thin client: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using_a_shell_SCREEN
20:02lbssousa has left IRC (lbssousa!~laercio@177.143.31.126, Quit: lbssousa)
20:03
<maldridge>
that one will let you get a root shell within the live system, but you seem to be having more of an issue connecting to the server if I understand you correctly
20:04
<metaf5>
Yes, that works. That's where I'm noticing that I can't su to my "test" user.
20:04
<maldridge>
ah, you probably don't want to su to them locally
20:04
they wouldn't have the sshfs mounted then
20:53GodFather has left IRC (GodFather!~rcc@2600:1007:b02d:772f:b1f8:cba0:93c1:3786, Ping timeout: 268 seconds)
21:00Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving)
21:06gravetech has left IRC (gravetech!433ac2c2@gateway/web/freenode/ip.67.58.194.194, Ping timeout: 250 seconds)
21:11Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
21:20tharkun has left IRC (tharkun!~0@unaffiliated/tharkun, Ping timeout: 244 seconds)
21:30ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:38tharkun has joined IRC (tharkun!~0@201.157.71.45)
22:10kjackal has left IRC (kjackal!~kjackal@ppp-2-86-52-112.home.otenet.gr, Ping timeout: 264 seconds)
22:18dtcrshr has joined IRC (dtcrshr!~datacrush@unaffiliated/datacrusher)
23:14vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
23:24ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
23:36GodFather has joined IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com)