abrams@dan.ccd.bnl.gov (The Ancient Programmer) (04/30/91)
I am running remote TRN on a Sun4 OS4.1.1. My NNTP server is an DecStation 5000. Everything was working well until this weekend when mthreads suddenly went berserk and began filling the mt.log file with thousands of messages: Apr 28 01:35 ** interrupt 11 ** : Apr 29 12:43 ** interrupt 11 ** Apr 29 12:43 ** interrupt 11 ** Apr 29 12:43 ** interrupt 11 ** Apr 29 12:43 ** interrupt 11 ** This fills the partition and causes the system to go around the bend. Normally, mthreads is run from cron, so I tried running it manually and got the same results. It started to print its regular output and then went wild. ---------------------------------------------------------------------------- #dan<1>mthreads -v X..................................................#####..######.#####..#############.##..#..#########################interrupt 11! interrupt 11! ^- it always happens about here. Is there interrupt 11! a way to tell on which group it is : working? ------------------------------------------------------------------------------ In /usr/include/signal.h, SIGSEGV is defined to be 11 (segmentation violation) but I'm not at all sure that mthreads' interrupt 11 is the same. Has anyone any idea what's happening to my mthreads? thanx in advance. -- INTERNET: abrams@bnl.gov |/ | ^ BITNET: abrams@bnlux0.BITNET |\ |__ /-\
technews@iitmax.iit.edu (Kevin Kadow) (05/01/91)
I'm a user here (we run RN on an ENCORE unix) and was wondering what would
be involved in upgrading from RN to TRN?
(in other words, could I pester the sysadmin to put in the upgrade or would
it be too expensive in terms of fees/downtime/overall hassle ??
--
technews@iitmax.iit.edu kadokev@iitvax (bitnet)
My Employer Disagrees.gerry@jts.com (G. Roderick Singleton ) (05/01/91)
In article <1991Apr29.204515.11126@bnlux1.bnl.gov> abrams@dan.ccd.bnl.gov (The Ancient Programmer) writes: > > I am running remote TRN on a Sun4 OS4.1.1. My NNTP server is an >DecStation 5000. Everything was working well until this weekend when mthreads >suddenly went berserk and began filling the mt.log file with thousands of >messages: >Apr 28 01:35 ** interrupt 11 ** > : [stuff deleted] > You forgot to mention the Revision and patchlevel of your TRN. I ask 'cause I saw similar behaviour with an early version of mthreads that I used with standalone TRN. The current version (Trn v1.0.2) corrects this problem at my site. Uunet, and possibly other archive sites, has the current version so you should be able to grab a copy easily. I am unaware of any further patches but stand to be corrected. Cheers, ger -- G. Roderick Singleton, System and Network Manager, JTS Computers {yunexus | uunet | geac | torsqnt}!gerry@jtsv16.jts.com
osyjm@warp.mhd.montana.edu (Jaye Mathisen) (05/01/91)
In article <1991Apr30.210127.3365@jts.com> gerry@jts.com (G. Roderick Singleton ) writes: >Uunet, and possibly other archive sites, has the current version You can alway get the latest version of trn by ftp from ftp.cs.montana.edu in pub/trn. I keep it pretty much up-to-date,although I don't archive the occasional patch from the net. -- Jaye Mathisen,sysmgr 410 Roberts Hall,Dept. of Computer Science Montana State University,Bozeman MT 59717 PHONE: (406) 994-{4780,3931}
abrams@dan.ccd.bnl.gov (The Ancient Programmer) (05/04/91)
I was running mthreads (trn 1.0.1), when it began be run amock,
filling up mt.log. I have since upgraded to trn v1.0.2, and mthreads now
dumps core or produces the output shown below.
----------------------------------------------------------------------------
mthreads -z -vvvv
X...................#..#..#....#.#.............E!eeee###eeee####e######eeee
e####e#eee#eee##eeeeeeeeeeeeeee#..eeeeeeeeeeeeeeeeeeeee#eeeeeeeeeeeeeeee#ee
eeeeeeee#eeee#eeeee#eeeeeeee#eeeeeeeeeeeeeeeeeeeeeeeeee#eee#e##e#ee#ee##eee
eeeeeeeeeee########eeeeeeeeeeeeeeeeeeeeeeeeee#eeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeeeee#e#eeeeeeeeeeeeeeeeeeeeeeee#eee#eeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeeeee#eeeeeeeeeeeeeeeeeeeeeeeeeeeee#eeeeeeeeeeeeeeeeeeeeee#eeeeeeeee
eeeeeeeeeeeeeeeeeeeee##eeeeeeee#eeeeeeeeeeeeeeeeeeeeee#eeeee#eeeee#eeeeeeee
eeeeeeeeeeeee#e#eeee#eeeeeee#eeeee#eee#eee#e#eeeeee#ee##dan<44>
^^^^^^
Note the displaced prompt.
Mt.log is filled with messages such as:
May 3 11:35 comp.graphics: Invalid author in data file: -18648 [0]
:
:
May 3 13:28 comp.sys.atari.st: Missing reference line! [36361]
(many, MANY of these)
:
May 3 13:29 misc.consumers: Reference ended in '*'.
and so on and on .....
Can anyone tell me what is happening here? Is Trn screwing up
or has the news gone bad? I'm running remote trn on a Sun4 (OS 4.1.1)
using a Decstation 5000 as the news server.
Thanx in advance,
--
INTERNET: abrams@bnl.gov |/ | ^
BITNET: abrams@bnlux0.BITNET |\ |__ /-\bill@bilver.uucp (Bill Vermillion) (05/06/91)
In article <1991May3.195034.9911@bnlux1.bnl.gov> abrams@dan.ccd.bnl.gov (The Ancient Programmer) writes: > Can anyone tell me what is happening here? Is Trn screwing up >or has the news gone bad? I'm running remote trn on a Sun4 (OS 4.1.1) >using a Decstation 5000 as the news server. Well I would suspect that some news article/directory is bad. I had a similar occurance. Mthreads would get to one point, and stop and leave the rest unprocessed. I ran mthreads with about 3 or 4 v's on the option line. Each extra v forces an extra level, and more output in the log. When I found where the output of the log stopped, I checked that group and found no problems. So I looked at active 2 to find out which newsgroup was to be processed next after the last one that was processed. When I went to that directory I found problems. One I found was that instead of a file .threads I had a directory called .threads. I found one or two other corrupt portions there. Rm'd the offending files and directories and all was fine. This may not be your problem, but it sounds similar. -- Bill Vermillion - UUCP: uunet!tarpit!bilver!bill : bill@bilver.UUCP