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


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

00:15gdi2k has left IRC (gdi2k!~gdi2k@119.94.31.20, Ping timeout: 240 seconds)
00:49Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 246 seconds)
00:54Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
01:46telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
01:48telex has joined IRC (telex!teletype@freeshell.de)
01:52vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
03:00j2_ has joined IRC (j2_!bdc1aa3d@gateway/web/freenode/ip.189.193.170.61)
03:01
<j2_>
hola
03:01j2_ has left IRC (j2_!bdc1aa3d@gateway/web/freenode/ip.189.193.170.61, Client Quit)
03:23dtcrshr has left IRC (dtcrshr!~datacrush@unaffiliated/datacrusher, Ping timeout: 268 seconds)
03:58AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-nrrcygetezbvhtwx, Quit: Connection closed for inactivity)
04:48quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: :wq)
04:49work_alkisg is now known as alkisg
04:49quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
04:50
<cyberorg>
alkisg, no, but can be added in our ltsp repo if required
04:51
<alkisg>
cyberorg: if it's not in all distros, we could just keep using jetpipe or use socat
04:51
<cyberorg>
alkisg, http://rpm.pbone.net/ only mandriva seems to have it in all rpm distros
04:52
<alkisg>
cyberorg: ah, then you could use that package in opensuse without much overhead for you/
04:52
?
04:53
(in your ltsp repo...)
04:53
<cyberorg>
packaging it shouldn't be too much trouble
04:53vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
04:56
<alkisg>
Cool, thanks, I'll switch the schools here to that model (not using cupsd on fat clients but something like jetpipe) and test to see which tool is best
04:57vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi)
05:30ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
05:35cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)
05:37cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
05:43cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)
05:51cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
06:23fnurl_ has joined IRC (fnurl_!3cf8605f@gateway/web/freenode/ip.60.248.96.95)
06:24
<fnurl_>
ugh - stupid chrome crashed, i hadn't finished reading the chat from y/day :(
06:24
<alkisg>
irclogs.ltsp.org
06:24fnurl has left IRC (fnurl!3cf8605f@gateway/web/freenode/ip.60.248.96.95, Ping timeout: 246 seconds)
06:25
<fnurl_>
awesome!!
06:25
i have to get off this webclient
06:27
<alkisg>
Thunderbird is easy enough to setup for a chat client
06:27* alkisg is using pidgin, but it's not preinstalled in many distros
06:28
<fnurl_>
i'm a big fan of pidgin, i haven't used thunderbird for years
06:28
<alkisg>
Thunderbird is preinstalled and does have an embedded irc client
06:29
So it's usually better using that, instead of the web chat client
06:29
<fnurl_>
yeah - i'm not a fan of web clients, but this is a work machine
06:29
windows
06:33
found what I was looking for, you were chatting y/day about ltsp-pnp
06:39
brb
06:39fnurl_ has left IRC (fnurl_!3cf8605f@gateway/web/freenode/ip.60.248.96.95)
06:57fnurl has joined IRC (fnurl!3cf8605f@gateway/web/freenode/ip.60.248.96.95)
07:24uXus has left IRC (uXus!~uXus@217.77.222.72, Remote host closed the connection)
07:26uXus has joined IRC (uXus!~uXus@217.77.222.72)
08:00uXus has left IRC (uXus!~uXus@217.77.222.72, Quit: ail bi bek)
08:03uXus has joined IRC (uXus!~uXus@217.77.222.72)
08:24khildin has joined IRC (khildin!~khildin@62.235.15.170)
08:36pbailey has joined IRC (pbailey!36f0c5e1@gateway/web/freenode/ip.54.240.197.225)
09:11khildin has left IRC (khildin!~khildin@62.235.15.170, Ping timeout: 265 seconds)
09:46mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
09:55sutula has left IRC (sutula!~sutula@207-118-180-127.dyn.centurytel.net, Quit: ZNC - http://znc.sourceforge.net)
09:56sutula has joined IRC (sutula!~sutula@207-118-180-127.dyn.centurytel.net)
10:14Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
10:19* alkisg has found the first school here that's infected with a real linux virus... :)
10:19
<alkisg>
Possibly this one: https://blog.avast.com/2015/01/06/linux-ddos-trojan-hiding-itself-with-an-embedded-rootkit/
10:20
Yup all the contents and init scripts and cron jobs etc match, it was this one
10:32
<vmlintu>
on a ltsp server?
10:32
<alkisg>
Meh the person that installed it was not a teacher but a 70 year old debian user that was trying to help... he probably set the root password to 1234
10:32
Yes, on the ltsp server
10:32
(ubuntu, the root user is not enabled by default)
10:32
I'll check tomorrow for how they managed to get infected...
10:46alkisg is now known as work_alkisg
11:14bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
11:38khildin has joined IRC (khildin!~khildin@62.235.15.170)
12:01danau11 has joined IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
12:04danau11 has left IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
12:05Faith has joined IRC (Faith!~paty_@unaffiliated/faith)
12:23gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
12:36vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
12:41Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Read error: Connection reset by peer)
12:52Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
12:55telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
12:56Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Read error: Connection reset by peer)
12:56telex has joined IRC (telex!teletype@freeshell.de)
13:06Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
13:09AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-kpetumemupeueksn)
13:12Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Read error: Connection reset by peer)
13:13johng has joined IRC (johng!631b708c@gateway/web/freenode/ip.99.27.112.140)
13:22Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
13:42khildin has left IRC (khildin!~khildin@62.235.15.170, Ping timeout: 265 seconds)
13:51ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
13:53khildin has joined IRC (khildin!~khildin@62.235.15.170)
14:10touchware has joined IRC (touchware!~drama@postolka.klikva.net)
14:14
<touchware>
Hi all, I'm trying to get to work LTSP mounts in clients under Debian Jessie. I've LOCALDEV true, but mounting didn't work. I had no problems with this in previous version. After lot of googling I've installed ltspfs in the client. It did help, there is /root/media/XXX. But this directory can be accessed only two seconds. After that it says endpoint not connected. Any advice on that?
14:15johng has left IRC (johng!631b708c@gateway/web/freenode/ip.99.27.112.140, Ping timeout: 246 seconds)
14:18
<vagrantc>
fat clients? thin clients?
14:18
<touchware>
thin clients
14:19
<vagrantc>
where are you seeing /root/media/XXX ?
14:19khildin has left IRC (khildin!~khildin@62.235.15.170, Ping timeout: 246 seconds)
14:19
<touchware>
on the client
14:19
<vagrantc>
how are you accessing the client? using localapps?
14:19
<touchware>
no ssh
14:20
<vagrantc>
ok
14:20
<touchware>
the client runs xfreerdp
14:20
<vagrantc>
look in /var/run/ltspfs_fstab
14:20
<touchware>
i've looked there, everything seems ok
14:20Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Read error: Connection reset by peer)
14:20
<touchware>
the usb stick is recognised
14:21
<vagrantc>
could you cut and paste the line?
14:23
<touchware>
sorry, i can't find this in terminal history, but this did work even before i've installed ltspfs
14:24
ive found it
14:24
root@ltsp159:~# cat /var/run/ltspfs_fstab
14:24
/dev/sda1 /var/run/drives/usbdisk-sda1 vfat defaults,utf8 0 0
14:25
<vagrantc>
i can't fathom how it would work with xfreerdp without ltspfs installed on the client.
14:26
<touchware>
ok, i've installed ltspfs
14:26
it works how i've described
14:26
here is the mount:
14:26danau111 has joined IRC (danau111!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
14:26
<touchware>
ltspfs on /media/root/usbdisk-sda1 type fuse.ltspfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
14:27
as i said i can ls /media/root/usbdisk-sda1
14:27
<vagrantc>
ok.
14:27
<touchware>
i can see the files on usb stick
14:27
but only 2 seconds
14:27
after that
14:27
there is still the mountpoint /media/root/usbdisk-sda1
14:27danau111 has left IRC (danau111!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
14:27
<touchware>
but i can't access the files
14:28
<vagrantc>
"ls /media/root/usbdisk-sda1" does what?
14:28
<touchware>
the error is something like this (translated):
14:28mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
14:29
<touchware>
ls: can't access /media/root/usbdisk-sda1: communication endpoing is not connected
14:29
any hints were can i look (logs) or what could be the problem?
14:29
<vagrantc>
look in /var/log/syslog
14:30
<touchware>
there is nothing interesting
14:31Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
14:31
<vagrantc>
same problem with other USB sticks?
14:31
<touchware>
yes
14:31
also with ntfs
14:31
exactly the same behaviour
14:33
could it be a problem on the server side? like ltspfs mounts device locally and then tries to export this to server and when there is no response from the server it somhow dies<
14:33
?
14:33
<vagrantc>
i've never used it in conjunction with an RDP client, so i can't say much... never really seen this behavior.
14:34
<touchware>
well, i think there is no big difference
14:34
i just need, to have it mounted locally
14:34
and this is imho done also when you use it with gnome/...
14:34
<vagrantc>
the big difference is it works fine for me...
14:35
<touchware>
it did work for me also in older versions of debian
14:37
<vagrantc>
does the line in ltspfs_fstab still exist after the errors?
14:37
<touchware>
yes, everything seems ok
14:38
after removing the usb stick, the /media/root/... disappears
14:38
which is also perfectly ok
14:38
is there a way to debug ltspfs?
14:39
<vagrantc>
!ltspfs
14:39
<ltsp>
I do not know about 'ltspfs', but I do know about these similar topics: 'ltspfs-source'
14:39
<vagrantc>
there were some rather outdated debugging instructions ... but i don't think they would handle this
14:39
<touchware>
ok
14:40
i see now, that there is no ltspfsd running on the server, this could be the problem...
14:40Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Read error: Connection reset by peer)
14:41work_alkisg is now known as alkisg
14:41
<alkisg>
touchware: are you using SCREEN_07="xfreerdp <options>"?
14:42
<touchware>
yes
14:42
<alkisg>
Then the client doesn't contact the ltsp server, no need for ltspfsd there
14:42
You only need ltspfsd + ltspfs locally
14:42
(in the chroot)
14:43
<touchware>
ok, so i need install ltspfsd on the client?
14:43
<alkisg>
If you don't have it already, yes
14:43
<touchware>
i've installed only ltpsfs
14:43
<alkisg>
Doesn't ltsp-client depend on ltspfsd?
14:44
<vagrantc>
it wouldn't mount anything at all if ltspfs wasn't installed
14:44
<touchware>
you're right
14:44
it is installed
14:44
it depends on ltspfs
14:45
<vagrantc>
touchware: if you're still having troubles after a bit more debugging, please file a bug
14:45
!bug
14:45
<ltsp>
bug: To file a bug report for upstream LTSP, go to https://bugs.launchpad.net/ltsp
14:46
<touchware>
ok, i'd love to debug more, but i've no clue what ltspfs does
14:46
all the docs says it should work out of the box...
14:46
<vagrantc>
ltsp: learn bug as for Debian specific bug reports: https://www.debian.org/Bugs/Reporting
14:46
<alkisg>
!debian-bug
14:46
<ltsp>
debian-bug: To file a bug report for Debian LTSP, go to https://bugs.debian.org/ltsp or one of the ltsp binary packages mentioned there
14:47
<alkisg>
!ubuntu-bug
14:47
<ltsp>
ubuntu-bug: To file a bug report for Ubuntu LTSP, go to https://bugs.launchpad.net/ubuntu/+source/ltsp
14:47
<alkisg>
!ltsp-bug
14:47
<ltsp>
ltsp-bug: To file a bug report for upstream LTSP, go to https://bugs.launchpad.net/ltsp
14:47
<alkisg>
!bug
14:47
<ltsp>
bug: To file a bug report for upstream LTSP, go to https://bugs.launchpad.net/ltsp
14:47
<alkisg>
ok...
14:47
<vagrantc>
hrm.
14:48
in general upstream should be fine, but if people are more comfortable with their host distro's bug reporting system, then that should be fine...
14:48
<touchware>
ok, I'll report upstream
14:48
<alkisg>
I wouldn't see an upstream bug in e.g. fedora's bug tracking system
14:48
<vagrantc>
no, but the maintainer's for that distro should forward bugs if appropriate
14:49
<touchware>
ok, so you prefer to report to debian<
14:49
<alkisg>
Yup, but I haven't seen any forwarded yet :)
14:49
<touchware>
or both?
14:49
<vagrantc>
touchware: i like the debian bts better, but i think alkisg pays more attention to upstream and often does great work :)
14:50
<touchware>
ok, thanks for all your answers and time
14:51Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
14:51* alkisg hasn't managed to get notifications from the debian's ltsp bug tracker yet...
14:51
<vagrantc>
alkisg: i could fix that... :)
14:52
<alkisg>
Sure, please do so...
14:52
Are there any plans for debian to move from the email-based bug tracking system to a real bug tracker?
14:53
<vagrantc>
are there any plans for launchpad to switch from a web based bug tracking system to a real bug tracker?
14:53touchware has left IRC (touchware!~drama@postolka.klikva.net)
14:53
<alkisg>
I'm not comparing distros... but it's quite hard to google each time that I want to file a bug report, to check the headers etc, and pray that I got them right
14:54
E.g. I can see a bug in the debian sources, and I don't have debian handy to run report-bug... so I have to send a mail.. and it takes me some time to find out how to do that each time
14:55
I have the same issue with mailing lists vs forums, for many many years before I started using linux, it's not about distros... :)
14:56
<vagrantc>
Package, Version, send the email to submit@bugs.debian.org ...
14:57
<alkisg>
There's no way I could tell teachers to do that, they'd send html mails and would be discarded
14:58
Anyway, I don't think I can persuade anyone over IRC for that, I was just really asking if debian is considering such a thing
14:59
<vagrantc>
i think there's some plans for a web based interface for submission
14:59
<alkisg>
But not e.g. to use bugzilla or something... ok
15:00
<vagrantc>
not that i'm aware of
15:37vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
15:45
<maldridge>
alkisg: https://alioth.debian.org/
15:45
its been around for a while, but very few packages use it
15:46
<alkisg>
maldridge: is there a bug tracker there?
15:47
Are there any packages at all that use alioth for bug management instead of bugs.debian.org?
15:48
<maldridge>
there is a bug tracker there, but I don't think there are any projects that use it over the bugs.debian.org one. Some projects use it in addition to that one though.
15:49
<alkisg>
Maybe it's meant for projects that use alioth as "upstream" management vs distro management
15:49
<maldridge>
I suspect so
15:49
<alkisg>
E.g. dpkg, apt are upstream (native) in debian, they're not developed elsewhere...
15:50
https://bugzilla.redhat.com/show_bug.cgi?id=737201
15:50
bugzilla is much more intuitive for me. launchpad too.
15:50
Even the kernel uses bugzilla...
15:51
<maldridge>
bugzilla took me a while to wrap my head around, it is just very very large
15:52
<alkisg>
To file my first bug against gnome bugzilla, it took me a minute or so. To file my first bug against debian... I couldn't believe that they were using mails to file bug reports...
15:54
<maldridge>
its certainly easier to automate mail
15:55
<alkisg>
Sure, but debian no longer needs to maintain the bug tracking system by itself, it can just use one of the others being developed elsewhere
15:56khildin has joined IRC (khildin!~khildin@62.235.15.170)
15:56
<maldridge>
it would be nice if there was some unified mechanism so that things like alioth and bugzilla and the mail system all talked to each other
15:57
<alkisg>
I don't think that the suggested method in debian is to send a mail, but to use report-bug
15:57
And I'm don't see why report-bug couldn't use a bugzilla backend...
15:57
*I don't...
15:57
<maldridge>
bugzilla is account based though isn't it
15:58
<alkisg>
Debian tries to prohibit spammers from filing bug reports by making the procedure difficult
15:58
Bugzilla does the same with accounts
15:58
I think accounts make more sense for that...
15:59
I don't see any downsides to having an account for bug trackers.. even if it's openid or alioth accounts
15:59
<maldridge>
well, there's certainly something to be said for spam, but any debian user can run report-bug with no additional steps
16:00
<alkisg>
I don't think that it would be difficult to allow bugzilla to accept any mail for the reporter
16:00
But as a developer I wouldn't want a bug report from a possible spammer
16:00
I'd like him to at least verify his email, either by generating an account or by using an openid provider
16:05
<maldridge>
hm, this is an interesting tangent, because that could break the GNU-strict install target
16:05
but would allow you to unify the bug tracker
16:06
<alkisg>
There are distro bugs and upstream bugs
16:06
Upstreams should use whatever bug trackers they want
16:07
<maldridge>
imho upstream bugs should be reported upstream and distros need not be aware of them
16:07
<alkisg>
Distros should have some tracker that allows linking with upstream bugs, whenever applicable
16:07
Launchpad does support that part
16:07
Often a user doesn't know if the bug he reports is upstream or not,
16:07
and, when forwarded upstream, the distro needs to know when it's solved, in order to incorporate it
16:08
<maldridge>
I've got it!
16:08
systemd-bugreportd
16:08* maldridge runs for the door
16:09
<alkisg>
Hahaha
16:10
<maldridge>
jokes aside, I agree that bug reporting is a critical issue among open source projects. It'll be interesting to see if there becomes one to rule them all in the next decade.
16:12
<alkisg>
bugzilla is used by the kernel, firefox, gnome, fedora etc
16:12gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
16:12
<alkisg>
freedesktop as well
16:13
So also libreoffice and all others managed by freedesktop
16:14
kde too... I think only debian and ubuntu don't use it :P
16:15
<maldridge>
pretty sure there are several others that don't use it
16:15
but my lecture class has ended and i have to move locations
16:16
<alkisg>
Just, I was joking... although many heavy names use it
16:16
Have a nice time
16:18
https://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems ==> a good comparison there...
16:31
<maldridge>
yeah, that article is great
16:31
If I could pick any though, I'd pick void's which is bug IRC and someone will deal with it
16:45
<alkisg>
Hehe
16:45* alkisg waves
16:45alkisg is now known as work_alkisg
16:51
<maldridge>
'later
16:53dtcrshr has joined IRC (dtcrshr!~datacrush@unaffiliated/datacrusher)
17:14Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving)
17:14Faith has joined IRC (Faith!~paty_@unaffiliated/faith)
17:25khildin has left IRC (khildin!~khildin@62.235.15.170, Ping timeout: 250 seconds)
17:28khildin has joined IRC (khildin!~khildin@62.235.15.170)
17:29Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Remote host closed the connection)
17:32vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:34vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Client Quit)
18:11telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
18:12telex has joined IRC (telex!teletype@freeshell.de)
18:40cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 256 seconds)
19:03prpplague has joined IRC (prpplague!~David@134.134.139.70)
19:10bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 268 seconds)
19:14vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi, Ping timeout: 240 seconds)
19:19cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
20:25ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
20:41dgroos has joined IRC (dgroos!~dgroos@x-134-84-0-169.vpn.umn.edu)
20:41
<dgroos>
Hi!
20:42
My ltsp-pnp setup with 14.04.3 was working great until all of a sudden it wasn’t :-(
20:43
<maldridge>
generally that's how things break; what broke in this iteration?
20:43
<dgroos>
Now, I can’t log into clients: neither as admin/local users or via binding to the AD network.
20:43
maldridge: hi :)
20:44
This is feeling like just a few days ago before I reinstalled and everything just worked.
20:45
<maldridge>
if you "tail -f /var/log/auth.log" what do you see when you try to log in
20:45
<dgroos>
Luckily I cloned the server and could re-install but I want to solve/understand.
20:49
http://paste.ubuntu.com/12323599/
20:50prpplague has left IRC (prpplague!~David@134.134.139.70, Quit: Leaving)
20:51
<maldridge>
odd, so it makes it as far as authenticating and then disconnects for no reason?
20:51
is there a firewall on the server?
20:52
<dgroos>
Don’t think so. I overstated the prob… actually AD-bound individuals can log in though they get an error message just before starting. Here’s the log: http://paste.ubuntu.com/12323622/
20:53vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
20:53
<dgroos>
I’m going to ‘un-join’ from the AD domain and re-try these 2 logins…
20:54
<maldridge>
ok
20:54dtcrshr has left IRC (dtcrshr!~datacrush@unaffiliated/datacrusher, Ping timeout: 252 seconds)
20:56
<dgroos>
got this when un-joining: http://paste.ubuntu.com/12323649/ …
20:59
<maldridge>
that looks normal, do your logins work unjoined?
20:59dtcrshr has joined IRC (dtcrshr!~datacrush@unaffiliated/datacrusher)
21:00
<dgroos>
when trying to login as a local user (on another client) now after AD in unjoined I get: http://paste.ubuntu.com/12323673/
21:03
<maldridge>
hm, that implies that its something in ldm that's killing it
21:04
as that is a clean disconnect from the client
21:06pbailey has left IRC (pbailey!36f0c5e1@gateway/web/freenode/ip.54.240.197.225, Ping timeout: 246 seconds)
21:07
<maldridge>
not really sure what to tell you in that case, that's farther into ltsp than I've gotten so far
21:09
<dgroos>
hmmm… I’ll try and google this, I imagine there’s a bug report, if not perhaps someone can help me craft one when it comes to that point, but I do need to communicate with someone who has the inside/current knowledge of ltsp (and maybe its -pnp version). Thanks again for your help.
21:10
<maldridge>
yeah, that's either vagrantc or work_alkisg, possible vmlintu but I'm not really sure
21:10
good luck!
21:10
<dgroos>
thanks!
21:20
<vagrantc>
what's the issue?
21:20
dgroos: ^^ ?
21:21* vagrantc is troubleshooting something else, but maybe can help
21:21
<dgroos>
This morning in the middle of class, login stopped working on the clients.
21:21
vagrantc: thanks!
21:22
Neither local nor AD-bound could log in.
21:23
Yeah, then some while later, AD people could log in. Seems like I didn’t do anything to cause this.
21:24
Here’s a paste of tail -f /var/log/auth.log: http://paste.ubuntu.com/12323599/
21:25myrdd_ has joined IRC (myrdd_!~quassel@55d43b08.access.ecotel.net)
21:25
<dgroos>
right now people in the AD group can log in but get this message:
21:26
<vagrantc>
anything in the user's ~/.xsession-errors that seems meaningful?
21:26
<dgroos>
“Xsession: warning: unable to write to /tmp; X session may exit with an error” and it has a button before that with an “Okay” and if I press that login works for that AD user.
21:27
I’ll check…
21:30zamba has left IRC (zamba!marius@flage.org, Ping timeout: 260 seconds)
21:30
<vagrantc>
"df -h /tmp" ?
21:30
maybe your /tmp or / is full?
21:30
<dgroos>
Nothing that I recognize BUT the time they were made seems around the time when the problem occurred, (approx.) http://paste.ubuntu.com/12323885/
21:31
says: /dev/sda1 70G 12G 55G 17% /
21:34
<Hyperbyte>
What about "ls -ald /tmp" ?
21:35
<dgroos>
hey Hyperbyte !
21:35
drwxrwxrwt 5 root root 36864 Sep 9 16:30 /tmp
21:51zamba has joined IRC (zamba!marius@flage.org)
21:57Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving)
21:58
<dgroos>
vagrantc Hyperbyte The strangest thing is that this problem just appeared in the middle of 3rd period (those logged in fine, but no one else could login).
21:58
No one could log in 4th period, and by chance a student tried in 7th period and it was working for them again. I did nothing to stop it working nor to get it working either time.
21:58
(talking about AD users, I haven’t been able to since 3rd)
21:59
<vagrantc>
can you ssh in?
21:59
<dgroos>
I didn’t know you could into ltsp clients… I’ll try.
22:02
“ssh 192.168.67.115” “Read from socket failed: Connection reset by peer”
22:03
<vagrantc>
no, to the server
22:04
<dgroos>
Oh yes, I’ve been working on the server and have ssh’ed into it from this laptop, no issue. (though I am a bit concerned logging out of the server (desktop session).
22:04
<vagrantc>
try as one of the users for the thin client
22:04
in your paste, you had user "d" ...
22:05
ssh d@localhost
22:05
if you don't want to log out
22:05
<dgroos>
ahhh… my attempt at not putting out my userid ‘out there’
22:05
k’
22:07
Yes, I’m able to login to an AD user, through ssh on my laptop, to the ltsp server.
22:07
<vagrantc>
do you have multiple logins with the same user on multiple terminals?
22:08
<dgroos>
I’m logged into the server, tried to log into client—that’s not working now, though have done that many times in the past, if that’s what you mean.
22:09
<vagrantc>
is your login from before or after the problems started?
22:09
and is your login using ssh from your laptop, or a thin client?
22:10
i'm just trying to get an understanding of your situation...
22:10
<dgroos>
that’s right, after, since I tried to update/rebuild the ltsp-image as a way to try and fix things after 4th period.
22:11
from laptop—I’ll try from a client to server.
22:12
Sure. Am using ltsp-pnp with 14.04.3. Have 1 teacher computer/server, 16 clients at the minute. 1 main switch to most of the client. 4 clients connected through a second switch which plugs into the first switch.
22:15khildin has left IRC (khildin!~khildin@62.235.15.170, Quit: I'm gone, bye bye)
22:15
<vagrantc>
ok, so these are fat clients?
22:16
<dgroos>
Right now, I just logged into the FAT client with a student user, then opened a terminal and was able to ssh into the server as myself d@192.168.67.1.
22:16
Yes, all fat clients.
22:17
<vagrantc>
my guess is there was just some transient glitch with your AD setup that wasn't really LTSP related at all...
22:18
if it's working now...
22:18
or, there's still the "cannot write to /tmp" issue?
22:19
<dgroos>
makes sense. The only issue is that I can’t log into the clients. But then, I don’t need to either. Just that it would be nice to get it working properly. Maybe I should re-build the clients again now that the problem for them isn’t happening.
22:20
vagrantc: yes, I’m going to do that and maybe it will be all working tomorrow :-)
22:20
worth a hope!
22:20
Thanks for investigating this problem.
22:21
<vagrantc>
without people using LTSP, a lot of my work goes to waste :)
22:21
<dgroos>
I’ve been working to make it the ‘next big thing’ here in our district. That continues to be another story :D
22:22
<vagrantc>
whereabouts, if you don't mind?
22:22
<dgroos>
Minneapolis, Minnesota, USA
22:23* vagrantc wonders if pschie is still in that area
22:25
<dgroos>
there was someone in Duluth…
22:28
I get no ‘hits’ when I type in “pschie” ltsp
22:29
<vagrantc>
i guess it was scheie
22:30
came out to at least one LTSP by the Sea get-together
22:33
<dgroos>
Cool. I just googled, looks like he’s “in town”, I’ll connect with him, I see he’s on linked in. :)
22:34
<vagrantc>
working on getting some LTSP setups going (or updated) in some local schools in Portland
22:35
<dgroos>
-pnp?
22:35
<vagrantc>
gets a little old working with virtual thin clients all the time... :)
22:35
basically, although using lightdm instead of LDM.
22:35
but they're basically kiosks with a full desktop, not authenticated users
22:36
much simpler setup from an administrator perspective, if that workflow works for the site
22:36
<dgroos>
why not user accounts? (though I’m swearing at the latter right now…)
22:36
anticipated my question…
22:37
<maldridge>
dgroos: most of the time people are authenticating to some service you don't manage?
22:37
and/or just want a web browser
22:37
<dgroos>
tell me about it!
22:37
<vagrantc>
yup, that's the main use-case ... web browser
22:37
some word processing
22:38
<dgroos>
True. Actually, I pretty much don’t even use the home folders much, mainly the browser with google docs and various other web apps.
22:38
<maldridge>
my site migrated away from windows and one of the only questions was "is there still going to be firefox/chrome?"
22:39
<dgroos>
But, we do cmaptools but I guess we could have that not store things on the desktop account though that does make things easier.
22:39
maldridge: for sure!
22:40
<vagrantc>
yeah, i think most users save things to usb sticks or remote drives of one form or another
22:41
not having user configuration also makes it more feasible to setup fully redundant LTSP servers, possibly with live failover (although NBD/NFS may make that difficult)
22:41
well, just simpler all around
22:41
<dgroos>
right, when they need images, it usually is temporary, just for the current session. Hmmmm…. would epoptes work with it?
22:45
<vagrantc>
should
22:45
haven't tried yet, but plan to soon
22:46
<dgroos>
I’ll be interested in hearing…
22:47* vagrantc waves
22:49vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
22:56
<dgroos>
as well dgroos :)
22:56dgroos has left IRC (dgroos!~dgroos@x-134-84-0-169.vpn.umn.edu, Quit: dgroos)
23:10myrdd_ has left IRC (myrdd_!~quassel@55d43b08.access.ecotel.net, Quit: myrdd_)