Date   
Re: Getting MRTG to work

David J Taylor
 

Hi all,
while trying to install MRTG on my receiver PC, I got stuck a little. XP Pro,
receiving functions work flawlessly (at least to my standards...). I studied
both the MRTG homepage and Davids pages on the installation of MRTG. I
have come so far as having run sucessfully perl cfgmaker@<mycomp>, as
described in the mrtg page. I guess the reason why I did not find it as a file
is that I did not add the --output option, and some more. At least, the
structure of the cfg file appeared in the DOS-box.
.. or just use a DOS redirection command:

perl cfgmaker public@....0.1 > config.txt

Now, that is still something I can try out alone, but David touches a few
topics in his page that are more than one of my short steps apart from each
other. Adding some options '~...noo' - where? In the mrtg config-file? And
other addenda? Where should they go, is it irrelevant, where in the config
file they are added, and so on. MRTG for Dummies...

Long story cut short: Is there any detailed how-to cookbook guide around, or
even an exemplary sample cfg file and some more steps of how to get it
working first locally, then also publicly?

Thanks in advance for any helpful hint!

Cheers,
U.
There's an example of the "-noo" option on my "How to" Web page:

http://www.satsignal.eu/mrtg/performance_howto.php

in the first section, under "What if the PC were single-core?"

I've recently added air temperature monitoring using a couple of cheap USB probes from China - working very nicely! Described briefly on that page.

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
 

David,
thanks for that pointer. Tons of useful information - a link to that page from
here:

http://www.satsignal.eu/mrtg/Eumetcast.html#HowTo

might help accidental visitors. Only now I saw that here (at the bottom) links
to these pages can befound, but I did not expect more on SNMP monitoring
from the CPU- etc. monitoring pages. Now I am not wiser, but older. (not
wiser because the balance is zero)

A key term for me was your mentioning of include files. I like that concept.

More questions guaranteed,

cheers and thanks,

U.

http://www.satsignal.eu/mrtg/index.htm


There's an example of the "-noo" option on m
y "How to" Web page:

http://www.satsignal.eu/mrtg/performance_howto.php

in the first section, under "What if the PC were single-core?"

Re: Getting MRTG to work

David J Taylor
 

David,
thanks for that pointer. Tons of useful information - a link to that page from
here:

http://www.satsignal.eu/mrtg/Eumetcast.html#HowTo

might help accidental visitors. Only now I saw that here (at the bottom) links
to these pages can befound, but I did not expect more on SNMP monitoring
from the CPU- etc. monitoring pages. Now I am not wiser, but older. (not
wiser because the balance is zero)

A key term for me was your mentioning of include files. I like that concept.

More questions guaranteed,

cheers and thanks,

U.
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!

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
 

Too
many ideas, too little time!
Better than the boolean inverse... :)

Cheers,
U.

Re: New to Metop

geoffreygee90
 

Alan

Many thanks for quick reply. Current position.

I had uninstalled ArSOFT Ram disk.
Using Explorer . Business TV-Ip shows .....received...Data Channel 1. Data Channel 2 Data Channel 3 . ( no EPS-10 )
receiving.....tmp

These appeared automatically and were not put in by me.

My recv channel.ini is

# recv-channels.ini - TelliCast+TelliVision Client channel configuration file
#
# 2-4-3 10-10-2005
#

[EUMETSAT Data Channel 1]
target_directory=C:&#92;received&#92;Data Channel 1

[EUMETSAT Data Channel 4]
target_directory=C:&#92;received&#92;Data Channel 4



[EUMETSAT Data Channel 2]
target_directory=C:&#92;received&#92;Data Channel 2

[EUMETSAT Data Channel 3]
target_directory=C:&#92;received&#92;Data Channel 3

#METOP AVHRR Data channel EPS-10
[EPS-10]
target_directory=C:&#92;received&#92;EPS-10



# target_directory: Directory for received files. The target_directory name
# is relative to the current working directory.
# syntax: target_directory=<directory>
# default: received

#temp_directory=receiving/tmp
# tmp_directory: If this parameter is given tc-recv will internally
# store/compose all received files within the given directory and
# later move them to the target directory.
# While this option requires an additional move operation it
# guarantees that all files appearing in the target directory are
# fully written to the file system.
# syntax: tmp_directory=<directory>
# default: undefined=off, but default value may be redefined in
# recv.ini




# Section per channel or channel group identified by channel name (wildcard
# "*" allowed at end of name)

#activate_ftp_forwarding=1
# activate_ftp_forwarding: Will activate FTP forwarding for the correctly
# received files according to the recv.ini [ftp_forwarding]
# parameters.
# syntax: activate_ftp_forwarding=<value of range>
# range: 0/1
# default: 0=off

#tmp_directory=receiving/tmp/files
# tmp_directory: If this parameter is given tc-recv will internally
# store/compose all received files within the given directory and
# later move them to the target directory.
# While this option requires an additional move operation it
# guarantees that all files appearing in the target directory are
# fully written to the file system.
# syntax: tmp_directory=<directory>
# default: undefined=off, but default value may be redefined in
# recv.ini

#tmp_prefix=.
# tmp_prefix: Like tmp_directory, but files are composed within the final
# target directories but stored with the given prefix in front of
# the normal filenames until the files are fully written.
# syntax: tmp_prefix=<file name start>
# default: undefined=off, but default value may be redefined in
# recv.ini

#tmp_suffix=.tmp
# tmp_suffix: Like tmp_prefix, but adding a suffix to the normal filenames
# until the files are fully written.
# syntax: tmp_suffix=<file suffix>
# default: undefined=off, but default value may be redefined in
# recv.ini


Again many thanks for your help. I wonder if it might be best if I re-installed Metop and started from scratch again ?

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

Re: New to Metop

Alan Sewards
 

Geoffrey,
You may be looking in the wrong place. In your recv_channels.ini file, you have specified that the target_directory for receiving is in the root of the C: drive (C:&#92;received&#92;eps-10) while you are looking in the C:&#92;Program files&#92;T Systems/Business TV-IP&#92;received&#92; tree from what you say. The folders you have in there were probably put there by the T-Systems tc-recv program when you ran it earlier. If you use the Windows Explorer and click on the C: drive you should find a folder named received which has the folders Data Channel 1, 2, 3 etc and EPS-10, as you have specified in the recv-_channels.ini you edited. The METOP files will appear in the EPS-10 folder.
I don't think there is any point in uninstalling METOP Manager until we have sorted out this problem.

Best regards - Alan S

On 24/02/2011 10:39 AM, Geoffrey Gee wrote:
Alan

Many thanks for quick reply. Current position.

I had uninstalled ArSOFT Ram disk.
Using Explorer . Business TV-Ip shows .....received...Data Channel 1. Data
Channel 2 Data Channel 3 . ( no EPS-10 )
receiving.....tmp

These appeared automatically and were not put in by me.

My recv channel.ini is

# recv-channels.ini - TelliCast+TelliVision Client channel configuration
file
#
# 2-4-3 10-10-2005
#

[EUMETSAT Data Channel 1]
target_directory=C:&#92;received&#92;Data Channel 1

[EUMETSAT Data Channel 4]
target_directory=C:&#92;received&#92;Data Channel 4



[EUMETSAT Data Channel 2]
target_directory=C:&#92;received&#92;Data Channel 2

[EUMETSAT Data Channel 3]
target_directory=C:&#92;received&#92;Data Channel 3

#METOP AVHRR Data channel EPS-10
[EPS-10]
target_directory=C:&#92;received&#92;EPS-10



# target_directory: Directory for received files. The target_directory name
# is relative to the current working directory.
# syntax: target_directory=<directory>
# default: received

#temp_directory=receiving/tmp
# tmp_directory: If this parameter is given tc-recv will internally
# store/compose all received files within the given directory and
# later move them to the target directory.
# While this option requires an additional move operation it
# guarantees that all files appearing in the target directory are
# fully written to the file system.
# syntax: tmp_directory=<directory>
# default: undefined=off, but default value may be redefined in
# recv.ini




# Section per channel or channel group identified by channel name (wildcard
# "*" allowed at end of name)

#activate_ftp_forwarding=1
# activate_ftp_forwarding: Will activate FTP forwarding for the correctly
# received files according to the recv.ini [ftp_forwarding]
# parameters.
# syntax: activate_ftp_forwarding=<value of range>
# range: 0/1
# default: 0=off

#tmp_directory=receiving/tmp/files
# tmp_directory: If this parameter is given tc-recv will internally
# store/compose all received files within the given directory and
# later move them to the target directory.
# While this option requires an additional move operation it
# guarantees that all files appearing in the target directory are
# fully written to the file system.
# syntax: tmp_directory=<directory>
# default: undefined=off, but default value may be redefined in
# recv.ini

#tmp_prefix=.
# tmp_prefix: Like tmp_directory, but files are composed within the final
# target directories but stored with the given prefix in front of
# the normal filenames until the files are fully written.
# syntax: tmp_prefix=<file name start>
# default: undefined=off, but default value may be redefined in
# recv.ini

#tmp_suffix=.tmp
# tmp_suffix: Like tmp_prefix, but adding a suffix to the normal filenames
# until the files are fully written.
# syntax: tmp_suffix=<file suffix>
# default: undefined=off, but default value may be redefined in
# recv.ini


Again many thanks for your help. I wonder if it might be best if I
re-installed Metop and started from scratch again ?

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

New to Metop

geoffreygee90
 

Alan

I have just found further down the Programmes Tree and quite separate to BusinessTV Ip folder............another folder ........received......
which has in it Data Channel 1..... Data channel 2..... Data Channel 4..... Data Channel 4..... and EPS-10.

Am I right in presuming this should be the one on BusinessTV-Ip ? If so how do I get it there ?

Regards................Geoffrey

Re: New to Metop

Alan Sewards
 

Geoffrey,
Do you really mean that the 'received' folder that you have found is under Program Files, or is it under C:&#92; (that is, in the c: drive root directory)? It should be the latter, because that is what you have specified in recv_channels.ini. There is nothing wrong with having them in either place, but you must be consistent: you can't have the files going into folders under C:&#92;Program Files&#92;Business TV-IP if you have told METOP to look for them under C:&#92;

Best regards - Alan S

On 24/02/2011 11:25 AM, Geoffrey Gee wrote:
Alan

I have just found further down the Programmes Tree and quite separate to
BusinessTV Ip folder............another folder ........received......
which has in it Data Channel 1..... Data channel 2..... Data Channel 4.....
Data Channel 4..... and EPS-10.

Am I right in presuming this should be the one on BusinessTV-Ip ? If
so how do I get it there ?

Regards................Geoffrey

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

Re: New to Metop

duncan
 

Geoffrey. Without interupting you i hope and this might mean nothing i have noticed you have an # in front of your #temp_directory=receiving/tmp

I may be wrong here but surely this will stop the files being sent to the directory.I am probably wrong so i would verify this with Alan. Regards Duncan

Re: New to Metop

Alan Sewards
 

Duncan,
The temp_directory is optional and will default to the specified received directory, as is explained in the commented text that follows the line. So it does not matter if it is undefined, although I use it myself for the reason stated.

Best regards - Alan S

On 24/02/2011 12:35 PM, Duncan Edwards wrote:
Geoffrey. Without interupting you i hope and this might mean nothing i
have noticed you have an # in front of your #temp_directory=receiving/tmp

I may be wrong here but surely this will stop the files being sent to
the directory.I am probably wrong so i would verify this with Alan.
Regards Duncan

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

Re: New to Metop

David J Taylor
 

Duncan,
The temp_directory is optional and will default to the specified
received directory, as is explained in the commented text that follows
the line. So it does not matter if it is undefined, although I use it
myself for the reason stated.

Best regards - Alan S
Alan,

It may matter that it's not defined. As I understand it, large files will be built up in situ if the "tmp_directory" is not defined, and therefore programs which check for the presence of a file may see the file as being present, even though it is not yet complete. Attempting to process such a file may result in an incomplete or lost image. With "tmp_directory=temp" in the recv.ini file, new data will be built up in the "temp" directory, and only moved to the appropriate &#92;received&#92; directory when it is complete.

My recommendation therefore is to include, a common line in the recv.ini such as:

[parameters]
tmp_directory=temp

(there will be other lines in the parameters section, of course).

By the way, much of the recv-channels.ini file is commented out - I have now taken to removing those comments to leave a clearer file, and one I find easier to understand. For example, this could be the entire file:

____________________________________
[EPS-10]
target_directory=received&#92;EPS-10

[EPS-15]
target_directory=received&#92;EPS-15

[EPS-18]
target_directory=received&#92;EPS-18

[EUMETSAT Data Channel 1]
target_directory=received&#92;Data Channel 1

[EUMETSAT Data Channel 2]
target_directory=received&#92;Data Channel 2

[EUMETSAT Data Channel 3]
target_directory=received&#92;Data Channel 3

[Info-Channel-1]
target_directory=received

[Info-Channel-2]
target_directory=received&#92;Info-Channel-2

[WWW-Channel]
target_directory=www/eumetsat
____________________________________


(I appreciate that you know this already, but others may not).

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

Re: New to Metop

geoffreygee90
 

Alan

Sorry for delay in coming back but I had to go out this morning.

Apologies for my poor description of the situation. You are quite right the second received file which I found is in the c root directory,just below programmes,i.e....C:&#92;received and in it are shown five folders for the Channels 1 to 4 plus EPS-10.

My Metop set up shows for the received files path.................C:&#92;received&#92;EPS-10

No data is coming through.

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

Re: New to Metop

geoffreygee90
 

Duncan

Thank you for your two messages.Everything helps and is appreciated, my faith in human nature is much restored by so many offering assistance.

Regards..........................Geoffrey

Re: New to Metop

Alan Sewards
 

Geoffrey,
Thanks for that info. Now, (1) is any data coming through Channels 1-4? And (2), have you removed the RAMdrive that you were trying? If no to (1) and yes to (2), have you changed the file_database_directory in recv.ini to point to the receiving folder? (It would have been set up to point to the RAMdisk when you were using that.)
The received directory seems to be correctly set up and so is METOP, so we have to work back up the chain to find out where the data loss is occurring.

Best regards - Alan S

On 24/02/2011 5:49 PM, Geoffrey Gee wrote:
Alan

Sorry for delay in coming back but I had to go out this morning.

Apologies for my poor description of the situation. You are quite right the
second received file which I found is in the c root directory,just below
programmes,i.e....C:&#92;received and in it are shown five folders for the
Channels 1 to 4 plus EPS-10.

My Metop set up shows for the received files
path.................C:&#92;received&#92;EPS-10

No data is coming through.

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: New to Metop

geoffreygee90
 

Alan

Thanks again......Files for Channels 1-4 show data 24/02/11................Nothing in file for EPS-10.................ramdisk all removed.

Rec.ini shows..............#file_database_directory=receiving /tmp

Regards.....Geoffrey

Re: New to Metop

Alan Sewards
 

Geoffrey,
Good, we are making progress if you have data files arriving in Channels 1-4. That shows that data is arriving and being processed into the right channels, which means the receiver and Tellicast software are working. There are only two reasons I can see that prevent the [EPS-10] data from coming through: (1) that it has not been activated by Eumetcast, and (2) the PID is not set in Setup4PC. We will assume that Eumetcast have done their part (although I have known them telling me I was activated and I wasn't), leaving the Sky Star software. The only way that data can be coming in with some missing is if the PID in Sky Star for that data is not set. Right-click on the green orb in the tray and select Setup4PC. Click on Data Services. Uncheck the box in the PID List labelled Hexadecimal, and verify that 510 appears in the list. If it does not, type 510 in the box under Hexadecimal and click Insert, when it should appear in the list. Then OK and Close to leave. You can then try and see if data is coming in to the EPS-10 received folder, but be aware, the data does not come in continuously, there are gaps of a few minutes between data dumps, so if nothing happens, wait say ten minutes to be sure.
Regarding the recv.ini entry for the receiving folder: the # at the start of the line indicates that the line is to be treated as a comment and the line is ignored as an instruction. That means that the receiving folder is undefined but the fact that you are receiving Channels 1-4 means that the software has found a place for receiving and knows how to get there. If you want the folder defined, just remove the # at the beginning of the line.

Best regards - Alan S

On 24/02/2011 7:18 PM, Geoffrey Gee wrote:


Alan

Thanks again......Files for Channels 1-4 show data
24/02/11................Nothing in file for EPS-10.................ramdisk
all removed.

Rec.ini shows..............#file_database_directory=receiving /tmp

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

New to Metop

geoffreygee90
 

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











Notification No : 300008749

Dear Geoffrey N. Gee,

Subject : 300008749 Licence Renewal

I am pleased to inform you that we have activated the services that you
have requested for.

Please see below the complete list of services to your account :
Services:
ears-avhrr
EPS-METOP-ASCA-L2
EPS-METOP-ATOV-L2
EPS-METOP-AVHR-L1
EPS-METOP-IASI-L2
EPS-NOAA-ATOV-L2
EPS-NOAA-AVHR-L1
EPS-SERVICE
High Rate SEVIRI - 15 min
High Rate SEVIRI - 30 min
High Rate SEVIRI - 3 hourly
High Rate SEVIRI - 60 min
High Rate SEVIRI - 6 hourly
Low Rate SEVIRI - 30 min
Low Rate SEVIRI - 3 hourly
Low Rate SEVIRI - 60 min
Low Rate SEVIRI - 6 hourly
Foreign Satellite Data
Hourly Foreign Satellite Data
Meteorological Products - 15min
msg-lrit-mpef-eur
Meteorological Products - 1 to 3 hourly
msg-rss-lrit-mpef
msg-rss-lrit-mpef-low
HRI - IODC - 6-hourly
SAF-LSA-afr
SAF-LSA-afr-15m
SAF-LSA-eur
SAF-LSA-eur-15m
SAF-LSA-sam
SAF-LSA-sam-15m
SAF-O3M-eur
Ocean + Sea-ice SAF
OSI-SAF Data Europe
UNS-general
www-eumetsat

Please do not hesitate to contact us if you experience any technical
issues with reception of the data.

Regards,

Pamela Sch�bel-Pattiselanno




User Service Helpdesk
EUMETSAT User Service
Tel: +49 6151 807 377
Fax: +49 6151 807 379
Email: ops@...

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!