Date   
Re: New to Metop

Ian Deans
 

Alan and Geoffrey,

To avoid too many mails and confusion ( too many cooks etc ) I have remained away from this thread but it is worth mentioning that Geoffrey did get up and running with Metop after sorting out the settings in Metop Manager. However without a RAMDisk he was experiencing a number of lost chunks. It is almost certain that the present loss of data is due to a misconfiguration with the RAMdisk.

Regards
Ian.

-----Original Message-----
From: Geoffrey Gee
Sent: Thursday, February 24, 2011 8:32 PM
To: MSG1 Yahoo Group
Subject: [MSG-1] New to Metop

Alan
After 20 mins.......... No data in EPS-10 other channels still receiving
data.

Checked PID's as instructed. 510 is shown.

See below Eumetsats confirmation of what I should be able to receive.


Best regards............Geoffrey

Re: New to Metop

Alan Sewards
 

Ian and Geoffrey,
At this point I am out of ideas. Data is coming in on some channels, so the receiver chain is working as is the Tellicast software. If one channel is not producing data it can only be because the data is not being sent or something required locally is not set. I can't think of anything other than the PID and that has been checked.
I had not realized that successful reception of METOP had occurred - I can't see how with the number of misconfigurations of the received folders recently uncovered! But if that is the case it should suffice to go back to the settings in recv.ini and recv.channels.ini that worked now that the RAMdisk has been removed.

Best regards - Alan (signing off for tonight)

On 24/02/2011 10:00 PM, Ian Deans wrote:
Alan and Geoffrey,

To avoid too many mails and confusion ( too many cooks etc ) I have remained
away from this thread but it is worth mentioning that Geoffrey did get up
and running with Metop after sorting out the settings in Metop Manager.
However without a RAMDisk he was experiencing a number of lost chunks. It
is almost certain that the present loss of data is due to a misconfiguration
with the RAMdisk.

Regards
Ian.

-----Original Message-----
From: Geoffrey Gee
Sent: Thursday, February 24, 2011 8:32 PM
To: MSG1 Yahoo Group
Subject: [MSG-1] New to Metop

Alan
After 20 mins.......... No data in EPS-10 other channels still receiving
data.

Checked PID's as instructed. 510 is shown.

See below Eumetsats confirmation of what I should be able to receive.


Best regards............Geoffrey















------------------------------------

Unsure what a term means? Check the Glossary at:
http://www.satsignal.eu/wxsat/glossary.htm
Yahoo! Groups Links



--
Alan Sewards
email: alan@...
web site: http://asewards.free.fr

Re: Getting MRTG to work

Ulrich G. Kliegis
 

David, it needn't be you to reply, maybe some of the other MRTG-ops can direct me too.

I created a first basic configuration file today, and - since I don't intend to monitor the ethernet
traffic of that PC right now, commented-out all line that deal with the ethernet interface -
realizing that an IP address deliberately given by the DHCP-server may cause additional efforts
- or will the mrtg mechanism look up the address each time the PC is restarted?

Anyway, not the topic right now, but rather this: Here ist the top of the DVB-related part of the
config file generated by the cfgmaker routine:

### Interface 131074 >> Descr: 'TechniSat-DVB-PC-TV-Star-PCI' | Name: '' | Ip:
'192.168.238.238' | Eth: '00-d0-d7-0f-ee-a5' ###

Target[windbuedel_131074]: 131074:public@windbuedel:
SetEnv[windbuedel_131074]: MRTG_INT_IP="192.168.238.238"
MRTG_INT_DESCR="TechniSat-DVB-PC-TV-Star-PCI"
MaxBytes[windbuedel_131074]: 12500000
Title[windbuedel_131074]: Traffic Analysis for 131074 -- WINDBUEDEL
PageTop[windbuedel_131074]: <h1>Traffic Analysis for 131074 -- WINDBUEDEL</h1> ...

windbuedel is the PC-name. I saw in your examples, David, that you use a nomenclature like
Target[windbuedel_dvb]. Is this preferable (except for readability)? And if so, where is the place
to tell mrtg that 131074 = dvb?

Sorry for my probably rather trivial questions, this is a new field for me. So, thanks in advance
for all helpful advice!

Cheers,
U.


An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Thu, 24 Feb 2011 08:08:58 -0000
Betreff: Re: [MSG-1] Getting MRTG to work
Antwort an: MSG-1@...

Ulrich, my apologies in that with all the effort put into the PHP
pages, I have rather neglected the plain HTML pages, but I've now
added a couple of links which may make it easier to find the extended
MRTG information. Too many ideas, too little time!

Re: Getting MRTG to work

David J Taylor
 

David, it needn't be you to reply, maybe some of the other MRTG-ops can direct me too.

I created a first basic configuration file today, and - since I don't intend to monitor the ethernet
traffic of that PC right now, commented-out all line that deal with the ethernet interface -
realizing that an IP address deliberately given by the DHCP-server may cause additional efforts
- or will the mrtg mechanism look up the address each time the PC is restarted?
You can use the loopback address (127.0.0.1) or PC name instead of the numeric IP address:

Target[Alta-LAN]: 11:public@....0.1

Target[Alta-LAN]: 11:public@Alta

The loopback address doesn't look as elegant, but is most likely to stay the same!

The interface/network number (11) may vary if you change the configuration (e.g. add Wi-Fi dongle). Once the configuration is set, I tend to reboot, and run cfgmaker, to see what the network numbers actually are.

Anyway, not the topic right now, but rather this: Here ist the top of the DVB-related part of the
config file generated by the cfgmaker routine:

### Interface 131074 >> Descr: 'TechniSat-DVB-PC-TV-Star-PCI' | Name: '' | Ip:
'192.168.238.238' | Eth: '00-d0-d7-0f-ee-a5' ###

Target[windbuedel_131074]: 131074:public@windbuedel:
SetEnv[windbuedel_131074]: MRTG_INT_IP="192.168.238.238"
MRTG_INT_DESCR="TechniSat-DVB-PC-TV-Star-PCI"
MaxBytes[windbuedel_131074]: 12500000
Title[windbuedel_131074]: Traffic Analysis for 131074 -- WINDBUEDEL
PageTop[windbuedel_131074]: <h1>Traffic Analysis for 131074 -- WINDBUEDEL</h1> ...

windbuedel is the PC-name. I saw in your examples, David, that you use a nomenclature like
Target[windbuedel_dvb]. Is this preferable (except for readability)? And if so, where is the place
to tell mrtg that 131074 = dvb?

Sorry for my probably rather trivial questions, this is a new field for me. So, thanks in advance
for all helpful advice!

Cheers,
U.
I try and keep a consistent set of names across the PCs here, so I would use:

Target[Alpha_DVB]: 16:public@....0.1

Target[Bravo_DVB]: 14:public@....0.1

Target[Charlie_DVB]: 11:public@....0.1

and once I know the DVB network number I tend to use copy-and-paste from an existing config such as:

________________________________________________________
#---------------------------------------------------------------
# PC Alta DVB World USB box
#---------------------------------------------------------------

Target[Alta_DVB]: 16:public@Alta
MaxBytes[Alta_DVB]: 12500000
Options[Alta_DVB]: unknaszero, growright, noo
Title[Alta_DVB]: EUMETCast - Eurobird-9 satellite on DVB World USB box
PageTop[Alta_DVB]: <H2>EUMETCast - PC Alta - DVB World USB box
</H2>
<TABLE>
<TR><TD>Interface:</TD><TD>DVB World USB box</TD></TR>
<TR><TD>Max Speed:</TD><TD>12.5? MBytes/s</TD></TR>
</TABLE>
________________________________________________________


The network number is the most awkward to get, as cfgmaker will list all sorts of artificial interfaces as well as the real ones! Tunneling, Toredo and all sorts. With experience, you get to spot the real ones, but sometimes using a ROUTE PRINT command from DOS will help, as there is a list of interfaces at the start of its output. That's the way to find the number for the Target line (such as 16 in the Alta example above). If you get a plot of zeroes you know you may have the wrong number!

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: Getting MRTG to work

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Fri, 25 Feb 2011 07:45:27 -0000
Betreff: Re: [MSG-1] Getting MRTG to work
Antwort an: MSG-1@...

If you
get a plot of zeroes you know you may have the wrong number!
Sounds like fundamental experience... :)

Thank you so much for the detailed background info, I'll try to do a few steps
of my own then...

Cheers,

U.

Re: Getting MRTG to work

David J Taylor
 

If you
get a plot of zeroes you know you may have the wrong number!
Sounds like fundamental experience... :)
"been there .. done that" as we say!

Thank you so much for the detailed background info, I'll try to do a few steps
of my own then...

Cheers,

U.
Have fun!

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: New to Metop

geoffreygee90
 

Alan and Ian

Many thanks for yesterdays mails, your help is much appreciated and I am sorry to be such a nuisance.

Following your comment, Alan, and as a double check I have this morning sent an e-mail to Eumetsat to see if I am still registered for Metop.

Best regards...........Geoffrey

Re: Getting MRTG to work

Ulrich G. Kliegis
 

sometimes using a ROUTE PRINT command from DOS will help, as there is
a list of interfaces at the start of its output.
David,
for this machine here (not the receiver) the interface list looks like this:

C:&#92;WINDOWS&#92;system32>route print
=============================================================
Schnittstellenliste
0x1 ........................... MS TCP Loopback interface
0x2 ...00 11 2f db ff c7 ...... Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethe
rnet Controller - Paketplaner-Miniport

So, I guess, the number right of the 0x ist the interface number, right?

Cheers,
U.

Re: Getting MRTG to work

David J Taylor
 

David,
for this machine here (not the receiver) the interface list looks like this:

C:&#92;WINDOWS&#92;system32>route print
=============================================================
Schnittstellenliste
0x1 ........................... MS TCP Loopback interface
0x2 ...00 11 2f 00 00 c7 ...... Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethe
rnet Controller - Paketplaner-Miniport

So, I guess, the number right of the 0x ist the interface number, right?

Cheers,
U.
Yes, they are hex numbers, so 0x2 hex (also 2 decimal) is the interface number for your 1Gb/s networking card. On the Windows XP PC I'm using right now, I get:

Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 80 56 00 00 08 ...... VMware Virtual Ethernet Adapter for VMnet8
0x3 ...00 80 56 00 00 01 ...... VMware Virtual Ethernet Adapter for VMnet1
0x10005 ...00 00 00 00 00 e0 ...... Intel(R) 82566DC Gigabit Network Connection

so 10005 (hex) is the network card number, which is 65541 (decimal). I used the Windows calculator to convert. Checking my mrtg.cfg file, I see a line:

Target[Narvik]: 65541:public@....0.1

By the way, I changed the MAC addresses before publication. Checking on the Windows-7 PC Alta we used earlier, which has a DVB World box attached (and this seems to give the results in decimal, not hex).

Interface List
16...00 00 00 00 08 08 ......DVB Net ETAdapter
11...20 cf 30 00 00 49 ......Realtek PCIe GBE Family Controller
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2

and we have in the mrtg.cfg file:

Target[Alta_DVB]: 16:public@Alta

Target[Alta]: 11:public@....0.1

You can see I used both versions of the IP address!

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: Getting MRTG to work

Giuseppe Cico
 

On Fri, February 25, 2011 08:45, David J Taylor wrote:
David, it needn't be you to reply, maybe some of the other MRTG-ops can

.....
You can use the loopback address (127.0.0.1) or PC
name instead of the
numeric IP address:

Target[Alta-LAN]: 11:public@....0.1

Target[Alta-LAN]: 11:public@Alta

The loopback
address doesn't look as elegant, but is most likely to stay
the
same!

The interface/network number (11) may vary if
you change the configuration
(e.g. add Wi-Fi dongle). Once the
configuration is set, I tend to reboot,
and run cfgmaker, to
see what the network numbers actually are.

Anyway, not the topic right now, but rather this: Here ist the top of
the DVB-related part of the
config file
generated by the cfgmaker routine:

###
Interface 131074 >> Descr: 'TechniSat-DVB-PC-TV-Star-PCI' | Name: ''

| Ip:
'192.168.238.238' | Eth:
'00-d0-d7-0f-ee-a5' ###

Target[windbuedel_131074]: 131074:public@windbuedel:
...

Ulrich,
you can solve the "131704"
problem using IP address as the reference for MRTG by
changing the line

Target[windbuedel_131074]:
131074:public@windbuedel:

to

Target[windbuedel_131074]: /192.168.238.238:public@windbuedel:

and then any of "windbuedel_131074" to
"windbuedel_DVB" or anything you want; it's just a name:

Target[windbuedel_DVB]: /192.168.238.238:public@windbuedel:
SetEnv[windbuedel_DVB]: MRTG_INT_IP="192.168.238.238"
....

Ciao

Giuseppe






[Non-text portions of this message have been removed]

Re: Getting MRTG to work

Ulrich G. Kliegis
 

Giuseppe,

mille grazie, this solves a couple of present and upcoming questions.

Cheers,
U.


An: MSG-1@...
Von: "Giuseppe Cico" <giuseppe.cico@...>
Datum: Fri, 25 Feb 2011 15:57:02 +0100 (CET)
Betreff: Re: [MSG-1] Getting MRTG to work
Antwort an: MSG-1@...

Ulrich,
you can solve the "131704"
problem using IP address as the reference for MRTG by
changing the line

Target[windbuedel_131074]:
131074:public@windbuedel:

to

Target[windbuedel_131074]: /192.168.238.238:public@windbuedel:

and then any of "windbuedel_131074" to
"windbuedel_DVB" or anything you want; it's just a name:

Target[windbuedel_DVB]: /192.168.238.238:public@windbuedel:
SetEnv[windbuedel_DVB]: MRTG_INT_IP="192.168.238.238"

Re: Getting MRTG to work

Giuseppe Cico
 

Glad for being helpful; bitte.
Now I have a problem to solve,
since I answered other questions in advance... I MUST think about
next lottery numbers!!!!

Ciao

Giuseppe


On Fri, February 25, 2011 17:13, Ulrich G. Kliegis wrote:
Giuseppe,

mille grazie, this solves a couple
of present and upcoming questions.

Cheers,
U.


An: MSG-1@...
Von: "Giuseppe Cico" <giuseppe.cico@...>
Datum: Fri, 25 Feb 2011 15:57:02 +0100 (CET)
Betreff:
Re: [MSG-1] Getting MRTG to work
Antwort an:
MSG-1@...

Ulrich,
you
can solve the "131704"
problem using IP address as the reference for MRTG by
changing the line

Target[windbuedel_131074]:
131074:public@windbuedel:

to

Target[windbuedel_131074]: /192.168.238.238:public@windbuedel:

and then any of
"windbuedel_131074" to
"windbuedel_DVB" or anything you want; it's just a name:

Target[windbuedel_DVB]:
/192.168.238.238:public@windbuedel:
SetEnv[windbuedel_DVB]:
MRTG_INT_IP="192.168.238.238"





[Non-text portions of this message have been removed]

Re: Getting MRTG to work

Ulrich G. Kliegis
 

An: MSG-1@...
Von: "Giuseppe Cico" <giuseppe.cico@...>
Datum: Fri, 25 Feb 2011 17:39:04 +0100 (CET)
Betreff: Re: [MSG-1] Getting MRTG to work
Antwort an: MSG-1@...

 I MUST think about
next lottery numbers!!!!
Just redefine "in advance" :)

Cheers,
U.
(who just wondered about the colons (:) after the public@... terms, but they
seem to be correct.)

Meteosat MTG weather satellite programme approved

David J Taylor
 

Meteosat MTG �2.9bn weather satellite programme approved See:

http://www.bbc.co.uk/news/science-environment-12583115

New Yahoo group:

http://tech.groups.yahoo.com/group/MTG-1/

(Yes, I would have preferred MTG alone, but there is already a defunct group with that name.)

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: Getting MRTG to work

Ulrich G. Kliegis
 

Giuseppe,

when these line in my cfg file look like this:

...
Target[windbuedel_131074]: /192.168.238.238:public@windbuedel:
Target[windbuedel_DVB]: /192.168.238.238:public@windbuedel:
SetEnv[windbuedel_DVB]: MRTG_INT_IP="192.168.238.238" MRTG_INT_DESCR="TechniSat-
DVB-PC-TV-Star-PCI"
MaxBytes[windbuedel_DVB]: 12500000
Options[windbuedel_DVB]: unknaszero, growright, noo
Title[windbuedel_DVB]: Traffic Analysis for DVB -- WINDBUEDEL
...

(like in your example, if I understood it right), I keep getting this error message:


C:&#92;mrtg2171&#92;bin>perl mrtg mrtg.cfg
WARNING: "Title[windbuedel_131074]" not specified
WARNING: "MaxBytes[windbuedel_131074]" not specified
ERROR: Please fix the error(s) in your config file

When I comment-out the 131074 - line, like this:

# Target[windbuedel_131074]: /192.168.238.238:public@windbuedel:
Target[windbuedel_DVB]: /192.168.238.238:public@windbuedel:
SetEnv[windbuedel_DVB]: MRTG_INT_IP="192.168.238.238" MRTG_INT_DESCR="TechniSat-
DVB-PC-TV-Star-PCI"
MaxBytes[windbuedel_DVB]: 12500000
Options[windbuedel_DVB]: unknaszero, growright, noo
Title[windbuedel_DVB]: Traffic Analysis for DVB -- WINDBUEDEL
...

I get this:

C:&#92;mrtg2171&#92;bin>perl mrtg mrtg.cfg
C:/mrtg2171/bin&#92;rateup: File exists
2011-02-25 22:01:03, Rateup Error: Can't rename e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb
-day.png.tmp to e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb-day.png
2011-02-25 22:01:02: ERROR: Skipping webupdates because rateup did not return an
ything sensible
2011-02-25 22:01:02: WARNING: rateup died from Signal 0
with Exit Value 1 when doing router 'windbuedel_dvb'
Signal was 0, Returncode was 1

Got stuck right now. Why can't mrtg rename the tmp-file, it also said for some oterations that if
could not rename the ~.old file

From previous attempts:


C:&#92;mrtg2171&#92;bin>perl mrtg mrtg.cfg
2011-02-25 19:51:23, Rateup WARNING: C:/mrtg2171/bin&#92;rateup could not read the p
rimary log file for windbuedel_dvb
2011-02-25 19:51:23, Rateup WARNING: C:/mrtg2171/bin&#92;rateup The backup log file
for windbuedel_dvb was invalid as well
2011-02-25 19:51:23, Rateup WARNING: C:/mrtg2171/bin&#92;rateup Can't remove windbue
del_dvb.old updating log file
2011-02-25 19:51:23, Rateup WARNING: C:/mrtg2171/bin&#92;rateup Can't rename windbue
del_dvb.log to windbuedel_dvb.old updating log file

C:&#92;mrtg2171&#92;bin>perl mrtg mrtg.cfg
2011-02-25 19:51:44, Rateup WARNING: C:/mrtg2171/bin&#92;rateup Can't remove windbue
del_dvb.old updating log file
C:/mrtg2171/bin&#92;rateup: File exists
2011-02-25 19:51:44, Rateup Error: Can't rename e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb
-day.png.tmp to e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb-day.png
2011-02-25 19:51:44: WARNING: rateup died from Signal 0
with Exit Value 1 when doing router 'windbuedel_dvb'
Signal was 0, Returncode was 1

C:&#92;mrtg2171&#92;bin>perl mrtg mrtg.cfg
C:/mrtg2171/bin&#92;rateup: File exists
2011-02-25 19:52:40, Rateup Error: Can't rename e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb
-day.png.tmp to e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb-day.png
2011-02-25 19:52:40: WARNING: rateup died from Signal 0
with Exit Value 1 when doing router 'windbuedel_dvb'
Signal was 0, Returncode was 1

C:&#92;mrtg2171&#92;bin>perl mrtg mrtg.cfg
C:/mrtg2171/bin&#92;rateup: File exists
2011-02-25 19:53:20, Rateup Error: Can't rename e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb
-day.png.tmp to e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb-day.png
2011-02-25 19:53:20: WARNING: rateup died from Signal 0
with Exit Value 1 when doing router 'windbuedel_dvb'
Signal was 0, Returncode was 1

Logging off for today after hitting the send button now...

Cheers,
U.



An: MSG-1@...
Von: "Giuseppe Cico" <giuseppe.cico@...>
Datum: Fri, 25 Feb 2011 15:57:02 +0100 (CET)
Betreff: Re: [MSG-1] Getting MRTG to work
Antwort an: MSG-1@...

Ulrich,
you can solve the "131704"
problem using IP address as the reference for MRTG by
changing the line

Target[windbuedel_131074]:
131074:public@windbuedel:

to

Target[windbuedel_131074]: /192.168.238.238:public@windbuedel:

and then any of "windbuedel_131074" to
"windbuedel_DVB" or anything you want; it's just a name:

Target[windbuedel_DVB]: /192.168.238.238:public@windbuedel:
SetEnv[windbuedel_DVB]: MRTG_INT_IP="192.168.238.238"

Re: Getting MRTG to work

Giuseppe Cico
 

On Fri, February 25, 2011 22:30, Ulrich G. Kliegis wrote:
Giuseppe,

when these line in my cfg file look like
this:

...
Target[windbuedel_131074]:
/192.168.238.238:public@windbuedel:
Target[windbuedel_DVB]:
/192.168.238.238:public@windbuedel:
.........................
When I comment-out the 131074 - line, like this:

# Target[windbuedel_131074]: /192.168.238.238:public@windbuedel:


line with "131074" has to be removed or marked as a
comment; OK


Target[windbuedel_DVB]: /192.168.238.238:public@windbuedel:
.........................
I get this:

C:&#92;mrtg2171&#92;bin>perl mrtg mrtg.cfg
C:/mrtg2171/bin&#92;rateup: File exists
2011-02-25 22:01:03, Rateup
Error: Can't rename
e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb
-day.png.tmp to e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb-day.png
2011-02-25 22:01:02: ERROR: Skipping webupdates because rateup did not
.........................

Uhm.... I really have "Eumetcast1_65540" in my cfg
file, unchanged because of some links on my website and on David's
site.
Anyway I have also the internet link monitored with
...
Target[Eumetcast1_USB_Link]: /192.168.2.2:public@Eumetcast1:
...
and it's working correctly.

I have made a quick check with "Eumetcast1_DVB" instead of
"Eumetcast1_65540" and MRTG is working.

I have just a little time this morning because of some family issues,
so just some advise:
- is there any file named
"windbuedel_dvb..." (files name are all in lower case, also if
target name has uppercase) in folder?
- I remember past experiences
when MRTG got me crazy because of simple typos, so get the working version
(backup first...) and modify by changing /all/ "131074" to
"DVB" 

As a reference this is my working configuration (maybe wrapped...) :

#---------------------------------------------------------------
### Interface 65540 >> Descr: 'TechniSat-DVB-PC-TV-Star-PCI' |
Name: '' | Ip: '192.168.238.238' | Eth: '00-d0-d7-05-13-f6' ###

Target[Eumetcast1_65540]: /192.168.238.238:public@Eumetcast1:
SetEnv[Eumetcast1_65540]: MRTG_INT_IP="192.168.238.238"
MRTG_INT_DESCR="TechniSat-DVB-PC-TV-Star-PCI"
Timezone[Eumetcast1_65540]: GMT
MaxBytes[Eumetcast1_65540]:
7500000
YTics[Eumetcast1_65540]: 3
Unscaled[Eumetcast1_65540]:
dwmy
WithPeak[Eumetcast1_65540]: ymw
Title[Eumetcast1_65540]:
SkyStar card on Eumetcast1 ( MSG+RSS+MODIS+AVHRR+METOP )
Options[Eumetcast1_65540]: growright, bits, noo, unknaszero
YLegend[Eumetcast1_65540]: Bits per Second
ShortLegend[Eumetcast1_65540]: bps
LegendI[Eumetcast1_65540]:
bps:&nbsp;
LegendO[Eumetcast1_65540]:
Legend1[Eumetcast1_65540]: Bits per second
Legend2[Eumetcast1_65540]:
Legend3[Eumetcast1_65540]: Maximal 5
Minute Bits per second
Legend4[Eumetcast1_65540]:
PageTop[Eumetcast1_65540]: <H1>SkyStar THROUGHPUT - Eumetcast1 (
MSG+RSS+MODIS+AVHRR+METOP )</H1>
  <div
id="sysdetails">
   <table>
    <tr>
     <td>Maintainer: Giuseppe Cico -
Turin (ITA)</td>
     <td></td>
    </tr>
   </table>
  </div>
#---------------------------------------------------------------

and it also works when modified ( all "65540" to
"DVB" ) as

#---------------------------------------------------------------
### Interface DVB >> Descr: 'TechniSat-DVB-PC-TV-Star-PCI' | Name:
'' | Ip: '192.168.238.238' | Eth: '00-d0-d7-05-13-f6' ###

Target[Eumetcast1_DVB]: /192.168.238.238:public@Eumetcast1:
...
#---------------------------------------------------------------

I'll be back later this evening or tomorrow morning.

Ciao

Giuseppe

Re: Getting MRTG to work

Ulrich G. Kliegis
 

Giuseppe,
I un-commented the ethernet-IF part of the cfg file now too, which appears
as windbuedel-3 (cfgmaker-generated).
The error message(s) indivated that I seem to have missed so far to give
rateup correct directions of where to look and where to act.

Here is the reponse from the DOS-Box:

C:&#92;mrtg2171&#92;bin>perl mrtg mrtg.cfg
C:/mrtg2171/bin&#92;rateup: File exists
2011-02-26 12:24:12, Rateup Error: Can't rename
e:&#92;mrtg_data&#92;html&#92;windbuedel_3-d
ay.png.tmp to e:&#92;mrtg_data&#92;html&#92;windbuedel_3-day.png
2011-02-26 12:24:12: WARNING: rateup died from Signal 0
with Exit Value 1 when doing router 'windbuedel_3'
Signal was 0, Returncode was 1
C:/mrtg2171/bin&#92;rateup: File exists
2011-02-26 11:24:12, Rateup Error: Can't rename
e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb
-day.png.tmp to e:&#92;mrtg_data&#92;html&#92;windbuedel_dvb-day.png
2011-02-26 12:24:12: ERROR: Skipping webupdates because rateup did
not return an
ything sensible
2011-02-26 12:24:12: WARNING: rateup died from Signal 0
with Exit Value 1 when doing router 'windbuedel_dvb'
Signal was 0, Returncode was 1

C:&#92;mrtg2171&#92;bin>



And here, sorry for the size, once the complete present mrtg.cfg

# Created by
# cfgmaker public@windbuedel


### Global Config Options

# or for NT
# WorkDir: c:&#92;mrtgdata

WorkDir: e:&#92;mrtg_data&#92;html

### Global Defaults

# to get bits instead of bytes and graphs growing to the right
# Options[_]: growright, bits

EnableIPv6: no

#############################################################
#########
# System: WINDBUEDEL
# Description: Hardware: x86 Family 15 Model 31 Stepping 0 AT/AT
COMPATIBLE - Software: Windows 2000 Version 5.1 (Build 2600
Uniprocessor Free)
# Contact:
# Location:
#############################################################
#########


### Interface 1 >> Descr: 'MS-TCP-Loopback-interface' | Name: '' | Ip:
'127.0.0.1' | Eth: '' ###
### The following interface is commented out because:
### * it is a Software Loopback interface
#
# Target[windbuedel_1]: 1:public@windbuedel:
# SetEnv[windbuedel_1]: MRTG_INT_IP="127.0.0.1"
MRTG_INT_DESCR="MS-TCP-Loopback-interface"
# MaxBytes[windbuedel_1]: 1250000
# Title[windbuedel_1]: Traffic Analysis for 1 -- WINDBUEDEL
# PageTop[windbuedel_1]: <h1>Traffic Analysis for 1 --
WINDBUEDEL</h1>
# <div id="sysdetails">
# <table>
# <tr>
# <td>System:</td>
# <td>WINDBUEDEL in </td>
# </tr>
# <tr>
# <td>Maintainer:</td>
# <td></td>
# </tr>
# <tr>
# <td>Description:</td>
# <td>MS-TCP-Loopback-interface
</td>
# </tr>
# <tr>
# <td>ifType:</td>
# <td>softwareLoopback (24)</td>
# </tr>
# <tr>
# <td>ifName:</td>
# <td></td>
# </tr>
# <tr>
# <td>Max Speed:</td>
# <td>1250.0 kBytes/s</td>
# </tr>
# <tr>
# <td>Ip:</td>
# <td>127.0.0.1 (localhost)</td>
# </tr>
# </table>
# </div>


### Interface 3 >> Descr: 'Marvell-Yukon-88E8001/8003/8010-PCI-Gigabit-
Ethernet-Controller---Paketplaner-Miniport' | Name: '' | Ip: '192.168.1.67' |
Eth: '00-13-d4-dc-7b-0c' ###

Target[windbuedel_3]: 3:public@windbuedel:
SetEnv[windbuedel_3]: MRTG_INT_IP="192.168.1.67"
MRTG_INT_DESCR="Marvell-Yukon-88E8001/8003/8010-PCI-Gigabit-
Ethernet-Controller---Paketplaner-Miniport"

Options[windbuedel_3]: growright, bits, noo, unknaszero
MaxBytes[windbuedel_3]: 12500000
Title[windbuedel_3]: Traffic Analysis for 3 -- WINDBUEDEL
PageTop[windbuedel_3]: <h1>Traffic Analysis for 3 -- WINDBUEDEL</h1>
<div id="sysdetails">
<table>
<tr>
<td>System:</td>
<td>WINDBUEDEL in Heikendorf /
Germany </td>
</tr>
<tr>
<td>Maintainer: Ulli Kliegis</td>
<td></td>
</tr>
<tr>
<td>Description:</td>
<td>Marvell-Yukon-
88E8001/8003/8010-PCI-Gigabit-Ethernet-Controller---Paketplaner-Miniport
</td>
</tr>
<tr>
<td>Max Speed:</td>
<td>12.5 MBytes/s</td>
</tr>
<tr>
<td>Ip:</td>
<td>192.168.1.67
(windbuedel)</td>
</tr>
</table>
</div>


### Interface 131074 >> Descr: 'TechniSat-DVB-PC-TV-Star-PCI' | Name: ''
| Ip: '192.168.238.238' | Eth: '00-d0-d7-0f-ee-a5' ###


Target[windbuedel_DVB]: /192.168.238.238:public@windbuedel:
SetEnv[windbuedel_DVB]: MRTG_INT_IP="192.168.238.238"
MRTG_INT_DESCR="TechniSat-DVB-PC-TV-Star-PCI"
MaxBytes[windbuedel_DVB]: 12500000

Timezone[windbuedel_DVB]: GMT

YTics[windbuedel_DVB]: 3
Unscaled[windbuedel_DVB]: dwmy
WithPeak[windbuedel_DVB]: ymw
Options[windbuedel_DVB]: growright, bits, noo, unknaszero
YLegend[windbuedel_DVB]: Bits per Second
ShortLegend[windbuedel_DVB]: bps
LegendI[windbuedel_DVB]: bps:&nbsp;
LegendO[windbuedel_DVB]:
Legend1[windbuedel_DVB]: Bits per second
Legend2[windbuedel_DVB]:
Legend3[windbuedel_DVB]: Max. 5 Minute Bits per second
Legend4[windbuedel_DVB]:

Title[windbuedel_DVB]: Traffic Analysis for DVB -- WINDBUEDEL
PageTop[windbuedel_DVB]: <h1>Traffic Analysis for DVB --
WINDBUEDEL</h1>
<div id="sysdetails">
<table>
<tr>
<td>System:Eumetcast-Reception
via </td>
<td>WINDBUEDEL in Heikendorf /
Germany</td>
</tr>
<tr>
<td>Maintainer: Ulli Kliegis</td>
<td></td>
</tr>
<tr>
<td>Description:</td>
<td>TechniSat-DVB-PC-TV-Star-
PCI </td>
</tr>
<tr>
<td>Max Speed:</td>
<td>12.5 MBytes/s</td>
</tr>
</table>
</div>




(EOF)

The temporary DVB- .png image looked correct when I cleared the one that
reatup could not remove and renamed the .tmp one.

That's why I suspect a problem in the environment of rateup.

Thanks for your patience!

Cheers,

U.

derfag

duncan
 

Hi Could anyone please advise on which defrag program to use . At this time i am running Smart Defrag2 but since this was installed i seem to have an issue with occasional missing segments. Any Help would be apreciated.
Best Regards Duncan

Re: write permission for rateup.exe - was: Getting MRTG to work

Ulrich G. Kliegis
 

David, Giuseppe, and other MRTGeroes,
the problem in my setup seems to be the write permission for rateup.exe,
which is unexplainable to me. I never experienced any problems with these
access rights on that machine (XP Pro).

The error messsages sent from MRTG / Rateup.exe indicate, though, that
rateup can't rename any *.png.tmp file to the corresponding ~.png file.
It seems to miss to delete the pevious ~png file first.
It writes new ~.tmp files, though.

When I rename a ~png.tmp file to, say, ~2.png, the content shows a correct
result, like a realistic strength value. So, apart from the rewriting function,
most other things look good so far.

I checked the permission properties. The files themselves are fully writable,
no restrictions

The folder(s), though, show a write-protect-box symbol filled with a pale
green square, not the 'v' check mark. I can clear that, but it reappears
immediately. As said, I have not experienced any other permission
restricitons on that machine.

Finally, MRTG somehow thinks it lives on a Win 2000 machine - that's what
the cfgmaker wrote into the mrtg-cfg header block. No idea why, no idea
what consequences this has upon the permission structure.

Thanks for any help.

Cheers,U.

Re: derfag

Robert Moore
 

I have run MSTdefrag for some time now - no trouble, works very effectively.

Robert

--- In MSG-1@..., "Duncan Edwards" <sueandunc@...> wrote:

Hi Could anyone please advise on which defrag program to use . At this time i am running Smart Defrag2 but since this was installed i seem to have an issue with occasional missing segments. Any Help would be apreciated.
Best Regards Duncan