Connection reset by peer errors in log
Hello guys,
Tell me please how to fix it if possible:
1394637158:0:/thelib/src/netio/epoll/tcpcarrier.cpp:88:OnEvent:Unable to read data from connection: (Far: 127.0.0.1:56752; Near: 127.0.0.1:1936) CTCP(95) <-> [TCP(9941)] <-> IR(9942). Error was (104): Connection reset by peer
1394637182:0:/thelib/src/netio/epoll/tcpcarrier.cpp:88:OnEvent:Unable to read data from connection: (Far: 127.0.0.1:56431; Near: 127.0.0.1:1936) CTCP(124) <-> [TCP(9395)] <-> IR(9396). Error was (104): Connection reset by peer
1394637182:0:/thelib/src/netio/epoll/tcpcarrier.cpp:88:OnEvent:Unable to read data from connection: (Far: 127.0.0.1:56518; Near: 127.0.0.1:1936) CTCP(262) <-> [TCP(9529)] <-> IR(9530). Error was (104): Connection reset by peer
1394637233:0:/thelib/src/netio/epoll/tcpcarrier.cpp:88:OnEvent:Unable to read data from connection: (Far: 127.0.0.1:56014; Near: 127.0.0.1:1936) CTCP(203) <-> [TCP(8613)] <-> IR(8614). Error was (104): Connection reset by peer
1394637263:0:/thelib/src/netio/epoll/tcpcarrier.cpp:88:OnEvent:Unable to read data from connection: (Far: 127.0.0.1:56119; Near: 127.0.0.1:1936) CTCP(67) <-> [TCP(8813)] <-> IR(8814). Error was (104): Connection reset by peer
EMS log is full of these errors. And I guess it happens when user closes connection to EMS. Port #1936 is used by wowza server. I.e. EMS is connected to wowza by command:
pullstream uri=rtmp://localhost:1936/live
All users connects to EMS using: rtmpe://xxx.xxx.xxx.xxx:1935/live.
When users connects to EMS through port 1935, EMS connects to Wowza through port 1936.