IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 11 September 2015   (all times are UTC)

02:08AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-ohbdkidnqmmgrhvy, Quit: Connection closed for inactivity)
02:23pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 255 seconds)
03:13pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
03:45work_alkisg is now known as alkisg
03:48dgroos has joined IRC (dgroos!~dgroos@vpn.mpls.k12.mn.us)
03:49pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Excess Flood)
03:59
<alkisg>
!vnc-dide | echo dgroos:
03:59
<ltsp>
dgroos: 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.
04:01dgroos_ has joined IRC (dgroos_!~dgroos@mail.troop187.org)
04:36
<alkisg>
!kvm
04:36
<ltsp>
kvm: Virtual thin client: kvm -vga-vmware -ctrl-grab -no-shutdown -net nic,model=virtio -net user,tftp=/var/lib/tftpboot,bootfile=/ltsp/i386/pxelinux.0
04:51dgroos has left IRC (dgroos!~dgroos@vpn.mpls.k12.mn.us, Ping timeout: 256 seconds)
04:51dgroos_ is now known as dgroos
05:08dgroos1 has joined IRC (dgroos1!~dgroos@mail.troop187.org)
05:55ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
06:08mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
06:16
<alkisg>
dgroos: truncate: cannot open \u2018/var/log/lastlog\u2019 for writing: Value too large for defined data type
06:17
That happens when lastlog is bigger than the available server ram
06:17
<dgroos1>
OK, I should have noticed that message then.
06:17
<alkisg>
Yours was 3.3 GB, and it went inside the image as 3.3 GB instead of 0 byte
06:17
Then, at login, useradd tries again to truncate that file and fails because the client doesn't have 3.3 GB in the tmpfs
06:18
<dgroos1>
why did it say that the image size was only 1.2 gigs or so?
06:18
<alkisg>
Now, to find a better way than "truncate" in order to fix it
06:18
Where did it say that?
06:18
<maldridge>
alkisg: I'm a fan of the echo "" > $file method myself
06:19
<dgroos1>
when it serves the image, I believe right next to the block size.
06:19
<alkisg>
dgroos1, the image is compressed
06:19
<dgroos1>
yes
06:19
<alkisg>
So inside the 1.3 GB compressed image, there's a 3.3 GB lastlog file
06:19
<dgroos1>
right!
06:20
<alkisg>
Let me check locally about truncate vs other things...
06:20
<dgroos1>
sure
06:25
<alkisg>
dgroos1, should we better just fix it for you by backing up or deleting lastlog from the ltsp server?
06:25vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi, Read error: Connection reset by peer)
06:25
<alkisg>
...and then I'll check it and fix it upstream in ltsp without hurry...
06:26
<dgroos>
hey maldridge!
06:26
up late…
06:27
alkisg: (ah, you asked a question!) I can just delete lastlog. but I’m concerned that if it get’s big again…
06:29
<maldridge>
dgroos: eh, troubleshooting an LTSP image rebuild issue before I get some sleep
06:30
<dgroos>
I feel that pain…
06:33
<maldridge>
its an issue with the way I wrote my ansible playbook, so I just need to add some logic to check if an image already exists before creating one
06:35
<alkisg>
truncate: cannot open \u2018/var/log/lastlog\u2019 for writing: Value too large for defined data type
06:48
OK I think I have enough info to reproduce the error, the problem is probably in overlayfs, not in tmpfs
06:49
<dgroos>
!
06:50
OK.
06:51pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
06:52
<alkisg>
http://www.noah.org/wiki/Lastlog_is_gigantic
06:53
Ah, so it's preallocated for all users in your ldap server...
06:53
<dgroos>
getting tired… :)
06:53
<alkisg>
OK then, it will be big again soon :-./
07:28
Steps to reproduce the issue (as root): cd $(mktemp -d); mkdir lower upper work root; truncate -s 4G lower/sparse; mount -t overlay -o workdir=work,upperdir=upper,lowerdir=lower overlay work; truncate -s 0 work/sparse; umount work
07:28
The `truncate -s 0 work/sparse` command errors out
07:38Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
07:44uXus has left IRC (uXus!~uXus@217.77.222.72, Quit: ail bi bek)
07:49uXus has joined IRC (uXus!~uXus@217.77.222.72)
08:12joe__ has joined IRC (joe__!c3c38a40@gateway/web/freenode/ip.195.195.138.64)
08:13joe__ has left IRC (joe__!c3c38a40@gateway/web/freenode/ip.195.195.138.64, Client Quit)
08:43oldjoe has joined IRC (oldjoe!c3c38a40@gateway/web/freenode/ip.195.195.138.64)
08:46
<alkisg>
OK, here's a good substitute...
08:46
find /var/log/ -type f -exec truncate -s 0 {} + ==> 20 seconds, won't work with files > 2GB
08:46
find /var/log/ -type f -exec tee {} + </dev/null ==> 0.5 second, works fine with > 2 GB
08:48
<oldjoe>
HI guys, Thinking of setting this up in our college lab. Does the DHCP server offer addresses to clients connected on both network cards? Or just on the 192.168.0.1 card? Thanks
08:48
<alkisg>
oldjoe: it depends on how you set it up, there's no default dhcp setting
08:49
If you specify a range, it only serves addresses in that one, from the nic that does have an ip in that range
08:50
<oldjoe>
alkisg, thanks, I guess that will become apparent when I do the install and start the configs, will have a go, many thanks.
08:51
<alkisg>
oldjoe: it's also possible to have a single nic setup
08:51
!ltsp-pnp
08:51
<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
08:51
<alkisg>
!proxydhcp
08:51
<ltsp>
proxydhcp: A proxy DHCP server is defined by the PXE specification as a server which sends auxiliary boot information to clients, like the boot filename, tftp server or rootpath, but leaves the task of IP leasing to the normal DHCP server. More info: https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP
08:52
<oldjoe>
Thnaks guyt
08:52
oops.... thanks guys, will save this and have a look when I get into the configs.
08:53
I may be back ;-)
08:54
<alkisg>
The first one is for the installation phase
08:54
I.e. you install different packages, dnsmasq instead of isc-dhcp-server
08:58
<oldjoe>
alkisg, do you have any preference of package? I have a little experience with linux, but am diving into the deep end with this, I suppose it the best way of learning.
08:59
<alkisg>
oldjoe: if this is your first time with ltsp, then ltsp-pnp is a good method to get your first installation going
08:59
Just read and follow that page
09:04
<oldjoe>
athnk
09:04
Thanks... will get into it later, got to go now, thanks for your help.
09:07oldjoe has left IRC (oldjoe!c3c38a40@gateway/web/freenode/ip.195.195.138.64)
09:18
<alkisg>
Reported to http://permalink.gmane.org/gmane.linux.file-systems.union/408 and fixed in LTSP, https://bugs.launchpad.net/ltsp/+bug/1494660.
09:18
dgroos, dgroos1 ^
09:51dgroos1 has left IRC (dgroos1!~dgroos@mail.troop187.org, Remote host closed the connection)
10:00mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Remote host closed the connection)
10:02mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
10:10alkisg is now known as work_alkisg
10:12gbaman has joined IRC (gbaman!~gbaman@host81-148-140-104.in-addr.btopenworld.com)
10:38telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
10:39Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Read error: Connection reset by peer)
10:40telex has joined IRC (telex!teletype@freeshell.de)
10:50Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
10:54Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Read error: Connection reset by peer)
11:05Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
11:09Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
11:16Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
11:45Faith has joined IRC (Faith!~paty_@unaffiliated/faith)
12:04danau11 has joined IRC (danau11!~durban@12.197.179.122)
12:04danau11 has left IRC (danau11!~durban@12.197.179.122)
12:08AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-taakoehxflxldwwk)
12:31
<dgroos>
bye!
12:31dgroos has left IRC (dgroos!~dgroos@mail.troop187.org, Quit: dgroos)
12:53gbaman_ has joined IRC (gbaman_!~gbaman@host81-148-140-104.in-addr.btopenworld.com)
12:56gbaman has left IRC (gbaman!~gbaman@host81-148-140-104.in-addr.btopenworld.com, Ping timeout: 250 seconds)
12:56gdi2k has left IRC (gdi2k!~gdi2k@119.94.31.20, Ping timeout: 244 seconds)
13:35Faith has left IRC (Faith!~paty_@unaffiliated/faith, Ping timeout: 250 seconds)
13:35Faith has joined IRC (Faith!~paty_@143.107.231.30)
13:36Faith is now known as Guest67653
13:54warren has left IRC (warren!~warren@fedora/wombat/warren, Ping timeout: 260 seconds)
13:56warren has joined IRC (warren!~warren@fedora/wombat/warren)
13:59Guest67653 has left IRC (Guest67653!~paty_@143.107.231.30)
14:00Faith has joined IRC (Faith!~paty_@unaffiliated/faith)
14:04cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)
14:06cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
14:07ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
14:09Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Read error: Connection reset by peer)
14:11cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)
14:21Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
14:21cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
14:31myrdd has joined IRC (myrdd!~quassel@55d4172f.access.ecotel.net)
14:33mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
14:51
<myrdd>
Hello, I'm using LTSP for one year now, and it's working very well – thanks to the developers! I've got a problem though: On the server I'm using "schroot" to get into /opt/ltsp/*/. However, when I'm in there, it is impossible for the clients to boot – it ends up in a kernel panic. I guess it has to do with "mount --bind" and NFS, but I don't know how to investigate. Do you have some tips for me?
15:19Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
15:42uXus has left IRC (uXus!~uXus@217.77.222.72, Quit: ail bi bek)
15:45uXus has joined IRC (uXus!~uXus@217.77.222.72)
15:51gdi2k has joined IRC (gdi2k!~gdi2k@119.94.31.20)
16:13vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
16:56gdi2k has left IRC (gdi2k!~gdi2k@119.94.31.20, Quit: Leaving)
17:00AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-taakoehxflxldwwk)
17:36telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
17:38telex has joined IRC (telex!teletype@freeshell.de)
18:03mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Remote host closed the connection)
18:06mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
18:34jammcq has joined IRC (jammcq!~jam@c-107-4-115-38.hsd1.mi.comcast.net)
18:39ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
19:07Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving)
19:36
<jammcq>
exit
19:36
quit
19:36jammcq has left IRC (jammcq!~jam@c-107-4-115-38.hsd1.mi.comcast.net, Quit: WeeChat 0.4.2)
19:58work_alkisg is now known as alkisg
19:59
<alkisg>
myrdd: that's normal, unionfs filesystems don't like the lower fs to be changed
20:00
E.g. suppose the user opens /path/to/file, which means that it generates a copy in his COW view of the file system, and then you change /path/to/file in NFS, or delete /path completely, what would unionfs do there...
20:00
So you would either not use the NFS dir when you boot the client with NFS, or you could use NBD, AoE...
20:01ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
20:02gbaman has joined IRC (gbaman!~gbaman@members.unit1.farsetlabs.org.uk)
20:12Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Quit: I Leave)
20:12
<myrdd>
Hi alkisg, thanks for your answer so far! Doesn't NBD have that problem as well?
20:13
<alkisg>
myrdd: no, because a snapshot is saved
20:13
ltsp-update-image runs mksquashfs which ...zips /opt/ltsp/i386 into /opt/ltsp/images/i386.img
20:13
So the chroot is free, it can be edited, deleted, etc
20:17
<myrdd>
ah-ha, I've missed that!
20:19
What happens if I call ltsp-update-image while clients are running?
20:20
<alkisg>
A new i386.img is created. The old one is renamed to i386.img.old. In the next logout, the clients get a warning that a new image is available, and if they want to reboot to it
20:21
No disruption in the client use..
20:21
<myrdd>
wow, great! I'll see if I get it working. Thanks a lot alkisg!
20:22
<alkisg>
you're welcome
20:22
Ah, it's also a lot faster than nfs
20:34alkisg is now known as work_alkisg
21:43gbaman has left IRC (gbaman!~gbaman@members.unit1.farsetlabs.org.uk, Remote host closed the connection)
21:43gbaman has joined IRC (gbaman!~gbaman@members.unit1.farsetlabs.org.uk)
22:52adrianorg has left IRC (adrianorg!~adrianorg@186.215.18.167, Quit: leaving)
23:04Tyrantelf has left IRC (Tyrantelf!~tyrantelf@2607:5300:60:48bd::1, Read error: Connection reset by peer)
23:04Tyrantelf has joined IRC (Tyrantelf!~tyrantelf@2607:5300:60:48bd::1)
23:28telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
23:30telex has joined IRC (telex!teletype@freeshell.de)
23:37gbaman has left IRC (gbaman!~gbaman@members.unit1.farsetlabs.org.uk, Ping timeout: 264 seconds)
23:46adrianorg has joined IRC (adrianorg!~adrianorg@186.215.18.167)
23:46Neytiri has joined IRC (Neytiri!~The_Acid_@2001:470:860d:127::219)
23:47
<Neytiri>
does anyone know of a way i can transfer a window from one thin client to another without closing and restarting the program?
23:53gbaman has joined IRC (gbaman!~gbaman@dab-yat1-h-55-9.dab.02.net)
23:56vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
23:59
<maldridge>
Neytiri: the way the X server is written, you can't