You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by in...@bureau-de-poste.net on 2020/10/10 05:31:21 UTC
TCP socket error: Connection reset by peer 195.54.161.237:16836 ( ?
Saint Petersburg IP ?)
Hello, We are getting a tcp connection error in coturn that is from
a Saint Petersburg IP address. What is this?:
root@server1:~# service coturn status
● coturn.service - coTURN STUN/TURN Server
Loaded: loaded (/lib/systemd/system/coturn.service; enabled;
vendor preset: enabled)
Active: active (running) since Sat 2020-09-26 16:21:41 CEST; 1
weeks 6 days ago
Docs: man:coturn(1)
man:turnadmin(1)
man:turnserver(1)
Process: 2052 ExecStart=/usr/bin/turnserver --daemon -c
/etc/turnserver.conf --pidfile /run/turnserver/turnserver.pid
(code=exited, status=0/SUCCESS)
Process: 2054 ExecStartPost=/bin/sleep 2 (code=exited, status=0/SUCCESS)
Main PID: 2053 (turnserver)
Tasks: 15 (limit: 4915)
Memory: 20.9M
CGroup: /system.slice/coturn.service
└─2053 /usr/bin/turnserver --daemon -c
/etc/turnserver.conf --pidfile /run/turnserver/turnserver.pid
Oct 09 02:04:58 server1 turnserver[2053]: 1071799: session
007000000000000469: TCP socket error: Connection reset by peer
195.54.161.237:16836
Warning: Journal has been rotated since unit was started. Log output
is incomplete or unavailable.
Best,
Ed
Re: TCP socket error: Connection reset by peer 195.54.161.237:16836 (
? Saint Petersburg IP ?)
Posted by Maxim Solodovnik <so...@gmail.com>.
AFAIK "Connection reset by peer" means the connection was closed by the
user or by the network error
why do you think this is a problem?
On Sat, 10 Oct 2020 at 12:31, <in...@bureau-de-poste.net> wrote:
> Hello, We are getting a tcp connection error in coturn that is from a
> Saint Petersburg IP address. What is this?:
>
> root@server1:~# service coturn status
> ● coturn.service - coTURN STUN/TURN Server
> Loaded: loaded (/lib/systemd/system/coturn.service; enabled; vendor
> preset: enabled)
> Active: active (running) since Sat 2020-09-26 16:21:41 CEST; 1 weeks 6
> days ago
> Docs: man:coturn(1)
> man:turnadmin(1)
> man:turnserver(1)
> Process: 2052 ExecStart=/usr/bin/turnserver --daemon -c
> /etc/turnserver.conf --pidfile /run/turnserver/turnserver.pid (code=exited,
> status=0/SUCCESS)
> Process: 2054 ExecStartPost=/bin/sleep 2 (code=exited, status=0/SUCCESS)
> Main PID: 2053 (turnserver)
> Tasks: 15 (limit: 4915)
> Memory: 20.9M
> CGroup: /system.slice/coturn.service
> └─2053 /usr/bin/turnserver --daemon -c /etc/turnserver.conf
> --pidfile /run/turnserver/turnserver.pid
>
> Oct 09 02:04:58 server1 turnserver[2053]: 1071799: session
> 007000000000000469: TCP socket error: Connection reset by peer
> 195.54.161.237:16836
> Warning: Journal has been rotated since unit was started. Log output is
> incomplete or unavailable.
>
> Best,
> Ed
>
--
Best regards,
Maxim