ignoring self-originating request
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
ignoring self-originating request
My 6.5.1 ums has become unstable and stops after 2 hours of video - stack overflow
I put my log in trace mode but it very quickly fills to several hundred mb
The log is consumed by the following messages accumulating for a sequential port number
Is this normal or should I be looking for something else?
016-10-28 05:48:13.143 [New I/O worker #5] Ignoring self-originating request from /192.168.1.3:53787
TRACE 2016-10-28 05:48:13.242 [New I/O worker #6] Ignoring self-originating request from /192.168.1.3:53788
TRACE 2016-10-28 05:48:13.243 [New I/O worker #7] Ignoring self-originating request from /192.168.1.3:53789
TRACE 2016-10-28 05:48:13.254 [New I/O worker #8] Ignoring self-originating request from /192.168.1.3:53790
TRACE 2016-10-28 05:48:13.255 [New I/O worker #1] Ignoring self-originating request from /192.168.1.3:53791
I put my log in trace mode but it very quickly fills to several hundred mb
The log is consumed by the following messages accumulating for a sequential port number
Is this normal or should I be looking for something else?
016-10-28 05:48:13.143 [New I/O worker #5] Ignoring self-originating request from /192.168.1.3:53787
TRACE 2016-10-28 05:48:13.242 [New I/O worker #6] Ignoring self-originating request from /192.168.1.3:53788
TRACE 2016-10-28 05:48:13.243 [New I/O worker #7] Ignoring self-originating request from /192.168.1.3:53789
TRACE 2016-10-28 05:48:13.254 [New I/O worker #8] Ignoring self-originating request from /192.168.1.3:53790
TRACE 2016-10-28 05:48:13.255 [New I/O worker #1] Ignoring self-originating request from /192.168.1.3:53791