I have a problem with running tellicast on a Lubuntu 18.04 system.

This is on a dual-boot PC (32-bits); the other OS on this PC is Ubuntu 16.04 which works fine with exactly the same Tellicast-scripts. (So same hardware, including receiver.)

There is one difference: the logfile on Lubuntu gives following warning (not on Ubuntu):

VRB:2023-01-17 09:16:47.014:Connecting to announcement channel `TSL Announcement Channel', address 224.223.222.223:4711 (announcement channel)
WRN:2023-01-17 09:16:47.047:Receive buffer size for socket could not be adapted to requested value (4000000 > 163840). This could cause reception problems. Check system limits!

There is no "Receiver active" message.

Commands '/proc/sys/net/ipv4/tcp_rmem' gives:

4096    131072    6138048

and '/proc/sys/net/ipv4/tcp_wmem' gives:

4096    16384    4194304

which is about the same for both OS's.

I don't know if this warning has something to do with the problem. Firewall off, Wireshark shows data coming in, including the TCL announcement channel, but TCL announcement on http://127.0.0.1:8100/ keeps on showing 'Connecting' instead of 'Active'.

Any idea what's causing this problem, and how to solve it? Extensively searching on Internet didn't show a solution.

Cheers,

Rob.

I have a problem with running tellicast on a Lubuntu 18.04 system.

This is on a dual-boot PC (32-bits); the other OS on this PC is Ubuntu 16.04 which works fine with exactly the same Tellicast-scripts. (So same hardware, including receiver.)

There is one difference: the logfile on Lubuntu gives following warning (not on Ubuntu):

VRB:2023-01-17 09:16:47.014:Connecting to announcement channel `TSL Announcement Channel', address 224.223.222.223:4711 (announcement channel)
WRN:2023-01-17 09:16:47.047:Receive buffer size for socket could not be adapted to requested value (4000000 > 163840). This could cause reception problems. Check system limits!

There is no "Receiver active" message.

Commands '/proc/sys/net/ipv4/tcp_rmem' gives:

4096    131072    6138048

and '/proc/sys/net/ipv4/tcp_wmem' gives:

4096    16384    4194304

which is about the same for both OS's.

I don't know if this warning has something to do with the problem. Firewall off, Wireshark shows data coming in, including the TCL announcement channel, but TCL announcement on http://127.0.0.1:8100/ keeps on showing 'Connecting' instead of 'Active'.

Any idea what's causing this problem, and how to solve it? Extensively searching on Internet didn't show a solution.

Cheers,

Rob.

I have a problem with running tellicast on a Lubuntu 18.04 system.

This is on a dual-boot PC (32-bits); the other OS on this PC is Ubuntu 16.04 which works fine with exactly the same Tellicast-scripts. (So same hardware, including receiver.)

There is one difference: the logfile on Lubuntu gives following warning (not on Ubuntu):

VRB:2023-01-17 09:16:47.014:Connecting to announcement channel `TSL Announcement Channel', address 224.223.222.223:4711 (announcement channel)
WRN:2023-01-17 09:16:47.047:Receive buffer size for socket could not be adapted to requested value (4000000 > 163840). This could cause reception problems. Check system limits!

There is no "Receiver active" message.

Commands '/proc/sys/net/ipv4/tcp_rmem' gives:

4096    131072    6138048

and '/proc/sys/net/ipv4/tcp_wmem' gives:

4096    16384    4194304

which is about the same for both OS's.

I don't know if this warning has something to do with the problem. Firewall off, Wireshark shows data coming in, including the TCL announcement channel, but TCL announcement on http://127.0.0.1:8100/ keeps on showing 'Connecting' instead of 'Active'.

Any idea what's causing this problem, and how to solve it? Extensively searching on Internet didn't show a solution.

Cheers,

Rob.

Rob,

do you have the EUMETSAT added entries in /etc/sysctl.conf?

Especially:
...
# Controls the read buffer sizes (for the Tellicast client)
net.core.rmem_max=10000000
# Controls the write buffer sizes (for the Tellicast client)
net.core.wmem_max=10000000
...

Ernst

Ernst,

Yes, it's there, and sysctl.conf is exactly the same as for Ubuntu 16.04, which works.

(Btw, sorry for sending my previous mail 3x; some hick-up in mail delivery...)

Rob.

--

Hm, very strange. Now and then Tellicast on Lubuntu works.

Start PC, tellicast doesn't work.
Reboot, tellicast works fine.
Reboot again, and it doesn't work.
Try a days later, it doesn't work.
Try some days later, it works again.

And I didn't change a bit on this PC. Ghosts floating around here...

What will happen after next reboot?

BrrrRob.

Rob,

what DVB-S2 receiver type do you use?

Ernst

Ernst,

I use a SR1.
Receiving bas+HVS-1 works fine now, since yesterday, no reboot done.

Rob.