after Squid logrotate system hangs

Bug #57096 reported by Martin Hofbauer on 2006-08-21
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.15-26-386

Environment:
Squid 2.5.STABLE12, Ubuntu 6.0.6, Kernel: 2.6.15-26-i386

Now this is the 2nd time this happened within a week.
After the weekend I found the system in a locked situation. I rebooted
and found following in the log files:

Immediatly after a logrotate of Squid there arethousends of (the same) entries in
the syslog and message file:

Aug 20 07:35:32 chef squid[5284]: storeDirWriteCleanLogs: Starting...
Aug 20 07:35:32 chef squid[5284]: Finished. Wrote 7209 entries.
Aug 20 07:35:32 chef squid[5284]: Took 0.0 seconds (2601587.9 entries/sec).
Aug 20 07:35:32 chef squid[5284]: logfileRotate: /var/log/squid/store.log
Aug 20 07:35:32 chef squid[5284]: logfileRotate: /var/log/squid/access.log
Aug 20 07:35:32 chef kernel: [17502033.772000] __find_get_block_slow() failed.
block=2179187, b_bloc
knr=2178966
Aug 20 07:35:32 chef kernel: [17502033.772000] b_state=0x00000029, b_size=4096
Aug 20 07:35:32 chef kernel: [17502033.772000] device blocksize: 4096
Aug 20 07:35:32 chef kernel: [17502033.772000] __find_get_block_slow() failed.
block=2179187, b_bloc
knr=2178966
Aug 20 07:35:32 chef kernel: [17502033.772000] b_state=0x00000029, b_size=4096
Aug 20 07:35:32 chef kernel: [17502033.772000] device blocksize: 4096
...
..

3 Seconds and thousends(millions?) of such messages later there is no more
entry in any log ( and I assume , that at this time the system has locked )

Additional informaiton:
1.) this system is running fine for about 2 month ( after upgrading to Ubuntu
6.06) and
2.) This system had about 5-10 power cuts within a day .
So, maybe some files or squid cache is corrupt

But how do I find this out, the system is running fine now !

What does this kernel message mean ?

regars
Martin

Martin Hofbauer (mhansi12) wrote :

I also reported this to the Squid community, got following answer:

that kernel error message suggests an operating system kernel or hardware
fault. Please file this in Malone accordingly.

description: updated
Vassilis Pandis (pandisv) wrote :

(Preface: I'm not involved with the Ubuntu kernel development) This could be a filesystem issue - what filesystems do you have? Maybe forcing an fsck would help ?

Martin Hofbauer (mhansi12) wrote :

I have already run fsck -n on this filesystem and found only:

# fsck -n /var
Inode 456073 was part of the orphaned inode list. IGNORED.
Inode 456074 was part of the orphaned inode list. IGNORED.
Inode 456078 was part of the orphaned inode list. IGNORED.
Inode 456079 was part of the orphaned inode list. IGNORED.

Does this could lead to the problem ?
Or indicates this open files ?

Jeremy Vies (jeremy.vies) wrote :

Hi all,
some parts of the FS seem corrupted. Have you some files in /var/lost+found ?

Maybe you should try to reinstall the package that is buggy.
(apt-get install --reinstall squid)
If you have troubles with some other packages, you should think about a complete reinstallation of the system...

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest updates or the latest Ubuntu release? Thanks in advance.

Changed in linux-source-2.6.15:
status: New → Incomplete

Dear Sebastion,

Thank your following up this bug report.
In the meantime I have installed the server from scratch with 7.04 - I do not see any problem there any more.

regards
Martin

Martin Hofbauer (mhansi12) wrote :

They main reason for this problem could be, that I had a lot of Kernel crashes with "Soft Bug:"... on this AMD maindboard. I changed it
to a core2duo processer as well . Since than I never had a crash again. ( I had see similar crashed in different bug reports).

Changed in linux-source-2.6.15:
status: Incomplete → New

This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report.
Appears to have been hardware related.

Changed in linux-source-2.6.15:
status: New → Incomplete
Changed in linux-source-2.6.15:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers