Hi,

Well, when you restart OpenSIPSall the DB connections will be terminated (killed by OpenSIPS) - and the effect you get on the server side are the logs you see. I agree that OpenSIPS should do a graceful DB conn termination, but this is asimple beautification at this point. Still, we have it on the plan.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 03/01/2018 05:52 PM, xaled wrote:

Hi,

I’m using postgres with virtual_db module and after opensips restarts I’m getting “Connection reset by peer” errors in postgres logs.

The errors don’t not seem to influence the DB connection after restart, but still kind of annoying.

Is there something I could do about it?

2018-03-01 15:41:47.599 CET [14600] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.603 CET [14604] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.603 CET [14590] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.605 CET [14603] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.605 CET [14588] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.606 CET [14607] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.607 CET [14601] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.609 CET [14592] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.610 CET [14606] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.611 CET [14597] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.611 CET [14591] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.612 CET [14595] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.614 CET [14605] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.614 CET [14576] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.616 CET [14585] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.617 CET [14580] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.617 CET [14596] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.619 CET [14594] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.619 CET [14598] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.620 CET [14567] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.620 CET [14593] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.621 CET [14608] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.622 CET [14587] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.623 CET [14574] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.625 CET [14599] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.625 CET [14568] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.626 CET [14602] user@sipapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.627 CET [14566] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.629 CET [14589] user@webapp LOG: could not receive data from client: Connection reset by peer

2018-03-01 15:41:47.630 CET [14565] user@webapp LOG: could not receive data from client: Connection reset by peer

14260 ?        Ss     0:00 postgres: 10/main: checkpointer process

14261 ?        Ss     0:00 postgres: 10/main: writer process

14262 ?        Ss     0:00 postgres: 10/main: wal writer process

14263 ?        Ss     0:00 postgres: 10/main: autovacuum launcher process

14264 ?        Ss     0:00 postgres: 10/main: stats collector process

14265 ? Ss 0:00 postgres: 10/main: bgworker: logical replication launcher

14647 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40684) idle

14648 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40686) idle

14649 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40688) idle

14650 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40690) idle

14656 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40692) idle

14658 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40694) idle

14662 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40696) idle

14663 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40698) idle

14665 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40700) idle

14668 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40702) idle

14671 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40704) idle

14672 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40706) idle

14673 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40708) idle

14674 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40710) idle

14675 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40712) idle

14676 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40714) idle

14677 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40716) idle

14678 ? Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40718) idle

14679 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40720) idle

14680 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40722) idle

14681 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40724) idle

14682 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40726) idle

14683 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40728) idle

14684 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40730) idle

14685 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40732) idle

14686 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40734) idle

14687 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40736) idle

14688 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40738) idle

14689 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40740) idle

14690 ? Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40742) idle

version: opensips 2.3.3 (x86_64/linux)

flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT

ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535

poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.

main.c compiled on  with gcc 6.3.0

PostgreSQL 10.2 (Debian 10.2-1.pgdg90+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 6.3.0-18) 6.3.0 20170516, 64-bit

SET::  i=0 name=set1 mode=FAILOVER

DB:: j=0 name=postgres://user:xxx@127.0.0.1/webapp can=1 may=1 r_rec=0

SET::  i=1 name=set2 mode=FAILOVER

DB:: j=0 name=postgres://user:xxx@127.0.0.1/sipapp can=1 may=1 r_rec=0

Thanks,

Xaled



_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to