cupsys creates a 4G error_log file

[i3dmaster]

After I upgraded to 2.6.15-17.26 kernel and reboot the box, I found that my / fs is mounted read only, then I issued "mount -o remout,rw /" to remount it as read/write. Then I found my driver starts spinning and no stop. From top, I found that the cupsys is the one that occupies all the i/o and cpu cycle, then I killed it. Later, I found my / is full and searched down to this monster giant error_log file from /var/log/cups dir.
ii linux-image-2.6.15-17-386 2.6.15-17.26
ii cupsys 1.1.99.b1.r4929-0ubuntu3
ls -la /var/log/cups:
-rw-r--r-- 1 cupsys lpadmin 6912 2006-03-08 07:41 access_log
-rw-r--r-- 1 cupsys lpadmin 21949 2006-03-08 07:35 access_log.1.gz
-rw-r--r-- 1 cupsys lpadmin 52600 2006-03-07 18:57 access_log.2.gz
-rw-r--r-- 1 cupsys lpadmin 90012 2006-03-06 07:35 access_log.3.gz
-rw-r--r-- 1 cupsys lpadmin 88759 2006-03-05 07:36 access_log.4.gz
-rw-r--r-- 1 cupsys lpadmin 90885 2006-03-04 07:36 access_log.5.gz
-rw-r--r-- 1 cupsys lpadmin 87732 2006-03-03 07:35 access_log.6.gz
-rw-r--r-- 1 cupsys lpadmin 50394 2006-03-02 07:36 access_log.7.gz
-rw-r--r-- 1 root lpadmin 4143390720 2006-03-08 08:10 error_log
-rw-r--r-- 1 root lpadmin 35582 2006-03-08 05:36 error_log.1.gz
-rw-r--r-- 1 root lpadmin 37796 2006-03-07 18:57 error_log.2.gz
-rw-r--r-- 1 root lpadmin 56640 2006-03-05 22:16 error_log.3.gz
-rw-r--r-- 1 root lpadmin 52311 2006-03-04 21:29 error_log.4.gz
-rw-r--r-- 1 root lpadmin 30548 2006-03-03 15:22 error_log.5.gz
-rw-r--r-- 1 root lpadmin 60834 2006-03-03 06:25 error_log.6.gz
-rw-r--r-- 1 root lpadmin 32586 2006-03-02 02:29 error_log.7.gz
-rw-r----- 1 cupsys lpadmin 0 2006-03-06 20:24 page_log

The last couple of lines from dmesg... Apparently, there is something wrong when reading hda3 fs which is my /...

[4336443.003000] EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #356445: rec_len % 4 != 0 - offset=0, inode=1868963944, rec_len=8306, name_len=97
[4336443.004000] Remounting filesystem read-only
[4336650.433000] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
[4336650.434000] EXT3 FS on hda3, internal journal
[4338373.112000] drivers/usb/input/hid-core.c: input irq status -71 received
[4345573.189000] EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #356445: rec_len % 4 != 0 - offset=0, inode=1868963944, rec_len=8306, name_len=97
[4345573.189000] Remounting filesystem read-only
[4345796.196000] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
[4345796.211000] EXT3 FS on hda3, internal journal
[4345924.468000] ipsec0: no IPv6 routers present
[4346605.807000] drivers/usb/input/hid-core.c: input irq status -71 received

[Patrice Vetsel (vetsel-patrice)]

Could you make a clean installation up to date with formated and verified partitions, and see if this problem happen again ?

[i3dmaster (i3dmaster-gmail)]

Its really difficult for me to wipe out my desktop and reinstall again. Actually the reinstallation happened not long ago since I've got many stuff customized I probably wouldn't do that lately. Anyway, after I upgraded the kernel and disabled the cupsys from booting up and delete that huge log file, Im free of this problem since then.

[Martin Pitt (pitti)]

Can you please take a look at the giant log file? (Possibly at the end of the file). I suspect there is just one or two error messages repeated over and over again. WHat does it say?

[i3dmaster (i3dmaster-gmail)]

I don't know how I can open that file. Nothing seemed to be able to open it. tried cat, vi, tail... I think its just too big to process.. And besides, my laptop didn't function at all with this file and I had to get rid of it. But I have the same feeling as what you had. Maybe the error in my / fs causes cupsys failing. If there is a way to configure how big the log file can be and cup doesn't throw more logs when it hits the limit, that would be a perfect solution I think.

[paulosfl (pauloslf)]

already reported 38042

[Martin Pitt (pitti)]

id3master: please try the following:

  sudo /etc/init.d/cupsys stop
  sudo rm -f /var/log/cups/error*
  sudo /etc/init.d/cupsys start

this will remove the huge files and restart cupsys. Then please wait a while and look into it again. I suspect it's the same issue as in bug 38042:

E [04/Apr/2006:21:18:27 +0100] CUPS-Get-Printers client-error-not-found: No destinations added.
E [04/Apr/2006:21:18:32 +0100] CUPS-Get-Default client-error-not-found: No default printer

Thank you!

[Martin Pitt (pitti)]

I believe this is fixed in the recent versions, so I'm closing this for now. Please reopen if you still have the issue.

[i3dmaster (i3dmaster-gmail)]

Thanks Martin! You guys rock!

Jim

On 4/24/06, Martin Pitt <email address hidden> wrote:
>
> I believe this is fixed in the recent versions, so I'm closing this for
> now. Please reopen if you still have the issue.
>
> ** Changed in: cupsys (Ubuntu)
> Status: Needs Info => Fix Released
>
> --
> cupsys creates a 4G error_log file
> https://launchpad.net/bugs/34111
>

--
yongjian (jim) xu
Linux user #392733
-------------------------------------
You want to know what a computer really is, play Linux!