[mrtg] Re: Forking problem: invalid log file format

[MRTG Mailing list]

HI all!
Same here ... I get irrelevant data in the html page in the following
section :
---------------------------------------------------
at which time 'xxxxxxxx' had been up for 'xxxxxxxxx' 
---------------------------------------------------

where 'xxxxxxx' = 'irrelevant data' as stated at the top of the log file.

After I removed Forks: 4 option and restarted mrtg it showed correct data.
I wanted to try out the modification given out by Tobi but I am not so
confident in editing the mrtg file.
Guess I shall run it w/o the Forks option till there is an update.

BTW what are those mrtg <defunct> zombie processes ???
I used to get them with Forks option ubt I don't get them w/o it.

Rgds,

\\Ritesh

  |  r i t e s h  r a j  j o s h i
  |  MERCANTILE COMMUNICATIONS PVT. LTD
  |  www.mos.com.np
  |  hotline:240920 

On Mon, 16 Oct 2000, Christopher Poetzel wrote:

> 
> hello all,
> 
> i am having issues with mrtg 2.9.2 forking feature.  I run it on Redhat 
> 6.2 and i assume that linux can do forking.  I am testing forking on just 
> one router and get these errors for about half of the interfaces:
> 
> Rateup ERROR: /usr/local/mrtg-2.9.2/bin/rateup found 
> 130.202.129.13_vlan666's log file was corrupt
>           or not in sorted order:
> time: 971710737.Rateup WARNING: /usr/local/mrtg-2.9.2/bin/rateup could 
> not read the primary log file for 130.202.129.13_vlan666
> Rateup ERROR: /usr/local/mrtg-2.9.2/bin/rateup found 
> 130.202.129.13_vlan666's log file was corrupt
>           or not in sorted order:
> time: 971710724.Rateup WARNING: /usr/local/mrtg-2.9.2/bin/rateup The 
> backup log file for 130.202.129.13_vlan666 was invalid as well
> WARNING: rateup died from Signal 0
>  with Exit Value 1 when doing router '130.202.129.13_vlan666'
>  Signal was 0, Returncode was 1
> Rateup ERROR: /usr/local/mrtg-2.9.2/bin/rateup found 
> 130.202.129.13_vlan156's log file was corrupt
>           or not in sorted order:
> time: 971710737.Rateup WARNING: /usr/local/mrtg-2.9.2/bin/rateup could 
> not read the primary log file for 130.202.129.13_vlan156
> Rateup ERROR: /usr/local/mrtg-2.9.2/bin/rateup found 
> 130.202.129.13_vlan156's log file was corrupt
>           or not in sorted order:
> time: 971710724.Rateup WARNING: /usr/local/mrtg-2.9.2/bin/rateup The 
> backup log file for 130.202.129.13_vlan156 was invalid as well
> WARNING: rateup died from Signal 0
>  with Exit Value 1 when doing router '130.202.129.13_vlan156'
>  Signal was 0, Returncode was 1
> 
> When lookin at these two log files, the appear like so
> # more 130.202.129.13_vlan666.log
> 971710737 xxx at 130.202.129.13 Descr   Loopback129     3  
> xxx at 130.202.129.13 Descr   Null0   2 971710737 0 0 0 0
> 971710200 0 0 0 0
> 971709900 0 0 0 0
> 971709600 0 0 0 0
> 
> The log file is oviusly messedup somehow.  this only happens when i try 
> to use the Forks: 4 option.  anyone had any similar problems.
> any help would be appreciated
> 
> chris poetzel
> cpoetzel at anl.gov
> argonne national labratory
> 
> --
> Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
> Archive     http://www.ee.ethz.ch/~slist/mrtg
> FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
> WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
> 


--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi