This issue might be related with the implementation of CHD (for PS3 ISOS) and the 10GB issue mentioned here: #40
When loading a "large" collection of PS3 games in CHD format, ps3netsrv-go takes too long to process them and then this appears in the console:
Apr 23 12:23:16.781 ERR Command handler failed remote=192.168.0.203:57616 opcode=CmdReadDir err="sendResult for BioShock - Ultimate Rapture Edition (USA) (En,Fr,Es).chd.iso failed: binary.Write failed: write tcp4 192.168.0.201:38008->192.168.0.203:57616: write: broken pipe" remote=192.168.0.203:57616
I tested this with a collection of +90 PS3 games in CHD format (Varying sizes). The same collection in ISO format does not causes this issue.
This issue happens when refreshing the games or when trying to explore the /netX/PS3ISO from webman mod.
Personally, believe that the problem may be in libchdr... but also, I believe that maybe caching beforehand the data that might be sent to the client might solve this issue... that, or keeping the client around for longer (it waited like 1 minute on my tests, and the disconnect message appeared at 2nd minute).
Thanks in advance!
This issue might be related with the implementation of CHD (for PS3 ISOS) and the 10GB issue mentioned here: #40
When loading a "large" collection of PS3 games in CHD format, ps3netsrv-go takes too long to process them and then this appears in the console:
Apr 23 12:23:16.781 ERR Command handler failed remote=192.168.0.203:57616 opcode=CmdReadDir err="sendResult for BioShock - Ultimate Rapture Edition (USA) (En,Fr,Es).chd.iso failed: binary.Write failed: write tcp4 192.168.0.201:38008->192.168.0.203:57616: write: broken pipe" remote=192.168.0.203:57616I tested this with a collection of +90 PS3 games in CHD format (Varying sizes). The same collection in ISO format does not causes this issue.
This issue happens when refreshing the games or when trying to explore the /netX/PS3ISO from webman mod.
Personally, believe that the problem may be in libchdr... but also, I believe that maybe caching beforehand the data that might be sent to the client might solve this issue... that, or keeping the client around for longer (it waited like 1 minute on my tests, and the disconnect message appeared at 2nd minute).
Thanks in advance!