I have encountered several cases lately where timing issues surfaced. I'm wondering if this may be connected to the spreading of 3.0 ports.
If you want to test, add the "WaitBefore=<n>" parameter to your custom config file. The value is in seconds - I'd start with 8 or so, decreasing it in case of success.
I have encountered several cases lately where timing issues surfaced. I'm wondering if this may be connected to the spreading of 3.0 ports.
If you want to test, add the "WaitBefore=<n>" parameter to your custom config file. The value is in seconds - I'd start with 8 or so, decreasing it in case of success.