IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 17 September 2017 (all times are UTC)
| 00:07 | <fuzzmew> I tried typing this, but all I get is busybox so it tries to boot, but it won't
| |
| 00:07 | sed 's/^dns=dnsmasq/# ltsp-pnp: dns=dnsmasq/' -i /etc/NetworkManager/NetworkManager.conf && sed 's/^port=0/# ltsp-pnp: port=0/' -i /etc/dnsmasq.d/ltsp-server-dnsmasq.conf && service network-manager restart && service dnsmasq restart
| |
| 00:09 | <vagrantc> separate issue that that would solve
| |
| 00:10 | <fuzzmew> huh? Oh sorry too much info?
| |
| 00:10 | <vagrantc> it's fine, fit on one line :)
| |
| 00:10 | it just wouldn't likely address the issue you had earlier, but now that you have a busybox prompt, it sounds like you've gotten past that initial issue
| |
| 00:11 | <fuzzmew> Its so weird, I have to type that line every time I reboot server or I get the first problem.
| |
| 00:12 | <vagrantc> are you running a live image or something?
| |
| 00:13 | <fuzzmew> No it is an install of Mint 18.2
| |
| 00:14 | <vagrantc> oh, not sure how good the support for Mint is
| |
| 00:14 | <fuzzmew> oh poop
| |
| 00:15 | <vagrantc> there are some people on this channel who might know better
| |
| 00:15 | <fuzzmew> I sure wish there was a way to run on mint. Nothing against ubuntu, its great, I just need mint on my server.
| |
| 00:15 | I only run ubuntu on my laptops
| |
| 00:15 | <vagrantc> fuzzmew: that sounds like a very odd division of OSes
| |
| 00:16 | <fuzzmew> I'm weird.
| |
| 00:16 | I run openBSD on my router, CentOS on my pbx, mint on the terminal server, ubuntu on my laptops and mac on my workstation
| |
| 00:17 | * vagrantc does all Debian | |
| 00:17 | <fuzzmew> I also like debian to run as a router, becausae its a bitch to crack into.
| |
| 00:19 | Even kevin mitnick would have a bitch of a time trying to crack a debian box.
| |
| 00:19 | <vagrantc> so, there's some mint support in the ltsp codebase, since it's *basically* ubuntu, but they do enough differently that sometimes it needs some additional code
| |
| 00:20 | though the ltsp-pnp method *should* work fairly straightforward...
| |
| 00:21 | <fuzzmew> huh. I wonder do I gotta re install to start over?
| |
| 00:22 | <vagrantc> with ltsp-pnp, you just build an LTSP image out of the running server
| |
| 00:22 | i don't know what you've done so far
| |
| 00:23 | though the problems you're having are most likely unreleated
| |
| 00:23 | <fuzzmew> funny, that is what I did.........god how did I gunge it up that bad?
| |
| 00:24 | <vagrantc> there are some issues with network-manager on ubuntu (and presumably derived) distributions
| |
| 00:25 | and where did /srv/tftpboot come from?
| |
| 00:25 | fuzzmew: did you use ltsp-config dnsmasq ?
| |
| 00:25 | fuzzmew: and what version of ltsp are you running? ltsp-info
| |
| 00:26 | <fuzzmew> it was not there to begin with I made a symlink
| |
| 00:26 | Yes used ltsp-config dnsmasq
| |
| 00:27 | <vagrantc> that should configure /var/lib/tftpboot, not /srv/tftpboot
| |
| 00:28 | <fuzzmew> that is the original setting shall I erase the sumlink?
| |
| 00:28 | Ok, pastebin coming up
| |
| 00:29 | https://pastebin.com/hHW5XtWR
| |
| 00:32 | <vagrantc> do you know where the ldm* and ltsp* packages came from? they have an unusual version
| |
| 00:32 | <fuzzmew> from the pnp page lemme find it
| |
| 00:32 | <vagrantc> and looks like you've also got a chroot, with fairly old packages
| |
| 00:32 | !ltsp-pnp | echo fuzzmew
| |
| 00:32 | <ltsp> fuzzmew ltsp-pnp: ltsp-pnp is the recommented method to install and maintain LTSP for "usual" setups. Since it doesn't involve chroots, it requires little to no command line to maintain it. It automatically supports both thin and fat ltsp clients. https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
| 00:33 | Royale_AJS has joined IRC (Royale_AJS!~Royale_AJ@75-128-100-130.dhcp.sgnw.mi.charter.com) | |
| 00:33 | <vagrantc> seems like you've got all sorts of random ltsp packages on your system
| |
| 00:34 | <fuzzmew> https://help.ubuntu.com/community/UbuntuLTSP/...
| |
| 00:34 | oh poop
| |
| 00:35 | https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
| 00:36 | I could swear this is the one I used
| |
| 00:36 | dang
| |
| 00:36 | <vagrantc> ?
| |
| 00:36 | <fuzzmew> That last URL is the instructions I used, is it the wrong one?
| |
| 00:37 | <vagrantc> well, we're now recommending ltsp-manager as an easy-to-use frontend.
| |
| 00:37 | no idea if it works on mint
| |
| 00:38 | the first public release for ltsp-manager was end of august, so it's kind of new
| |
| 00:38 | though based on stuff used in greek schools for years
| |
| 00:38 | fuzzmew: it sounds like you've got a number of different attempts at LTSP on your system; you might want to try starting with a clean slate
| |
| 00:40 | otherwise some old configurations might interfere with what you've got
| |
| 00:42 | <fuzzmew> Ok, now runing that, looks good, doing a rebuild of the image now.
| |
| 00:43 | still hits the busybox, do I need to reboot the server?
| |
| 00:44 | <vagrantc> any messages before you get to busybox?
| |
| 00:45 | <fuzzmew> yes, it says setting up the nbd client and nbd@ registered device at major 43 something or other
| |
| 00:45 | Begin running screipts local premount thing then running scripts local block ... done over and over
| |
| 00:46 | <vagrantc> from busybox: mount
| |
| 00:46 | <fuzzmew> then gave up waiting for reoot device then busybox
| |
| 00:46 | Ok I typed mount
| |
| 00:46 | <vagrantc> output? screenshot? etc.
| |
| 00:46 | <fuzzmew> I can'[t screencap
| |
| 00:47 | its a bunch of shint
| |
| 00:47 | lemme try
| |
| 00:47 | tmpfs on /run type fptfs
| |
| 00:47 | rootfs on / type rootfs/ rw
| |
| 00:47 | initramfs m random non blocking pool is initialized
| |
| 00:49 | <vagrantc> mostly looking for stuff mounted on /root or /target or /rofs
| |
| 00:50 | also, the output of /proc/cmdline would be useful
| |
| 00:50 | er, the contents ... e.g. cat /proc/cmdline
| |
| 00:50 | <fuzzmew> proc on /proc type proc (rw,nosuid,nodev.noexect.relatime)
| |
| 00:51 | <vagrantc> mostly looking for stuff mounted on /root or /target or /rofs
| |
| 00:54 | <fuzzmew> BOOT_IMAGE=vmlinuz-4.4.0-93-generic ro initrd=initrd.img-4.4.0-83-generic init=/sbin/init-ltsp forcepae root=/dev/nbd0 BOOTIF=01-08-00-27-09-a1-b3
| |
| 00:55 | rootfs on / type rootfs (rw)
| |
| 00:55 | no target or rofs found
| |
| 00:56 | <vagrantc> or /root ?
| |
| 00:56 | <fuzzmew> nope
| |
| 00:56 | <vagrantc> sounds like the connection to your NBD server failed
| |
| 00:56 | <fuzzmew> strange, I wonder what causes that?
| |
| 00:57 | <vagrantc> probably DHCP didn't tell it the right information
| |
| 00:57 | it looks like you don't have /etc/ltsp/update-kernels.conf configured with IPAPPEND=3
| |
| 00:57 | <fuzzmew> I have seen that, in what file does it belong?
| |
| 00:58 | <vagrantc> it looks like you don't have /etc/ltsp/update-kernels.conf configured with IPAPPEND=3
| |
| 00:58 | <fuzzmew> dang lag, sorry
| |
| 00:58 | <vagrantc> you also might want to purge /opt/ltsp/* and re-generate your images
| |
| 00:58 | as you've got a chroot and you're trying to do ltsp-pnp ... might cause some issues
| |
| 01:00 | <fuzzmew> Ok, will purge /opt/ltsp and re generate
| |
| 01:01 | <vagrantc> fuzzmew: and you've updated update-kernels.conf ?
| |
| 01:01 | <fuzzmew> I don't think so, what do I type for that?
| |
| 01:02 | Oh u mean iappend 3? yes
| |
| 01:02 | that is in there
| |
| 01:02 | <vagrantc> it doesn't look like it was there before you booted your client ...
| |
| 01:02 | <fuzzmew> weird...shall I pastebin you the file? maybe I did not put it in correctly?
| |
| 01:02 | <vagrantc> also might need to remove /boot/pxelinux*
| |
| 01:03 | <fuzzmew> Ok will remove that
| |
| 01:03 | <vagrantc> so /opt/ltsp is empty?
| |
| 01:03 | <fuzzmew> yes
| |
| 01:03 | <vagrantc> grep IPAPPEND /etc/ltsp/update-kernels.conf
| |
| 01:04 | <fuzzmew> system1 ltsp # grep IPAPPEND /etc/ltsp/update-kernels.conf
| |
| 01:04 | # Use pxelinux/syslinux's IPAPPEND parameter to add useful networking and
| |
| 01:04 | #IPAPPEND=3
| |
| 01:04 | IPAPPEND=3
| |
| 01:04 | system1 ltsp #
| |
| 01:05 | <vagrantc> ok, then regenerate the image, if you've got ltsp-manager installed, go ahead and use that
| |
| 01:05 | <fuzzmew> ok
| |
| 01:05 | just regenerate, No initial setup right?
| |
| 01:06 | <vagrantc> re-running initial setup shouldn't hurt
| |
| 01:06 | and then try to boot again ...
| |
| 01:06 | hopefully it works ... you might be the first to test ltsp-manager on mint
| |
| 01:07 | <fuzzmew> any info I can provide from this I will do my best to help others also
| |
| 01:08 | ok attempting to boot client
| |
| 01:09 | Begin: running scripts local block .. done over and over
| |
| 01:10 | busy box says ALERT! /dev/nbd0 does not exist
| |
| 01:10 | <vagrantc> run "pgrep -l -a -f nbd" on the server
| |
| 01:10 | <fuzzmew> ok
| |
| 01:11 | system1 ltsp # pgrep -l -a -f nbd
| |
| 01:11 | 903 /bin/nbd-server
| |
| 01:11 | system1 ltsp
| |
| 01:13 | <vagrantc> from the busybox prompt, cat /proc/cmdline
| |
| 01:13 | fuzzmew: you can just paste the output
| |
| 01:13 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 246 seconds) | |
| 01:14 | <vagrantc> fuzzmew: from /proc/cmdline, mostly interested in if it put something into ip=
| |
| 01:14 | <fuzzmew> it won't paste across machines
| |
| 01:14 | how do I screen shot virtualbox vm from my mac?
| |
| 01:14 | <vagrantc> i don't know virtualbox
| |
| 01:15 | fuzzmew: but if i ask you to run a command, just paste the output, not the line you typed the command and the line after
| |
| 01:16 | <fuzzmew> oh shit
| |
| 01:23 | <vagrantc> ?
| |
| 01:29 | <fuzzmew> Ok I think I found a way to video capture, I will upload it to youtube then send the url
| |
| 01:31 | <vagrantc> !pae
| |
| 01:31 | <ltsp> I do not know about 'pae', but I do know about these similar topics: 'non-pae'
| |
| 01:31 | <vagrantc> even a useful screenshot would be fine
| |
| 01:31 | !non-pae
| |
| 01:31 | <ltsp> non-pae: To allow non-pae thin clients to boot in Ubuntu 12.04+, one can install the debian 486 kernel in the chroot: https://packages.debian.org/wheezy/linux-image-3.2.0-4-486
| |
| 01:43 | <fuzzmew> https://www.youtube.com/watch?v=Ndn9HbU3yus&feature=youtu.be
| |
| 01:50 | adrianor1 has joined IRC (adrianor1!~adrianorg@177.18.102.121) | |
| 01:53 | <fuzzmew> updated one
| |
| 01:53 | adrianorg has left IRC (adrianorg!~adrianorg@177.156.62.231, Ping timeout: 240 seconds) | |
| 01:54 | <fuzzmew> https://youtu.be/JyNJ2125odY
| |
| 01:55 | <vagrantc> could you just send some screenshots rather than videos?
| |
| 01:56 | all i'm asking for is the output of /proc/cmdline, specifically if it has an ip= portion
| |
| 01:56 | i can't believe virtualbox has a video feature but no screenshot
| |
| 01:58 | anyways, looks like it has ip= ...
| |
| 01:59 | fuzzmew: is your server's ip address 192.168.6.1 ?
| |
| 01:59 | er, 192.168.1.6
| |
| 02:00 | fuzzmew: what's in the server's /etc/nbd/config.d/* ?
| |
| 02:00 | fuzzmew: could you paste that?
| |
| 02:31 | <fuzzmew> -bash: cd: /etc/nbd: No such file or directory
| |
| 02:38 | https://scontent-lga3-1.xx.fbcdn.net/v/t1.0-9/21751508_1906115559711896_4167171606794704554_n.jpg?oh=f3cce93258f6f3b910d0462474a8d6a5&oe=5A5F4FE1
| |
| 02:47 | <vagrantc> wat?
| |
| 02:47 | earlier, you said nbd-server was running ...
| |
| 02:47 | ls /etc/nbd* ?
| |
| 02:54 | well, i went ahead and filed #875990
| |
| 03:16 | * vagrantc waves | |
| 03:16 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 03:18 | <fuzzmew> Well, I thought it was.....
| |
| 03:19 | I will just come back tomorrow then.
| |
| 07:02 | <alkisg> fuzzmew: it's /etc/nbd-server, not /etc/nbd
| |
| 07:02 | fuzzmew: the problem is that /etc/nbd-server/conf.d/ltsp_i386.conf has the wrong exports line there
| |
| 08:51 | Statler has joined IRC (Statler!~Georg@p579FE7F6.dip0.t-ipconnect.de) | |
| 09:04 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 09:42 | ||cw has left IRC (||cw!~chrisw@unaffiliated/cw/x-1182934, Ping timeout: 255 seconds) | |
| 09:46 | ||cw has joined IRC (||cw!~chrisw@unaffiliated/cw/x-1182934) | |
| 10:30 | tek_ has joined IRC (tek_!tek@kapsi.fi) | |
| 10:49 | adrianor1 is now known as adrianorg | |
| 12:20 | legg has joined IRC (legg!18b2956f@gateway/web/freenode/ip.24.178.149.111) | |
| 12:56 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
| 13:03 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Read error: No route to host) | |
| 13:03 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
| 13:15 | <legg> Can some one please answer a question? Will the /var/lib directory be saved separately for each client on the LTSP?
| |
| 13:21 | Also will the /etc directory be saved separately for each client on the LTSP?
| |
| 13:22 | Thanks for your help in advance.
| |
| 13:22 | <highvoltage> legg: on ltsp clients, all changes outside of home are committed to RAM and discarded on shutdown
| |
| 13:22 | <legg> Thank you highvoltage
| |
| 13:26 | I think I can still accomplish my goal, which is to run folding at home on a 6 different diskless workstations. I would just need to store the work cache and config.xml files in the home directory.
| |
| 13:27 | Can you have the thin client auto login a user?
| |
| 13:27 | <highvoltage> yep, see lts.conf
| |
| 13:27 | <legg> Thank you again highvoltage
| |
| 13:30 | <alkisg> legg: for local processing, you should run the apps on the client, i.e. you should use ltsp fat clients
| |
| 13:30 | !fatclients
| |
| 13:30 | <ltsp> fatclients: Nowadays LTSP supports thin and fat clients. They are both diskless and netbooted from the same LTSP chroot, but while thin clients run the session on the server and transfer the screen, fat clients run the session locally with their own CPU/RAM, thus performing amazingly better. See also !ltsp-pnp and https://help.ubuntu.com/community/UbuntuLTSP/FatClients
| |
| 13:31 | <alkisg> One way to install ltsp to support fat clients, is with ltsp-pnp:
| |
| 13:31 | !ltsp-pnp
| |
| 13:31 | <ltsp> ltsp-pnp: ltsp-pnp is the recommented method to install and maintain LTSP for "usual" setups. Since it doesn't involve chroots, it requires little to no command line to maintain it. It automatically supports both thin and fat ltsp clients. https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
| 13:32 | <legg> thanks alkisg
| |
| 14:13 | Royale_AJS has left IRC (Royale_AJS!~Royale_AJ@75-128-100-130.dhcp.sgnw.mi.charter.com, Quit: Royale is leaving) | |
| 14:54 | Statler has left IRC (Statler!~Georg@p579FE7F6.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 15:47 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 16:31 | Eric5 has joined IRC (Eric5!~eric@sdi.iut-valence.fr) | |
| 16:35 | mmarconm has joined IRC (mmarconm!~mmarconm@179.254.234.47) | |
| 17:28 | markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it) | |
| 17:42 | mmarconm has left IRC (mmarconm!~mmarconm@179.254.234.47, Quit: Leaving) | |
| 18:01 | Eric5 has left IRC (Eric5!~eric@sdi.iut-valence.fr, Ping timeout: 255 seconds) | |
| 18:01 | markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, ) | |
| 18:51 | legg has left IRC (legg!18b2956f@gateway/web/freenode/ip.24.178.149.111) | |
| 19:22 | <fuzzmew> https://scontent-sea1-1.xx.fbcdn.net/v/t1.0-9/21765095_1906449949678457_3495389920533738536_n.jpg?oh=c34ae3b1e774e5f19afb98dfb96ce637&oe=5A417E6D
| |
| 19:39 | gverv has joined IRC (gverv!8b5b4936@gateway/web/freenode/ip.139.91.73.54) | |
| 19:49 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 20:01 | <alkisg> fuzzmew: I already gave you the solution, did you not see it?
| |
| 20:02 | sudo nano /etc/nbd-server/conf.d/ltsp_i386.conf
| |
| 20:02 | exportname = /opt/ltsp/images/i386.img
| |
| 20:02 | Fix that line and restart nbd server...
| |
| 20:16 | <fuzzmew> sorry i must not have seen it, will try this, thank you
| |
| 20:21 | did not work, restarted nbd server and client does not boot
| |
| 20:46 | fuzzmew has left IRC (fuzzmew!~fuzzmew@96-18-71-242.cpe.cableone.net, Quit: Leaving) | |
| 20:54 | gverv has left IRC (gverv!8b5b4936@gateway/web/freenode/ip.139.91.73.54, Ping timeout: 260 seconds) | |