IRCD suddenly shuts down

IRCD suddenly shuts down

Post by Mohammed a Haf » Wed, 04 Jul 2001 15:48:43



Please Help,

I have a FreeBSD 4.0 running IRCD among some other services.

During the last couple of days, the IRCD had been suddenly shutting
down.
In the 'messages' log file I got the following:

news /kernel: pid 22476 (ircd), uid 0: exited on signal 11 (core
dumped)

I restarted the server then ran fsck, and the result for /usr was:

** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
PARTIALLY TRUNCATED INODE I=968489
SALVAGE? no

INCORRECT BLOCK COUNT I=1087316 (4 should be 0)
CORRECT? no

** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
SUMMARY INFORMATION BAD
SALVAGE? no

BLK(S) MISSING IN BIT MAPS
SALVAGE? no

FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no

52732 files, 1516322 used, 6003049 free (16593 frags, 748307 blocks,
0.2% fragmentation)

Please give any clue of what is going on ?

Your prompt support is highly appreicated,

 
 
 

IRCD suddenly shuts down

Post by Bill Vermilli » Wed, 11 Jul 2001 02:19:17




Quote:>I have a FreeBSD 4.0 running IRCD among some other services.
>During the last couple of days, the IRCD had been suddenly shutting
>down.
>In the 'messages' log file I got the following:
>news /kernel: pid 22476 (ircd), uid 0: exited on signal 11 (core
>dumped)
>I restarted the server then ran fsck, and the result for /usr was:
>** Last Mounted on /usr
>** Phase 1 - Check Blocks and Sizes
>PARTIALLY TRUNCATED INODE I=968489
>SALVAGE? no
>INCORRECT BLOCK COUNT I=1087316 (4 should be 0)
>CORRECT? no
>** Phase 2 - Check Pathnames
>** Phase 3 - Check Connectivity
>** Phase 4 - Check Reference Counts
>** Phase 5 - Check Cyl groups
>SUMMARY INFORMATION BAD
>SALVAGE? no
>BLK(S) MISSING IN BIT MAPS
>SALVAGE? no
>FREE BLK COUNT(S) WRONG IN SUPERBLK
>SALVAGE? no

Rerun fsck and answer yes to the above errors.  Not doing so
can lead to further errors.

Did you manually run fsck from a command line.  You should not have
had those errors in a normally operating system unless you just
turned the power off.

Run the fsck again and see if you still get the errors.  

There security alerts posted against some version of IRCD in the
last month or so.  could that be it?

--