[MRTG] redhat linux:rateup died from Signal 11
philip bridge
I've overcome numerous issues. But now I'm stumped by the following...
PROBLEM: rateup died from Signal 11
with Exit Value 0 when doing router '195.65.89.30'
If this happens all the time,
you should probably investigate the cause. :-)
A sniffer shows that MRTG actually sends and receives SNMP
request/responses to the router.
Heres the config fileWorkDir: /usr/www/test.bridgenet.ch/htdocs
Target[195.65.89.30]: 4:uni...@195.65.89.30
MaxBytes[195.65.89.30]: 1250000
Title[195.65.89.30]: Maggie.ip-plus.net (No hostname defined for IP
address): Et
hernet0
PageTop[195.65.89.30]: <H1>Traffic Analysis for Ethernet0
Ideas, suggestions?
Thanks in advance
Phil
______________________________________________________________
Philip Bridge
++41 31 688 8262 bri...@ip-plus.net www.ip-plus.ch
PGP: DE78 06B7 ACDB CB56 CE88 6165 A73F B703
--
* To unsubscribe from the mrtg mailing list, send a message with the
subject: unsubscribe to mrtg-r...@list.ee.ethz.ch
* The mailing list archive is at http://www.ee.ethz.ch/~slist/mrtg
G.E.F...@lboro.ac.uk
On 18-Nov-98 philip bridge wrote:
> I've got MRTG installed on Red Hat Linux v. 5.1
>
> I've overcome numerous issues. But now I'm stumped by the
> following...
>
> PROBLEM: rateup died from Signal 11
> with Exit Value 0 when doing router '195.65.89.30'
> If this happens all the time,
> you should probably investigate the cause. :-)
From the RedHat FAQs:
<snippet>
E.6.10
Signal 11's and signal 7's are errors indicating a hardware error
in memory or on the bus. This can be due to problems in executables
or with the hardware of the system. The Linux kernel uses a lot more
capabilities of the CPU, Cache, and memory, and is more prone to
faulting on marginal hardware.
</snippet>
This is (usually) due to a duff SIMM/DIMM, but can be due to other
causes too. Try replacing the RAM first. (BTW, I just read in a post on
DejaNews that Linux is apparently a much better test of RAM than most
BIOS RAM tests! How true this is I don't know...)
Graeme
________________________________________________
Graeme Fowler
Network Officer, Infrastructure & Networks Group
Loughborough University Computing Services
+44 1509 228426
Borek Lupomesky
> > PROBLEM: rateup died from Signal 11
> > with Exit Value 0 when doing router '195.65.89.30'
> > If this happens all the time,
> > you should probably investigate the cause. :-)
> Signal 11's and signal 7's are errors indicating a hardware error
> in memory or on the bus. This can be due to problems in executables
> or with the hardware of the system. The Linux kernel uses a lot more
> capabilities of the CPU, Cache, and memory, and is more prone to
> faulting on marginal hardware.
> This is (usually) due to a duff SIMM/DIMM, but can be due to other
> causes too. Try replacing the RAM first. (BTW, I just read in a post on
> DejaNews that Linux is apparently a much better test of RAM than most
> BIOS RAM tests! How true this is I don't know...)
Sorry, but with MRTG it apparently is not the case. This happens to
too many people and it happens on hardware that otherwise seems faultless.
It's apparent bug in MRTG or something else, but not hardware.
Bye Borek
--
=====================================================================
BOREK LUPOMESKY, network administrator University of J. E. Purkyne
WWW: http://www.ujep.cz/~lupomesk/ Ceske mladeze 8
IRCnet: Borek @ #usti Usti nad Labem, 40096
talk: bo...@ishtar.ujep.cz The Czech Republic
PGP keyid: 9DD1C54D ICQ: 10139578 tel: +420-602-376368
==========[ MIME/ISO-8859-2 & PGP encrypted mail welcome ]===========
Ariancylch
>
> On Wed, 18 Nov 1998 G.E.F...@lboro.ac.uk wrote:
>
> > > PROBLEM: rateup died from Signal 11
> > > with Exit Value 0 when doing router '195.65.89.30'
> > > If this happens all the time,
> > > you should probably investigate the cause. :-)
> > Signal 11's and signal 7's are errors indicating a hardware error
> > in memory or on the bus. This can be due to problems in executables
> > or with the hardware of the system. The Linux kernel uses a lot more
> > capabilities of the CPU, Cache, and memory, and is more prone to
> > faulting on marginal hardware.
> > This is (usually) due to a duff SIMM/DIMM, but can be due to other
> > causes too. Try replacing the RAM first. (BTW, I just read in a post on
> > DejaNews that Linux is apparently a much better test of RAM than most
> > BIOS RAM tests! How true this is I don't know...)
>
> Sorry, but with MRTG it apparently is not the case. This happens to
> too many people and it happens on hardware that otherwise seems faultless.
> It's apparent bug in MRTG or something else, but not hardware.
It could be all sorts of things :)
I got sig11 deaths when the underlying smb share had vanished (other end
got rebooted). Everything else works fine...
(Almost, but that's irrelevant here)
Rhorer, Kyle
error
>> in memory or on the bus. This can be due to problems in
executables
>> or with the hardware of the system. The Linux kernel uses a
lot more
>> capabilities of the CPU, Cache, and memory, and is more prone
to
>> faulting on marginal hardware.
>> This is (usually) due to a duff SIMM/DIMM, but can be due to
other
>> causes too. Try replacing the RAM first. (BTW, I just read in
a post on
>> DejaNews that Linux is apparently a much better test of RAM
than most
>> BIOS RAM tests! How true this is I don't know...)
>
> Sorry, but with MRTG it apparently is not the case. This
happens to
>too many people and it happens on hardware that otherwise seems
faultless.
>It's apparent bug in MRTG or something else, but not hardware.
No, Borek, I think you're thinking about rateup dying from
signal 127, not 11 or 7.
Signal 11's can often be cured by adjusting the RAM timing in
your BIOS configuration. I've noticed that computer vendors almost
never configure that aspect of the system, they just take whatever
settings the motherboard already had from the factory. Open your box up
and look at the RAM to determine its speed (generally 70ns or 60ns for
SIMMs), then make sure your BIOS configuration matches. If it does and
you are getting signal 11's, then take the BIOS out of automatic
configuration mode and set the timings yourself. Be a little more
conservative than the "automatic" settings and you'll probably find that
your troubles disappear. Of course if your troubles *don't* disappear,
then you should look at replacing your RAM and/or your motherboard.
I remember seeing a Signal 11 FAQ somewhere, but I don't
remember the URL. I'm sure you could find it if you check the standard
Linux resources.
Kyle