Hi all,
First, a belated Happy New Year to everyone!
I've had a report of our VK2RFS-R EchoIRLP node randomly closing
connections, often after 20min or so.
In this case, a club member had connected into the repeater node using his computer/phone Echolink app (not sure which). Apparently it's fine if there is activity on the repeater, but when everything's quiet, it disconnects after a while.
The first obvious thought was the timeout settings, as per a previous question on this group,
"REFLECT_TIMEOUT_VALUE" in '/home/irlp/custom/environment" for conferences/reflectors and the file "/home/irlp/custom/timeoutvalue" for nodes.
I set these to 100min last year, and to check they were still set I
connected to the repeater node myself, from my VK2STG node useing Echolink
on Windows - it stayed connected for over an hour, before I disconnected
it. (with no repeater activity as far as I noticed).
I should say that I have been disconnected myself, almost mid-QSO, previously, but had put it down to an unreliable internet service at my end. I don't have direct access to the RPi, so I'd prefer to have some idea of what to check before I ask the repeater owner for access.
Any thoughts or ideas would be appreciated!
Steven VK2STG
I'd prefer to have some idea of what to check before I ask the repeater owner for access
Where do I find the log?
On Fri, Jan 21, 2022 at 05:25 PM, Steven VK2STG wrote:
Where do I find the log?
I believe it would be /home/irlp/log/messages by default.
Hi all,often after 20min or so.
First, a belated Happy New Year to everyone!
I've had a report of our VK2RFS-R EchoIRLP node randomly closing connections,
In this case, a club member had connected into the repeater node using hiscomputer/phone Echolink app (not sure which). Apparently it's fine if there is activity on the repeater, but when everything's quiet, it disconnects after a while.
The first obvious thought was the timeout settings, as per a previousquestion on this group,
"REFLECT_TIMEOUT_VALUE" in '/home/irlp/custom/environment" for conferences/reflectors and the file "/home/irlp/custom/timeoutvalue" for nodes.to the repeater node myself, from my VK2STG node useing Echolink on Windows - it stayed connected for over an hour, before I disconnected it. (with no repeater activity as far as I noticed).
I set these to 100min last year, and to check they were still set I connected
I should say that I have been disconnected myself, almost mid-QSO,previously, but had put it down to an unreliable internet service at my end.
I don't have direct access to the RPi, so I'd prefer to have some idea ofwhat to check before I ask the repeater owner for access.
Any thoughts or ideas would be appreciated!
Steven VK2STG
Check the value of $ECHO_TIMEOUT_VALUE, which if present, controls the
idle timeout for most Echolink connections. Best to keep it non zero,
so that someone camped on your system doesn't block IRLP connections
more than necessary. Increase it to what suits. The value is in seconds.
On 22/1/22 9:05 am, Steven VK2STG wrote:
Hi all,
First, a belated Happy New Year to everyone!
I've had a report of our VK2RFS-R EchoIRLP node randomly closingconnections, often after 20min or so.
In this case, a club member had connected into the repeater node usinghis computer/phone Echolink app (not sure which). Apparently it's fine if there is activity on the repeater, but when everything's quiet, it disconnects after a while.
The first obvious thought was the timeout settings, as per a previousquestion on this group,
"REFLECT_TIMEOUT_VALUE" in '/home/irlp/custom/environment" for conferences/reflectors and the file "/home/irlp/custom/timeoutvalue" for nodes.connected to the repeater node myself, from my VK2STG node useing Echolink
I set these to 100min last year, and to check they were still set I
on Windows - it stayed connected for over an hour, before I disconnected
it. (with no repeater activity as far as I noticed).
I should say that I have been disconnected myself, almost mid-QSO,previously, but had put it down to an unreliable internet service at my end.
I don't have direct access to the RPi, so I'd prefer to have some ideaof what to check before I ask the repeater owner for access.
Any thoughts or ideas would be appreciated!
Steven VK2STG
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
Thanks Tony, I haven't had a look at things yet, I'll check that one out
too. Where would it be located?
Steven
On Sun, 23 Jan 2022 at 07:30, Tony Langdon <vk3jed@vkradio.com> wrote:
Check the value of $ECHO_TIMEOUT_VALUE, which if present, controls the
idle timeout for most Echolink connections. Best to keep it non zero,
so that someone camped on your system doesn't block IRLP connections
more than necessary. Increase it to what suits. The value is in seconds. >>
On 22/1/22 9:05 am, Steven VK2STG wrote:
Hi all,connections, often after 20min or so.
First, a belated Happy New Year to everyone!
I've had a report of our VK2RFS-R EchoIRLP node randomly closing
In this case, a club member had connected into the repeater node usinghis computer/phone Echolink app (not sure which). Apparently it's fine if
there is activity on the repeater, but when everything's quiet, it
disconnects after a while.
The first obvious thought was the timeout settings, as per a previousquestion on this group,
"REFLECT_TIMEOUT_VALUE" in '/home/irlp/custom/environment" forconnected to the repeater node myself, from my VK2STG node useing Echolink >> on Windows - it stayed connected for over an hour, before I disconnected
conferences/reflectors and the file "/home/irlp/custom/timeoutvalue" for >>> nodes.
I set these to 100min last year, and to check they were still set I
it. (with no repeater activity as far as I noticed).
I should say that I have been disconnected myself, almost mid-QSO,previously, but had put it down to an unreliable internet service at my end. >>> I don't have direct access to the RPi, so I'd prefer to have some idea
of what to check before I ask the repeater owner for access.
--
Any thoughts or ideas would be appreciated!
Steven VK2STG
73 de Tony VK3JED/VK3IRL
http://vkradio.com
/home/EchoIRLP/custom/echo_env (or echo_environment) - I currently don't
have a working EchoIRLP node to check. :)
On 23/1/22 9:09 am, Steven VK2STG wrote:
Thanks Tony, I haven't had a look at things yet, I'll check that one out too. Where would it be located?
Steven
On Sun, 23 Jan 2022 at 07:30, Tony Langdon <vk3jed@vkradio.com> wrote:
seconds.Check the value of $ECHO_TIMEOUT_VALUE, which if present, controls the
idle timeout for most Echolink connections. Best to keep it non zero,
so that someone camped on your system doesn't block IRLP connections
more than necessary. Increase it to what suits. The value is in
if
On 22/1/22 9:05 am, Steven VK2STG wrote:
Hi all,connections, often after 20min or so.
First, a belated Happy New Year to everyone!
I've had a report of our VK2RFS-R EchoIRLP node randomly closing
In this case, a club member had connected into the repeater node usinghis computer/phone Echolink app (not sure which). Apparently it's fine
forthere is activity on the repeater, but when everything's quiet, it
disconnects after a while.
The first obvious thought was the timeout settings, as per a previousquestion on this group,
"REFLECT_TIMEOUT_VALUE" in '/home/irlp/custom/environment" for
conferences/reflectors and the file "/home/irlp/custom/timeoutvalue"
Echolinknodes.connected to the repeater node myself, from my VK2STG node useing
I set these to 100min last year, and to check they were still set I
on Windows - it stayed connected for over an hour, before I disconnected >> it. (with no repeater activity as far as I noticed).
I should say that I have been disconnected myself, almost mid-QSO,previously, but had put it down to an unreliable internet service at my end.
I don't have direct access to the RPi, so I'd prefer to have some ideaof what to check before I ask the repeater owner for access.
--
Any thoughts or ideas would be appreciated!
Steven VK2STG
73 de Tony VK3JED/VK3IRL
http://vkradio.com
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
| Sysop: | deepend |
|---|---|
| Location: | Calgary, Alberta |
| Users: | 253 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 50:24:48 |
| Calls: | 1,647 |
| Files: | 4,010 |
| Messages: | 388,078 |