lance-tek
commented
1 year ago I guess the 110 seconds was not a timeout... the most recent is over 25 minutes. This is for a Movies directory and it had just gotten to 400...
On the TV shows directory (discussed above) I was getting around 1800 before it blew up at me in around 110 seconds...
plexwrapper 2023-01-10 13:51:11,508 DEBUG plexwrapper.py:get_dupe_content Found media: plex://movie/5d77686d103a2d001f571448 database 2023-01-10 13:51:11,508 DEBUG database.py:get_ignored_item content_key /library/metadata/41293 plexwrapper 2023-01-10 13:51:25,317 DEBUG plexwrapper.py:get_dupe_content Get results from offset 400 to limit 450 Tue Jan 10 13:51:25 2023 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /content/dupes (ip 192.168.30.111) !!! Tue Jan 10 13:51:25 2023 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 306] during GET /content/dupes (192.168.30.111) OSError: write error [pid: 16|app: 0|req: 1/4] 192.168.30.111 () {42 vars in 651 bytes} [Tue Jan 10 13:25:45 2023] GET /content/dupes => generated 0 bytes in 1540079 msecs (HTTP/1.1 200) 3 headers in 0 bytes (0 switches on core 0)
I have a couple of really large directories and it looks like there is a timeout while collecting the directory information. I've tried larger page size setting and super low but it seems that maybe the scan itself is just taking too long to complete?
it seems to be about 110 seconds (+/- a couple) from the beginning of the load each time this occurs. I changed a couple of timeout settings in the browser (Mozilla) but it didn't have an impact on this. In fact, I closed the browser and this continued to run until the roughly 110 second mark. So, it seems to be something on the backend not the UI directly.
Any thoughts?
plexwrapper 2023-01-10 11:28:34,603 DEBUG plexwrapper.py:get_dupe_content Found media: plex://episode/5d9c110102391c001f5e6386 database 2023-01-10 11:28:34,603 DEBUG database.py:get_ignored_item content_key /library/metadata/30531 plexwrapper 2023-01-10 11:28:34,642 DEBUG plexwrapper.py:get_dupe_content Get results from offset 1730 to limit 1740 Tue Jan 10 11:28:34 2023 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /content/dupes (ip 192.168.30.111) !!! Tue Jan 10 11:28:34 2023 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 306] during GET /content/dupes (192.168.30.111) OSError: write error [pid: 16|app: 0|req: 4/8] 192.168.30.111 () {42 vars in 651 bytes} [Tue Jan 10 11:26:43 2023] GET /content/dupes => generated 0 bytes in 111019 msecs (HTTP/1.1 200) 3 headers in 0 bytes (0 switches on core 0)
Thanks!