Error "Failed to copy stdout.txt/ivf, continuing anyway"

[YannisGuyon]

When running the all-in-one Docker instance and submitting new jobs, I get the following output:

Building codec 'rav1e' (using BUILD_OPTIONS '')
[...]
Finished release [optimized + debuginfo] target(s) in 2m 52s

null
ok
2020-01-28 14:11:22.811 Encoding grandma_short.y4m with quality 252 for run @Job1 on 127.0.0.1
2020-01-28 14:11:23.815 Encoding grandma_short.y4m with quality 220 for run @Job1 on 127.0.0.1
scp: /data/work/slot3/grandma_short.y4m-252-stdout.txt: No such file or directory
2020-01-28 14:11:31.556 Failed to copy back grandma_short.y4m-252-stdout.txt, continuing anyway
protocol error: filename does not match request
2020-01-28 14:11:31.667 Failed to copy back grandma_short.y4m-252.ivf, continuing anyway
2020-01-28 14:11:31.838 grandma_short.y4m with quality 252 for run @Job1 finished.
2020-01-28 14:11:31.838 Encoding grandma_short.y4m with quality 80 for run @Job1 on 127.0.0.1
scp: /data/work/slot2/grandma_short.y4m-220-stdout.txt: No such file or directory
2020-01-28 14:11:32.445 Failed to copy back grandma_short.y4m-220-stdout.txt, continuing anyway
protocol error: filename does not match request
2020-01-28 14:11:32.577 Failed to copy back grandma_short.y4m-220.ivf, continuing anyway
2020-01-28 14:11:32.844 grandma_short.y4m with quality 220 for run @Job1 finished.

I get similar protocol error issues with the "libaom (High Latency CQP)" codec.

Are these scp and protocol errors expected or did I forget to do something? The localhost web UI seems to be working fine, curves and BD Rate Reports are displayed.

[vibhoothi]

@tdaede I am also having similar issue when deploying AWCY, looks like the file is not being stored in work/slots$number folder ivf, if we kill any encode in middle of jobs, we get the ivf files, thus it is having some issue in middle of the code, need to narrow down. As there is no .ivf files, analyzer is also not working,
in the vimeo's instance when they deployed, similar issue was being noticed.