00:11 | ricotz_ has left IRC (ricotz_!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
01:43 | gp has left IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net, Quit: Leaving) | |
05:29 | fuzzmew has joined IRC (fuzzmew!~fuzzmew@71.216.56.79) | |
05:40 | <fuzzmew> i kind of cheated last night and used a screen share app, bleah,
| |
05:42 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: :wq) | |
05:42 | quinox has joined IRC (quinox!~quinox@ghost.qtea.nl) | |
05:53 | fuzzmew has left IRC (fuzzmew!~fuzzmew@71.216.56.79, Quit: Ex-Chat) | |
07:05 | <gehidore> dirty
| |
07:05 | ;)
| |
07:11 | mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk) | |
07:24 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
07:42 | robb_nl has joined IRC (robb_nl!~robb_nl@ip-83-134-23-150.dsl.scarlet.be) | |
08:11 | FGXR6 has left IRC (FGXR6!~phantom@ppp121-45-182-65.lns20.syd7.internode.on.net, Ping timeout: 240 seconds) | |
08:18 | FGXR6 has joined IRC (FGXR6!~phantom@121.45.182.65) | |
08:24 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection) | |
08:42 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
09:27 | fuzzmew has joined IRC (fuzzmew!~fuzzmew@71.216.56.79) | |
09:28 | <fuzzmew> hi
| |
09:28 | <alkisg> Hello fuzzmew
| |
09:29 | <fuzzmew> Hi sorry to fill the room with chatter lately.
| |
09:30 | <alkisg> Haha no worries it was too silent in here anyway :D
| |
09:30 | Did you solve all your problems?
| |
09:31 | <fuzzmew> not yet.
| |
09:31 | <alkisg> What's left?
| |
09:32 | <fuzzmew> Well, I don't what to put in the config files.
| |
09:33 | All I know is that eth0 is 192.168.1.6 and that eth1 is 192.168.2.1
| |
09:33 | <alkisg> But what is the issue that you're trying to solve?
| |
09:33 | What are the error messages etc?
| |
09:34 | <fuzzmew> it was say something like TFTP.....
| |
09:34 | <alkisg> Are you trying to make ltsp work, and you can't?
| |
09:34 | Which distro/version and which tutorial did you follow?
| |
09:34 | <fuzzmew> Correct. it dont work
| |
09:36 | https://wiki.debian.org/LTSP/Howto
| |
09:36 | and
| |
09:36 | kjackal has joined IRC (kjackal!~kjackal@onopfy.static.otenet.gr) | |
09:36 | <fuzzmew> Mint Linux 17.3 is what I'm trying to put it on
| |
09:37 | <alkisg> Is that the debian edition (LMDE) of linux mint?
| |
09:38 | <fuzzmew> Yes
| |
09:38 | <alkisg> The last version of LMDE is 2
| |
09:38 | https://www.linuxmint.com/download_lmde.php
| |
09:39 | It's not possible to have LMDE 17
| |
09:39 | Maybe you are using the ubuntu version of linux mint?
| |
09:39 | https://www.linuxmint.com/ ?
| |
09:40 | <fuzzmew> I do not understand, it says 17.3 on mine.....
| |
09:40 | <alkisg> There are two versions of linux mint
| |
09:40 | One is based on ubuntu, the other on debian
| |
09:41 | I believe you are using the version based on ubuntu, so it's not LMDE
| |
09:41 | <fuzzmew> Oh poop. sorry.
| |
09:41 | <alkisg> That means that you followed the wrong tutorial for LTSP, because you followed the debian tutorial and not the ubuntu tutorial
| |
09:41 | <fuzzmew> Strange. I do not see a tutorial for Mint Linux.......
| |
09:42 | Theer was a blog page or two, tried those and they don't work.
| |
09:42 | <alkisg> bennabiy: do you have a tutorial for linux mint anywhere?
| |
09:42 | fuzzmew: how many clients do you have, and what cpu/ram do they have?
| |
09:45 | <fuzzmew> Plan to only have two, one upstairs, and one downstairs, might use an intel atom thin mini itx 4Gb of ra=m
| |
09:46 | <alkisg> I think it will be better to tell me more details about your hardware, so that I help you decide if you want to use ltsp fat clients or ltsp thin clients
| |
09:47 | And about the software you're planning to run there
| |
09:47 | E.g. if you plan to run games, they won't work so well with thin clients, it's best to use fat clients there
| |
09:47 | Also, what about your server, your networking speed (gigabit or not) etc...
| |
09:48 | <fuzzmew> I had wondered about that, well the server is an 8 core amd 4.3Ghz speed, and will have 32Gb of ram when in full use. I don't plan on gaming, just web surfing, maybe a little youtube, def some Handbraking to encode videos.
| |
09:48 | the network is a 1000 speed board on the thin/thick client side
| |
09:48 | and the built in one should be the same
| |
09:49 | <alkisg> Gigabit networking is only gigabit if all the items are gigabit, server, switch, client
| |
09:49 | Have you tried surfing on the atom client? Without LTSP?
| |
09:49 | Was its performance acceptable?
| |
09:49 | <fuzzmew> Have not tested that yet. Not yet purchased.
| |
09:50 | My fear is they will be too slow to act as that.
| |
09:50 | <alkisg> Good. In my experience, atom-based clients are too slow
| |
09:50 | And, desktop over the net is also not very good experience
| |
09:50 | (even over gigabit)
| |
09:50 | For example:
| |
09:50 | !flash
| |
09:50 | <ltsp> flash: Yes, flash sucks. An HD full screen 30 fps video needs 2.5 Gbps bandwidth (1920×1080×4×30)! Make sure you have LDM_DIRECTX=True in your lts.conf file, or if it's just youtube you're after, try some flash replacing plugin like http://linterna-magica.nongnu.org
| |
09:51 | <alkisg> It's impossible to have 2.5 gigabit local network to see an HD movie in a thin client
| |
09:51 | <fuzzmew> yeah i don't plan to do a whole lot of youtubing, mostly surfing and email and using Handbrake.
| |
09:51 | <alkisg> So for new clients, buying fat clients are recommented
| |
09:51 | You can also use ltsp remoteapps to take advantage of the server cpu for handbrake
| |
09:51 | <fuzzmew> hmmmm....I"d wondered about fat clients. Maybe that is a better choice
| |
09:52 | <alkisg> I.e. everything will run locally, browsing and emails etc, but handbrake will run remotely on the server (all transparent to the users)
| |
09:52 | fuzzmew: are you on the "server" now?
| |
09:53 | <fuzzmew> I'm cheating, I'm using it from a desktop share thing on my mac upstairs.
| |
09:53 | <alkisg> OK, open a terminal and run this: awk -F': ' '/^model name/ { print $2; exit }' /proc/cpuinfo
| |
09:53 | <fuzzmew> that chicken share thing chicken of the vnc
| |
09:53 | ook
| |
09:53 | <alkisg> This will tell me the exact cpu of your server
| |
09:54 | <fuzzmew> fuzzmew@System01 ~ $ awk -F': ' '/^model name/ { print $2; exit }' /proc/cpuinfoAMD FX-8370 Eight-Core Processor
| |
09:54 | <alkisg> https://www.cpubenchmark.net/cpu.php?cpu=AMD+FX-8370+Eight-Core
| |
09:54 | That has a score of 9000, a very fast server
| |
09:54 | So, in your place, I'd buy a client with 2000 score or so
| |
09:55 | <fuzzmew> Ok.
| |
09:55 | <alkisg> A cheap, diskless one that can run youtube etc, and I would run handbrake on the server
| |
09:55 | So, you should test ltsp fat clients
| |
09:55 | Do you have a test client now?
| |
09:55 | <fuzzmew> dang. no. sorry.
| |
09:56 | <alkisg> How are you trying to see if ltsp works?
| |
09:57 | <fuzzmew> I was taking the thin client approach with an old laptop, kind of lacking in video
| |
09:57 | <alkisg> No problem there, a server that supports ltsp fat clients also supports thin clients
| |
09:57 | So, I propose this tutorial to you:
| |
09:57 | !ltsp-pnp
| |
09:57 | <ltsp> ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
09:58 | <fuzzmew> ah ha, I will have to give that a good study. Many thanks
| |
09:59 | <alkisg> You'll need to undo the steps you have done already
| |
09:59 | E.g. delete the /opt/ltsp folder, uninstall xinetd and whatever else you have there
| |
10:00 | <fuzzmew> will do
| |
10:01 | <alkisg> Good luck, ping me if you need help :)
| |
10:01 | <fuzzmew> thanx
| |
10:14 | I deleted the /opt/ltsp and uninstalled xintetd, then I started following the tutorial, does this look right?
| |
10:14 | System01 ~ # ltsp-config dnsmasq
| |
10:14 | Created /etc/dnsmasq.d/ltsp-server-dnsmasq.conf
| |
10:14 | * Restarting DNS forwarder and DHCP server dnsmasq [ OK ]
| |
10:14 | System01 ~ # echo 'IPAPPEND=3' >> /etc/ltsp/update-kernels.conf
| |
10:14 | System01 ~ # /usr/share/ltsp/update-kernels
| |
10:14 | Skipping yaboot configuration. install yaboot package if you need it.
| |
10:14 | Skipping etherboot images. Install the mkelfimage package if you need them.
| |
10:14 | System01 ~ # ltsp-update-image --cleanup /
| |
10:14 | mount: wrong fs type, bad option, bad superblock on overlayfs,
| |
10:14 | missing codepage or helper program, or other error
| |
10:14 | (for several filesystems (e.g. nfs, cifs) you might
| |
10:14 | need a /sbin/mount.<type> helper program)
| |
10:14 | In some cases useful info is found in syslog - try
| |
10:14 | dmesg | tail or so
| |
10:14 | Could not mount /tmp/tmp.dL8xyg3ASM/amd64.
| |
10:20 | <alkisg> fuzzmew: did you add the ppa as the instructions said?
| |
10:20 | Also, did you install ltsp-client etc?
| |
10:22 | <fuzzmew> I typed it in as it is written......
| |
10:23 | shall I copy and paste it in again?
| |
10:25 | <alkisg> No, let me see:
| |
10:25 | !vnc-dide
| |
10:25 | <ltsp> 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.
| |
10:25 | <alkisg> Run these things to share your screen with me
| |
10:26 | adrianorg has left IRC (adrianorg!~adrianorg@189.58.230.246.dynamic.adsl.gvt.net.br, Ping timeout: 260 seconds) | |
10:28 | adrianorg has joined IRC (adrianorg!~adrianorg@179.187.28.9.dynamic.adsl.gvt.net.br) | |
10:28 | <alkisg> You had the old ltsp version
| |
10:28 | It's because you installed ltsp before following the instructions from the wiki
| |
10:28 | So now an apt-get dist-upgrade is neede
| |
10:28 | d
| |
10:28 | <fuzzmew> How strange, I thought I had delted it...
| |
10:28 | <alkisg> You deleted the folder but not the ltsp-server package etc
| |
10:31 | fuzzmew: I also uninstalled isc-dhcp-server, you don't need it
| |
10:31 | <fuzzmew> Many thankx
| |
10:31 | <alkisg> Are you going to use a dual nic setup, or a single nic setup?
| |
10:31 | <fuzzmew> Dual
| |
10:31 | eth1 is the internal client one
| |
10:31 | eth0 is for the internet
| |
10:31 | <alkisg> Why? It's harder for people to understand it. Do you know enough about networks etc?
| |
10:32 | <fuzzmew> It is how I connected it.
| |
10:32 | <alkisg> OK
| |
10:33 | <fuzzmew> I do not know alot of the networks, enough to get things going
| |
10:33 | <alkisg> Do you know what ip masquerade is ?
| |
10:33 | <fuzzmew> heard of it, but not sure...
| |
10:33 | <alkisg> I think it'll be simpler for you to use a single nic setup
| |
10:34 | <fuzzmew> No poop? Ok. Lets just let eth1 mellow then.
| |
10:36 | If it will work, thats all that will matter to me.
| |
10:38 | <alkisg> Boot a client
| |
10:38 | frederickjh has joined IRC (frederickjh!~frederick@84-74-197-237.dclient.hispeed.ch) | |
10:38 | <alkisg> Let's leave the 2-nic setup for now since you already have that correctly set up
| |
10:39 | <fuzzmew> Ok will go downstiars and hook it up and try to boot. Pls stand by....
| |
10:44 | <alkisg> Hmmm
| |
10:44 | <fuzzmew> sorry
| |
10:44 | <alkisg> You have amd64 server, you can't serve i386 clients
| |
10:44 | <fuzzmew> oh poop
| |
10:44 | <alkisg> But wait
| |
10:45 | OK, so your options are:
| |
10:45 | 1) run ltsp-build-client --arch i386
| |
10:45 | 2) reinstall the server with i386 architecture
| |
10:45 | 3) use another client
| |
10:45 | ...choose :)
| |
10:45 | 1) means it's not ltsp-pnp anymore, it's the harder method to install ltsp
| |
10:45 | <fuzzmew> hmmm. well, 1 sounds preferable so far.
| |
10:45 | oh poop
| |
10:46 | <alkisg> So it'll be harder for you to maintain it
| |
10:46 | <fuzzmew> ah spackle
| |
10:46 | <alkisg> You'll have to install things in the chroot for your fat clients, while ltsp-pnp doesn't have chroots
| |
10:47 | <fuzzmew> dang, might just have to get wait until i get a intel thingy
| |
10:47 | i had my eye on a dual core of sokeme kind
| |
10:48 | the atom
| |
10:48 | <alkisg> Check its cpubenchmark score before buying it
| |
10:48 | <fuzzmew> o right thanx
| |
10:48 | <alkisg> Don't buy new stuff with under 1500 score, they suck
| |
10:49 | <fuzzmew> eww. ok no 1500
| |
10:49 | <alkisg> Let's go with (1) until you go with (3)
| |
10:49 | <fuzzmew> ok sounds good
| |
10:51 | <alkisg> For new cheap+fast fat clients, we're currently using this motherboard here (use google translate): http://www.e-shop.gr/mitriki-asrock-qc5000m-retail-p-PER.528863
| |
10:51 | It scores 1900 on passmark
| |
10:52 | <fuzzmew> poop let me do that over
| |
10:54 | looks good
| |
10:54 | <alkisg> http://www.asrock.com/mb/AMD/QC5000M/
| |
10:55 | SOUL_OF_r00T has joined IRC (SOUL_OF_r00T!~leonardo@unaffiliated/soul-of-r00t/x-4421326) | |
10:56 | <alkisg> fuzzmew: it has the cpu and everything on board, it costs about $60, so if you build a box with it it'll be very cheap
| |
10:56 | <SOUL_OF_r00T> hello great guys, here is time to say good morning!
| |
10:56 | <fuzzmew> hope it is sold in the states
| |
10:56 | <alkisg> Sure it is
| |
10:56 | Hi SOUL_OF_r00T
| |
10:56 | <fuzzmew> Greetings
| |
10:56 | <alkisg> Time to get the kids, bb all
| |
10:56 | alkisg is now known as alkisg_away | |
10:57 | <fuzzmew> ok
| |
10:57 | <SOUL_OF_r00T> how is the better way to use multiple xorg setups between the ltsp client box and the server?
| |
10:57 | <fuzzmew> sorry, alkisg may know better than I
| |
10:59 | frederickjh has left IRC (frederickjh!~frederick@84-74-197-237.dclient.hispeed.ch, Quit: Out of here! See you around!) | |
11:05 | robb_nl has left IRC (robb_nl!~robb_nl@ip-83-134-23-150.dsl.scarlet.be, Ping timeout: 248 seconds) | |
11:08 | SOUL_OF_r00T has left IRC (SOUL_OF_r00T!~leonardo@unaffiliated/soul-of-r00t/x-4421326, Read error: Connection reset by peer) | |
11:17 | <fuzzmew> i get a busybox now. see you tomorrow then?
| |
11:25 | <vsuojanen> fuzzmew: can you paste here output of cat /proc/cmdline ?
| |
11:27 | at the client while you are at busybox. the problem is that client - it's stopped booting in initramfs before finding and mounting the rootfs (image)
| |
11:27 | <fuzzmew> cannot paste from client
| |
11:28 | cat /proc/cmdline
| |
11:28 | BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=b9a71c14-77f8-4287-8872-2c67418679fe ro quiet splash vt.handoff=7
| |
11:28 | <vsuojanen> it's less than 100 chars. perhaps write it in paper and then here
| |
11:28 | <fuzzmew> Oh ok will go downstairs
| |
11:32 | ro initrd=initrd.img-3.19.
| |
11:33 | generic init=/sbin/init-letsp corcepae
| |
11:34 | root=/dev/ndb0 BOOT_IMAGE=vmlinuz-3.19.0032-generic ip=192.
| |
11:36 | 167.216:192.168.67.1:192.168.1:255.255.255.0 BOOTIF=01-00-0f-b0
| |
11:36 | 75=df-30
| |
11:41 | <vsuojanen> was it that you use ltsp-pnp ? https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp ?
| |
11:43 | <fuzzmew> i think that is what alkisg and I did already...
| |
11:43 | I thought he was set it up for 1) run ltsp-build-client --arch i386
| |
11:43 | 2) reinstall the server with i386 architecture
| |
11:43 | 3) use another client
| |
11:43 | I think it was choice 1 for now
| |
11:45 | <vsuojanen> ok. did you follow the installation page from the start. before you did option 1 ?
| |
11:45 | <fuzzmew> yes. we did that
| |
11:46 | <vsuojanen> do you have on the server IPAPPEND=3 enabled in file /etc/ltsp/update-kernels.conf ?
| |
11:47 | and have you run /usr/share/ltsp/update-kernels after you did option 1 ?
| |
11:48 | I suggest try them and boot and if you didn't do them
| |
11:49 | Faith has joined IRC (Faith!~paty_@unaffiliated/faith) | |
11:49 | <fuzzmew> sudo /usr/share/ltsp/update-kernels
| |
11:49 | Skipping yaboot configuration. install yaboot package if you need it.
| |
11:49 | Skipping etherboot images. Install the mkelfimage package if you need them.
| |
11:49 | Is this right?
| |
11:49 | frederickjh has joined IRC (frederickjh!~frederick@84-74-197-237.dclient.hispeed.ch) | |
11:49 | <vsuojanen> * try them and boot your thin client. yes. test your thin client booting now
| |
11:49 | <fuzzmew> ok
| |
11:51 | its busy box again
| |
11:54 | <vsuojanen> is there any error messages ? perhaps some message about rootfs or something ?
| |
11:58 | <fuzzmew> no
| |
11:58 | alot of "no such file or directory"
| |
11:58 | <vsuojanen> ok. that's helpful information also
| |
11:58 | <frederickjh> Hi! I have a new Ubuntu 14.04.4 ltsp-pnp setup. The clients boot to the login but after login in are sent right back to the login. I have tracked this down to the permissions on the /tmp directory on the client. These are being sent to drwxr-xr-x but should be set to drwxrwxrwt or put another way it is set to 755 but should be 1777. Does anyone know how to have the permissions setup correctly on the client image or on boot?
| |
11:59 | Faith has left IRC (Faith!~paty_@unaffiliated/faith, Ping timeout: 250 seconds) | |
11:59 | Faith has joined IRC (Faith!~paty_@200.144.182.219) | |
12:03 | <vsuojanen> fuzzmew: I suggest start all over following https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp Installation part. there before "IPAPPEND..." part do that here suggested option 1). then continue with the guide generating the image and editin the lts.conf
| |
12:04 | fuzzmew: if you do this first remove the subdirectories on server /opt/ltsp/
| |
12:08 | <fuzzmew> Ok. have a good nihgt
| |
12:08 | thank you
| |
12:08 | fuzzmew has left IRC (fuzzmew!~fuzzmew@71.216.56.79, Quit: Ex-Chat) | |
12:09 | <vsuojanen> frederickjh: I have Ubuntu 14.04.4 Helmikivi57/tmp 777
| |
12:09 | frederickjh: I have Ubuntu 14.04.4 /tmp 777
| |
12:09 | <frederickjh> On the client?
| |
12:10 | Proper permissions for /tmp in a Linux system are 1777
| |
12:10 | The 1 means that users can not delete other users files.
| |
12:11 | http://unix.stackexchange.com/a/71625/156578
| |
12:12 | I have a root shell on tty2 Ctrl-AlT-F2 that I use on the client to check the permissions.
| |
12:14 | The root shell is setup in lts.conf with the line:
| |
12:14 | SCREEN_02=shell
| |
12:15 | <vsuojanen> both server and client environments should be running same filesystem permissions
| |
12:15 | kjackal has left IRC (kjackal!~kjackal@onopfy.static.otenet.gr, Ping timeout: 276 seconds) | |
12:16 | <frederickjh> But they are not.
| |
12:16 | The server:
| |
12:16 | ls -ld /tmp
| |
12:17 | drwxrwxrwt 7 root root /tmp
| |
12:17 | The client: (needs to boot first)
| |
12:17 | ls -ld /tmp
| |
12:18 | drwxr-xr-x 1 root root /tmp
| |
12:19 | It looks like the client is being setup as a fatclient with its own /tmp instead of mounting /tmp on the server.
| |
12:20 | However because no permissions are being given for /tmp it is defaulting to 755 when it should be 1777.
| |
12:20 | <vsuojanen> not necessary. /tmp it really should be included in the image (ltsp-update-image should not touch the directory)
| |
12:21 | are you running same arch for the client with the server?
| |
12:21 | <frederickjh> So what directory is ltsp-pnp using when it add /tmp to the image?
| |
12:22 | Yes, The server is 64 bit but clients are i386 so I installed 32 bit version of Ubuntu on the server.
| |
12:22 | <vsuojanen> it should be server /tmp that gets to the image with ltsp-update-image
| |
12:22 | but not in your case
| |
12:22 | chmod 1777 that /tmp in client chroot
| |
12:22 | <frederickjh> I have done that. Then I can log in.
| |
12:23 | <vsuojanen> how did you build that client chroot ?
| |
12:23 | <frederickjh> However on next boot I need to to that again.
| |
12:23 | In lts.config SCREEN_02=shell
| |
12:23 | then switch to tty2 with Ctrl-Alt-F2
| |
12:24 | Sorry, I miss read your question.
| |
12:24 | I thought that ltsp-pnp did not use a chroot but build from what was on the server?
| |
12:26 | <vsuojanen> yes. sorry i did not read to the word that 14:20
| |
12:29 | stay in the channel so someone can help you. sorry i can't help right now with the issue. maybe later today
| |
12:29 | <frederickjh> I guess I do not know enough about how ltsp-pnp creates its image to fix this.
| |
12:29 | I did see someone who in the past had this problem and fixed it with a script in rc.local but I am not sure if that is the best way.
| |
12:30 | http://comments.gmane.org/gmane.linux.terminal-server.general/12715
| |
12:31 | gvy has joined IRC (gvy!~mike@altlinux/developer/mike) | |
12:32 | <vsuojanen> you shouldn't need to do anything like that. ltsp should be able to maintain this kind of bugs/issues with you
| |
12:36 | Faith has left IRC (Faith!~paty_@200.144.182.219, Ping timeout: 240 seconds) | |
12:40 | <frederickjh> OK, do I need to file an issue some where?
| |
12:42 | Well in the mean time I have added a chmod 1777 /tmp command to /etc/rc.local and am creating an new image to boot to see if this can fix it.
| |
12:45 | alkisg_web has joined IRC (alkisg_web!bc04e403@gateway/web/freenode/ip.188.4.228.3) | |
12:46 | <alkisg_web> frederickjh: do you have /tmp in your server's /etc/fstab?
| |
12:46 | By default, /tmp is the same file system as /, but maybe you put some tmpfs or something there?
| |
12:47 | <frederickjh> I will check but I did not change anything. I just did a normal i386 install of Ubuntu then installed ltsp-pnp.
| |
12:47 | <alkisg_web> grep tmp /proc/mounts
| |
12:47 | If this shows nothing, then it's not the issue I thought it'd be
| |
12:48 | You don't need rc.local to work around it, just put INIT_COMMAND_TMP="chmod ... /tmp"
| |
12:48 | in lts.conf
| |
12:49 | <frederickjh> http://pastebin.com/dyHKms0b
| |
12:49 | that is the output of grep tmp /proc/mounts
| |
12:49 | <alkisg_web> That's the problem then
| |
12:49 | /dev/mapper/henderson--ltsp-tmp /tmp ext4 rw,relatime,data=ordered 0 0
| |
12:50 | For some reason your tmp is not the "default ubuntu install", it's something special
| |
12:50 | <frederickjh> Oh, that is right.
| |
12:50 | <alkisg_web> So, you first need to unmount /tmp on your server somehow (e.g. in recovery), then chmod that dir
| |
12:50 | Because now ltsp-pnp picks up the real /tmp, not the mounted one
| |
12:50 | <frederickjh> I used LVM and put /tmp on a separate volume.
| |
12:51 | <alkisg_web> The real /tmp is a subdirectory of /, and it has wrong permissions on your installation
| |
12:51 | It's not a fault of ltsp
| |
12:51 | <frederickjh> So why does /tmp on the server have the correct permissions?
| |
12:51 | <alkisg_web> Because you mounted things on top of the real /tmp
| |
12:51 | And it shows the submount permissions there
| |
12:52 | But mksquashfs reads files with something like "--same-file-system"
| |
12:52 | <frederickjh> Oh, so ltsp-pnp is using the permisson of the /tmp before the mount
| |
12:52 | <alkisg_web> Right
| |
12:52 | <frederickjh> Thanks!
| |
12:52 | <alkisg_web> So you need to unmount, chmod, then remount. Once.
| |
12:52 | <frederickjh> That is a big help
| |
12:52 | <alkisg_web> Then it'll stick
| |
12:53 | Faith has joined IRC (Faith!~paty_@143.107.231.49) | |
12:54 | <vsuojanen> that was a nice lesson. thanks alkisg_web frederickjh
| |
12:54 | <alkisg_web> np :)
| |
12:56 | frederickjh: you *might* be able to do this: sudo -i; mkdir /tmp/root; mount --bind / /tmp/root; chmod 1777 /tmp/root/tmp; umount /tmp/root
| |
12:56 | And then revert rc.local and run ltsp-update-image -c /
| |
13:09 | lbssousa has joined IRC (lbssousa!~laercio@177.143.57.194) | |
13:09 | <frederickjh> alkisg_web should
| |
13:10 | mount --bind / /tmp/root
| |
13:10 | be
| |
13:10 | mount --bind /tmp/ /tmp/root
| |
13:10 | <alkisg_web> No
| |
13:10 | It's as I wrote it
| |
13:11 | <frederickjh> Ah, now I see
| |
13:11 | You are mounting the whole file system into /tmp/root then chmoding it. Is that right?
| |
13:12 | <alkisg_web> Right
| |
13:12 | And it's a bind-mount, i.e. a second remount of the existing mount to another place (/tmp/root)
| |
13:12 | This doesn't inherit submounts, so you'll see the real /tmp there
| |
13:12 | ...and chmod it
| |
13:12 | <frederickjh> So to check if we have the wrong permission I could do a ls -ld /tmp/root/tmp to see what they are before chmoding.
| |
13:14 | <alkisg_web> Yup
| |
13:14 | And then the bug report should go to whatever is responsible for *those* wrong permissions there (ubuntu installer?)
| |
13:16 | <frederickjh> Or is that upstream lvm
| |
13:16 | kjackal has joined IRC (kjackal!~kjackal@2a02:587:3101:3500:60fa:29d4:cb6e:3d61) | |
13:17 | gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving) | |
13:17 | <alkisg_away> No, I don't think lvm is responsible for the tmp permissions
| |
13:17 | alkisg_away is now known as alkisg | |
13:17 | <vsuojanen> hmm. did you move /tmp after you installed ubuntu or while installing ubuntu? lvm should not have anything to do with it
| |
13:18 | alkisg_web has left IRC (alkisg_web!bc04e403@gateway/web/freenode/ip.188.4.228.3, Quit: Page closed) | |
13:22 | <alkisg> Probably ubiquity first mounted lvm over /tmp/, and *then* chmoded it
| |
13:24 | <frederickjh> So does anyone know where I should file this? A link or at least a site would be helpful.
| |
13:25 | <vsuojanen> imo if you encounted this first time with ubuntu and just resolved it you may save your time and money doing your business or hobby
| |
13:28 | <alkisg> If you google for ubiquity bug, you'll find its bug tracker
| |
13:30 | <frederickjh> OK, thanks
| |
13:31 | The ls -ld of /tmp/root/tmp showed that the client permissions for /tmp were coming from it.
| |
13:32 | I have reverted rc.local and rebooted the client.
| |
13:34 | Login was not successful. Permissions on tmp are the same as before on the client.
| |
13:34 | It looks like I will try the recovery.
| |
13:35 | Anyone know what keystroke to hit to bring up grub to enter recovery?
| |
13:35 | <vsuojanen> please try alkisg suggestion again carefully
| |
13:37 | <alkisg> frederickjh: *after* the chmod of /tmp/root/tmp, did you run ltsp-update-image?
| |
13:37 | <vsuojanen> it's just client permissions wrong. you should at least be able to workaround it
| |
13:38 | <frederickjh> alkisg, yes
| |
13:38 | I just remount and check the permissions of /tmp before mount and they are correct.
| |
13:39 | <alkisg> The `ls -ld /tmp/root/tmp` command now says that the permissions are correct?
| |
13:40 | <frederickjh> yes
| |
13:40 | The client is still showing the 755 permissions for /tmp.
| |
13:41 | <alkisg> To check the image, there's no need to boot the client
| |
13:41 | <frederickjh> I think that I will try and reboot the server then see what the permission are then try runing ltsp-update-image.
| |
13:41 | <alkisg> mount -o loop,ro /opt/ltsp/i386.img /mnt
| |
13:41 | ls -ld /mnt/tmp
| |
13:41 | umount /mnt
| |
13:42 | <frederickjh> OK, true a loop mount.
| |
13:42 | <alkisg> OK, try a server reboot, it might help for some reason
| |
13:43 | <frederickjh> drwxr-xr-x 2 root root 3 Mär 15 14:28 /mnt/tmp
| |
13:43 | still not right.
| |
13:50 | Faith has left IRC (Faith!~paty_@143.107.231.49, Ping timeout: 244 seconds) | |
13:51 | Faith has joined IRC (Faith!~paty_@200.144.182.219) | |
13:51 | fuse has joined IRC (fuse!d5f13682@gateway/web/freenode/ip.213.241.54.130) | |
13:51 | <frederickjh> I found this existing bug. https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/371236 Should I add the ltsp aspect to it or create a new issue?
| |
13:51 | <fuse> hi
| |
13:52 | i install ltsp on debian, when i login to thin client i can't create socket in /home/user ....
| |
13:53 | if i create socket in /tmp it's ok
| |
13:54 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
13:56 | <alkisg> frederickjh: you should check "it affects me too" and comment about your distro/version there
| |
13:56 | <frederickjh> That is what I thought.
| |
13:56 | <alkisg> I don't think you need to mention ltsp, it'll just complicate things without reason
| |
13:56 | fuse: I think that sshfs doesn't support sockets, which app is trying to do that?
| |
13:56 | <frederickjh> You don't think that it would add to the urgency to fix it.
| |
13:57 | Faith has left IRC (Faith!~paty_@200.144.182.219, Ping timeout: 268 seconds) | |
13:57 | <alkisg> frederickjh: I think that it would make people thing that it's ltsp's fault while it isn't, so they wouldn't bother fixing it in ubiquity
| |
13:57 | Or that your setup is too uncommon for them to bother with
| |
13:58 | <vsuojanen> +1
| |
13:58 | <alkisg> fuse: also, I assume that you're talking about ltsp fat clients, not thin clients
| |
13:58 | Thin clients' /home is on the server, locally, so it shouldn't have any issue with sockets
| |
13:59 | (the thin client session runs on the server)
| |
14:01 | <frederickjh> alkisg I still have not had success. After the reboot checked the permission of /tmp before mount by doing a --bind mount, the permissions are correct. I then did a ltsp-update-image.
| |
14:01 | I then mounted the image and the permissons of /tmp are still 755
| |
14:02 | <alkisg> frederickjh: dpkg -l ltsp-server | grep ^ii
| |
14:02 | <frederickjh> Looks like I will try the recovery method.
| |
14:02 | <alkisg> You can also try with a live cd
| |
14:03 | <frederickjh> ltsp-server 5.5.5~r2703+p1238+201512091628~ubuntu14.04.1
| |
14:04 | <alkisg> frederickjh: I'm in a hurry now so I can't do it, but sometime later or tomorrow we may check with vnc:
| |
14:04 | !vnc-dide
| |
14:04 | <ltsp> 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.
| |
14:04 | <frederickjh> OK, we will see.
| |
14:04 | Thanks!
| |
14:08 | With the live CD there is no recovery option in the menu.
| |
14:09 | <alkisg> frederickjh: file a bug report under ltsp, I think it's an additional problem at ltsp-update-image
| |
14:10 | * alkisg waves, later... | |
14:10 | alkisg is now known as alkisg_awawy | |
14:10 | alkisg_awawy is now known as alkisg_away | |
14:10 | <frederickjh> OK, but I am not sure where.
| |
14:13 | Faith has joined IRC (Faith!~paty_@143.107.231.49) | |
14:19 | <frederickjh> alkisg_away Update: I booted the live CD and then mounted the root partion. The permissions for /tmp are correct 1777 so I am not sure what to do here other than go back to the rc.local solution.
| |
14:37 | Faith has left IRC (Faith!~paty_@143.107.231.49, Changing host) | |
14:37 | Faith has joined IRC (Faith!~paty_@unaffiliated/faith) | |
14:54 | <frederickjh> alkisg_away I went back to the rc.local solution. Nothing else works. I have not filed and bug reports as launchpads login is down right now.
| |
15:05 | gvy has joined IRC (gvy!~mike@altlinux/developer/mike) | |
15:06 | mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving) | |
15:55 | gp has joined IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net) | |
15:57 | robb_nl has joined IRC (robb_nl!~robb_nl@ip-83-134-23-29.dsl.scarlet.be) | |
16:00 | <lbssousa> Do you know the ssvnc Debian/Ubuntu package maintainer?
| |
16:01 | fuse has left IRC (fuse!d5f13682@gateway/web/freenode/ip.213.241.54.130, Quit: Page closed) | |
16:13 | robb_nl has left IRC (robb_nl!~robb_nl@ip-83-134-23-29.dsl.scarlet.be, Remote host closed the connection) | |
16:27 | frederickjh has left IRC (frederickjh!~frederick@84-74-197-237.dclient.hispeed.ch, Quit: Out of here! See you around!) | |
16:46 | alkisg_away is now known as alkisg | |
17:22 | estcap has joined IRC (estcap!c3391364@gateway/web/freenode/ip.195.57.19.100) | |
17:22 | <estcap> hola grup
| |
17:23 | estcap has left IRC (estcap!c3391364@gateway/web/freenode/ip.195.57.19.100, Client Quit) | |
17:30 | kjackal has left IRC (kjackal!~kjackal@2a02:587:3101:3500:60fa:29d4:cb6e:3d61, Ping timeout: 246 seconds) | |
17:34 | <alkisg> frederickjh: (for when you come back) try: sudo -i; sed 's,sys/\*,&|/tmp,p' -i /usr/sbin/ltsp-update-image; ltsp-update-image -c /
| |
17:39 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
17:47 | gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving) | |
17:59 | lbssousa has left IRC (lbssousa!~laercio@177.143.57.194, Ping timeout: 244 seconds) | |
18:00 | lbssousa has joined IRC (lbssousa!~laercio@177.143.57.194) | |
18:32 | <alkisg> stgraber: am I permitted to syncpackage from debian for bug-fixing-only epoptes and ltsp releases? Until when?
| |
18:33 | <stgraber> so long as they are bugfix only and the archive isn't frozen for release, you can, yes
| |
18:33 | typically 2-3 days before final release
| |
18:34 | <alkisg> stgraber: thanks, also, I saw this: https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
| |
18:34 | I'd like to keep ltsp 5.5 in such a state so as that will apply for a few months from now
| |
18:34 | I.e. only commit bug fixes etc
| |
18:35 | Does that mean that SRUs will be much easier for us?
| |
18:35 | LTSP is pretty dynamic, it fixes regressions caused by other packages as they appear
| |
18:35 | E.g. we release some ltsp version now, then in a month systemd might get an update and break something, we'll need an SRU LTSP then
| |
18:36 | So for a few months I'd like to be able to sync LTSP from Debian... Will that be possible?
| |
18:38 | <stgraber> alkisg: yeah, with an MRE you don't need to confirm every single bug in a bugfix release, you can just do generic testing on it
| |
18:39 | <alkisg> Cool, thank you
| |
18:40 | If this works as advertised, I'll be sending new ltsp+epoptes microreleases to the ubuntu archives instead of the greek schools ppa
| |
18:41 | <jammcq> hi guys
| |
18:41 | <alkisg> Hi jammcq! Long time no see!
| |
18:41 | jammcq: so I'll take the opportunity and report that the server is in dire need of an update... e.g. from 10.04 to 16.04 :D
| |
18:42 | <jammcq> yeah, I lurk occasionally
| |
18:42 | hmm, that's old
| |
18:42 | * vagrantc waves | |
18:42 | <alkisg> (10.04 doesn't even get security updates anymore)
| |
18:42 | <jammcq> vagrantc: hey
| |
18:43 | <alkisg> It's not a standard installation (e.g. no kernel installed, it's some sort of a chroot), so I don't think we should be upgrading it via ssh
| |
18:43 | <jammcq> yeah, I gotta figure out the upgrade path for that thing
| |
18:54 | gp has left IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net, Quit: Leaving) | |
18:58 | gp has joined IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net) | |
19:01 | <vsuojanen> alkisg frederickjh issue today. is it possible to change permissions for /tmp when system is booted. I'm thinking did frederickjh check the permissions after trying to bind mount system and change /tmp
| |
19:01 | kjackal has joined IRC (kjackal!~kjackal@2a02:587:3101:3500:958a:6039:25c8:7c7) | |
19:03 | <alkisg> vsuojanen: the first problem was what we talked about, the underlying /tmp parameters under his lvm mount
| |
19:03 | <vsuojanen> I doubt ltsp-update-image is to blame
| |
19:03 | <alkisg> The second problem is in ltsp-update-image, that it bind-mounts the /tmp submount for ltsp-update-image -c /
| |
19:03 | That sed above should fix it
| |
19:03 | <vsuojanen> I see :)
| |
19:03 | <alkisg> Run this: sed -n 's,sys/\*,&|/tmp,p' /usr/sbin/ltsp-update-image
| |
19:04 | You'll see the line that should be fixed
| |
19:04 | I've put mounts under /dev, /sys etc there, but I haven't put /tmp
| |
19:04 | Because normally tmp is either not a mount, or a tmpfs... being an lvm ext4 partition wasn't something that I had in mind :)
| |
19:07 | <vsuojanen> ok then.
| |
19:08 | * alkisg waves | |
19:08 | alkisg is now known as alkisg_away | |
19:13 | <vagrantc> was the issue that /tmp was separated?
| |
19:16 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Ping timeout: 248 seconds) | |
19:21 | <vsuojanen> vagrantc yes separate disk/volume was used for /tmp mountpoint and it showed on server with permissions 755
| |
19:22 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
19:25 | <vsuojanen> I think so because the problem was that 755 /tmp permissions in clients
| |
19:25 | <vagrantc> i recalled the issue, and was curious about the resolution
| |
19:33 | kjackal has left IRC (kjackal!~kjackal@2a02:587:3101:3500:958a:6039:25c8:7c7, Ping timeout: 246 seconds) | |
19:36 | <MCMXI> I have a ltsp server thats set up for i386 images, I built the amd64 image, but the client is still downloading the i386 image, whats the best way to use the amd64 one?
| |
19:36 | kjackal has joined IRC (kjackal!~kjackal@2a02:587:3101:3500:958a:6039:25c8:7c7) | |
19:37 | <Hyperbyte> MCMXI, see config in dhcpd.conf and /var/lib/ltsp/
| |
19:39 | <MCMXI> Hyperbyte: that was it, had to edit my dnsmasq conf, thanks
| |
19:41 | kjackal has left IRC (kjackal!~kjackal@2a02:587:3101:3500:958a:6039:25c8:7c7, Ping timeout: 246 seconds) | |
19:42 | <Hyperbyte> MCMXI, ah, or dnsmasq.conf yeah... good. :-)
| |
19:45 | <MCMXI> Anyone have experience with the Zotac Zbox as a thin client?
| |
19:49 | im using the B series BI320 and when I try to pxe boot it does everything, the DHCP discovery downloads the image ect, but then its just booting into busybox not acutally loading the image
| |
19:59 | <||cw> MCMXI: maybe a network driver issue? enable verbose kernel (disable "quiet")?
| |
19:59 | lbssousa has left IRC (lbssousa!~laercio@177.143.57.194, Quit: Konversation terminated!) | |
20:17 | robb_nl has joined IRC (robb_nl!~robb_nl@ip-83-134-23-29.dsl.scarlet.be) | |
20:36 | Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving) | |
20:43 | ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 268 seconds) | |
20:44 | ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de) | |
20:50 | robb_nl has left IRC (robb_nl!~robb_nl@ip-83-134-23-29.dsl.scarlet.be, Remote host closed the connection) | |
21:09 | gp has left IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net, Quit: Leaving) | |
21:09 | frederickjh has joined IRC (frederickjh!~frederick@84-74-197-237.dclient.hispeed.ch) | |
22:11 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
22:27 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |
22:50 | <frederickjh> alkisg Just a quick update. I some how missed your comment about the INIT_COMMAND_TMP in lts.conf. I am now using this. I also tried one other thing which also did not work.
| |
22:51 | That was in recovery mode to change the permissions of the logical volume device before it got mounted. Its permissions were also 755, but this too failed.
| |
22:53 | I marked as affects me too added a comment to the ubiquity issue https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/371236 and also . . .
| |
22:53 | filed one against ltsp that maybe you would like to add some more information to. https://bugs.launchpad.net/ltsp/+bug/1557779
| |
22:54 | The work around for anyone else finding this is the logs is to add the following to your lts.conf file:
| |
22:55 | # Fix permission on /tmp on the clients. Currently we have bug and they get mounted 755 instead of 1777
| |
22:55 | INIT_COMMAND_TMP="chmod 1777 /tmp"
| |
22:55 | Add that to the [Default] section at the top of the lts.conf file.
| |
23:06 | <vagrantc> huh.
| |
23:06 | wonder if that's ubuntu-specific
| |
23:06 | frederickjh: only happens when /tmp is a separate partition?
| |
23:08 | <frederickjh> I am not totally sure. I just know it my case I used LVM and made /tmp a separate partition.
| |
23:08 | Symptom was that the client could boot but after a successful login you were quickly returned to the login screen.
| |
23:08 | You never saw the desktop.
| |
23:09 | I took me a bit to figure it out with some help.
| |
23:10 | I believe you pointed me to a ~/.xsession_errors file were I found some errors to work with.
| |
23:11 | alkisig seemed to think that it was also a problem with ltsp-update-image and asked me to file a bug report against ltsp too.
| |
23:11 | <vagrantc> ah, glad i said something useful :)
| |
23:11 | yeah, saw the report
| |
23:11 | <frederickjh> Thanks for your help!
| |
23:11 | <vagrantc> frederickjh: thanks for taking the trouble to file it!
| |
23:12 | <frederickjh> I was drawing a blank as the syslog was giving me nothing to work with.
| |
23:12 | <vagrantc> i sometimes worry asking people to file bug reports means we never hear from them again
| |
23:12 | so it's great to see someone willing to do it right :)
| |
23:12 | <frederickjh> I think that filing bug reports is one of the main ways that I contribute to open source.
| |
23:13 | * vagrantc nods | |
23:13 | <frederickjh> I work as a web developer with Drupal and file most of my bug reports against it.
| |
23:13 | <vagrantc> it's certainly where i got started...
| |