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