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


Channel log from 24 November 2017   (all times are UTC)

00:20alazyworkaholic has joined IRC (alazyworkaholic!~alan@179.126.36.204)
01:17vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
02:26alazyworkaholic has left IRC (alazyworkaholic!~alan@179.126.36.204, Ping timeout: 255 seconds)
02:39sutula has left IRC (sutula!~sutula@207-118-156-253.dyn.centurytel.net, Read error: No route to host)
02:39sutula has joined IRC (sutula!~sutula@207-118-156-253.dyn.centurytel.net)
05:15kjackal has joined IRC (kjackal!~quassel@2a02:587:3114:a000:35b2:facd:bb9f:5fed)
06:01forum has joined IRC (forum!~Thunderbi@193-154-17-226.adsl.highway.telekom.at)
06:28forum has left IRC (forum!~Thunderbi@193-154-17-226.adsl.highway.telekom.at, Quit: forum)
07:15Statler has joined IRC (Statler!~Georg@p5B30E880.dip0.t-ipconnect.de)
09:27Statler has left IRC (Statler!~Georg@p5B30E880.dip0.t-ipconnect.de, Remote host closed the connection)
10:38forum has joined IRC (forum!~Thunderbi@193-154-17-226.adsl.highway.telekom.at)
10:43lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
10:47Statler has joined IRC (Statler!~Georg@gwrz3.lohn24.de)
11:02forum has left IRC (forum!~Thunderbi@193-154-17-226.adsl.highway.telekom.at, Quit: forum)
11:20Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
11:58ricotz has joined IRC (ricotz!~ricotz@p5B2A89A0.dip0.t-ipconnect.de)
11:58ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
12:05lucas_ has joined IRC (lucas_!~lucas@201.182.221.14)
12:05lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Read error: Connection reset by peer)
12:46lucas_ has left IRC (lucas_!~lucas@201.182.221.14, Remote host closed the connection)
12:50lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
14:13alazyworkaholic has joined IRC (alazyworkaholic!~alan@191.54.132.16)
15:29mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 248 seconds)
15:32mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
16:06alazyworkaholic has left IRC (alazyworkaholic!~alan@191.54.132.16, Disconnected by services)
16:07alazyworkaholic has joined IRC (alazyworkaholic!~alan@191.54.132.16)
16:08kjackal has left IRC (kjackal!~quassel@2a02:587:3114:a000:35b2:facd:bb9f:5fed, Ping timeout: 250 seconds)
16:11jesusupmp has joined IRC (jesusupmp!b1ea07ce@gateway/web/freenode/ip.177.234.7.206)
16:11
<jesusupmp>
help
16:11alazyworkaholic has left IRC (alazyworkaholic!~alan@191.54.132.16, Disconnected by services)
16:11
<jesusupmp>
Ey!
16:11alazyworkaholic has joined IRC (alazyworkaholic!~alan@191.54.132.16)
16:11
<jesusupmp>
i need help :(
16:12
Can i distribuite another system, like windows?
16:12
putos todos entonces
16:13
<alkisg>
Hi jesusupmp
16:13
LTSP boots linux clients,
16:14
then you can run windows VMs on top of them, or use RDP (remote desktop) to a windows server
16:14
If you want to natively boot windows, use aoe or iscsi, no ltsp needed there, but it's much more difficult than the above 2 solutions ^
16:17
<jesusupmp>
But could I distribute windows to several clients? right?
16:18
is for homework, and my teacher told me that with LTSP will works
16:18
So, i need to install LTSP on my PC and then a Windows VM?
16:19
And then ??
16:19
<alkisg>
Yes
16:19
You can have as many users as you like and as many VMs as you like
16:20
<jesusupmp>
Thanks!
16:22
<alkisg>
!ltsp-manager
16:22
<ltsp>
ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
16:22
<alkisg>
jesusupmp: that's the recommended method to install ltsp ^
16:24
<jesusupmp>
Ok, thank u
16:46Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Remote host closed the connection)
16:54lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection)
16:54jesusupmp has left IRC (jesusupmp!b1ea07ce@gateway/web/freenode/ip.177.234.7.206, Quit: Page closed)
17:42lucascastro has joined IRC (lucascastro!~lucas@170.78.53.20)
17:46vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:10Statler has left IRC (Statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
19:15lionrouge has joined IRC (lionrouge!~user@185.18.5.23)
19:15
<lionrouge>
hi !
19:16
after running ltsp-update-image i get weird behaviour: some users can't login in LDM (though some can - which were created earlier)
19:17
LDM raises error "permission denied (public key, password)"
19:17
if a user is created while a client is on it can login right now
19:18
i tried run ltsp-update-sshkeys but it didn't help
19:18lucascastro has left IRC (lucascastro!~lucas@170.78.53.20, Remote host closed the connection)
19:19
<lionrouge>
what can be the issue?
19:22
if i login to local root on client machine and try to ssh from command line it works ok (with the same username and password LDM fails to login)
19:24lucascastro has joined IRC (lucascastro!~lucas@170.78.53.20)
19:28
<alkisg>
lionrouge: try with: ssh user@server. But, use the "server" name exactly as it is, don't use your real server name
19:28
(from the client root shell, before trying with ldm again)
19:28
Btw, /var/log/ldm.log on the client , and /var/log/auth.log on the server, have login related info
19:29
<lionrouge>
alkisg, where do i get server name?
19:29
it's hostname?
19:29
or some config file?
19:32lucascastro has left IRC (lucascastro!~lucas@170.78.53.20, Remote host closed the connection)
19:36
<lionrouge>
or you mean the word "server" ?
19:41
when i do ssh <username>@server it works under local client root
19:46
the most weird thing is that some users can login with LDM and some cannot
19:53
<alkisg>
lionrouge: do you see a successful login in the server's /var/log/auth.log?
19:54
If yes, then it's not a login issue but a xorg crashing issue
19:54
In which case, you should mention your DE and if you're using thin or fat clients
19:55
E.g. some users may have a non-existing DE entry in their .dmrc
19:59
<lionrouge>
this is what i see in server's /var/log/auth.log: https://dpaste.de/hRb9
19:59
first line is failed login attempt for one user and other lines are successful login for another user
19:59
both in LDM
19:59
<alkisg>
lionrouge: if you see "session opened" for a user that "can't login", this is a xorg/de issue
19:59
Not a login issue
19:59
Read my remarks above ^
20:00
<lionrouge>
no i don't see it for failed login
20:00
this log extract contains 2 login attempts: 1 failed and the other (for another user) successful
20:01
all i get in case of failure is "connection closed"
20:02
<vagrantc>
both attempts from the same client (192.168.1.20) ...
20:02
<lionrouge>
yup
20:03
<vagrantc>
are both users defined in the same way? local users on the server, or in ldap, or some other remote authentication mechanism?
20:03
<lionrouge>
they were created the same way: with adduser command on server machine
20:04
<vagrantc>
and you can ssh user@server from the client for both users?
20:04
<lionrouge>
the only difference is that test3 (which logins ok) was created earlier than failing user
20:04
yes, for both of them
20:04
<vagrantc>
did something change in /etc/skel ?
20:05
<lionrouge>
yes
20:05
<vagrantc>
...
20:05
<lionrouge>
i changed XFCE defaults by inserting some files there
20:05
<vagrantc>
if you remove those files in the new user's home dirs ... can they log in?
20:07
although you should still see the successful login in auth.log
20:07
so that's perplexing at best
20:10
<lionrouge>
removeing those files doesn't help
20:10
i can login with ssh to ALL users from client root console
20:10
i can't login to newly created users from LDM
20:11
client's /var/log/ldm.log has "permission denied (publickey,password)" for new users and "established ssh connection" for old ones
20:13
can updating ltsp image break anything?
20:17
<vagrantc>
what do you mean when you say "client root console" ?
20:18
<lionrouge>
local root account in the image that is booted over network
20:19
<vagrantc>
so you boot the client, and log in as root how?
20:19
<lionrouge>
i press Ctrl+Alt+F1 and can login to it with LDM at Ctrl+Alt+F7
20:19
<vagrantc>
got it
20:20
is the client generated from a chroot (classic ltsp), or from the server's OS (ltsp-pnp style) ?
20:21
what's the exact command you use to run ltsp-update-image? is there an /etc/ltsp/ltsp-update-image.conf ?
20:22
<lionrouge>
separate chroot
20:22
no i don't have this file
20:23
and i run ltsp-update-image without any parameters
20:24
<vagrantc>
from what you've said, the ldm.log suggests the new users don't even successfully authenticate with ssh
20:25
<lionrouge>
looks like
20:25
<vagrantc>
but there isn't a lot of difference between what ldm does and running "ssh USER@server" from the console
20:25
<lionrouge>
i see
20:26
<vagrantc>
Nov 24 22:57:16 debian sshd[1943]: Connection closed by 192.168.1.20 port 45666 [preauth]
20:26
that suggests that it didn't even get as far as specifying the user and passphrase
20:27
so it shouldn't matter which user is specified, if it's from the same client
20:27
<lionrouge>
but it does matter
20:28
<vagrantc>
which makes this really bizarre
20:29
what are the usernames?
20:29
<lionrouge>
what does --cleanup option do with ltsp-update-image ?
20:29
us41 and test3
20:29
<vagrantc>
only really useful whn building the image from the server OS, rather than a chroot
20:31
lionrouge: can you show auth.log from the successful logins with us41 from the client root console?
20:31
<alkisg>
lionrouge: try to type the password where the username is expected, so that you make sure you type it properly, e.g. due to unexpected keyboard layout
20:31
I.e. so that you see what you typed
20:32
<vagrantc>
ah
20:32
<alkisg>
The console layout may be different to the xorg layout
20:32
And if you're using some new password that requires a key that is in a different place.. .it could explain it
20:35
<lionrouge>
the password is just space
20:37
sorry, i need to go
20:37
thanks for your help
20:37
<vagrantc>
just space?
20:37
<lionrouge>
yes
20:37
<vagrantc>
a single space?
20:37
<lionrouge>
yes
20:38
it's a testing environment
20:38
<vagrantc>
could you try setting a different password, and try logging in?
20:38
<lionrouge>
it worked previously
20:38
<vagrantc>
i presume test3 has a different password?
20:38
if you change test3 to have a single space as as password, does it fail?
20:40
well, good luck ...
20:40
i could see it being possible that a single space might not work with LDM
20:41
<lionrouge>
test3 has "1" as password
20:41
i changed password for us41 to a longer one with Latin letters and numbers and now it works
20:42
<vagrantc>
so ... there arguably may be a "bug" in LDM that it doesn't accept " " as a valid password
20:42
<lionrouge>
maybe
20:42
it's the only explanation
20:42
thanks
20:43
bb
20:43lionrouge has left IRC (lionrouge!~user@185.18.5.23, Quit: Leaving)
20:47
<vagrantc>
yup, i can confirm
20:49
ok, i can confirm that ldm doesn't handle passwords with spaces in them
20:56
actually, only leading/trailing spaces, spaces in the middle work fine.
20:59
https://bugs.launchpad.net/ltsp/+bug/1734386
21:15kjackal has joined IRC (kjackal!~quassel@2a02:587:3114:a000:35b2:facd:bb9f:5fed)
21:48cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 240 seconds)
21:52cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
22:01
<vagrantc>
huh. ltsp-manager got an en_GB translation ... which so far, seems to have no actual differences from the untranslated strings
22:27lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
22:42ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)