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


Channel log from 11 April 2011   (all times are UTC)

00:01vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) left irc: Quit: leaving
00:09
<viks_>
#ubuntu
00:34dobber (~dobber@89.190.197.77) joined #ltsp.
00:36
01:07srvmng (~chatzilla@adsluser2907.att.sch.gr) joined #ltsp.
01:08
<srvmng>
hi
01:08
I have an ltsp problem
01:09
Everything was working fine
01:10
But after an update and compression of the virtual disk I get an authentication failure
01:10
how can I login in console mode and check the error?
01:10
<alkisg>
Try: sudo ltsp-update-sshkeys && sudo ltsp-update-image
01:10
That's the most usual cause of the problem
01:10
<srvmng>
01:10
<alkisg>
If that fails, you can troubleshoot later :)
01:10
Hehe :)
01:10
Hi srvmng
01:10
<srvmng>
OK
01:11
<alkisg>
srvmng: Are you using sch-scripts?
01:11
<srvmng>
YUes
01:11
Yes
01:11
<alkisg>
Ah ignore the above then
01:11
In sch-scripts we ignore the ssh keys
01:11
Go to system > administration > log viewer
01:12
Then open a client and try to login
01:12
See if you get an authentication entry in auth.log
01:15
<srvmng>
I dont get one
01:15
Also the login screen is different
01:16
<alkisg>
srvmng: ah, fat clients?
01:16
<srvmng>
Instead of the white one with the red strip on the middle I get the same login screen I get on the server
01:16
<alkisg>
You probably selected "gdm" instead of "ldm" as the login manager
01:16
<srvmng>
Thin
01:16
And Fat
01:17
<alkisg>
In the update, you probably got a prompt "what display manager do you want? gdm/ldm"
01:17
<srvmng>
I tried the login on the thin though
01:17
<alkisg>
With ldm preselected
01:17
<srvmng>
gdm
01:17
<alkisg>
And you chose gdm instead
01:17
You need to undo that, and select ldm again
01:17
Then, compress the image and you're ready to go
01:17
Let me get you the link to all the necessary steps...
01:17
<srvmng>
I did, same thing
01:18
<alkisg>
http://users.sch.gr/alkisg/tosteki/index.php?topic=3347.0
01:23vmlintu_ (~vmlintu@nblzone-240-143.nblnetworks.fi) left irc: Ping timeout: 258 seconds
01:23
<srvmng>
OK I did the steps and now it recompresses
01:23
I didn't update though
01:23
Just selected recompress
01:23
<alkisg>
No need to update. dpkg-reconfigure gdm in the chroot, and create that file mentioned in the link
01:24
<srvmng>
Ah, OK thanks!
01:24
Lets see
01:24
<alkisg>
...and then compress, as you did.
01:24
srvmng: btw, you do know about #linux.sch.gr, right?
01:24
<srvmng>
Although I didn't get a prompt to select gdm or ldm
01:25
I do now!
01:25
Thanks!
01:25
<alkisg>
;)
01:31viks__ (ca8a720f@gateway/web/freenode/ip.202.138.114.15) joined #ltsp.
01:31
<viks__>
how to set default page to firefox in ltsp
01:33
alkisg : let me know how to set default page in firefox
01:38otavio (~otavio@debian/developer/otavio) left irc: Ping timeout: 246 seconds
02:01
<viks__>
.
02:02
can anybody provide me the link to set ltsp with AD
02:02
<NeonLicht>
What is AD?
02:04
<elias_a>
Active Directory. Foul acronym by MS. Stay away from it :)
02:05Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
02:06
<knipwim>
viks__: try google, i see some links
02:07
<NeonLicht>
Some people use that, really? Come on! :D
02:15
<Hyperbyte>
viks__: default page in Firefox has nothing to do with LTSP. It's a Firefox setting. I believe Firefox has some 'mandatory' settings in /etc/, in which you can place settings that users cannot change. You could probably set the homepage there. Refer to the Firefox docs for more info.
02:35vmlintu_ (~vmlintu@dsl-hkibrasgw2-ff2cc300-244.dhcp.inet.fi) joined #ltsp.
02:41
02:54viks_ (ca8a720f@gateway/web/freenode/ip.202.138.114.15) left irc: Ping timeout: 252 seconds
02:54viks (ca8a720f@gateway/web/freenode/ip.202.138.114.15) left irc: Ping timeout: 252 seconds
02:55viks__ (ca8a720f@gateway/web/freenode/ip.202.138.114.15) left irc: Ping timeout: 252 seconds
03:17Trixboxer (~Trixboxer@office.supportdepartment.net) joined #ltsp.
03:29srvmng (~chatzilla@adsluser2907.att.sch.gr) left irc: Read error: Operation timed out
03:31U4 (~User_4574@unaffiliated/user-4574/x-8844190) joined #ltsp.
03:58Da-Geek (~Da-Geek@94-116-151-144.dynamic.thecloud.net) joined #ltsp.
03:58Da-Geek (~Da-Geek@94-116-151-144.dynamic.thecloud.net) left irc: Remote host closed the connection
04:01
<andygraybeal>
morning :)
04:01
<elias_a>
andygraybeal: G'day!
04:01
<andygraybeal>
:)
04:01
<elias_a>
andygraybeal: How's the weather?
04:01
<andygraybeal>
It's actually starting to feel great out!! the past two days have been amazing
04:01
i walked about 4 miles yesterday! and got some sun. it's wonderful
04:02
how about for yuo?
04:02Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Quit: I Leave
04:04
<U4>
hi guys, im having a problem.
04:04
I recently changed shell to fish (yeah, i like it) and on my home machine (std lucid install) all is well and i've chsh'd to fish now. my work machine however is an ltsp client. i apt-get installed fish, and it works ok, but when i chsh to fish, whenever i try to log in it gives me a black screen and returns me to the login screen. i logged onto the host machine with a kbd/monitor and changed it back to bash and i can log on again. anyone got
04:19
<alkisg>
U4: your sentence was too big, it was cut off at "anyone got "
04:20
<U4>
"too big"?
04:20
how does that even...
04:20
<alkisg>
Yes, there's a limit in irc
04:20
Maybe 255 chars
04:20
<U4>
really?
04:20
bizzaro
04:20
anyone got any ideas as to why it doesnt work?
04:20
<alkisg>
If you `chsh fish`, can you ssh to the server from another machine?
04:31Nick change: zz_evil_root -> evil_root
04:40otavio (~otavio@debian/developer/otavio) joined #ltsp.
05:10artista_frustrad (~artista_f@187.7.151.105) left irc: Read error: Operation timed out
05:17RiXtEr (~blah@72-161-238-34.dyn.centurytel.net) left irc: Ping timeout: 276 seconds
05:18RiXtEr (~blah@72-161-236-101.dyn.centurytel.net) joined #ltsp.
05:24artista_frustrad (~artista_f@187.7.151.105) joined #ltsp.
05:25brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
05:30mgariepy (~mgariepy@ubuntu/member/mgariepy) joined #ltsp.
05:30komunista (~slavko@adsl-195-168-237-003.dynamic.nextra.sk) joined #ltsp.
05:35
<mgariepy>
good morning everyone
05:41
<elias_a>
mgariepy: Good afternoon to you, brother!
05:49
<mgariepy>
still walking upside down elias_a ?
05:51
<muppis>
Same side we are, if we are same side of ecuador. ;)
05:52
<mgariepy>
hehe ;)
05:52
summer is slowly getting through over here :)
05:55
<elias_a>
mgariepy: We still have some snow here.
05:55
Rabbits have eaten my appletrees...
05:55
Or hares, more likely....
05:56
Next winter I am going to eat the hares...
05:56
<mgariepy>
haha
05:57
elias_a, you do hunting or are just pissed off by the hares?
05:57brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left irc: Quit: brunolambert
05:59U4 (User_4574@unaffiliated/user-4574/x-8844190) left #ltsp.
05:59
<elias_a>
mgariepy: Used to hunt. Now I am just pissed off.
06:01
While having a morning cigarrette I read aloud the editorial of the local shitty newspaper and one of the hares just looked at me and listened!
06:01
The beasts just listen to the scariest stuff I know about without a sign of fear!
06:02
Something has to be done! :D
06:16shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) joined #ltsp.
06:21brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
06:22
<mgariepy>
lol
06:56bobby_C (~bobby@85.124.22.227) joined #ltsp.
07:01wwx (~ww@raamat.polva.ee) left irc: Read error: Connection reset by peer
07:01wwx (~ww@raamat.polva.ee) joined #ltsp.
07:14komunista (~slavko@adsl-195-168-237-003.dynamic.nextra.sk) left irc: Quit: Leaving.
07:18komunista (~slavko@adsl-195-168-237-003.dynamic.nextra.sk) joined #ltsp.
07:23komunista (~slavko@adsl-195-168-237-003.dynamic.nextra.sk) left irc: Quit: Leaving.
07:24komunista (~slavko@adsl-195-168-237-003.dynamic.nextra.sk) joined #ltsp.
07:28patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
07:39mistik1 (mistik1@unaffiliated/mistik1) left irc: Read error: Connection reset by peer
07:39mistik1 (mistik1@69.160.123.173) joined #ltsp.
07:39mistik1 (mistik1@69.160.123.173) left irc: Changing host
07:39mistik1 (mistik1@unaffiliated/mistik1) joined #ltsp.
07:43patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Quit: Ex-Chat
07:52Nick change: evil_root -> zz_evil_root
08:02Roasted (~jason@206.82.22.190) joined #ltsp.
08:12alexqwesa (~alex@alexo-veto.broker.freenet6.net) left irc: Ping timeout: 260 seconds
08:17staffencasa (~staffenca@128.193.148.149) joined #ltsp.
08:19Nick change: zz_evil_root -> evil_root
08:21alexqwesa (~alex@alexo-veto.broker.freenet6.net) joined #ltsp.
08:24cliebow (~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us) joined #ltsp.
08:32Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) left irc: Ping timeout: 260 seconds
08:35Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) joined #ltsp.
08:37patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
08:39Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) left irc: Ping timeout: 240 seconds
08:42Ahmuck-Sr (~quietly@p178n22.ruraltel.net) joined #ltsp.
08:43Nick change: evil_root -> zz_evil_root
08:47dobber (~dobber@89.190.197.77) left irc: Remote host closed the connection
08:49Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) joined #ltsp.
08:53Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) left irc: Read error: Operation timed out
09:01
<Roasted>
All right. Time talk again. I hereby give up for now as it is not a big deal. The time between the login screen and the actual box does not match on my thin clients.
09:01
I have NTP installed on the server, it's pointed to our local time server, it's running, it's fine.
09:01
Once clients log in, perfect time. Once they log out, it's whacked out to some other foreign time. 7:58, 7:59, 8:04 are just a few I see from where I sit.
09:02
<_UsUrPeR_>
Roasted: I believe I can give you some information that may help. Let me check my notes
09:02
<Roasted>
Just wanted to throw that out there, as my time is fine but the login screen time is still whacked out. Appreciate all of the help you guys gave me, and I hate to be a nag, but I figured I would at least make it known in case.
09:02
_UsUrPeR_, all right. I wasn't looking for help necessarily, but if you have some guidance that would be great. I've just spent a lot of time on it and I want to make my findings known since it's the least I can do to help.
09:02
<_UsUrPeR_>
first thing first: have you set a time server in your lts.conf?
09:02
<Roasted>
yes
09:03
via IP
09:03
<_UsUrPeR_>
ok, cool
09:03
<Roasted>
TIMESERVER=1.2.3.4
09:03
under default
09:04
<_UsUrPeR_>
ok. What does 1.2.3.4 correspond to? APNIC? Is that a valid time server?
09:04
<Roasted>
oh I was just disguising the IP of our actual time server
09:04
our REAL IP of the time server is in place of 1.2.3.4
09:04
I just did that so you could see the exact formatting I had in lts.conf
09:04
<_UsUrPeR_>
lol oh, ok :)
09:04
that's a fine format
09:05Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) joined #ltsp.
09:05
<_UsUrPeR_>
Are all the thin client BIOSes set properly?
09:05
I believe I have a fix for that.
09:05
that may be where the strange times are coming from
09:05
<Roasted>
I'm nearly positive they are. However this lab I haven't been to in about a month since... well... LTSP has given me ZERO issues here :P
09:05
Let me reboot one or two and see
09:05
yes, time is set correct
09:06
<_UsUrPeR_>
ok, for the record, the command to set the BIOS time from a local thin client is as follows: "hwclock --systohc"\
09:06
minus the backslas and quotes
09:06
<Roasted>
these two boxes were showing me 7:58 and 8:03, yet they have 12:03 and 12:04 in BIOS
09:06
<_UsUrPeR_>
ok, so are they "off" by hours then? I.E. wrong time zone?
09:06
<Roasted>
okay, that's a good tip
09:07
all of these in this lab are off by the same amount of hours yet their minutes vary
09:07Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) left irc: Read error: Operation timed out
09:07
<_UsUrPeR_>
You can also set the time zone in the lts.conf
09:07
<Roasted>
I have 758, 803, 759, 806, etc
09:07
<_UsUrPeR_>
that's why I am asking
09:07
<Roasted>
I already had that in there
09:07
but I removed it when I added timeserver
09:07
I didnt want it to conflict (not sure if it would)
09:07
however, the lab at the high school was different
09:07
<_UsUrPeR_>
No, it's good to have the time zone noted
09:07
<Roasted>
I had 1914, 1914, 1915, 2314, 2135, etc
09:07
ah okay, let me re-add it
09:07
<_UsUrPeR_>
hmm. ok, that's weird.
09:07
<Roasted>
I wasn't aware
09:08
now mind you, Im not sure if I have NTP set up right there
09:08
I learned a lot this morning about NTP in the middle school (where Im at now)
09:08
<_UsUrPeR_>
I would recommend that you try an external NTP source
09:08
<Roasted>
so now that I think about it, pretend I didnt say anything about the 19 and 23 etc
09:08
<_UsUrPeR_>
I notmally use ntp.ubuntu.com
09:08
notmally = normally
09:08
just see if there's a difference
09:08
<Roasted>
as your time server?
09:09
<_UsUrPeR_>
(ntp.ubuntu.com = 91.189.94.4)
09:09
yes
09:09
just for testing purposes
09:09
because your times should not be off by a matter of minutes
09:09
<Roasted>
I agree
09:09
<_UsUrPeR_>
it should normally be fractions of a second :)
09:09
<Roasted>
mind you, these two had their minutes offset in BIOS
09:09
however they didnt match up there either
09:10
thin client time was off by like 6 minutes
09:10
bios time off by 1 minute
09:10
okay, image updated, timezone added with timeserver, still pointing to our internal time server, booting up
09:10
<abeehc>
do you have ntpdate in the chroot\
09:10
<Roasted>
I'll try the ntp server in a sec
09:10
<_UsUrPeR_>
ahh hmm. The BIOS clock tends to only affect localapps
09:10
<Roasted>
ntpdate... the installed package?
09:10
<abeehc>
YES
09:10
<_UsUrPeR_>
however, it has appeared for me other places
09:10
<abeehc>
4th time
09:10Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) joined #ltsp.
09:10
<Roasted>
pretty sure I do
09:10
<abeehc>
ntpdate is chroot is really helpful
09:11
<Roasted>
this is a thin environment though
09:11
<abeehc>
login screen shows client time, logged in and you see server time
09:11
<_UsUrPeR_>
chroot to your ltsp image and "dpkg -i *ntp*"
09:11
<abeehc>
doesn't make any difference
09:11
<Roasted>
good to know. let me take that in my notes quick...
09:11
<abeehc>
if you had ntpdate in the chroot you simply wouldn't be here right now
09:11
<Roasted>
okay okay, give me a second.
09:11
<_UsUrPeR_>
abeehc: is ntpdate installed by default?
09:11
<abeehc>
nah not to my knowledge
09:11
I'm not sure why
09:12
<_UsUrPeR_>
strange. It's not something that I am familiar with pertaining to getting a proper time
09:12
<abeehc>
i wasn't sure it is required but now i am pretty sure
09:12
<Roasted>
abeehc, is what you said about login screen = client, logged in = server time, the same for thin and fat?
09:12
(just for my note references)
09:12
<abeehc>
in any ccase it makes troubleshooting the server much much easier
09:12
no that's just for thin, Roasted
09:12
<Roasted>
okay, thank you
09:13
abeehc, in a thin environment, when you say is something installed ot chroot, it simply refers to being installed on the server itself, right.
09:13
I dont need to sudo chroot in as I do fat clients in this scenario
09:13
right?
09:13
<_UsUrPeR_>
Roasted: incorrect. The chroot is the thin client image, completely independant of the server's installed files
09:13
<abeehc>
no it means being installed in the thin chroot
09:14
<_UsUrPeR_>
but that only pertains to locally-run applications
09:14
<Roasted>
okay, so for this scenario I should sudo chroot to the i386 folder and install ntpdate
09:14
<abeehc>
yep
09:14
<Roasted>
okay
09:14
that's where I fouled up
09:14
<_UsUrPeR_>
client time is a locally-run application pertaining to time on the thin client itself. Typically that would be transparent to the user
09:14
<abeehc>
then reb oot and MAGIVC
09:14
<Roasted>
I associated thin client chroots as being PART OF the server
09:14
since if I install audacity on the server, bam, it shows up on the client end
09:14
<abeehc>
once you have it in the chroot you could test like this (i shelled into client) http://pastebin.com/S9bLPuv9
09:15Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) left irc: Ping timeout: 240 seconds
09:15
<_UsUrPeR_>
Roasted: that's because audacity is being run on the server. If you wanted to run audacity on the clients, you would have to install it on the chroot
09:15
<Roasted>
right right
09:15
I should have never touched fat clients
09:15
I should have stayed with thin till I learned them through and through
09:15
<abeehc>
in your case I think, from clientshell, "ntpdate -d server" will work
09:16
and confirm your ntp server is talking correctly
09:16
but i imagine, upon adding that package and rebooting client, everything will just work
09:16
<Roasted>
so uh
09:16
sudo apt-get install ntpdate...
09:16
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
09:16
within the chroot
09:18
abeehc, from the server I was able to get ntp working correctly with ntpdate, etc. It told me I was off by .000000029 and sync'd me, then I started the service and it was fine. I didn't realize I had to have the service off to ntpdate successfully.
09:18
<abeehc>
i have no idea what you just said
09:18
that's cool thought I'm guessing ntpdate is installed in the chroot already
09:18
<Roasted>
just expanding on what you suggested to me
09:18
<abeehc>
and you can confirm from a client shell
09:19
i never suggested disabling services of any sort
09:19
<Roasted>
stop ntp service, sudo ntpdate ip.of.our.server, sync'd me up, started ntp service
09:19
I know
09:19
I just had issues running sudo ntpdate
09:19
and I had issues because the service was running. users in Ubuntu told me I need to stop the service, then sudo ntpdate, then start it
09:19
and bam - it worked then
09:19vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) joined #ltsp.
09:20
<abeehc>
meh clients are interesting
09:20
client shell - > my suggestion 'ntpdate -d server'
09:20
<Roasted>
I'm just not going to worry about the login screen time.
09:20
Once I'm in, it's fine.
09:20
<abeehc>
whatever
09:20
<Roasted>
I just have no idea WHY
09:20
<abeehc>
i suspect
09:20
in 3 days
09:20
you'll come back and ask the same questions
09:20
<Roasted>
well, it'd be nice if it... worked... ;)
09:21
it would avoid user confusion who sits down at these clients
09:21
but from what I've read and from what's been suggested to me, I've done everything, I believe.
09:21
<abeehc>
i can assure you, it works
09:21
nope
09:21
<alkisg>
Roasted: when you login it's fine because YOU ARE ON THE SAME MACHINE. THE SERVER. (sorry for yelling :))
09:21
<Roasted>
what didn't I do?
09:21
<abeehc>
you've not done what i sugeested
09:21
i've suggested it at least 4 times over the last two weeks
09:21
<Roasted>
alkisg, I understand.
09:22
<alkisg>
(07:20:37 PM) Roasted: I just have no idea WHY
09:22
<Roasted>
abeehc, okay. what did you suggest to me?
09:22
alkisg, I meant why it doesn't work at login screen.
09:22
<abeehc>
get a client shell and run that ntpdate command
09:22
because the client time is wrong
09:22
<Roasted>
you're suggesting I do this on every single client?
09:22
<abeehc>
no i just want to see you paste the same output as i pastewd ABOVE
09:23
<alkisg>
abeehc: btw, ntpdate on thin clients doesn't work as a service on ubuntu
09:23
<abeehc>
that is what i understood
09:23
<alkisg>
They don't receive an if-up event, and ltsp-build-client disables most services by default
09:23
<Roasted>
abeehc, sec. pasting in a minute
09:24
http://tinypaste.com/d73a1
09:24
<abeehc>
alkisg: for the clients to adhere to the bits in lts.conf pertaining to timeserver, ntpdate isn't required?
09:24
at the least i find it helpful with testing
09:24
but i've never been sure it's required fro the client to get the right time from an ntp server
09:24
<alkisg>
abeehc: it's required, but it's ran manually from the ltsp init code, not as a service
09:24
Also, to use an external TIMESERVER, nat is needed on the server
09:24
<abeehc>
ok that's what i understood hence a reboot will kick it in
09:24Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) joined #ltsp.
09:25
<alkisg>
Finally, I think that if ntpd is installed in the chroot, then ntpdate won't work. But I'm not sure of that one.
09:25
<abeehc>
Roasted: is 10.52.1.8 exactly what you have in lts.conf?
09:25
<Roasted>
abeehc, sure is.
09:25
and /etc/ntp.conf
09:25
<alkisg>
Roasted: sudo chroot /opt/ltsp/i386/ dpkg -l '*ntp*' | grep ^ii ==> if you run that on the server, what's the output?
09:26
<vagrantc>
Roasted: so TIMESERVER=auto didn't work?
09:26
<Roasted>
vagrantc, nope.
09:26
vagrantc, I just went back to using the IP.
09:26
alkisg, ii ntpdate 1:4.2.4p8+dfsg-1ubuntu6 client for setting system time from NTP servers
09:27
<vagrantc>
Roasted: there must be firewalling in the way somewhere.
09:27
Roasted: did you ever run the "iptables -L" and "iptables -L -n" commands?
09:27
<alkisg>
Roasted: to be able to troubleshoot, like abeehc said, follow these steps to get a local console: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using%20a%20shell%20SCREEN
09:27
From there you can troubleshoot ntpdate etc
09:28
<abeehc>
i think he has done that? http://tinypaste.com/d73a1
09:28
wait that doesn't make sense
09:28
<alkisg>
abeehc: that's on the server
09:28
He didn't understand that he was supposed to do it locally on a client
09:28
<abeehc>
agreed :(
09:28
<Roasted>
I did do it from the client, but I was logged in as a local user
09:28
<alkisg>
That's on the server. :)
09:29Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) left irc: Read error: Operation timed out
09:29
<Roasted>
so I need a domain user?
09:29
<alkisg>
No, read the link I pasted above
09:29
Follow the instructions ther
09:29
e
09:29
And when we say "execute something locally", do it in screen_02, i.e. press alt+ctrl+f2 on the client
09:30
You won't be able to copy-paste, but it should get you going
09:31
<Roasted>
updating image
09:32
<alkisg>
Did you really read the page?
09:32
<Roasted>
am I to just repeat the command I did in the pastebin but on the client? as in alt-ctrl-f2
09:32
<alkisg>
"Instead of unlocking the root account and updating the image, "
09:32
==> i.e. you don't have to update the image
09:32
<Roasted>
oh. I always update it out of habit when I touch lts.conf
09:32
<alkisg>
Yes, on the client run: ntpdate -d server
09:33
Exactly. Don't change anything.
09:33
(in screen_02)
09:33
Don't change the word "server"
09:33
<Roasted>
it comes back with the static IP of the LTSP server
09:33
<alkisg>
Then run "date" to see your date
09:34
<Roasted>
Mon Apr 11 08:31:32 EDT 2011
09:34
<alkisg>
Apart from the server IP, did it produce any errors in synchronization?
09:34
11 Apr 19:34:35 ntpdate[8753]: adjust time server 91.189.94.4 offset 0.069773 sec
09:34
Something like this, as the last line
09:35
<Roasted>
offset 14537.827146
09:35Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) joined #ltsp.
09:35
<alkisg>
So it did synchonize. Is your time OK now on that station?
09:35
You can switch to vt7 with alt+ctrl+f7
09:36
And see the time. But don't login.
09:36
<Roasted>
Nope
09:36
says 8:33
09:36
its 12:36
09:36
<alkisg>
On your server, it's 12:36?
09:36
Not on your hand watch
09:36
Or is it 12:33 ?
09:36
<Roasted>
server via ssh "date"
09:36
Mon Apr 11 12:36:24 EDT 2011
09:37
<alkisg>
OK we'll need some copy/paste here
09:37
So, here's how to do it:
09:37
Again on screen_02
09:37
ntpdate -d server >/tmp/d 2>&1
09:37
scp /tmp/d roasted@server:
09:38
Replace only roasted with your username
09:38Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) left irc: Read error: Operation timed out
09:38
<Roasted>
well, I'm in as root. so root?
09:38
<alkisg>
After those commands you'll get the output in your home folder, as the file named "d"
09:38
Pastebin that file
09:38
<Roasted>
oh nevermind
09:38
<alkisg>
No, use your actual username. It doesn't matter if you're logged in or not.
09:38
<Roasted>
do I use "server"
09:38
<alkisg>
Yes
09:38
<Roasted>
or replace it with hostname
09:38
<alkisg>
No
09:39
<Roasted>
okay
09:39
done
09:39
sec
09:39
http://tinypaste.com/f2592
09:40
<alkisg>
Roasted: no sync happened
09:40
Your ntpd server is not working properly
09:41
On the server, verify that you actually have ntpd installed: dpkg -l '*ntp*' | grep ^ii
09:41
(when we say "on the server", you can do that from a thin client too, logged on normally)
09:41
<Roasted>
ii ntp 1:4.2.4p8+dfsg-1ubuntu6 Network Time Protocol daemon and utility programs
09:41
ii ntpdate 1:4.2.4p8+dfsg-1ubuntu6 client for setting system time from NTP servers
09:41
I did it via SSH from my laptop
09:41
<alkisg>
And what do you have in /etc/ntp.conf ?
09:41
<Roasted>
I'll pastebin. sec.
09:42
<vagrantc>
alkisg: ntpdate -d doesn't sync the clock
09:42
<alkisg>
vagrantc: doesn't it set the date?
09:42
OK, no cmos writing, but I thought it sets the date
09:42
<vagrantc>
-d Enable the debugging mode, in which ntpdate will go through all the steps, but not adjust the local clock.
09:42
Information useful for general debugging will also be printed.
09:42
<alkisg>
Ah, sorry
09:42
<vagrantc>
maybe i misread
09:42
<abeehc>
that's accurate
09:43
<alkisg>
vagrantc: you're correct
09:43
<vagrantc>
talk about an annoying debug feature
09:43
<Roasted>
I'm not sure if I got everything since I'm on a small screen using nano over ssh, but I think the whole bottom part is commented out
09:43
http://tinypaste.com/5addf
09:43
<alkisg>
Roasted: go back to screen_02
09:43
<vagrantc>
what if you actually want it to set the clock but print debugging info
09:43
<alkisg>
And run: ntpdate server
09:43
That's the same as before but without the -d
09:44
(which was wrong, it means "debugging but not set the clock")
09:44
After that, try: date
09:44
And see if the time is correct now
09:44
<abeehc>
i think yout ntp.conf has teh server's address i'm not sure that's sane
09:44
<Roasted>
11 Apr 12:43:48 ntpdate(2902): step time server 10.52.66.6 offset 14537.893031 sec
09:44Selveste1 (~Selveste1@88.83.86.20.static.dong.customer.smilecontent.dk) joined #ltsp.
09:44
<Roasted>
date shows 12:44:25
09:44
<alkisg>
Roasted: erm, how were you able to copy/paste?
09:44
<Roasted>
I wasn't
09:44
accurate typing, my friend :P
09:44
<alkisg>
Whoah :)
09:44
<abeehc>
haha
09:44
<Roasted>
login screen says 12:44 now
09:44
nice, nice
09:44
<alkisg>
OK, the time is correct now?
09:45
<abeehc>
ssh on the chroot is the ticket
09:45
<alkisg>
Roasted: now, try: getltscfg -a
09:45
<Roasted>
alt ctrl f2?
09:45
<alkisg>
And see what you have for TIMESERVER there
09:45
Yes
09:45
<Roasted>
TIMESERVER=10.52.1.8
09:45
which is our DC/time server
09:46
<abeehc>
damn
09:46
<alkisg>
Now, try: ntpdate 10.52.1.8
09:46
You probably don't have route to that
09:46
<abeehc>
no
09:46
<Roasted>
11 Apr 12:46:25 ntpdate(3046): adjust time server 10.52.1.8 offset 0.026138 sec
09:47
<alkisg>
That's very strange then
09:47
Which ubuntu version are you using?
09:47
<Roasted>
10.10 64 bit edubuntu
09:47
<vagrantc>
maybe Roasted is running into the race condition around the ntpdate code...
09:47
<alkisg>
vagrantc: what race condition? Haven't heard of that one...
09:48
<vagrantc>
in ltsp-init-common, change: (ntpdate $TIMESERVER; hwclock --systohc --${HWCLOCK:-"utc"} --noadjfile) &
09:48
to: ntpdate $TIMESERVER; hwclock --systohc --${HWCLOCK:-"utc"} --noadjfile
09:48
and rebuild the image
09:49
er, /opt/ltsp/i386/usr/share/ltsp/ltsp-init-common
09:50
apparently, fast clients sometimes finish the init script that calls ntpdate before ntpdate finishes, and that somehow breaks the ntpdate call
09:51
<Roasted>
would that explain why sometimes a small number of clients get the proper time, whereas the majority fails? yet if I reboot the lab, the same thing happens, but with different clients succeeding?
09:51
<alkisg>
Ouch. We can change it to sh -c 'command' & then
09:51mikkel (~mikkel@80-71-132-15.u.parknet.dk) joined #ltsp.
09:53
<alkisg>
gym time, bb all
09:53
<Roasted>
thanks for your help alkisg
09:53alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
09:53
<Roasted>
vagrantc, I'm a little confused. is this a bug that I'm seeing?
09:54
<vagrantc>
alexqwesa: that might have the same issue
09:54
Roasted: might be.
09:54
<Roasted>
was alexqwesa in here expressing the same symptoms I was?
09:54
<vagrantc>
oops. meant that to go to alkisg
09:54
<Roasted>
oh
09:54
<vagrantc>
tab-completion after alkisg left
09:55
Roasted: so edit /opt/ltsp/i386/usr/share/ltsp/ltsp-init-common
09:55
Roasted: change the ntpdate line like i mentioned above.. removing the "(" at the beginning and the ") &" at the end. and then ltsp-update-image
09:56
Roasted: that *might* fix the issue.
09:56
<Roasted>
for what it's worth, that one client alkisg helped me with earlier to get the correct time... just rebooted it, its back to 8:53
09:56
okay, let me do that quick
09:57
vagrantc, do I have to be chroot'd in or can I just nano it with the full path?
09:57
<vagrantc>
Roasted: that's because you only manually ran ntpdate, not the code that syncs with the hardware clock
09:57
<Roasted>
but my hardware (bios) clock has the right time
09:58
<vagrantc>
Roasted: you can just edit the file directly with the full path
09:58
<Roasted>
that's where I get so confused over how these clients are pulling this 4 hour earlier time
09:58
<vagrantc>
Roasted: your BIOS clock should be set to UTC
09:58drdata (~drdata@tw2.udallas.edu) joined #ltsp.
09:59
<Roasted>
my bios clock is 12:57 right now
09:59
whereas server time on ltsp server is 12:58
09:59
yet when I boot it up, login screen says 8:50 something
09:59drdata (drdata@tw2.udallas.edu) left #ltsp.
09:59
<vagrantc>
Roasted: are these machines dual-boot?
09:59
<Roasted>
vagrantc, windows is installed locally, and they pxe boot as first boot option
09:59
<vagrantc>
AH
10:00
<Roasted>
uh oh
10:00
<vagrantc>
you'll also want to set HWCLOCK=local in lts.conf
10:00
i think windows stupidly uses local time instead of UTC
10:00
<Roasted>
so you think windows existence is fouling up my time issue?
10:00
because this is how its set up everywhere...
10:00
<vagrantc>
i think it's setting the clock differently
10:01
but that should still result in a consistantly wrong offset, whereas you reported multiple radically different times
10:01
Roasted: anyways ....
10:01
<abeehc>
even a minute or two is prety much radical
10:01
<vagrantc>
Roasted: one problem at a time...
10:01
abeehc: it was off by arbitrary hours
10:02
<abeehc>
as you say, it shouldn't be
10:02
if it were windows goofing stuff up it should be predicatable
10:02
<vagrantc>
Roasted: so, have you edited ltsp-init-common, rebuilt your image (ltsp-update-image) and rebooted?
10:05drdata (~drdata@tw2.udallas.edu) joined #ltsp.
10:05drdata (drdata@tw2.udallas.edu) left #ltsp.
10:05
<Roasted>
sec, still working on it
10:06
this is hard doing on nano with a small laptop screen...
10:11
are ( ) all I'm changing?
10:11
and &?
10:12
theres already a & though..
10:12
<vagrantc>
Roasted: get rid of them
10:12
your line should be: "ntpdate $TIMESERVER; hwclock --systohc --${HWCLOCK:-"utc"} --noadjfile"
10:13
<Roasted>
without quotes?
10:14
<vagrantc>
*sigh*
10:15
yes.
10:15
<Roasted>
updating
10:16
13:16 as time
10:17
<vagrantc>
worked?
10:18
<Roasted>
every single machine is 13:17 now
10:18
what exactly did that accomplish? just for learning purposes
10:18
<vagrantc>
Roasted: does that mean it worked? or they got it all wrong?
10:18
<Roasted>
they all work
10:18
you nailed it
10:19
vagrantc, where do I send you the case of cold ones you rightfully deserve? :P
10:19
<vagrantc>
Roasted: what that did was wait for ntpdate to finish before proceeding
10:19
<Roasted>
would XP being on the native drives have anything to do with that? Or was that a completely separate idea?
10:19zz_evil_root (~evil@host-98-127-38-101.bln-mt.client.bresnan.net) left irc: Ping timeout: 246 seconds
10:20
<vagrantc>
Roasted: that's sort of a separate problem
10:20
<Roasted>
vagrantc, would this thereby be considered a bug?
10:20
a fixed bug, at that
10:21
<vagrantc>
Roasted: well, it's not really fixed
10:21zz_evil_root (~evil@host-98-127-38-101.bln-mt.client.bresnan.net) joined #ltsp.
10:21Nick change: zz_evil_root -> evil_root
10:21
<vagrantc>
people didn't want ntpdate stalling out to cause a problem... though that obviously has consequences
10:22
<Roasted>
so if ntpdate stalls, it hangs up the entire script?
10:22
the entire boot process, etc
10:22
<vagrantc>
but i think it's better to be slightly slower and correct than faster and broken
10:22
<Roasted>
oh you menat stall as in lag
10:22
I thought you meant stall as in flat out shut off
10:23
I agree, I'd rather have the thing take a second or two longer to boot and be correct.
10:23
vagrantc, is this something exclusive to 10.10 or would it apply to all versions?
10:24
<vagrantc>
Roasted: well, i'm not sure how long ntpdate will wait before proceeding
10:27
apparently, it's been there all along
10:27
it always ran backgrounded ... that's what the "&" does
10:28
<Roasted>
why is it that I ran into it then, but nobody else did?
10:28
I can't imagine our environment here is THAT different from other successful schools in the US who've adapted to it
10:29
<vagrantc>
Roasted: it's not that *nobody* has ever run into it, just not very many
10:30
<Roasted>
I'm failing to see the downside of publishing this "fix" you had me to into the mainstream. What is the worst that could happen? Slightly longer boot time?
10:31
<vagrantc>
yeah, that's what i'm thinking too
10:31
there might have been a discussion on one of the mailing lists recently
10:31
<Roasted>
If ntpdate TANKS and it completely interrupts the boot process, I can see that being an issue.
10:31
But if it just stalls and takes a few more seconds, I'd rather have that.
10:36
<vagrantc>
yup, gadi called that out on march 25th on the ltsp-discuss@lists.sourceforge.net list
10:36
i'll push the commit upstream, and see if anyone balks at it
10:36
<Roasted>
he agrees with you?
10:37
<vagrantc>
Roasted: he figured out the problem
10:37
but gadi also committed the code with it backgrounded
10:38
ntpdate defaults to delaying 1 second, and that seems a price worth paying for correct behavior
10:38
<Roasted>
vagrantc, so wait, what problem did he solve if he committed it backgrounded?
10:38
<vagrantc>
Roasted: he committed the original code that runs it backgrounded
10:38
<Roasted>
on march 25th, or prior?
10:38
<vagrantc>
but he also posted the fix
10:39
Roasted: sometime in 2008
10:39
<Roasted>
ahhh
10:39
<vagrantc>
and posted a fix recently
10:39
<Roasted>
so he posted march 25th bringing the issue I currently have to attention
10:39
<vagrantc>
yes
10:39
<Roasted>
I see, I see
10:40
so if his fix a workaround while backgrounded, or removing the backgrounded entry?
10:40
is*
10:40
<vagrantc>
Roasted: his fix is exactly what i told you to do.
10:40
and that seemed to work.
10:40
<Roasted>
bingo
10:40
gotcha
10:40* vagrantc is weary of the degree of explicitness necessary today...
10:41
<Roasted>
my apologies
10:41
family emergency late last night
10:41
slept all but 2 hours
10:41
what a monday :(
10:44
all right, it's lunch time. vagrantc - your help is very appreciated.
10:44
<vagrantc>
i think this should be even better: ntpdate $TIMESERVER && hwclock --systohc --${HWCLOCK:-"utc"} --noadjfile || true
10:44
otherwise, ntpdate failing might exit the script
10:44
<Roasted>
whats that do?
10:45
<vagrantc>
it basically says "if ntpdate suceeds, also sync the clock, otherwise, just continue on without error"
10:45
<Roasted>
what constitutes ntpdate failing? If it doesn't respond in x-amount of seconds?
10:47
<vagrantc>
committed upstream.
10:48
Roasted: let's just not get into it :P
10:48
<Roasted>
What? I was just curious. :(
10:49
<vagrantc>
any type of failure could cause a problem
10:49
so we just don't worry about it failing
10:50
<Roasted>
do you think I should change my file to what you suggested just now with the true statement?
10:50
or should I sit tight as-is
10:50
<vagrantc>
Roasted: it would be great if you could test the code :)
10:51
<Roasted>
well, it's the least I could do, right? Give me a minute and I'll switch it over.
10:58
vagrantc, I'm not sure it's working
10:58
they're all hanging at the purple Ubuntu loading screen
10:59
dots going across
10:59
been about 120 seconds now
11:04
I switched the file back to the original setting, same deal
11:04
they're still hanging on boot
11:10
well, so much for the fix. they're stalling out now at the ubuntu splash screen. however I backed up the original file, and I can at least restore that and boot htem like normal
11:12
now that Im booting back up with the original ltsp-init-common file, all of them have the same time.
11:12
anyway, lunch time. appreciate the help vagrantc.
11:15brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left irc: Read error: Connection reset by peer
11:15
<vagrantc>
Roasted: well, they synced the time when it worked
11:15brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
11:16Roasted (~jason@206.82.22.190) left irc: Ping timeout: 246 seconds
11:25brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left irc: Ping timeout: 264 seconds
11:25vvinet (~vince@2001:470:8829:1000:227:eff:fe25:ee64) left irc: Read error: Operation timed out
11:25mgariepy (~mgariepy@ubuntu/member/mgariepy) left irc: Read error: Operation timed out
11:25alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
11:37mgariepy (~mgariepy@ubuntu/member/mgariepy) joined #ltsp.
11:38vvinet (~vince@2001:470:8829:1000:227:eff:fe25:ee64) joined #ltsp.
11:43kusznir (~kusznir@casas-net.ailab.wsu.edu) joined #ltsp.
11:44
<alkisg>
vagrantc: I'm not able to reproduce the bug...
11:44
#!/bin/sh
11:44
(sleep 3; echo "It works") &
11:44
echo "Finished"
11:45
I tried closing the file descriptors, nothing, it always works fine
11:45
<vagrantc>
alkisg: might behave differently in the init script?
11:46
<alkisg>
OK, so if I make a wrapper for ntpdate that delays 3 seconds, would that be a reasonable way to reproduce it?
11:46
I.e. if I'm not able to, then that's probably not the reason it fails?
11:46
There isn't a mechanism that kills initscripts, is there?
11:46
(if they delay too long)
11:47
<vagrantc>
alkisg: go for broke... try 30 seconds :)
11:47
<alkisg>
OK
11:48
<vagrantc>
3 seconds seems feasibly not long enough
11:48primeministerp (~ppouliot@64.119.153.82) left irc: Ping timeout: 252 seconds
11:52Roasted (~jason@206.82.22.190) joined #ltsp.
11:52otavio (~otavio@debian/developer/otavio) left irc: Ping timeout: 252 seconds
11:59otavio (~otavio@189.114.111.55) joined #ltsp.
11:59otavio (~otavio@189.114.111.55) left irc: Changing host
11:59otavio (~otavio@debian/developer/otavio) joined #ltsp.
12:10shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) left irc: Quit: Leaving.
12:22emilholstein (~emil@f055118040.adsl.alicedsl.de) joined #ltsp.
12:26
<vagrantc>
alkisg: http://packages.qa.debian.org/i/ipxe.html
12:26
<alkisg>
Cooool!
12:27
(btw I fell into another bug where /etc/rcS.d/S32ltsp-client-setup doesn't source my /usr/share/ltsp/ltsp_config.d/010-sch-client-defaults, so I'm still troubleshooting this before testing time...
12:28
vagrantc, how long before there are builds available to download?
12:28
(.debs etc)
12:28
About a day? Or it takes longer?
12:28otavio (~otavio@debian/developer/otavio) left irc: Ping timeout: 240 seconds
12:28
<vagrantc>
alkisg: you can snag them off of http://incoming.debian.org
12:29
<alkisg>
Thanks :)
12:35otavio (~otavio@189.114.111.55) joined #ltsp.
12:35otavio (~otavio@189.114.111.55) left irc: Changing host
12:35otavio (~otavio@debian/developer/otavio) joined #ltsp.
12:40cliebow (~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us) left irc: Quit: Leaving
12:46Ahmuck (~quietly@p178n22.ruraltel.net) joined #ltsp.
12:47Ahmuck-Sr (~quietly@p178n22.ruraltel.net) left irc: Ping timeout: 276 seconds
12:51Roasted (~jason@206.82.22.190) left irc: Ping timeout: 246 seconds
13:12shawnp0wers (~spowers@linuxjournal/staff/shawnp0wers) joined #ltsp.
13:20brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
13:25brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left irc: Ping timeout: 260 seconds
13:29alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
13:30emilholstein (~emil@f055118040.adsl.alicedsl.de) left irc: Quit: Leaving
13:39Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
13:43Trixboxer (~Trixboxer@office.supportdepartment.net) left irc: Quit: "Achievement is not the end, its the beginning of new journey !!!"
13:50shawnp0wers (~spowers@linuxjournal/staff/shawnp0wers) left irc: Quit: Leaving.
14:31komunista (~slavko@adsl-195-168-237-003.dynamic.nextra.sk) left irc: Quit: Leaving.
14:52ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Read error: Operation timed out
14:55ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
14:57Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Quit: I Leave
14:57ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Changing host
14:57ogra_ (~ogra@ubuntu/member/ogra) joined #ltsp.
14:58Gadi_android (~yaaic@ool-44c75887.dyn.optonline.net) joined #ltsp.
15:02Gadi_android (~yaaic@ool-44c75887.dyn.optonline.net) left irc: Client Quit
15:04
<vagrantc>
huh. there's some sort of /etc/X11/xorg.conf.d ...
15:04
could maybe leverage that instead of generating a monolithic config for X
15:06
wonder what version xorg.conf.d was introduced in
15:17mikkel (~mikkel@80-71-132-15.u.parknet.dk) left irc: Quit: Leaving
15:25Nick change: evil_root -> zz_evil_root
15:38tekoholic (tekoholic@76.249.179.148) left irc: Quit: ZNC - http://znc.sourceforge.net
15:49bobby_C (~bobby@85.124.22.227) left irc: Ping timeout: 260 seconds
16:44staffencasa (~staffenca@128.193.148.149) left irc: Quit: Leaving
17:24MorningSon (~MorningSo@cpe-72-181-35-91.satx.res.rr.com) joined #ltsp.
20:12MorningSon (~MorningSo@cpe-72-181-35-91.satx.res.rr.com) left irc: Quit: WeeChat 0.3.0
20:43tekoholic (tekoholic@bbis.us) joined #ltsp.
21:06alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
21:31alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
22:28dobber (~dobber@89.190.197.77) joined #ltsp.
22:34alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
00:00--- Tue Apr 12 2011