/var/log/kdm.log file now 7.3GB HELP
in [Suse]
|
Prev: KDE 4.3.4 vs 4.3.1?
Next: Find Syntax Question [CLI]
From: gb on 24 Dec 2009 17:56 gb wrote: Thanks for all the suggestions guys. here is the edited content of the file. ----------------------------------------- (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 9 12:04:02 2009 (==) Using default built-in configuration (48 lines) (EE) Failed to load module "nvidia" (module does not exist, 0) (EE) Failed to load module "nouveau" (module does not exist, 0) Wacom Intuos2 4x5 Wacom X driver grabbed event device (==) Wacom using pressure threshold of 61 for button 1 (==) Wacom USB Intuos2 tablet speed=9600 (38400) maxX=12700 maxY=10600 maxZ=1023 resX=2540 resY=2540 tilt=en abled (==) Wacom device "Wacom Intuos2 4x5" top X=0 top Y=0 bottom X=12700 bottom Y=10600 resol X=2540 resol Y=2540 (==) Wacom device "Wacom Intuos2 4x5 pad" top X=0 top Y=0 bottom X=12700 bottom Y=10600 resol X=2540 resol Y= 2540 Driver not XRANDR 1.2 capable, ignoring DISPLAYMANAGER_RANDR_MODE_* settings The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Duplicate shape name "" > Using first definition > Warning: Multiple doodads named "" > Using first definition Errors from xkbcomp are not fatal to the X server Wacom Intuos2 4x5 eraser - usbParse: dropping empty event for serial 53478013 ***This last line is then repeated for the next 102,415,334 lines !!*** Any suggestions on how to stop this will be gratefully received. Incidentally the PC is never switched off. Thanks Geoff Beale
From: gb on 25 Dec 2009 10:12 houghi wrote: > Moe Trin wrote: >> On Thu, 24 Dec 2009, in the Usenet newsgroup alt.os.linux.suse, in >> article <slrnhj6uij.deu.houghi(a)penne.houghi>, houghi wrote: >> >>>gb wrote: >> >>>> Every time I try to open the file the editor crashes. >> >> As others have suggested 'tail -200 /var/log/kdm.log' > > I would go with `tail -f /var/log/kdm.log` as that will show things as > they happen and that _might_ give extra help as well. > >>>Use vim (or vim if you have it installed) and look whit that. >> >> Assumes knowledge of vi or it's many clones - not very likely. > > Also never to late to start IF the klnowledge is not there. > >> 'vim' normally creates a copy of the file (.$FILENAME~) when editing, >> and there may not be enough space on the hard disk to do so. > > Could well be, but then I would be asuming some other errors as well > by now. > >> Yes - it will remain at zero size because the logging daemon is still >> writing to the original file until that application is restarted. > > Something learned. > >> Only if the daemon is restarted. Why isn't the log rotation cron >> task handling this? > > For all you know, that is the thing that screws things up. But untill > we get to see what is in those logs, it is anybodies guess. > > houghi gb wrote: Thanks for all the suggestions guys. here is the edited content of the file. ----------------------------------------- (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 9 12:04:02 2009 (==) Using default built-in configuration (48 lines) (EE) Failed to load module "nvidia" (module does not exist, 0) (EE) Failed to load module "nouveau" (module does not exist, 0) Wacom Intuos2 4x5 Wacom X driver grabbed event device (==) Wacom using pressure threshold of 61 for button 1 (==) Wacom USB Intuos2 tablet speed=9600 (38400) maxX=12700 maxY=10600 maxZ=1023 resX=2540 resY=2540 tilt=en abled (==) Wacom device "Wacom Intuos2 4x5" top X=0 top Y=0 bottom X=12700 bottom Y=10600 resol X=2540 resol Y=2540 (==) Wacom device "Wacom Intuos2 4x5 pad" top X=0 top Y=0 bottom X=12700 bottom Y=10600 resol X=2540 resol Y= 2540 Driver not XRANDR 1.2 capable, ignoring DISPLAYMANAGER_RANDR_MODE_* settings The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Duplicate shape name "" > Using first definition > Warning: Multiple doodads named "" > Using first definition Errors from xkbcomp are not fatal to the X server Wacom Intuos2 4x5 eraser - usbParse: dropping empty event for serial 53478013 ***This last line is then repeated for the next 102,415,334 lines !!*** Any suggestions on how to stop this will be gratefully received. Incidentally the PC is never switched off. Thanks Geoff Beale
From: Rob on 25 Dec 2009 13:04 gb <gb(a)gb.com.invalid> wrote: > Wacom Intuos2 4x5 eraser - usbParse: dropping empty event for serial > 53478013 > > > ***This last line is then repeated for the next 102,415,334 lines !!*** > > Any suggestions on how to stop this will be gratefully received. Do you actually have that "Wacom Intuos2 4x5" thing connected? Try unplugging it.
From: Moe Trin on 25 Dec 2009 13:23 On Thu, 24 Dec 2009, in the Usenet newsgroup alt.os.linux.suse, in article <slrnhj7nl3.7iu.houghi(a)penne.houghi>, houghi wrote: Merry Christmas! >Moe Trin wrote: >> Yes - it will remain at zero size because the logging daemon is still >> writing to the original file until that application is restarted. >Something learned. [compton ~]$ whatis fopen fopen (3) - stream open functions [compton ~]$ RETURN VALUES Upon successful completion fopen, fdopen and freopen return a FILE pointer. Otherwise, NULL is returned and the global vari- able errno is set to indicate the error. The program holding a file open is actually holding a file pointer rather than holding the file name. Thus, you can move the logfile to another name, or even remove the file with 'rm' and the program keeps on ticking as if nothing happened - because it still has the file handle which isn't altered by a move or rm. A very common problem for less experienced *nix users ('fopen' is an ANSI 'C' command used by things like operating systems written in C) is when they try to gain disk space by removing a [log] file and maybe creating a new one as a replacement. While the directory listing no longer shows the (removed) file, it's still taking up diskspace, and the log daemon (or what ever is using the file) is still stuffing more data into it. The "new" file (if it was created) remains empty. Then you get the user whining about the disk full, and can't figure out why. Comparing the outputs of the commands 'df' and 'du' provides a clue. 'du' measures directory entries - 'df' measures actual space in use at the moment which would include deleted (but in use) files. You can get confirmation by using 'fuser' or 'lsof' which will show the still open file[s]. '/usr/sbin/lsof +d /name/of/directory' or '/usr/sbin/fuser /name/of/directory/file_name' do the trick. (fuser needs to be run as root, and will allow wild-cards.) The fix is to restart the application that is using the file - either by terminating it normally, or having it re-read it's configuration data: ('kill $DAEMON_PID' or 'kill -1 $DAEMON_PID' - 'killall' works just as well, as does using '-HUP' as the signal name rather than the '-1'). The windoze solution of 're-booting' also works because that action closes the file. It is only when everything that _had_ been using the file actually closes that the file is removed from the disk, and disk space freed. Many *nix operating systems have some form of log-rotation program run by the cron daemon, either a simple script, or something fancy like 'logrotate' from Erik Troan (RedHat ~1995) and clones. Old guy
From: gb on 25 Dec 2009 17:59
Rob wrote: > gb <gb(a)gb.com.invalid> wrote: >> Wacom Intuos2 4x5 eraser - usbParse: dropping empty event for serial >> 53478013 >> >> >> ***This last line is then repeated for the next 102,415,334 lines >> !!*** >> >> Any suggestions on how to stop this will be gratefully received. > > Do you actually have that "Wacom Intuos2 4x5" thing connected? > Try unplugging it. Problem solved. I deleted the kdm.log file completely from the system, shut down, and swapped the Wacom pad and pen for a Logitech wireless mouse. Then rebooted and there is a now new kdm.log file 1.6Kb only. Thanks for all the help. Geoff Beale |