On Thursday, 1 December 2016 13:35:38 UTC-5, rohan kumbhar wrote: > Hi, > > Context for said subject: > task : automation > src vm : work > target vm : win7-64 > operation : file-copy > File-Copy src : /home/user/files > File-Copy target : /user/Documents/QubesIncoming/win7-64 > > the 2 vm's mentioned above are connected to different firewalls. > hence, there are 2 isolated networks. > > work vm fetches *.* into the files folder using a python-script-1. the same > script further issues qvm-copy-to-vm command on every file fetched to win7-64 > vm. > > inside win7-64 vm another python-script-2 resides. it processes the received > files. > > Issue: > While python-script-1 dumps files, if python-script-2 accesses the > File-Copy target, then python-script-1 in work vm starts displaying "connect: > connection refused." > > How to interpret whats wrong? > Is it that the qrexec-agent lost the handle to directory? > There was a race-condition? > Virtual channel closed? if yes, why?
checked sudo journalctl -b -u qubes-qrexec-agent.service nothing found there. how to debug this connect: Connection refused -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6af3071d-4281-4c23-bdf0-54e4bdf721d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
