Date   
Re: not yet perfect, but...

Ian Deans
 

David,

I mentioned in a mail a few weeks ago that a completely new mstdefrag version is to be released sometime in the future. However it is not yet available and the download version is still 3.6 which should work fine with the 2.4.4 client, but not of course (with the not to be released) 2.5.17 client.

Regards
Ian.

-----Original Message-----
From: David J Taylor
Sent: Friday, March 04, 2011 11:49 AM
To: MSG-1@...
Subject: Re: [MSG-1] not yet perfect, but...



I would recommend having a real-time defragmenter running - with the
TelliCast 2.4.4 client software we have found mstDefrag to be very
acceptable, and have almost zero effect on received data (i.e. we could
not attribute any extra losses to running the defragmenter). I've used
version 2 and 3, but I see they are up to version 7 now. How did they
manage that?

http://www.mstsoftware.com/mst-Defrag

Re: not yet perfect, but...

David J Taylor
 

Also TURN OFF SYSTEM RESTORE
Sorry for the shouting, but that can take up a lot of resources.
Use one of the free disk imaging utilities and you don't need sytem restore.
See here for a choice of what's available
http://www.techsupportalert.com/best-free-drive-imaging-program.htm
Cheers

Alan
What you might want to do is to have System Restore running on your system disk, but not on your data disk(s). That gives you some chance of recovery if you don't routinely run disk imaging.

In this case, System Restore is unlikely to be the problem, as Ulrich's system shows a steady packet loss correlated with the data flow, and not daily peaks when System Restore might be active.

http://eumetmon.rummelecke.de/

I've suggested that, for the moment at least, he move the missed packets graph up to below the DVB-S traffic graph.

By the way, Ulrich. I have noticed that on a reboot you MRTG can give you a false peak, like the peak seen in your LAN traffic. If I get such a false peak (and I appreciate that yours may be real and not false), is to stop MRTG, edit the log file, and restart MRTG. I do this so that the regular variations are seen in their correct context, and not hidden by a reboot. Here's a contrived example, from a reboot of my main PC this morning (after an iTunes update):

___________________________________
1299232200 679564 17203 701035 17579
1299231900 605254 18251 718448 24061
1299231600 447832 14998 718448 24061
1299231300 4478320 149980 7184480 240610
1299231000 4478320 149980 7184480 240610
1299230700 4478320 149980 7184480 240610
1299230400 414766 10333 514455 11263
1299230100 302383 9131 514455 11263
1299229800 278167 13189 284949 14310
___________________________________
1299232200 679564 17203 701035 17579
1299231900 605254 18251 718448 24061
1299231600 447832 14998 718448 24061
1299231300 0 0 0 0
1299231000 0 0 0 0
1299230700 0 0 0 0
1299230400 414766 10333 514455 11263
1299230100 302383 9131 514455 11263
1299229800 278167 13189 284949 14310
___________________________________


The false lines tend to stand out visually by being longer than the other lines, and often have repeated values. You can see the gap in the LAN traffic around 09:30 UTC:

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

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

Re: not yet perfect, but...

David J Taylor
 

David,

I mentioned in a mail a few weeks ago that a completely new mstdefrag
version is to be released sometime in the future. However it is not yet
available and the download version is still 3.6 which should work fine with
the 2.4.4 client, but not of course (with the not to be released) 2.5.17
client.

Regards
Ian.
Thanks, Ian. Looking at their Web site it seemed that 7.0 beta was on offer, but that may have just been their enthusiasm for the newer version. Actually, even version 2.x works with Windows-7.

If it /is/ "completely new", how well it works with TelliCast reception is unknown, and I might therefore be more inclined to steer folk towards one of the free solutions you have been finding and evaluating, as even though they are not continuous defraggers, they seem be gentle and not to interfere with reception on today's PCs.

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

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Fri, 4 Mar 2011 14:00:32 -0000
Betreff: Re: [MSG-1] not yet perfect, but...
Antwort an: MSG-1@...

By the way, Ulrich. I have noticed that on a reboot you MRTG can give
you a false peak, like the peak seen in your LAN traffic.
Yes, David, I saw that already but was not sure what to do with the log files.
Thanks for the advice. Later...

And right now, the defragmentation seems to increase the missed rate, but I
take it that that's due to the large amount of shifting data around.

The HDDs are SATA, btw, running at 150 Mbits/s (due to limitations of the
controller) . 32 MByte cache each.


Cheers,
U.

Re: not yet perfect, but...

David J Taylor
 

And right now, the defragmentation seems to increase the missed rate, but I
take it that that's due to the large amount of shifting data around.

The HDDs are SATA, btw, running at 150 Mbits/s (due to limitations of the
controller) . 32 MByte cache each.


Cheers,
U.
Not sure whether the controller speed would make a lot of difference, Ulrich.

I assume you have installed one of the suggested defrag programs. Yes, during an initial pass you might see a higher lost packet rate, the real test is later, of course. Did the programs report a highly fragmented disk?

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

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Fri, 4 Mar 2011 15:19:43 -0000
Betreff: Re: [MSG-1] not yet perfect, but...
Antwort an: MSG-1@...

Did the programs report a highly fragmented
disk?
If 76% resp. 95% is high, well, yes... ;)

I passed the data lawnmower over the dvb data, as you may have seen...

Cheers,
U.

Re: mrtg reboot

Alan Banks <alan@...>
 

On 04/03/2011 14:00, David J Taylor wrote:

By the way, Ulrich. I have noticed that on a reboot you MRTG can give you
a false peak, like the peak seen in your LAN traffic. If I get such a
false peak (and I appreciate that yours may be real and not false), is to
stop MRTG, edit the log file, and restart MRTG. I do this so that the
regular variations are seen in their correct context, and not hidden by a
reboot. Here's a contrived example, from a reboot of my main PC this
morning (after an iTunes update):

___________________________________
1299232200 679564 17203 701035 17579
1299231900 605254 18251 718448 24061
1299231600 447832 14998 718448 24061
1299231300 4478320 149980 7184480 240610
1299231000 4478320 149980 7184480 240610
1299230700 4478320 149980 7184480 240610
1299230400 414766 10333 514455 11263
1299230100 302383 9131 514455 11263
1299229800 278167 13189 284949 14310
___________________________________
1299232200 679564 17203 701035 17579
1299231900 605254 18251 718448 24061
1299231600 447832 14998 718448 24061
1299231300 0 0 0 0
1299231000 0 0 0 0
1299230700 0 0 0 0
1299230400 414766 10333 514455 11263
1299230100 302383 9131 514455 11263
1299229800 278167 13189 284949 14310
___________________________________

Thanks for that David - had sometimes wondered how to achieve that!
You learn something new every day!
Cheers

Alan

Re: mrtg reboot

Ulrich G. Kliegis
 

An: MSG-1@...
Von: Alan Banks <alan@...>
Datum: Fri, 04 Mar 2011 16:21:22 +0000
Betreff: Re: [MSG-1] mrtg reboot
Antwort an: MSG-1@...

Thanks for that David - had sometimes wondered how to achieve that!
You learn something new every day!
Alan and David,

here, it is just data for a graph. But imagine my horror some years back,
when I found out that one of our sales guys used a hexeditor to change
some coordinates in the program for a five-axes CNC milling machine. He
must have had tremendous luck or was an unrecognized hypergenious,
nothing serious happened, but it could have. The workshop was off limits for
him after that. Don't ask why he did that...

I just also modified the log files - after rebooting again. Deactivated sys
restore, thanks for that hint.

About 400 Gigs to defrag now, will take some hours...

Which mode do you use with mst ? Smart/M ?

Cheers,
U.

Re: mrtg reboot

David J Taylor
 

Alan and David,

here, it is just data for a graph. But imagine my horror some years back,
when I found out that one of our sales guys used a hexeditor to change
some coordinates in the program for a five-axes CNC milling machine. He
must have had tremendous luck or was an unrecognized hypergenious,
nothing serious happened, but it could have. The workshop was off limits for
him after that. Don't ask why he did that...
I'm sure he "thought" he was trying to be "helpful"! Amazing!

I just also modified the log files - after rebooting again. Deactivated sys
restore, thanks for that hint.

About 400 Gigs to defrag now, will take some hours...

Which mode do you use with mst ? Smart/M ?

Cheers,
U.
Yes, the "Monitor" mode works just fine. I allow it to defragment the system files at boot-up.

The only thing I found to watch out for is if you use USB disks plugged in and removed from time to time, then you may want to exclude that drive letter. Otherwise, when you "Safely remove" the disk, you find it locked by mstDefrag.

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

Re: mrtg reboot

Ulrich G. Kliegis
 

I'm sure he "thought" he was trying to be "helpful"! Amazing!
I was not aware you know him? :)))

Thanks for that advice re USB sticks and mst. Not applicable on that
machine, but could be on others.

Cheers,
U.

Re: not yet perfect, but...

Ulrich G. Kliegis
 


I assume you have installed one of the suggested defrag programs.
Yes, during an initial pass you might see a higher lost packet rate,
the real test is later, of course. Did the programs report a highly
fragmented disk?
David,
this morning, mst.defrag finished restructuring the two collection disks. I
switched them to the watch and defrag mode now, in Smart/M mode. The
missed packets rate is still higher than before starting this operation.
Strange.

I also cut back the hold times for many formats so that more disk space
remains free now.

And I fine-adjusted the LNB position to the maximum strength level.

Just as a status report.

Cheers,
U.

Re: not yet perfect, but...

David J Taylor
 

David,
this morning, mst.defrag finished restructuring the two collection disks. I
switched them to the watch and defrag mode now, in Smart/M mode. The
missed packets rate is still higher than before starting this operation.
Strange.

I also cut back the hold times for many formats so that more disk space
remains free now.

And I fine-adjusted the LNB position to the maximum strength level.

Just as a status report.

Cheers,
U.
Ulrich, I'm looking at the graphs here:

http://eumetmon.rummelecke.de/

and wondering whether what we see as TelliCast statistics might actually be something else, whether the recording in is error. If you look at the TelliCast HTML Shell, Statistics menu, do you actually see a large number of "Missed Packets before FEC" and "FEC Recovered Packets"? It seems like you are getting - on average - perhaps 200 missed and recovered an hour, which is 2 or 3 a minute. However, it does also seem that most missed packets are recovered.

Just to check, you /do/ have a tmp_directory entry in your recv.ini:

_____________________________________
[parameters]
tmp_directory=temp
_____________________________________

pointing to the same partition as all the other receive directories?

With the sort of errors I see, it's a small packet rate loss which can be recovered, anything higher is not recovered. I'm wondering whether the cause of the loss is something not even associated with the PC, such as some radio-frequency interference getting into the IF channel. Perhaps something from the port at Kiel, just across from you? I expect you have already made sure that the connectors are not loose.

If it /is/ the PC, then for what it's worth, on the less powerful PCs here which doing EUMETCast reception, but not used interactively, even though they are connected to the LAN they run without firewall, virus or malware protection - i.e. they run with the very minimum operating system. On the other hand, a quad-core PC is running nominally without loss, receive and processing, even though it has Windows Defender and Microsoft Security Essentials installed, and runs the Windows-7 firewall. I've even run multi-hour video format conversions on that PC without affecting EUMETCast! Might be worth checking that the hard disks are not IDE ones working in PIO mode (although the higher CPU load would usually show that straight away, and you haven't reported high CPU, as I recall).

Note that some of the commercial security suites can be very intrusive. I also found that a "manufacturer's" Windows installation can bring in a lot of unwanted software, and I normally will install from plain Windows disks instead, to avoid this.

I would normally aim to keep a hard-disk not more than about 75% full.

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

Re: not yet perfect, but...

Ulrich G. Kliegis
 

David,
I love this physicist's approach, do we see what we think to see? Oh well.

Just to check, you /do/ have a tmp_directory entry in your recv.ini:

_____________________________________
[parameters]
tmp_directory=temp
_____________________________________

pointing to the same partition as all the other receive directories?
How could this box run for years without the tmp definition in the parameters
section - don't ask me why, when, how, this recv.ini file was ported from
installation to installation... At least, there was no tmp_directory entry.

Now, as in my special (really that special?) setup where I want metop and
MSG data to be on different disks (having the least possible data
movements and maximized storage space in mind), how do I achieve that? I
have two target partitions, but the tmp obviously has to be on only one of
them. If that is the case, then the final files will be composed on only one
partition but will be shifted to the other later on.

Alternatively, I could bring both together now on a single terabyte or larger
disk. What has more advantages?

This is the content of the present recv.ini file, and note that I added the tmp
pointer only minutes ago, being aware that it is only 21, half the truth... still
reflected in the missed packets rate.

[recv.ini]
# recv.ini - TelliNet+TelliCast+TelliVision: central Receiver Configuration File

# additional files: see license.ini, recv-channels.ini (optional)
# for more information on file format use help menu in Tellicast shell
#
# 2-4-3 10-10-2005
#


[recipient]
user_name=UlrichKliegis
user_key_crypt= xxxxxxxxxxxxxxxx


[shell]
login=none
port=2517
refresh=3

[watchdog]
#error_script=none./error.sh
#error_script_cause_announcement=30

[logging]
log_file_size=1000000
log_file_number=2
log_level=quiet

[locations]
file_database_directory=R:&#92;receiving&#92;tmp
log_file=>>recv.log
license_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;license.ini
channels_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;recv-channels.ini

[announcement_channel]
address=224.223.222.223:4711
name=TSL Announcement Channel

[parameters]
interface_address=192.168.238.238
file_database_size=325000000
#file_delivery_counter=50
file_delivery_speed=50000000
temp_directory=E:&#92;receiving&#92;tmp
# the previous line added 2011-03-06 - or should this point to R: too?


[EOF]

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



[EUMETSAT Data Channel 1]
# Section per channel or channel group identified by
# channel name (wildcard "*" allowed at end of name)

#priority=500
# priority: priority of this channel/channel group reception
# in case reception would case reception bandwidth sum
# to exceed "recv.ini [parameters] total_bandwidth"
# 0=highest; 1000=lowest
# (default: 500=medium priority)

target_directory=F:&#92;received
# target_directory: directory for received files.
# The target_directory name is relative to the current
# working
# directory.
# (default: ./received)

# allow_execute=1
# allow_execute: 1=allow execution of programs/scripts after job
# reception if specified within the sender job file
# (default: 0=not allowed)

temp_directory=F:&#92;receiving&#92;tmp
# temp_directory: If this parameter is given tqrecv 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.
# (default: undefined=off
# but default value may be redefined in recv.ini)

[EUMETSAT Data Channel 2]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp


[EUMETSAT Data Channel 3]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 4]


target_directory=F:&#92;received&#92;Data Channel 4

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 5]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 6]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[Americas-CH1]

target_directory=F:&#92;Americas-CH1

temp_directory=F:&#92;receiving&#92;tmp

[EPS-1]

target_directory=E:&#92;EPS&#92;EPS-1

temp_directory=E:&#92;receiving&#92;tmp

[EPS-2]

target_directory=E:&#92;EPS&#92;EPS-2

temp_directory=E:&#92;receiving&#92;tmp

[EPS-3]

target_directory=E:&#92;EPS&#92;EPS-3

temp_directory=E:&#92;receiving&#92;tmp

[EPS-4]

target_directory=E:&#92;EPS&#92;EPS-4

temp_directory=E:&#92;receiving&#92;tmp

[EPS-5]

target_directory=E:&#92;EPS&#92;EPS-5

temp_directory=E:&#92;receiving&#92;tmp

[EPS-6]

target_directory=E:&#92;EPS&#92;EPS-6

temp_directory=E:&#92;receiving&#92;tmp

[EPS-7]

target_directory=E:&#92;EPS&#92;EPS-7

temp_directory=E:&#92;receiving&#92;tmp

[EPS-8]

target_directory=E:&#92;EPS&#92;EPS-8

temp_directory=E:&#92;receiving&#92;tmp

[EPS-9]

target_directory=E:&#92;EPS&#92;EPS-9

temp_directory=E:&#92;receiving&#92;tmp

[EPS-10]

target_directory=E:&#92;EPS&#92;EPS-10

temp_directory=E:&#92;receiving&#92;tmp

[EPS-11]

target_directory=E:&#92;EPS&#92;EPS-11

temp_directory=E:&#92;receiving&#92;tmp

[EPS-12]

target_directory=E:&#92;EPS&#92;EPS-12

temp_directory=E:&#92;receiving&#92;tmp

[EPS-13]

target_directory=E:&#92;EPS&#92;EPS-13

temp_directory=E:&#92;receiving&#92;tmp

[EPS-14]

target_directory=E:&#92;EPS&#92;EPS-14

temp_directory=E:&#92;receiving&#92;tmp

[EPS-15]

target_directory=E:&#92;EPS&#92;EPS-15

temp_directory=E:&#92;receiving&#92;tmp

[EPS-16]

target_directory=E:&#92;EPS&#92;EPS-16

temp_directory=E:&#92;receiving&#92;tmp

[EPS-17]

target_directory=E:&#92;EPS&#92;EPS-17

temp_directory=E:&#92;receiving&#92;tmp

[EPS-18]

target_directory=E:&#92;EPS&#92;EPS-18

temp_directory=E:&#92;receiving&#92;tmp

[DWDSAT]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[SAF-Europe]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EOF]

What I thought about more than once is to draft a graphical description of
the data path - describing the various instances where the data pass
through and what happens where... Kind of a workflow map.

Again and again, I am desoriented by the various receiving directories...

Cheers, and thanks in advance for a new re-railing...

U.

Re: not yet perfect, but...

Alan Banks <alan@...>
 

Hi Ulrich,
in my system Tellicast is on its own drive 'D'.
The tmp file is in the BusinessTV-IP folder and this is my Recv-channels.ini file


tmp_directory=tmp

[Info-Channel-1]
target_directory=D:&#92;dailylog

[Info-Channel-2]
target_directory=D:&#92;dailylog

[WWW-Channel]
target_directory=D:&#92;www&#92;eumetsat

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

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

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

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

[EUMETSAT Data Channel 5]
target_directory=D:&#92;received-56

#[EUMETSAT Data Channel 6]
#target_directory=D:&#92;received-56

[EUMETSAT Data Channel 11]
target_directory=D:&#92;received

[EUMETSAT Data Channel 12]
target_directory=D:&#92;received

#[SAF-Europe]
#target_directory=D:&#92;received

#[SAF Europe]
#target_directory=D:&#92;received

[EPS-10]
target_directory=D:&#92;EPSreceived

#[EPS-4]
#target_directory=D:&#92;EPSreceived&#92;EPS4

#[EPS-13]
#target_directory=D:&#92;EPSreceived&#92;EPS13

[EPS-15]
target_directory=D:&#92;EPSreceived&#92;EPS15

#[EPS-16]
#target_directory=D:&#92;EPSreceived&#92;EPS16

#[EPS-17]
#target_directory=D:&#92;EPSreceived&#92;EPS17

[EPS-18]
target_directory=D:&#92;EPSreceived&#92;EPS18

[EPS-19]
target_directory=D:&#92;EPSreceived&#92;EPS19

Cheers

Alan

On 06/03/2011 14:16, Ulrich G. Kliegis wrote:

[recv.ini]
# recv.ini - TelliNet+TelliCast+TelliVision: central Receiver Configuration File

# additional files: see license.ini, recv-channels.ini (optional)
# for more information on file format use help menu in Tellicast shell
#
# 2-4-3 10-10-2005
#


[recipient]
user_name=UlrichKliegis
user_key_crypt= xxxxxxxxxxxxxxxx


[shell]
login=none
port=2517
refresh=3

[watchdog]
#error_script=none./error.sh
#error_script_cause_announcement=30

[logging]
log_file_size=1000000
log_file_number=2
log_level=quiet

[locations]
file_database_directory=R:&#92;receiving&#92;tmp
log_file=>>recv.log
license_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;license.ini
channels_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;recv-channels.ini

[announcement_channel]
address=224.223.222.223:4711
name=TSL Announcement Channel

[parameters]
interface_address=192.168.238.238
file_database_size=325000000
#file_delivery_counter=50
file_delivery_speed=50000000
temp_directory=E:&#92;receiving&#92;tmp
# the previous line added 2011-03-06 - or should this point to R: too?


[EOF]

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



[EUMETSAT Data Channel 1]
# Section per channel or channel group identified by
# channel name (wildcard "*" allowed at end of name)

#priority=500
# priority: priority of this channel/channel group reception
# in case reception would case reception bandwidth sum
# to exceed "recv.ini [parameters] total_bandwidth"
# 0=highest; 1000=lowest
# (default: 500=medium priority)

target_directory=F:&#92;received
# target_directory: directory for received files.
# The target_directory name is relative to the current
# working
# directory.
# (default: ./received)

# allow_execute=1
# allow_execute: 1=allow execution of programs/scripts after job
# reception if specified within the sender job file
# (default: 0=not allowed)

temp_directory=F:&#92;receiving&#92;tmp
# temp_directory: If this parameter is given tqrecv 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.
# (default: undefined=off
# but default value may be redefined in recv.ini)

[EUMETSAT Data Channel 2]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp


[EUMETSAT Data Channel 3]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 4]


target_directory=F:&#92;received&#92;Data Channel 4

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 5]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 6]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[Americas-CH1]

target_directory=F:&#92;Americas-CH1

temp_directory=F:&#92;receiving&#92;tmp

[EPS-1]

target_directory=E:&#92;EPS&#92;EPS-1

temp_directory=E:&#92;receiving&#92;tmp

[EPS-2]

target_directory=E:&#92;EPS&#92;EPS-2

temp_directory=E:&#92;receiving&#92;tmp

[EPS-3]

target_directory=E:&#92;EPS&#92;EPS-3

temp_directory=E:&#92;receiving&#92;tmp

[EPS-4]

target_directory=E:&#92;EPS&#92;EPS-4

temp_directory=E:&#92;receiving&#92;tmp

[EPS-5]

target_directory=E:&#92;EPS&#92;EPS-5

temp_directory=E:&#92;receiving&#92;tmp

[EPS-6]

target_directory=E:&#92;EPS&#92;EPS-6

temp_directory=E:&#92;receiving&#92;tmp

[EPS-7]

target_directory=E:&#92;EPS&#92;EPS-7

temp_directory=E:&#92;receiving&#92;tmp

[EPS-8]

target_directory=E:&#92;EPS&#92;EPS-8

temp_directory=E:&#92;receiving&#92;tmp

[EPS-9]

target_directory=E:&#92;EPS&#92;EPS-9

temp_directory=E:&#92;receiving&#92;tmp

[EPS-10]

target_directory=E:&#92;EPS&#92;EPS-10

temp_directory=E:&#92;receiving&#92;tmp

[EPS-11]

target_directory=E:&#92;EPS&#92;EPS-11

temp_directory=E:&#92;receiving&#92;tmp

[EPS-12]

target_directory=E:&#92;EPS&#92;EPS-12

temp_directory=E:&#92;receiving&#92;tmp

[EPS-13]

target_directory=E:&#92;EPS&#92;EPS-13

temp_directory=E:&#92;receiving&#92;tmp

[EPS-14]

target_directory=E:&#92;EPS&#92;EPS-14

temp_directory=E:&#92;receiving&#92;tmp

[EPS-15]

target_directory=E:&#92;EPS&#92;EPS-15

temp_directory=E:&#92;receiving&#92;tmp

[EPS-16]

target_directory=E:&#92;EPS&#92;EPS-16

temp_directory=E:&#92;receiving&#92;tmp

[EPS-17]

target_directory=E:&#92;EPS&#92;EPS-17

temp_directory=E:&#92;receiving&#92;tmp

[EPS-18]

target_directory=E:&#92;EPS&#92;EPS-18

temp_directory=E:&#92;receiving&#92;tmp

[DWDSAT]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[SAF-Europe]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EOF]

What I thought about more than once is to draft a graphical description of
the data path - describing the various instances where the data pass
through and what happens where... Kind of a workflow map.

Again and again, I am desoriented by the various receiving directories...

Cheers, and thanks in advance for a new re-railing...

U.



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

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




Re: not yet perfect, but...

Alan Sewards
 

Ulrich,
As far as I can see from your recv.ini and recv-channels.ini, you have got the correct tmp folders in recv-channels.ini and the entry under parameters in recv.ini is not necessary.

Best regards - Alan S

On 06/03/2011 3:16 PM, Ulrich G. Kliegis wrote:

David,
I love this physicist's approach, do we see what we think to see? Oh well.

> Just to check, you /do/ have a tmp_directory entry in your recv.ini:
>
> _____________________________________
> [parameters]
> tmp_directory=temp
> _____________________________________
>
> pointing to the same partition as all the other receive directories?

How could this box run for years without the tmp definition in the
parameters
section - don't ask me why, when, how, this recv.ini file was ported from
installation to installation... At least, there was no tmp_directory entry.

Now, as in my special (really that special?) setup where I want metop and
MSG data to be on different disks (having the least possible data
movements and maximized storage space in mind), how do I achieve that? I
have two target partitions, but the tmp obviously has to be on only one of
them. If that is the case, then the final files will be composed on only
one
partition but will be shifted to the other later on.

Alternatively, I could bring both together now on a single terabyte or
larger
disk. What has more advantages?

This is the content of the present recv.ini file, and note that I added
the tmp
pointer only minutes ago, being aware that it is only 21, half the
truth... still
reflected in the missed packets rate.

[recv.ini]
# recv.ini - TelliNet+TelliCast+TelliVision: central Receiver
Configuration File

# additional files: see license.ini, recv-channels.ini (optional)
# for more information on file format use help menu in Tellicast shell
#
# 2-4-3 10-10-2005
#

[recipient]
user_name=UlrichKliegis
user_key_crypt= xxxxxxxxxxxxxxxx

[shell]
login=none
port=2517
refresh=3

[watchdog]
#error_script=none./error.sh
#error_script_cause_announcement=30

[logging]
log_file_size=1000000
log_file_number=2
log_level=quiet

[locations]
file_database_directory=R:&#92;receiving&#92;tmp
log_file=>>recv.log
license_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;license.ini
channels_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;recv-channels.ini

[announcement_channel]
address=224.223.222.223:4711
name=TSL Announcement Channel

[parameters]
interface_address=192.168.238.238
file_database_size=325000000
#file_delivery_counter=50
file_delivery_speed=50000000
temp_directory=E:&#92;receiving&#92;tmp
# the previous line added 2011-03-06 - or should this point to R: too?

[EOF]

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

[EUMETSAT Data Channel 1]
# Section per channel or channel group identified by
# channel name (wildcard "*" allowed at end of name)

#priority=500
# priority: priority of this channel/channel group reception
# in case reception would case reception bandwidth sum
# to exceed "recv.ini [parameters] total_bandwidth"
# 0=highest; 1000=lowest
# (default: 500=medium priority)

target_directory=F:&#92;received
# target_directory: directory for received files.
# The target_directory name is relative to the current
# working
# directory.
# (default: ./received)

# allow_execute=1
# allow_execute: 1=allow execution of programs/scripts after job
# reception if specified within the sender job file
# (default: 0=not allowed)

temp_directory=F:&#92;receiving&#92;tmp
# temp_directory: If this parameter is given tqrecv 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.
# (default: undefined=off
# but default value may be redefined in recv.ini)

[EUMETSAT Data Channel 2]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 3]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 4]

target_directory=F:&#92;received&#92;Data Channel 4

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 5]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 6]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[Americas-CH1]

target_directory=F:&#92;Americas-CH1

temp_directory=F:&#92;receiving&#92;tmp

[EPS-1]

target_directory=E:&#92;EPS&#92;EPS-1

temp_directory=E:&#92;receiving&#92;tmp

[EPS-2]

target_directory=E:&#92;EPS&#92;EPS-2

temp_directory=E:&#92;receiving&#92;tmp

[EPS-3]

target_directory=E:&#92;EPS&#92;EPS-3

temp_directory=E:&#92;receiving&#92;tmp

[EPS-4]

target_directory=E:&#92;EPS&#92;EPS-4

temp_directory=E:&#92;receiving&#92;tmp

[EPS-5]

target_directory=E:&#92;EPS&#92;EPS-5

temp_directory=E:&#92;receiving&#92;tmp

[EPS-6]

target_directory=E:&#92;EPS&#92;EPS-6

temp_directory=E:&#92;receiving&#92;tmp

[EPS-7]

target_directory=E:&#92;EPS&#92;EPS-7

temp_directory=E:&#92;receiving&#92;tmp

[EPS-8]

target_directory=E:&#92;EPS&#92;EPS-8

temp_directory=E:&#92;receiving&#92;tmp

[EPS-9]

target_directory=E:&#92;EPS&#92;EPS-9

temp_directory=E:&#92;receiving&#92;tmp

[EPS-10]

target_directory=E:&#92;EPS&#92;EPS-10

temp_directory=E:&#92;receiving&#92;tmp

[EPS-11]

target_directory=E:&#92;EPS&#92;EPS-11

temp_directory=E:&#92;receiving&#92;tmp

[EPS-12]

target_directory=E:&#92;EPS&#92;EPS-12

temp_directory=E:&#92;receiving&#92;tmp

[EPS-13]

target_directory=E:&#92;EPS&#92;EPS-13

temp_directory=E:&#92;receiving&#92;tmp

[EPS-14]

target_directory=E:&#92;EPS&#92;EPS-14

temp_directory=E:&#92;receiving&#92;tmp

[EPS-15]

target_directory=E:&#92;EPS&#92;EPS-15

temp_directory=E:&#92;receiving&#92;tmp

[EPS-16]

target_directory=E:&#92;EPS&#92;EPS-16

temp_directory=E:&#92;receiving&#92;tmp

[EPS-17]

target_directory=E:&#92;EPS&#92;EPS-17

temp_directory=E:&#92;receiving&#92;tmp

[EPS-18]

target_directory=E:&#92;EPS&#92;EPS-18

temp_directory=E:&#92;receiving&#92;tmp

[DWDSAT]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[SAF-Europe]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EOF]

What I thought about more than once is to draft a graphical description of
the data path - describing the various instances where the data pass
through and what happens where... Kind of a workflow map.

Again and again, I am desoriented by the various receiving directories...

Cheers, and thanks in advance for a new re-railing...

U.

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

Re: not yet perfect, but...

James Brown
 

I don't suppose the issue of an incompatible motherboard is raising it's head here. It's just that I've never seen such a pattern of losses before.

Cheers
James
--
James Brown

Re: not yet perfect, but...

Ulrich G. Kliegis
 

I'm wondering whether the
cause of the loss is something not even associated with the PC, such
as some radio-frequency interference getting into the IF channel.
Perhaps something from the port at Kiel, just across from you? I
expect you have already made sure that the connectors are not loose.
David,
at the same time that I re-adjusted the EB9 LNB, I now also re-positioned
the LNBs for ASTRA and Hotbird. Although the receiver shows 98% signal
strength there and 92% quality (whatever that means) there are
someartifacts in the video image. But that may still be due to some position
error. I'll have to investigate that. The LNBs are phasically and galvanically
totaly separate for TV and Eumetcast, though. Just the cable shields meet
at some distinct earthing point.

I then suspected noise from a DECT phone nearby the dish. Switching it off
(completely) did not show any effect.

The dish does not point to the harboujr at all, and there is nothing in the
heighbourhood that could cause any interference.

At the moment, I feel a bit stranded.

Cheers,
U.

Re: not yet perfect, but...

ernstlobsiger
 

--- In MSG-1@..., "Ulrich G. Kliegis" <Ulrich.Kliegis@...> wrote:


David,
I love this physicist's approach, do we see what we think to see? Oh well.

Just to check, you /do/ have a tmp_directory entry in your recv.ini:

_____________________________________
[parameters]
tmp_directory=temp
_____________________________________

pointing to the same partition as all the other receive directories?
How could this box run for years without the tmp definition in the parameters
section - don't ask me why, when, how, this recv.ini file was ported from
installation to installation... At least, there was no tmp_directory entry.

Now, as in my special (really that special?) setup where I want metop and
MSG data to be on different disks (having the least possible data
movements and maximized storage space in mind), how do I achieve that? I
have two target partitions, but the tmp obviously has to be on only one of
them. If that is the case, then the final files will be composed on only one
partition but will be shifted to the other later on.

Alternatively, I could bring both together now on a single terabyte or larger
disk. What has more advantages?

This is the content of the present recv.ini file, and note that I added the tmp
pointer only minutes ago, being aware that it is only 21, half the truth... still
reflected in the missed packets rate.

[recv.ini]
# recv.ini - TelliNet+TelliCast+TelliVision: central Receiver Configuration File

# additional files: see license.ini, recv-channels.ini (optional)
# for more information on file format use help menu in Tellicast shell
#
# 2-4-3 10-10-2005
#


[recipient]
user_name=UlrichKliegis
user_key_crypt= xxxxxxxxxxxxxxxx


[shell]
login=none
port=2517
refresh=3

[watchdog]
#error_script=none./error.sh
#error_script_cause_announcement=30

[logging]
log_file_size=1000000
log_file_number=2
log_level=quiet

[locations]
file_database_directory=R:&#92;receiving&#92;tmp
log_file=>>recv.log
license_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;license.ini
channels_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;recv-channels.ini

[announcement_channel]
address=224.223.222.223:4711
name=TSL Announcement Channel

[parameters]
interface_address=192.168.238.238
file_database_size=325000000
#file_delivery_counter=50
file_delivery_speed=50000000
temp_directory=E:&#92;receiving&#92;tmp
# the previous line added 2011-03-06 - or should this point to R: too?


[EOF]

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



[EUMETSAT Data Channel 1]
# Section per channel or channel group identified by
# channel name (wildcard "*" allowed at end of name)

#priority=500
# priority: priority of this channel/channel group reception
# in case reception would case reception bandwidth sum
# to exceed "recv.ini [parameters] total_bandwidth"
# 0=highest; 1000=lowest
# (default: 500=medium priority)

target_directory=F:&#92;received
# target_directory: directory for received files.
# The target_directory name is relative to the current
# working
# directory.
# (default: ./received)

# allow_execute=1
# allow_execute: 1=allow execution of programs/scripts after job
# reception if specified within the sender job file
# (default: 0=not allowed)

temp_directory=F:&#92;receiving&#92;tmp
# temp_directory: If this parameter is given tqrecv 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.
# (default: undefined=off
# but default value may be redefined in recv.ini)

[EUMETSAT Data Channel 2]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp


[EUMETSAT Data Channel 3]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 4]


target_directory=F:&#92;received&#92;Data Channel 4

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 5]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 6]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[Americas-CH1]

target_directory=F:&#92;Americas-CH1

temp_directory=F:&#92;receiving&#92;tmp

[EPS-1]

target_directory=E:&#92;EPS&#92;EPS-1

temp_directory=E:&#92;receiving&#92;tmp

[EPS-2]

target_directory=E:&#92;EPS&#92;EPS-2

temp_directory=E:&#92;receiving&#92;tmp

[EPS-3]

target_directory=E:&#92;EPS&#92;EPS-3

temp_directory=E:&#92;receiving&#92;tmp

[EPS-4]

target_directory=E:&#92;EPS&#92;EPS-4

temp_directory=E:&#92;receiving&#92;tmp

[EPS-5]

target_directory=E:&#92;EPS&#92;EPS-5

temp_directory=E:&#92;receiving&#92;tmp

[EPS-6]

target_directory=E:&#92;EPS&#92;EPS-6

temp_directory=E:&#92;receiving&#92;tmp

[EPS-7]

target_directory=E:&#92;EPS&#92;EPS-7

temp_directory=E:&#92;receiving&#92;tmp

[EPS-8]

target_directory=E:&#92;EPS&#92;EPS-8

temp_directory=E:&#92;receiving&#92;tmp

[EPS-9]

target_directory=E:&#92;EPS&#92;EPS-9

temp_directory=E:&#92;receiving&#92;tmp

[EPS-10]

target_directory=E:&#92;EPS&#92;EPS-10

temp_directory=E:&#92;receiving&#92;tmp

[EPS-11]

target_directory=E:&#92;EPS&#92;EPS-11

temp_directory=E:&#92;receiving&#92;tmp

[EPS-12]

target_directory=E:&#92;EPS&#92;EPS-12

temp_directory=E:&#92;receiving&#92;tmp

[EPS-13]

target_directory=E:&#92;EPS&#92;EPS-13

temp_directory=E:&#92;receiving&#92;tmp

[EPS-14]

target_directory=E:&#92;EPS&#92;EPS-14

temp_directory=E:&#92;receiving&#92;tmp

[EPS-15]

target_directory=E:&#92;EPS&#92;EPS-15

temp_directory=E:&#92;receiving&#92;tmp

[EPS-16]

target_directory=E:&#92;EPS&#92;EPS-16

temp_directory=E:&#92;receiving&#92;tmp

[EPS-17]

target_directory=E:&#92;EPS&#92;EPS-17

temp_directory=E:&#92;receiving&#92;tmp

[EPS-18]

target_directory=E:&#92;EPS&#92;EPS-18

temp_directory=E:&#92;receiving&#92;tmp

[DWDSAT]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[SAF-Europe]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EOF]

What I thought about more than once is to draft a graphical description of
the data path - describing the various instances where the data pass
through and what happens where... Kind of a workflow map.

Again and again, I am desoriented by the various receiving directories...

Cheers, and thanks in advance for a new re-railing...

U.
Hello Ullrich

I am far from my (Linux!) reception station and this is purely out of my head. Also the thread is pretty long by now. So for what it is worth:

a)
I think it should read "tmp_directory" instead of "temp_directory" in recv-channels.ini. Not sure the Tellicast Client understands both ...
b)
You have a very high file_delivery_speed in recv.ini. Default is 10000000 and I have never set it above 20000000 (on my old PCs).
c)
I don't understand the temp_directory under [parameters] in recv.ini.

Cheers
Ernst

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: MSG-1@...
Von: "ernstlobsiger" <ernst.lobsiger@...>
Datum: Sun, 06 Mar 2011 16:13:27 -0000
Betreff: [MSG-1] Re: not yet perfect, but...
Antwort an: MSG-1@...

I think it should read "tmp_directory" instead of "temp_directory" in
recv-channels.ini.
Ernst,
danke für den Kommentar, but temp... seems to be the pregiven spelling in
the original sample, as I have it here.

Reducing the max rate to 20E6 did not change anything.

I also commented out EPS 5 temporarily - (almost) no effect. at least, in this
phase (about 15:50 UT) the rate of not-recovered packets grew.
Switching off a Dexatrek USB receiver (same as the world box) being
connected to a different PC two meters (about 6.7 ft) away, - no effect (I
suspected the open output socket, but it wasn't the culprit yet.) Connecting
the LNB cable shielding to a solid ground - nothing.

Ernst, the (temporary) temp_directory in recv.ini was derived from David's
question.

Alan, the board "looks good", no bad elcaps.

I feel a bit embarassed that just mine (out of millions of PCs running David's
software) makes such troubles. Hadn't I installed MRTG, everything would
look fine... :)

Cheers,
U.

Re: not yet perfect, but...

David J Taylor
 

David,
I love this physicist's approach, do we see what we think to see? Oh well.

Just to check, you /do/ have a tmp_directory entry in your recv.ini:

_____________________________________
[parameters]
tmp_directory=temp
_____________________________________

pointing to the same partition as all the other receive directories?
How could this box run for years without the tmp definition in the parameters
section - don't ask me why, when, how, this recv.ini file was ported from
installation to installation... At least, there was no tmp_directory entry.
Yes, it may be that you need to add this entry by hand.

Now, as in my special (really that special?) setup where I want metop and
MSG data to be on different disks (having the least possible data
movements and maximized storage space in mind), how do I achieve that? I
have two target partitions, but the tmp obviously has to be on only one of
them. If that is the case, then the final files will be composed on only one
partition but will be shifted to the other later on.

Alternatively, I could bring both together now on a single terabyte or larger
disk. What has more advantages?

This is the content of the present recv.ini file, and note that I added the tmp
pointer only minutes ago, being aware that it is only 21, half the truth... still
reflected in the missed packets rate.
[]
[EUMETSAT Data Channel 2]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp
What I thought about more than once is to draft a graphical description of
the data path - describing the various instances where the data pass
through and what happens where... Kind of a workflow map.

Again and again, I am desoriented by the various receiving directories...

Cheers, and thanks in advance for a new re-railing...

U.
Ulrich, according to the 2.2.4a TelliCast Help information (viewed via the HTML shell), you need

tmp_directory=<directory>

So, for example:

_____________________________________
[EUMETSAT Data Channel 2]
target_directory=F:&#92;received
tmp_directory=F:&#92;receiving&#92;tmp
_____________________________________


You are correct that with the data on different disks, one common entry in recv.ini would not provide the best solution. By the way: I hope that is two different physical disks, otherwise you will have the disk head madly dashing between the two partitions on the one physical disk! Far better to have all the received data going to one partition, and the processed images on a /different/ physical disk. Can you not hear the noise the disk is making? <G> The hard disk of my receive-only PC is just 80GB.

Talking of recv.ini, it happens that mine has:

_____________________________________
[parameters]
file_delivery_speed=20000000
_____________________________________


So, broadly, I would have one large and one small HD, ~100GB for just the &#92;received&#92; directory tree, and 1-2TB for the processed and archived files. Topic for discussion - which HD should have the OS? I might suggest the small HD, but it would likely depend what else was on the system.

Thanks to the others for their input as well - Arne/Ernst's log file analysis program has help uncover anomalies in other areas. I'm sure that with Linux you also need to work out the data flow carefully for best results.

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