On Tue, Nov 8, 2016 at 12:50 PM, วีร์ ศรีทิพโพธิ์ <wee.s@forest.go.th> wrote:

On Nov 8, 2559 BE, at 16:50, Amit Aviram <aaviram@redhat.com> wrote:

Hi Wee.
Looking in your logs, it looks like "ovirt-imageio-daemon" service, which runs in the oVirt's host (ovirt03.forest.go.th), doesn't accept the requests as should. Please, log into this host and restart this service, running:

service ovirt-imageio-daemon restart

And try upload.

If this won't work, please send us the output of "journalctl -xeu ovirt-imageio-daemon" from ovirt03.forest.go.th.

Thanks, Amit.

Hi Amit,

I restarted ‘overt-imageio-daemon’ service in

ovirt03.forest.go.th but still can’t upload. Here is the output from ‘journalctl -xeu overt-imageio-daemon’ command in ovirt03.forest.go.th:

Thank you,
Wee.

Indeed the requests from ovirt-imageio-proxy doesn't get to ovirt-imageio-daemon. you can see in the proxy logs that a "No route to host" is logged.

Initially our setup opens up the needed ports in iptables in order to allow this connection, but if it was changed somehow it will break the upload flow. Can you make sure that port 54322 is open for input requests in

ovirt03.forest.go.th, and also open for output request where the proxy resides? Or whatever reason for the host not be reachable?