Dear debian fellows,
I suddenly bumped into a very severe problem, for which I have not the
slightest clue. Several things depending on syslogd (some ppp logging
scripts I have cooked) stopped working. After a while, I realised my
/var/log/messages file was growing too fast with:
Aug 27 12:40:21 xxxhostname pppd[7578]: Exit.
Aug 27 12:40:28 xxxhostname syslogd: exiting on signal 15
Aug 27 19:32:28 xxxhostname syslogd 1.3-0#11: restart.
Aug 27 19:32:28 xxxhostname kernel: klogd 1.3-0, log source = /proc/kmsg start\
ed.
Aug 27 19:32:28 xxxhostname syslogd 1.3-0#11: restart.
Aug 27 19:32:28 xxxhostname syslogd: select: Bad file number
Aug 27 19:32:58 xxxhostname last message repeated 175865 times
Aug 27 19:33:58 xxxhostname last message repeated 363011 times
Aug 27 19:34:58 xxxhostname last message repeated 407157 times
Aug 27 19:35:58 xxxhostname last message repeated 434367 times
.....and so on: only messages from syslogd itself.
I thought one of the files in /var/log was in a dubious state, maybe
after a bad shutdown, but although there has been a bad shutdown, an
fsck -sArP run didn't help. Anyway, the end to the 12:40 session seems to
terminate normally. So the bad shutdown was maybe not connected to
this. I have tried removing all files in /var/log to start from
scratch, it doesn't help...
Question: would anyone have any clue of something worth trying? Unfortunately,
I am not sitting next to the machine, and can only connect to it through a
modem. Upgrading to 1.3 is for instance not a solution. But gee: it did work!
What happened? I include below the fsck log for info: it doesn't look too
frightening to me... Is this a bug of kernel 2.0.27? I saw through dejanews a
lost soul that had the same problem with the same kernel, but no answer...
Amities,
Jean Orloff
+++++++++ + + + + + + + ++++++
+ Tel:(33)474.40.72.86 Fax:(33)473.26.45.98 http://lapphp0.in2p3.fr/~orloff/ +
+++++++++ + + + + + + + ++++++
Outside a Paris dress shop:
Dresses for street walking.
+++++++++ + + + + + + + ++++++
root# fsck -rAsP
Parallelizing fsck version 1.06 (7-Oct-96)
e2fsck 1.06, 7-Oct-96 for EXT2 FS 0.5b, 95/08/09
/dev/hda3 is mounted. Do you really want to continue (y/n)? yes
/dev/hda3 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Fix summary information<y>? yes
Block bitmap differences: -38495 -75172 -75173 -75174 -75175 -75176 -76140
-76141 -76142 -76143 -76144 -76145 -76146 -616920 -616921 -616922 -616923
-616924 -616925 -616926 -616928 -616929 -616930 -616931 -616932 -616933 -616934
-616937 -616938 -616939 -616940 -616941 -616942 -616943. FIXED
Free blocks count wrong for group 4 (2481, counted=2482). FIXED
Free blocks count wrong for group 9 (5915, counted=5927). FIXED
Free blocks count wrong for group 75 (5466, counted=5487). FIXED
Free blocks count wrong (352139, counted=352173). FIXED
/dev/hda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/hda3: 27199/163200 files (1.8% non-contiguous), 298995/651168 blocks
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
