Re: inn2 problem (core dump, history-files > 2 GB)
2G was the limit on a single file under ext2 file system. I remember
having a bad time trying to get rid of a 2G file on ext2. If you are
running ext2, and you upgrade to ext3? If so, it appears the 2G
limit has gone away.
I do not know about inn (never used it), but the 2G file sounds very
familiar. If you can not get rid of it, try stopping whatever daemon
inn runs as, rename the file, then start the inn daemon again.
As for the problem for the future, is this history file just a log
file? If so, simply add it to the logrotate daemon. You could have
it rotate the log every night if you wanted.
Rod
> Hi list,
>
> I have a critical problem with inn2. It appears that the
> history-file
> has exeeded the 2G limit, and every time I start inn, it just crash
> with
> a core-dump.
>
> Questions:
>
> 1) How do I recover (fast) from the problem? I have
> 30 peers that try to send me feed, and
> who also urgently waits for feed from me.
>
> 2) How do I perevent this from happening again?
>
>
>
> I'm Running Debian GNU/Linux stable on a Intel Pentium 4 machine
> with 1
> GB physical ram.
>
> news@news:~$ ls -l /var/lib/news/history*
> -rw-rw-r-- 1 news news 2147483647 Jun 28 01:09
> /var/lib/news/history
> -rw-rw-r-- 1 news news 120 Jun 28 01:09
> /var/lib/news/history.dir
> -rw-rw-r-- 1 news news 352461552 Jun 28 01:09
> /var/lib/news/history.hash
> -rw-rw-r-- 1 news news 234974368 Jun 28 01:09
> /var/lib/news/history.index
> -rw-rw-r-- 1 news news 2147483647 Jun 19 08:14
> /var/lib/news/history.n
> -rw-rw-r-- 1 news news 113 Jun 27 07:05
> /var/lib/news/history.n.dir
> -rw-rw-r-- 1 news news 0 Jun 27 07:05
> /var/lib/news/history.n.hash
> -rw-rw-r-- 1 news news 0 Jun 27 07:05
> /var/lib/news/history.n.index
>
>
> news:/var/spool/news# gdb /usr/lib/news/bin/innd articles/core
> Core was generated by `/usr/lib/news/bin/innd -p 3 -C'.
> Program terminated with signal 25, File size limit exceeded.
>
> Backtrace:
> #0 0x40388e18 in write () from /lib/libc.so.6
> (gdb) back
> #0 0x40388e18 in write () from /lib/libc.so.6
> #1 0x403ee880 in ?? () from /lib/libc.so.6
> #2 0x4032a552 in _IO_file_write () from /lib/libc.so.6
> #3 0x40328fbe in _IO_do_write () from /lib/libc.so.6
> #4 0x40328f56 in _IO_do_write () from /lib/libc.so.6
> #5 0x40329bc7 in _IO_file_sync () from /lib/libc.so.6
> #6 0x4031eb7c in fflush () from /lib/libc.so.6
> #7 0x080955fa in hisv6_check ()
> #8 0x080956ee in hisv6_write ()
> #9 0x080918b9 in HISwrite ()
> #10 0x0806fd09 in InndHisWrite ()
> #11 0x08055292 in ARTpost ()
> #12 0x0805e877 in NCwriteshutdown ()
> #13 0x0805fca9 in NCwriteshutdown ()
> #14 0x0805ba99 in CHANreadloop ()
> #15 0x0805ddc0 in main ()
>
>
> Jarle
> --
> Jarle Aase email: jgaa@jgaa.com
> Author of freeware. http://www.jgaa.com
> news:alt.comp.jgaa
>
> War FTP Daemon: http://www.warftp.org
> War FTP Daemon FAQ: http://www.warftp.org/faq/warfaq.htm
> Jgaa's PGP key: http://war.jgaa.com/pgp
> NB: If you reply to this message, please include all relevant
> information from the conversation in your reply. Thanks.
> <<< no need to argue - just kill'em all! >>>
>
>
> --
> To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>
--
Meddle not in the Affairs of Dragons
for thou art crunchy, and good with catsup.
Reply to: