IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 9 January 2019 (all times are UTC)
| 00:54 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 01:20 | josefig_ has joined IRC (josefig_!~jose@unaffiliated/josefig) | |
| 01:23 | josefig has left IRC (josefig!~jose@unaffiliated/josefig, Ping timeout: 244 seconds) | |
| 04:57 | josefig has joined IRC (josefig!~jose@unaffiliated/josefig) | |
| 05:02 | josefig_ has left IRC (josefig_!~jose@unaffiliated/josefig, *.net *.split) | |
| 05:02 | ||cw has left IRC (||cw!~chrisw@unaffiliated/cw/x-1182934, *.net *.split) | |
| 05:27 | <ZAJDAN> yeees...via 'dbus-launch epoptes' it works
| |
| 07:15 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:23 | kjackal has joined IRC (kjackal!~quassel@62.103.222.236) | |
| 08:07 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 09:22 | kjackal has left IRC (kjackal!~quassel@62.103.222.236, Read error: Connection reset by peer) | |
| 09:22 | kjackal has joined IRC (kjackal!~quassel@62.103.222.236) | |
| 09:38 | kjackal has left IRC (kjackal!~quassel@62.103.222.236, Read error: Connection reset by peer) | |
| 09:38 | kjackal has joined IRC (kjackal!~quassel@62.103.222.236) | |
| 11:05 | spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Ping timeout: 250 seconds) | |
| 13:22 | <mwalters> oh cool, I can use this too on my remote servers!
| |
| 13:22 | (without having to launch the VM viewer)
| |
| 13:22 | thanks quinox ;)
| |
| 13:34 | spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut) | |
| 13:39 | <alkisg> If your master server has a static IP, you can set your other servers as epoptes-clients of the master server. Then you can control them with a single click from within the master epoptes.
| |
| 14:04 | (or even a dynamic ip with dyndns etc)
| |
| 14:18 | ||cw has joined IRC (||cw!~chrisw@unaffiliated/cw/x-1182934) | |
| 14:26 | <ZAJDAN> alkisg-> are You here?
| |
| 14:27 | JuJUBee has joined IRC (JuJUBee!~knichel@24.148.115.153) | |
| 14:29 | <JuJUBee> Just installed fresh server (xubuntu 18.04) with LTSP. Followed docs for chrootless and dual nic. I am installing on VM where one nic will be internet and other will be local LAN. After restart the sch-scripts ran but second nic does not have IP and first is connected to internet.
| |
| 14:30 | <alkisg> ZAJDAN: not all the time, but I look at the channel a few times per day
| |
| 14:31 | JuJUBee: you're supposed to put a static ip on the second nic from network-manager
| |
| 14:31 | Create a static IP connection and set it to 192.168.67.1
| |
| 14:33 | <JuJUBee> alkisg, my bad, missed that. Thanks
| |
| 14:33 | Can that be changed to a different network? I currently use 192.168.6.0/24 inside my LAN
| |
| 14:51 | <mwalters> alkisg: from what I can gather, I just need to make "server" resolvable to my "master" server on the remote servers?
| |
| 14:51 | (resolvable to my "master" epoptes server)
| |
| 14:54 | <alkisg> mwalters: put this https://termbin.com/t3ry in your remote servers, in /etc/NetworkManager/dispatcher.d/20sch-scripts, and chmod +x it. Change the ip to your master server external ip, and port-forward port 789 if needed.
| |
| 14:54 | JuJUBee: if you grep all the code for 192.168.67 and replace it, yes, but it's not configurable
| |
| 14:54 | E.g. check the sch-scripts script that you downloaded; the .67 there needs to be replaced a few times
| |
| 14:55 | <JuJUBee> OK, no biggie, more hassle than its worth
| |
| 14:55 | I only have a few other static IPs that will need changing.
| |
| 14:59 | Just rebooted server and booted a client, client doesn't have internet. Is the script in if-up supposed to insert the iptables rule to masquerade?
| |
| 15:02 | <alkisg> Yes
| |
| 15:02 | Can the client ping the server;
| |
| 15:02 | Can it ping 8.8.8.8;
| |
| 15:02 | Does it get a reply with `hosts www.google.com`?
| |
| 15:02 | <JuJUBee> Yes, ping server and 8.8.8.8
| |
| 15:03 | <alkisg> Then nat works
| |
| 15:03 | Does dns work?
| |
| 15:03 | I.e. host www.google.com
| |
| 15:05 | <JuJUBee> No, Not Found: 2(SERVFAIL)
| |
| 15:05 | <alkisg> There are many ways to configure dns, which one did you choose?
| |
| 15:06 | Did you run ltsp-config dnsmasq --enable-dns?
| |
| 15:06 | Did you put DNS_SERVER in lts.conf?
| |
| 15:06 | <JuJUBee> ltsp-config dnsmasq --no-proxy-dhcp
| |
| 15:06 | as per directions
| |
| 15:07 | <alkisg> http://wiki.ltsp.org/wiki/Installation/Ubuntu => Additionally, you may choose to append --enable-dns in the commands below, to configure dnsmasq to act as a DNS server as well, which will then speed up DNS lookups and allow you to easily blacklist certain sites if you need to. If you don't, you might need to define something like DNS_SERVER="8.8.8.8 8.8.4.4" in lts.conf.
| |
| 15:07 | These are the directions :)
| |
| 15:07 | Let me paste the last part, I don't know if IRC cut the long line there,....
| |
| 15:07 | If you don't, you might need to define something like DNS_SERVER="8.8.8.8 8.8.4.4" in lts.conf.
| |
| 15:09 | <JuJUBee> Is it still ok to use --no-proxy-dhcp?
| |
| 15:09 | <alkisg> Of coursre
| |
| 15:11 | <JuJUBee> So now I need to ltsp-update-image ? or not needed when editing the lts.conf?
| |
| 15:11 | <alkisg> Are you doing both options now?
| |
| 15:12 | Both running ltsp-config AND putting DNS_SERVER in lts.conf?
| |
| 15:12 | Choose only ONE of them
| |
| 15:12 | No need to run ltsp-update-image in any case
| |
| 15:12 | <JuJUBee> I only added DNS to lts.conf
| |
| 15:12 | <alkisg> Why did you ask this? (05:09:19 μμ) JuJUBee: Is it still ok to use --no-proxy-dhcp?
| |
| 15:12 | OK, if you added dns in lts.conf, reboot the client
| |
| 15:12 | It should now work
| |
| 15:24 | jgee has joined IRC (jgee!~jgee@190.159.118.121) | |
| 15:26 | <JuJUBee> Yep, thanks a ton.
| |
| 15:32 | Im running the update-image since I installed a new package. Im getting a bunch of "unrecognized xattr prefix system.posix_acl_..." messages. Read online it is nothing to worry about? Is that correct
| |
| 15:35 | <alkisg> Indeed
| |
| 15:39 | <JuJUBee> ok
| |
| 15:41 | TheFlyingCrocodi has joined IRC (TheFlyingCrocodi!56073c89@gateway/web/freenode/ip.86.7.60.137) | |
| 15:41 | <TheFlyingCrocodi> !greeter
| |
| 15:41 | <ltsp> I do not know about 'greeter', but I do know about these similar topics: 'greek'
| |
| 15:43 | <TheFlyingCrocodi> im having an issue where i cant update the LTSP logo on the login screen ive updated the themes and changed the default symlink to point to the LTSP theme but none of the changes ive made are being put into effect after updating the image
| |
| 15:47 | and any google searches give me nothing appart from "works fine for me"
| |
| 15:51 | GodFather has joined IRC (GodFather!~rcc@109.sub-174-238-15.myvzw.com) | |
| 16:03 | <TheFlyingCrocodi> !ldm
| |
| 16:03 | <ltsp> ldm: LDM is the LTSP Display Manager, required for LTSP thin/fat clients, because it authenticates the users to the server via SSH.
| |
| 16:14 | kjackal has left IRC (kjackal!~quassel@62.103.222.236, Ping timeout: 272 seconds) | |
| 16:21 | <TheFlyingCrocodi> i cant seem to update LDM at all
| |
| 16:32 | <alkisg> TheFlyingCrocodi: what's the output of `sudo ltsp-info | nc termbin.com 9999` ?
| |
| 16:42 | <TheFlyingCrocodi> No LSB modules are available. https://termbin.com/m0r3
| |
| 16:43 | <alkisg> TheFlyingCrocodi: which of the chroots are you trying in?
| |
| 16:44 | Also, are you trying to use the chroots, or are you running `ltsp-update-image -c /` which then creates the image out of the server / ?
| |
| 16:44 | <TheFlyingCrocodi> armhf is the most important one the amd64 is just me testing different clients
| |
| 16:44 | <alkisg> Because your installation is a bit of a mess, it looks like you're trying to do it in many different ways
| |
| 16:44 | kjackal has joined IRC (kjackal!~quassel@62.103.222.236) | |
| 16:44 | <TheFlyingCrocodi> im not adding -c but yes im updating the image
| |
| 16:45 | <alkisg> So, you're booting raspberry pis and they have the old logo?
| |
| 16:45 | <TheFlyingCrocodi> yep
| |
| 16:45 | <alkisg> Or are you testing with amd64 now?
| |
| 16:45 | OK. Are you using epoptes?
| |
| 16:45 | <TheFlyingCrocodi> yes
| |
| 16:46 | <alkisg> Are the clients thin or fat? Green or blue icons in epoptes?
| |
| 16:46 | <TheFlyingCrocodi> thin
| |
| 16:46 | <alkisg> OK, try this: right click on a client, open root terminal
| |
| 16:46 | Then, using the "ls" command, see if your changes are there
| |
| 16:46 | E.g. ls /usr/share/ldm/themes/whatever
| |
| 16:47 | If they are there, then run: getltscfg -a
| |
| 16:47 | And verify that the LDM directives actually reach the client
| |
| 16:47 | <TheFlyingCrocodi> okay ill try that
| |
| 16:52 | i can open the terminal but its not accepting commands i have no root@serv
| |
| 16:52 | <alkisg> On the client itself, try `ltsp-localapps xterm`
| |
| 16:52 | and see if you can make it from there
| |
| 16:53 | It sounds like you don't have epoptes-client installed properly in the chroot
| |
| 17:04 | <TheFlyingCrocodi> well i only have 2 user atm and the admin user cant log on and my test one cant open local apps but navigating in caja on the client shows the updated logo
| |
| 17:06 | and running get ltsconf says it cant find the conf
| |
| 17:12 | ive made a symlink to the amd64 one
| |
| 17:12 | <alkisg> TheFlyingCrocodi: caja on the thin client shows the server, not the client
| |
| 17:12 | So it's useless
| |
| 17:13 | !screen_02
| |
| 17:13 | <ltsp> screen_02: To get a root shell on an Ubuntu thin client: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using_a_shell_SCREEN
| |
| 17:13 | <alkisg> !root
| |
| 17:13 | <ltsp> I do not know about 'root', but I do know about these similar topics: 'ROOT_PASSWORD_HASH'
| |
| 17:13 | <alkisg> !ROOT_PASSWORD_HASH
| |
| 17:13 | <ltsp> ROOT_PASSWORD_HASH: To be able to login as root in vt1, with password "qwer1234", put this in lts.conf: INIT_COMMAND_ROOT_HASH="sed 's!^root:[^:]*:!root:\$6\$p2LdWE6j\$PDd1TUzGvvIkj9SE8wbw1gA/MD66tHHlStqi1.qyv860oK47UnKcafSKqGp7cbgZUPlgyPv6giCVyCSCdJt1b0:!' -i /etc/shadow"
| |
| 17:13 | <alkisg> !localxterm
| |
| 17:13 | <ltsp> localxterm: Any applications that you launch on a thin client actually runs on the server, not on the client itself. If you want to open a program on the client locally, you can type 'ltsp-localapps <program>' in a run dialog or in a terminal. For example, 'ltsp-localapps xterm' to open a terminal running on the client.
| |
| 17:13 | <alkisg> TheFlyingCrocodi: there are many ways to get a shell on the *client*, not on the server via a thin client
| |
| 17:13 | Use one of the above ^
| |
| 17:17 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 18:35 | JuJUBee has left IRC (JuJUBee!~knichel@24.148.115.153, Quit: Leaving) | |
| 19:27 | GodFather has left IRC (GodFather!~rcc@109.sub-174-238-15.myvzw.com, Ping timeout: 240 seconds) | |
| 20:03 | mixone1995 has joined IRC (mixone1995!bc7f6b99@gateway/web/freenode/ip.188.127.107.153) | |
| 20:19 | mixone1995 has left IRC (mixone1995!bc7f6b99@gateway/web/freenode/ip.188.127.107.153) | |
| 20:35 | GodFather has joined IRC (GodFather!~rcc@2600:1011:b127:a1d5:95d3:6e04:4912:c01f) | |
| 20:41 | kjackal has left IRC (kjackal!~quassel@62.103.222.236, Ping timeout: 268 seconds) | |
| 20:41 | GodFather has left IRC (GodFather!~rcc@2600:1011:b127:a1d5:95d3:6e04:4912:c01f, Ping timeout: 250 seconds) | |
| 21:25 | TheFlyingCrocodi has left IRC (TheFlyingCrocodi!56073c89@gateway/web/freenode/ip.86.7.60.137, Ping timeout: 256 seconds) | |
| 22:23 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection) | |
| 22:57 | jgee has left IRC (jgee!~jgee@190.159.118.121, Quit: The Lounge - https://thelounge.github.io) | |
| 23:23 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
| 23:27 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Read error: Connection reset by peer) | |
| 23:35 | jgee has joined IRC (jgee!~jgee@190.159.118.121) | |
| 23:36 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
| 23:53 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |