00:32 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40, Quit: leaving) | |
00:34 | mac41 has left IRC (mac41!~mac@ip-209-124-249-106.eatel.net, Ping timeout: 260 seconds) | |
01:18 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
01:18 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
03:41 | <alkisg> 👍️
| |
05:15 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 3.6) | |
05:18 | quinox has joined IRC (quinox!~quinox@ghost.qtea.nl) | |
06:51 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
07:30 | wyre is back | |
07:42 | eu^c-69-255-134- has joined IRC (eu^c-69-255-134-!~eu^c-69-2@2600:8806:5006:fb00:45f9:fa9e:d8b2:4c98) | |
07:42 | <eu^c-69-255-134-> Hey
| |
07:43 | eu^c-69-255-134- is now known as Meeting | |
07:51 | Meeting has left IRC (Meeting!~eu^c-69-2@2600:8806:5006:fb00:45f9:fa9e:d8b2:4c98, Quit: Client closed) | |
07:52 | <alkisg> Hey
| |
08:29 | ricotz is now away: I'm busy | |
08:51 | eu^c-69-255-134- has joined IRC (eu^c-69-255-134-!~eu^c-69-2@2600:8806:5006:fb00:45f9:fa9e:d8b2:4c98) | |
08:55 | eu^c-69-255-134- has left IRC (eu^c-69-255-134-!~eu^c-69-2@2600:8806:5006:fb00:45f9:fa9e:d8b2:4c98, Client Quit) | |
13:08 | wyre is now away: Auto away at Fri Mar 3 13:08:00 2023 UTC | |
13:51 | Lantizia_ has left IRC (Lantizia_!~Lantizia@195.62.201.126, Remote host closed the connection) | |
13:51 | Lantizia_ has joined IRC (Lantizia_!~Lantizia@195.62.201.126) | |
16:00 | jannyboy[m] has left IRC (jannyboy[m]!~jannyboym@2001:470:69fc:105::1:fb25, Quit: You have been kicked for being idle) | |
18:35 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40) | |
21:20 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
21:20 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
21:38 | jvfernandez[m] has joined IRC (jvfernandez[m]!~jvfernand@2001:470:69fc:105::3:260f) | |
21:38 | <jvfernandez[m]> Hello !
| |
21:41 | <alkisg> Hi jvfernandez
| |
21:43 | <jvfernandez[m]> I am a LTSP user, and I have an issue with tmpfs installation.
| |
21:43 | I use only one user profile on the server, which is "user".
| |
21:43 | It's worked very finely, but since monday I have an issue.
| |
21:43 | The image is copied correctly, the system boot correctly, but the "/home/user" directory isn't create.
| |
21:43 | I think this is a problem with ssh, but I don't know exactly where search.
| |
21:44 | <alkisg> Press Ctrl+Alt+F5 to switch to the vt5 terminal; there, login as user; and paste whatever errors you see
| |
21:47 | <jvfernandez[m]> The device is booting...
| |
21:52 | OK ! Good question.
| |
21:52 | I realize something strange.
| |
21:52 | When session start automatically, the /home/user is not created, but when I go on other tty and I create a new session with the same user, the /home/user is automatically created.
| |
21:52 | <alkisg> Do you have autologin enabled?
| |
21:53 | <jvfernandez[m]> Yes
| |
21:53 | <alkisg> If you disable autologin, it then works properly?
| |
21:54 | <jvfernandez[m]> I don't load GUI in my configuration, so, when tty1 is ready I have a session opened for "user"
| |
21:54 | But it's a session without /home/user
| |
21:55 | <alkisg> How do you open the session, are you using pam
| |
21:55 | <jvfernandez[m]> I need to go to tty2 or other to open session manualy for the creation of /home/user
| |
21:57 | <alkisg> You're saying that in your configuration, you're not using GUI, nor a display manager, nor Xorg etc, right? So then how do you log in the user? E.g. are you using openvt, or pam, or login, or systemd to log the user in?
| |
22:02 | <jvfernandez[m]> I use a login simply.
| |
22:02 | In the image ltsp there is a account "user" with id 1002 and on the server I have the same account with the same ID.
| |
22:02 | And it's a simple login connexion.
| |
22:03 | <alkisg> The "login" program doesn't support autologin
| |
22:04 | The user accounts in the image don't matter; the /home/user directory in the image doesn't matter; these things come from the server
| |
22:05 | But for sshfs to succeed, it needs to know the user's password, and pass through PAM, a normal login process
| |
22:06 | <jvfernandez[m]> As I said, until Monday it worked. I think that on the server, the keys in the /home/user/.ssh folder were accidentally destroyed. Can it come from there?
| |
22:06 | <alkisg> I didn't understand you setup. So when you say in tty1 you have a session opened, which commands are you running to open that session?
| |
22:09 | <jvfernandez[m]> I am sorry. It's a pam session :
| |
22:09 | Mar 3 11:49:46 ltsp10 systemd[2214]: pam_unix(systemd-user:session): session opened for user user(uid=1002) by (uid=0)
| |
22:09 | Mar 3 11:49:46 ltsp10 sshd[2211]: pam_unix(sshd:session): session closed for user user
| |
22:10 | <alkisg> A few log lines aren't very helpful. Is it a secret, you can't describe how you've set up autologin to text mode?
| |
22:13 | <jvfernandez[m]> Actually what I have to say is we use KVM virtual machines Our image is a small virtual machine from which we created the img file. When you start it separately, it is already autologin, even without the server.
| |
22:14 | <alkisg> OK, and HOW is that configured?
| |
22:14 | <jvfernandez[m]> I will boot my image in KVM.
| |
22:14 | <alkisg> How did you set up the image to autologin? That's the key part, to see the login process, so that we know why sshfs isn't properly called
| |
22:14 | Anyway it's past midnight here, it might be best to continue another day (unless someone else is available to help...)
| |
22:19 | <jvfernandez[m]> OK I remember.
| |
22:19 | And I find it.
| |
22:19 | I use a autologin.conf
| |
22:19 | /etc/systemd/system/getty@tty1.service.d/autologin.conf
| |
22:19 | [Service]
| |
22:19 | ExecStart=
| |
22:19 | ExecStart=/sbin/agetty --autologin user --noclear %I 38400 linux
| |
22:20 | <alkisg> And do you have PASSWORDS_x in ltsp.conf, to provide the password for SSHFS?
| |
22:22 | <jvfernandez[m]> No :
| |
22:22 | root@ltsp10:/etc/ltsp# cat ltsp.conf | grep PASSWORD
| |
22:22 | root@ltsp10:/etc/ltsp#
| |
22:23 | <alkisg> OK, then that's the issue. Either provide the PASSWORD via ltsp.conf, or via normal login (not autologin), or set up ssh keys; otherwise sshfs can't work
| |
22:23 | Or set up NFS home instead of SSHFS home... these are the available options
| |
22:23 | Time to hit the bed, cheers
| |
22:24 | <jvfernandez[m]> I think it's a problem with ssh keys.
| |
22:24 | But I don't know how to recover or recreate file.
| |
22:25 | OK good night and thank you.
| |
22:25 | For me it's time to go to eat.
| |
22:29 | The question is "How to create new rsa keys for the image and the server ?"
| |
22:29 | See you later.
| |
22:51 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |