03:21 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 255 seconds) | |
08:42 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
09:16 | Klimm has left IRC (Klimm!~Georg@p5B30E384.dip0.t-ipconnect.de, Remote host closed the connection) | |
09:23 | <meo> alkisg: guess what, you were right, it was a broken kernel and image -r helped
| |
09:24 | I guess long time ago I allowed ubuntu to update but never regenerated the image
| |
09:24 | and then when I did this popped up
| |
09:30 | adrianor1 has joined IRC (adrianor1!~adrianorg@187.115.106.99) | |
09:33 | adrianorg has left IRC (adrianorg!~adrianorg@187.113.250.127, Ping timeout: 256 seconds) | |
11:32 | section1 has joined IRC (section1!~section1@vps-1722311-x.dattaweb.com) | |
12:04 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
13:42 | mwalters has joined IRC (mwalters!~ubox@c-73-152-61-86.hsd1.va.comcast.net) | |
13:43 | <mwalters> Starting to think about upgrading to ltsp19+... looking at the vm image option... am I correct in thinking that this should be 100% ok to do a headless server with, since none of the client image is generated from the server root?
| |
13:45 | eh, this looks like unneeded complexity, though... at least for me
| |
13:45 | and looks like I could add additional boot options if I wanted more client image options in the future
| |
13:46 | (by starting chrootless)
| |
14:02 | <alkisg> mwalters: indeed
| |
14:03 | In general, if you're using the server for other things as well, e.g. it's also an ldap server or a web server etc etc, then a VM or a chroot do make sense, while if the server is mainly just an LTSP server, then chrootless sounds best
| |
14:03 | <mwalters> Yeah, you're right. It'll be ltsp only. Headless started to make less sense the moment I thought about things like epoptes
| |
14:05 | <alkisg> What's your usage scenario, how many clients etc?
| |
14:05 | <mwalters> 4 separate servers separated by wan
| |
14:06 | <alkisg> meo: nice, thanks for the update
| |
14:06 | mwalters: 4 separate servers => then it does make sense to have those headless and maintain a single image=VM that you sync between servers
| |
14:06 | <mwalters> Client count varies, but larges is like 30 clients
| |
14:06 | <alkisg> Well, if you do want that, to maintain a single image and not 4 separate ones
| |
14:06 | <mwalters> smallest is 5
| |
14:07 | yeah, we have reasonable connections, so syncing an image over wan isn't a big deal
| |
14:07 | (and I really wanted to get there eventually ;) )
| |
14:07 | <alkisg> And of course chrootless can do that as well
| |
14:07 | <mwalters> right now (ltsp5) they're all just clones of a base VM (the ltsp servers)
| |
14:08 | <alkisg> I think in your case I'd go for minimal, headless servers, a single VM, and I'd rsync the VM or the generated squashfs
| |
14:09 | <meo> alkisg: is image -r stateful? if I run this again will it revert to the newer kernel?
| |
14:09 | <mwalters> how does epoptes work in that type of environment? Right now I'm using virt-manager to connect to a remote client to use it if needed
| |
14:09 | <alkisg> meo: yes; it just renames stuff, no overwriting involved
| |
14:09 | <mwalters> since ssh -Y is sllooooooooow
| |
14:09 | <alkisg> mwalters: you can specify that the epoptes server is one of the "fat" clients
| |
14:09 | If you have an admin pc, you can indicate that
| |
14:10 | <mwalters> ah ok... so I could have a netbooting VM act as the epoptes server itself
| |
14:10 | (or any VM with epoptes on it)
| |
14:11 | <alkisg> yeah
| |
14:16 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Remote host closed the connection) | |
14:23 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
15:24 | woernie has joined IRC (woernie!~werner@pD9E8BE9E.dip0.t-ipconnect.de) | |
16:38 | woernie has left IRC (woernie!~werner@pD9E8BE9E.dip0.t-ipconnect.de, Ping timeout: 255 seconds) | |
16:38 | woernie has joined IRC (woernie!~werner@pD9E8BE9E.dip0.t-ipconnect.de) | |
17:11 | <alkisg> !learn apt-purge as `To clean up packages in rc state: apt purge --auto-remove $(dpkg -l | awk '/^rc/ { print $2 }')`
| |
17:11 | <ltspbot> The operation succeeded.
| |
17:12 | <alkisg> !apt-purge
| |
17:12 | <ltspbot> apt-purge: To clean up packages in rc state: apt purge --auto-remove $(dpkg -l | awk '/^rc/ { print $2 }')
| |
18:05 | JuJUBee has joined IRC (JuJUBee!~knichel@24.148.115.153) | |
18:07 | <JuJUBee> I just built a new ltsp server following the installation docs. When I boot a client, it finds the server but I get the following message "Begin: Retrying nfs mount ... mount call failed - server replied: Permission denied"
| |
18:07 | I never ran the ltsp nfs command
| |
18:09 | <alkisg> JuJUBee: well, run it :)
| |
18:09 | !install
| |
18:09 | <ltspbot> install: To install LTSP: https://ltsp.org/docs/installation/
| |
18:09 | <JuJUBee> alkisg, I thought sshfs is better?
| |
18:09 | <alkisg> https://ltsp.org/docs/installation/#nfs-server-configuration
| |
18:09 | <JuJUBee> I got the impression it was optional
| |
18:09 | <alkisg> JuJUBee: sshfs is the default for /home, nfs the default for / (rootfs)
| |
18:09 | <JuJUBee> Ah, ok
| |
18:09 | <alkisg> This isn't about nfs home
| |
18:10 | It's about nfs root
| |
18:10 | IF you wanted nfs home, you'd run: ltsp nfs --home=1
| |
18:10 | ....or such, see its man page
| |
18:10 | <JuJUBee> got it. Do I need to recreate the image?
| |
18:10 | <alkisg> No
| |
18:10 | <JuJUBee> Thanks
| |
18:10 | <alkisg> You don't even need to reboot the client
| |
18:10 | It should continue right when you start nfs :D
| |
18:11 | <JuJUBee> Cool
| |
18:56 | Teridon has left IRC (Teridon!~Teridon@dragon.teridon.com, Remote host closed the connection) | |
19:23 | foxhoundv has joined IRC (foxhoundv!d06285e6@dialup-208-98-133-230.fmtc.com) | |
19:23 | <foxhoundv> alkisg hello, this is Travis
| |
19:23 | <alkisg> Hi foxhoundv
| |
19:23 | !vnc-dide
| |
19:23 | <ltspbot> vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
| |
19:23 | <alkisg> Let's use vnc, it'll be lots faster
| |
19:25 | <foxhoundv> it says reverse connect failed
| |
19:25 | <alkisg> Do you have xorg access?
| |
19:25 | Or are you e.g. via ssh?
| |
19:26 | E.g. does `xrandr` work?
| |
19:27 | <foxhoundv> I am remoted in through ESXi
| |
19:27 | <alkisg> Does xrandr work where you are?
| |
19:27 | <foxhoundv> never heard of it
| |
19:27 | <alkisg> Just type that command
| |
19:27 | It shows the available resolutions
| |
19:27 | To see if you have xorg or not
| |
19:27 | type: xrandr
| |
19:28 | <foxhoundv> it doesn't say anything about xorg
| |
19:29 | <alkisg> Does your server have a graphical interface?
| |
19:29 | <foxhoundv> yes
| |
19:29 | i used a desktop iso
| |
19:30 | <alkisg> https://termbin.com/pveic
| |
19:30 | foxhoundv: this is the output of my xrandr
| |
19:30 | If it says "Can't open display", then that's a problem
| |
19:30 | Does `xrandr` show the resolutions for you, or does it show "can't open display"?
| |
19:31 | <foxhoundv> yes it shows the resolutions
| |
19:31 | <alkisg> Which distribution and desktop environment and version is that?
| |
19:32 | E.g. ubuntu mate 18.04?
| |
19:32 | <foxhoundv> Ubuntu 18.04.4 LTS
| |
19:32 | <alkisg> So, gnome?
| |
19:32 | <foxhoundv> yes
| |
19:33 | <alkisg> Can you type this?
| |
19:33 | xrandr | nc termbin.com 9999
| |
19:33 | And paste the output here
| |
19:33 | So that I see if you're using wayland or xorg
| |
19:33 | (I thought you would be using kubuntu, btw...)
| |
19:33 | <foxhoundv> https://termbin.com/n4sd
| |
19:34 | <alkisg> OK this is normal xorg, it's not wayland
| |
19:34 | Are you sure you typed the command correctly there?
| |
19:34 | x11vnc -connect srv1-dide.ioa.sch.gr
| |
19:38 | <foxhoundv> I removed the /etc/ltsp/ltsp.conf file because I would get problems when I tried to create the image
| |
19:39 | section1 has left IRC (section1!~section1@vps-1722311-x.dattaweb.com, Quit: Leaving) | |
19:42 | <foxhoundv> it worked
| |
19:43 | <alkisg> foxhoundv: nice, but we're not done yet
| |
19:43 | Now please login to that client, and do these steps
| |
19:43 | "Now boot a single client, add the LTSP PPA to your sources, and install the client-side packages: apt install --install-recommends ltsp epoptes-client"
| |
19:44 | When that's done, move to "ltsp mode netbooting"
| |
19:44 | Ping if you get any issues
| |
19:44 | <foxhoundv> So I won't be installing the ltsp-proposal?
| |
19:44 | <alkisg> No, you don't need the proposed ppa
| |
19:45 | anywhere
| |
19:49 | <foxhoundv> Ok, it is finishing the last part right now
| |
19:50 | Done
| |
19:55 | alkisg will I still need to run "ltsp image raspbian --mksquashfs-params='-comp lzo'" or just "ltsp image raspbian" at the end?
| |
20:13 | <alkisg> foxhoundv: nah you already ran that
| |
20:13 | It should be fine now
| |
22:24 | woernie has left IRC (woernie!~werner@pD9E8BE9E.dip0.t-ipconnect.de, Remote host closed the connection) | |
23:06 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving) | |