ikoon Posted May 3, 2019 Share Posted May 3, 2019 Hello, I reinstalled my little farm and I have the issue, as attached: - HQueue ERROR: Cannot find file ... - but I have tried to manually run hython and load the file ... and from the command line tools everything works fine - I turned off the firewall and restarted the HQueueClient service. I have no other ideas. Please, where might be the problem? Quote Link to comment Share on other sites More sharing options...
dzigakaiser Posted July 5, 2019 Share Posted July 5, 2019 Hey ikoon, unfortunately, I m just gonna leave a +1 here since I encounter the same problem right now. I get the same error log and when I copy the path and paste it into the explorer on the client it opens the file. No idea what the cause could be besides something to do with Windows path mapping not being natively with forward slashes :/ Did you ever figure it out? Cheers, Dziga Quote Link to comment Share on other sites More sharing options...
dzigakaiser Posted July 8, 2019 Share Posted July 8, 2019 In case someone comes across this thread finding themselves lost in one HQeue issue after another, here is a quick list of problems I came across (as a google help or contact me if you need assistance): 1. Manually create inbound and outbound rules for ports 5000 and 5001 in your Windows Firewall to enable communication between server and clients (on all machines). 2. Use the IP address to connect the client to server to avoid possible name resolving issues in your network. 3. Even after changing the "Log On" account for the HClient windows service it was not able to see my network mount. I instead used this inside the hqserver.ini hqserver.sharedNetwork.path.windows = \\XXX\SHARE hqserver.sharedNetwork.mount.windows = \\XXX\SHARE 4. Don't forget to set your target HFS inside the HQ ROP to the installation path of Houdini (took me way too long to realize that I forgot to do this :D) 5. Imports in your HIP might have trouble to load (geo or textures read from your drive/mounted share), the same reason being the one behind point 3. To avoid this you can change those paths to your network share by using //XXX/share instead of using the drive letter. You can get a python script going relatively easy to search and replace file paths in your hip, save the file as a copy/submission file and then submit to hqueue. Hopefully this points anyone with similar issues in the right direction:) 1 1 Quote Link to comment Share on other sites More sharing options...
ikoon Posted July 10, 2019 Author Share Posted July 10, 2019 Dziga thank you very much for your description. Mine issue was due to improper installation. After reinstalling it went fine. Here are some details: SESI recommends: Please use UNC paths with Hqueue, never letter drives. If you are still having problems after switching to UNC paths, please check if you can see the location on the windows file explorer. If yes, then the job failure is likely due to the HQueue Client not having access to that location. Check the HQueue Client service and verify that the service's Logon account is set to a Windows user account that has access to it. Personaly I have set it like this: - on the Server, I don't share a folder but whole Q:\ drive - on Clients, I map the Q:\ drive - so the $HQROOT paths are identical On the server I don't use UNC paths. Accessing directly Q: on the server (without UNC) is much faster. Here is described why: https://stackoverflow.com/questions/12903054/unc-path-pointing-to-local-directory-much-slower-than-local-access/12943869#12943869 It is not a solution for studios, but for me (Indie) I am really glad, that I have that extra speed. It is against the recommendation but so far it works fine. Here is the usual process I do, step by step. I am no guru, so I hope that everything is as it should be: Share Q: drive on the server machine: Map Q: drive on the client machines: Set firewalls on client and server machines: Set service login on client machines: Service login set, it looks like this: This is probably not necessary. If I remember correctly, I have read somewhere, that I should set local network addresses as an "intranet": Quote Link to comment Share on other sites More sharing options...
ikoon Posted July 10, 2019 Author Share Posted July 10, 2019 Here are the contents of my .ini files: C:\HQueueClient\hqnode.ini (on the client machines) [main] server = 192.168.1.200 port = 5000 sharedNetwork.mount = \\192.168.1.200\Q [job_environment] C:\HQueueServer\hqserver.ini (on the server machine) # # I did not paste whole file here on odforce, there are many lines before and after # [server:main] use = egg:Paste#http host = 192.168.1.200 port = 5000 [app:main] # The shared network. hqserver.sharedNetwork.host = 192.168.1.200 hqserver.sharedNetwork.path.linux = %(here)s/shared hqserver.sharedNetwork.path.windows = Q hqserver.sharedNetwork.path.macosx = %(here)s/HQShared hqserver.sharedNetwork.mount.linux = /mnt/hq hqserver.sharedNetwork.mount.windows = Q: hqserver.sharedNetwork.mount.macosx = /Volumes/HQShared # Server port number. hqserver.port = 5000 # # I did not paste whole file here on odforce, there are many lines before and after # Quote Link to comment Share on other sites More sharing options...
ikoon Posted July 10, 2019 Author Share Posted July 10, 2019 Here is how I submit the job. Here is the HQueue Simulation: HQueue Render is similar. Btw sometimes I want only a subset of clients. For example I have the commercial Redshift license only on one client machine, PC-A: 1 Quote Link to comment Share on other sites More sharing options...
ikoon Posted July 10, 2019 Author Share Posted July 10, 2019 Well, I am just a self taught freelancer, so I hope that mine settings are correct. BTW it is recommended to use $JOB instead of $HIP. @dzigakaiserI really think that the script, which replaces $HIP, is not necessary. Quote Link to comment Share on other sites More sharing options...
dzigakaiser Posted July 11, 2019 Share Posted July 11, 2019 Thanks for sharing your setup!:) My script is only neccessary for file imports that come from outside the $HIP directory. And as I am saving a copy anyways, the copy might as well have the network share path. Or at least, that was the quickest solution I could think of, since I am also in the same boat as you, being a self taught freelancer ^^ And about the script saving the extra copy, that's more of a personal preference. I like to have the exact hip file the renderings came from untouched for debugging and clarity. By using the script I avoid accidentally submitting abc_v009.hip, then continue working in v009 and overwriting it. Thanks for the pointer to use $JOB! 1 Quote Link to comment Share on other sites More sharing options...
kidsreturnjj Posted June 15, 2021 Share Posted June 15, 2021 (edited) On 7/10/2019 at 12:33 PM, ikoon said: Here are the contents of my .ini files: C:\HQueueClient\hqnode.ini (on the client machines) [main] server = 192.168.1.200 port = 5000 sharedNetwork.mount = \\192.168.1.200\Q [job_environment] C:\HQueueServer\hqserver.ini (on the server machine) # # I did not paste whole file here on odforce, there are many lines before and after # [server:main] use = egg:Paste#http host = 192.168.1.200 port = 5000 [app:main] # The shared network. hqserver.sharedNetwork.host = 192.168.1.200 hqserver.sharedNetwork.path.linux = %(here)s/shared hqserver.sharedNetwork.path.windows = Q hqserver.sharedNetwork.path.macosx = %(here)s/HQShared hqserver.sharedNetwork.mount.linux = /mnt/hq hqserver.sharedNetwork.mount.windows = Q: hqserver.sharedNetwork.mount.macosx = /Volumes/HQShared # Server port number. hqserver.port = 5000 # # I did not paste whole file here on odforce, there are many lines before and after # Hi Ikoon, hope to ask how did you keep hqnode.ini => sharedNetwork.mount path I set my hqnode.ini as below [main] server = 192.168.xx.001 port = 5000 sharedNetwork.mount = \\fx100\hq but when I submitted the job, it is overwritten as below [main] server = 192.168.xx.001 port = 5000 sharedNetwork.mount = \\localhost\hq I've set hqserver.ini as below hqserver.sharedNetwork.path.windows = \\fx100\hq hqserver.sharedNetwork.mount.windows = H: Should I do something else to avoid overwritten issue of hqnode.ini as "\\localhost\hq" for client machine? If you can give any advice, it would be really helpful. Thanks! Edited June 15, 2021 by kidsreturnjj Quote Link to comment Share on other sites More sharing options...
ikoon Posted June 15, 2021 Author Share Posted June 15, 2021 Hi, I haven't used HQueue for a very long time, so I am not able to help now unfortunately. But you should probably do the tests from the docs ... to see, if the services are running well and computers see each other: https://www.sidefx.com/docs/houdini/hqueue/gettingstarted.html Or try to describe the issue here https://www.sidefx.com/bugs/submit/ and the Support team should be able to help you. Quote Link to comment Share on other sites More sharing options...
JoelF Posted September 28, 2021 Share Posted September 28, 2021 (edited) On 6/15/2021 at 2:27 PM, kidsreturnjj said: Hi Ikoon, hope to ask how did you keep hqnode.ini => sharedNetwork.mount path I set my hqnode.ini as below [main] server = 192.168.xx.001 port = 5000 sharedNetwork.mount = \\fx100\hq but when I submitted the job, it is overwritten as below [main] server = 192.168.xx.001 port = 5000 sharedNetwork.mount = \\localhost\hq I've set hqserver.ini as below hqserver.sharedNetwork.path.windows = \\fx100\hq hqserver.sharedNetwork.mount.windows = H: Should I do something else to avoid overwritten issue of hqnode.ini as "\\localhost\hq" for client machine? If you can give any advice, it would be really helpful. Thanks! Hi, I was just having this problem. It is the Network Folder that is added to the menu of the HQServer interface that is overwriting the mount. This can be used to add details to you hqnode.ini. It gets written to with the details contained in this everytime you submit a job: Edited September 28, 2021 by JoelF Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.