IRC log for #fredlug on 20101215

02:28.32*** join/#fredlug GGD (~GGD@pool-70-109-55-219.clppva.fios.verizon.net)
02:31.09GGDhey stickster_afk
09:06.30*** join/#fredlug nmcbride (~nmcbride@12.48.235.5)
13:26.33*** join/#fredlug GGD (47ffe2b8@gateway/web/freenode/ip.71.255.226.184)
13:26.43GGDmorning stickster
13:27.00GGDjsmith-away:
14:07.42GGDhi jsmith
14:08.25jsmithMorning GGD
14:08.46GGDthings are not so fun fun over here at the GGD land
14:08.58GGDi was working with paul yesterday but work got in the way...
14:09.10GGDand yes i hate it when that happens
14:11.38GGDany ideas?
14:20.10GGDi can log in but after that the screen totally freezes
14:21.53sticksterGGD: Have you tried creating a brand new user? 'useradd newguy' and then 'passwd newguy'
14:22.08sticksterThen see what happens to that user. If he can log in OK, you know it's a local config problem in your account.
14:22.11GGDhold on and i will do that
14:27.12GGDno dice
14:28.21GGD"there is a problem with the configuration server  (/usr/libexec/gconf-sanity-check-2 exited with status of 256)  with a close button
14:29.01GGDand there was a gnome power manager has not been installed correctly please contact your computer admin
14:29.08GGDerror that popped up as well
14:29.35sticksterSo that happens with the brand new user?
14:29.43GGDyes
14:29.58sticksterThat seems to imply you've got RPM problems on this system -- a bad schema in a shared location that otherwise should be fine
14:31.09sticksterCan you run 'package-cleanup --problems | tee pcreport' and see what's reported?
14:31.12GGDwhich is odd as i didn't do anything crazy with it
14:31.19GGDok hold on
14:32.16GGDcould i pipe that to fpaste?
14:32.21GGDthe outcome?
14:32.42sticksterYou can fpaste the 'pcreport' file that was just created
14:32.55stickster'tee' means 'copy the output also to the following filename'
14:33.03GGDahh
14:33.10sticksterIt's nifty!
14:33.36GGD"nothing found"
14:33.42sticksterOK, that's good then.
14:33.54GGDcorrecion "no problems found"
14:34.02sticksterDo 'rpm -V gnome-power-manager' for the heck of it
14:34.17sticksterYou should ideally get no output
14:34.51GGDdone with the power manager
14:35.30sticksterGGD: One other 'simple' suggestion for now
14:35.33sticksterAs root, run this:
14:35.38stickstertouch /.autorelabel
14:35.51sticksterThen reboot the system. It will relabel your SELinux contexts system-wide, which may take a while.
14:36.10sticksterI'm assuming you're running in SELinux enabled mode.
14:36.24stickster(which is recommended)
14:36.39GGDyes as it throws up a whole bunch of those when i boot on my regular login
14:37.09sticksterHm, that may indeed be one of the problems then.
14:37.25GGD16 of them to be exact
14:37.29sticksteryou can see if there are AVC errors by doing 'grep AVC /var/log/audit/audit.log | less'
14:37.51sticksterDo the autorelabel shown above, reboot, and see if you're in any better shape then.
14:38.11GGDrebooting now
14:38.41GGDis it normal to get modprobe errors at first boot up?
14:38.50sticksterNot usually
14:38.58sticksterIt depends on the module
14:39.28GGDi always seem to get them when i boot up a fedora machine.. no mater the hardware,.
14:39.47GGDok we are doing the relabel now
14:40.14GGDand i want to very much appologize for yesterday
14:40.20GGDto your Paul
14:40.37GGDi was trying to get things done here and work got in the way...
14:43.49GGDok relabel is done
14:44.11GGDstill get that gnome power issue error again
14:44.50sticksterDoes the login work though?
14:45.15GGDthe test one or my main log in or either?
14:45.22sticksterThe new one
14:45.27sticksterThe test one
14:45.36GGDno same error
14:45.44GGDthe config server error
14:45.53sticksterCan you click through it and get a session?
14:46.38GGDi get a selinux message box with 19 errors
14:46.44GGDor alerts rather
14:46.47sticksterThat's fine, dismiss it
14:46.53sticksterDo you get a session? panel, menu?
14:47.12GGDget a crash in the setroubleshoot server
14:47.15GGDtwo of them
14:47.51sticksterAgain, dismiss all this stuff
14:47.54sticksterDo you get a panel?
14:48.02GGDno freezes
14:48.09sticksterIt totally freezes?
14:48.14GGDyes
14:48.22sticksterHit Ctrl+Alt+F2 -- do you get a text screen login?
14:48.24GGDi have mouse movement and such but nothing else
14:49.26GGDyes i can get to that
14:49.31sticksterOK, login as the test user there
14:49.31GGDthe text
14:49.45sticksterThen 'fpaste ~/.xsession-errors'
14:49.49GGDim in
14:50.35GGD"no text to send"
14:50.49sticksterdo this:
14:50.54sticksterls -l .x*
14:50.58sticksterThat's dot, x, star
14:51.05sticksteroops
14:51.08sticksterls -ld .x*
14:51.35GGDok i get two files
14:52.01sticksterls -ld .x* | fpaste
14:52.02GGD.xsession-errors and one that says .xsession-errors.old
14:52.36GGDhttp://fpaste.org/LJdT/
14:52.45sticksterWow, interesting
14:53.45GGDis this on the same realm as the cobbler server issue the other day or is this a whole NEW realm?
14:53.48GGDlol
14:53.53sticksterNo, brand new
14:54.20GGDand btw that lappy got so hot that it shut itself down the other night....
14:54.52sticksterAt the terminal run
14:54.57stickster/usr/libexec/gconf-sanity-check-2
14:55.50GGDy or n on the continue?
14:56.27sticksterDoes it give you some output?
14:56.44sticksterhas no idea what this produces since it always completes without output (i.e. no problems found) on his system
14:57.22GGD"the files that contain your perference settings are currently in use
14:57.41sticksterThat's OK, you can continue then
14:57.41GGDyou might be logged in to a session,
14:57.50sticksterOh wait
14:57.51sticksterbetter yet
14:58.24sticksterhit Ctrl+Alt+F1 to return to the GUI, logout there (or hit Ctrl+Alt+Bksp to kill the X server), then Ctrl+Alt+F2 to come back here
14:59.10GGDinteresting...
14:59.18GGDi did that and re did the command
14:59.46GGD"please contact your sysadmin.,..  to resolve this following problem
15:01.14GGD"could not resolve the address "xml:readwrite:/home/test/ .gconf"  in the configuration file "/etc/gconf/2/path": failed: could not make directory  '/home/test/.gconf' :  no space left on device
15:01.26sticksterThere's your problem :-)
15:01.29sticksterType 'df -h'
15:01.32GGDhowever i have a 250 gig hd and i know that its not full
15:01.41sticksterActually...
15:01.43sticksterdf -h | fpaste
15:01.53sticksterkeeps forgetting that useful pipe :-)
15:01.57GGDi have a 250 gig ext that it thinks is a system drive ( i think)
15:02.01GGDlol
15:02.34GGDhttp://fpaste.org/EU0Y/
15:03.00sticksterYup, you've filled your whole system drive somehow
15:03.15GGDhow??
15:03.23sticksterI'm betting the culprit is in /tmp but let's see
15:03.33GGD300 gig????
15:03.36sticksterrun this:
15:03.37sticksterdu -sm /* | fpaste
15:03.55sticksterIt will probably take a while.
15:04.24GGDi get a WHOLE bunch of permission denied's
15:04.40GGDhttp://fpaste.org/WKiU/
15:05.06sticksterGGD: My apologies
15:05.08sticksterYou need to run that as root
15:05.13sticksterlogout
15:05.14GGDno prob man
15:05.18sticksterThen login as root this time :-)
15:06.17GGDhttp://fpaste.org/ywKV/
15:06.45sticksterOK, so /var seems to be quite full -- ~169G
15:06.49GGDi got a few could not access errors
15:06.55sticksterDo you mirror a bunch of web content there in /var/www?
15:07.10GGDi don't mirror anything
15:07.14sticksterOK, run this:
15:07.19sticksterdu -sm /var/* | fpaste
15:07.49sticksterInterestingly, there's a cool tool called 'baobab' that does a graphical version of what we're doing now... if you could login that would be very useful :-D
15:07.55GGDhttp://fpaste.org/311p/
15:08.01*** part/#fredlug stickster (~pfrields@fedora/stickster)
15:08.13*** join/#fredlug stickster (~pfrields@fedora/stickster)
15:08.21sticksterNuts, I hit a wrong key
15:08.27sticksterCan you repaste that, GGD?
15:08.29GGDhttp://fpaste.org/3IIp/
15:08.43sticksterWow, /var/lib? That's totally bogus
15:08.49sticksterNext...
15:08.51sticksterdu -sm /var/lb/* | fpaste
15:09.00sticksterHopefully you're seeing my pattern here :-)
15:09.34GGDyes i am... :)
15:10.06GGDi take that back..  i think i do some web caching on the machine but not 169gig of it
15:10.13sticksterYou ran into one of the more interesting problems -- having a full filesystem can cause all sorts of nasty things that are more difficult to track down than the average error
15:10.21GGDhttp://fpaste.org/q6HQ/
15:10.34sticksterAh, I see the problem
15:10.36GGDPaul....
15:10.41sticksterYou are using a big bunch of disk in /var/lib/libvirt
15:10.47sticksterMaybe you have a really large disk image there.
15:11.15GGDi always seem to have the "more interesting problems" LOL
15:11.44GGDyea i have a couple there i am working with...  but these are like 10 -20 gig machines
15:12.06sticksterGGD: Have you maybe removed some VMs without removing their disk files, even though you maybe meant to?
15:12.19GGDthats a very good possiblity
15:12.55GGDive had problems with virt in general as well
15:13.14stickstercd /var/lib/libvirt/images
15:13.19sticksterThen look at what you see there:
15:13.20sticksterls -l
15:13.39sticksterYou'll need to figure out which of these images is in use, and which you can get rid of
15:14.21GGDi could dump all of them and start over fresh
15:14.30GGDif i can do that
15:14.48sticksterGGD: That's up to you -- but if you do that, keep in mind you'll have XML definitions for those machines in /var/lib/libvirt/qemu/ that will reference disk images that are no longer there
15:15.13GGDok how do i do that the "clean way"?
15:15.50GGDwith out having the xml diffinitions there
15:16.03sticksterGGD: Sorry, the XML definitions are in /etc/libvirt/qemu/
15:16.13GGDok
15:16.17sticksterWell, it should be 'clean' to do this:
15:16.38sticksterrm -f /var/lib/libvirt/images/* /etc/libvirt/qemu/*xml
15:16.43sticksterservice libvirtd reload
15:16.52sticksterThat will wipe ALL images
15:16.54sticksterAND the machines
15:17.00sticksterSo make sure that's what you want to do!
15:17.07sticksteris not responsible for data loss :-)
15:17.15GGDthose were test machines anyway...
15:17.23sticksterIf all you've been doing is playing around, should be OK then
15:17.41GGDyes
15:18.05sticksterOnce you're done, let me know
15:18.07GGDalthough...  i am having issues with the virt currently as well
15:18.08GGDok
15:18.10GGDhold on
15:18.19sticksterThe 'disk full' problem would affect *A LOT* of stuff on your machine
15:18.31sticksterBecause you're sharing one disk partition for everything (system, virt, user data, etc.)
15:18.45sticksterIf no process can write more data to the disk, lots of things will start failing
15:19.29sticksterOnce you're done, I would recommend rebooting so that your message bus and other stuff can restart normally. This is not normally needed in Linux but a disk full error could have affected other things at startup time, so rebooting would be a good thing in this particular case.
15:20.25GGDrebooting now
15:20.41sticksterGGD: When it comes up, try logging in as your normal user
15:22.25GGDthat was it  THANK YOU PAUL!!!
15:22.27GGD:)
15:22.31GGDit came up
15:23.23sticksterBingo!
15:23.56GGDhmm i am looking at the disk usage analyser
15:24.01GGDand it still says 100%
15:24.44sticksterThat seems odd. Can you open a terminal, and run 'df -h | fpaste' again?
15:26.39GGDhttp://fpaste.org.org/2BOX/
15:26.47GGDhttp://fpaste.org/2BOX/
15:27.28sticksterNope, looks like you're in fine shape
15:27.37GGDodd
15:27.49sticksterYou may want to look closer at the disk usage analyzer -- it may be telling you what percentage of a certain area is being used and by what
15:28.31sticksterIt should say "Total filesystem capacity" at 100% but that's not really usage, just the total of... your total :-)
15:28.36sticksterThe real usage is in the gray bar above that IIRC
15:28.53GGDok
15:28.56sticksterYou can do 'scan filesystem' in the toolbar to get a real readout
15:29.12sticksterIt will take a while
15:29.31stickstergets back to $DAYJOB now that crisis is over :-)
15:29.48GGDLOL
15:29.58GGDi will bring my lappy the next meeting
15:30.06GGDthat will be the fun one..
15:30.08GGD;)
15:30.17GGDagain thanks a bunch stickster
15:30.27sticksternp, enjoy!
15:30.32GGD:)
23:05.56*** join/#fredlug theunwiseman (~matthew@pool-71-171-87-156.clppva.fios.verizon.net)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.