Hi Aaron,
Really interested in this work, and timely as I'm currently trying to automate building a hqueue farm. In the past I've done it with cobbled together scripts and files shared via NFS mounts, but now that hqueue has python3 support it's time to modernise.
At the moment I get this error if I try and run houdini with your container. Hython and hscript work fine. I'm running on Ubuntu 22.04. (For my purposes I'll mostly be running headless tasks.)
root@539d5b0c2631:/opt/hfs19.5# houdini
/opt/hfs19.5/bin/houdini-bin: error while loading shared libraries: libsmime3.so: cannot open shared object file: No such file or directory
Cheers,
Drew
Found 78 posts.
Search results Show results as topic list.
3rd Party » Houdini Docker - Containerize & automate Houdini installs
- drew
- 117 posts
- Offline
Houdini Lounge » Houdini 20 Rumors
- drew
- 117 posts
- Offline
liberalarts
Sure. But could Houdini learn from other software? Yes. Could Houdini be more user friendly? Hell yes.
The other question to ask here is could Blender's UI be extended to provide the vastly more complex and deep functionality of Houdini and still be "user friendly"? I'm going to suggest the answer is no.
These arguments always remind me of this great talk - https://www.youtube.com/watch?v=SxdOUGdseq4 [www.youtube.com]
-Drew
Houdini Lounge » Houdini for a Met Office
- drew
- 117 posts
- Offline
Well Houdini plus someone who can drive it could definitely be an asset See here for a few examples of large weather simulations visualized.
https://vimeo.com/user100884632 [vimeo.com]
https://vimeo.com/user100884632 [vimeo.com]
Houdini Lounge » H19 unable to launch on Ubuntu 20.4 with Qt Error
- drew
- 117 posts
- Offline
For the record, this was fixed with "sudo apt-get install --reinstall libxcb-xinerama0".
Houdini Lounge » Houdini 19 doesn't load AT ALL on Ubuntu 21.10
- drew
- 117 posts
- Offline
This fixed the problem for us, except we were having it with Ubuntu 20.04/h19 (h18.5 was working ok). Curious to know how/where you found this fix? I wasted quite a few hours reinstalling nVidia drivers and other futzing around.
Cheers
Drew
Cheers
Drew
kubo-vonmariusz8
In my case this fix is not working:qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.
Ubuntu 21.10
That's a different error though.
You have to doto fix this one.sudo apt-get install --reinstall libxcb-xinerama0
Houdini Lounge » Any rumours of Houdini 19?
- drew
- 117 posts
- Offline
Daryl DunlapNanoVDB is still being developed and hasn't made it into the main OpenVDB distribution yet so it's going to be hard for any application to expose it fully till that happens.
Well, with the Arnold 7 launch, it reminded me, that Houdini only has partial NanoVDB support, I wondered if SideFX improved NanoVDB support in H19?
Houdini Lounge » Any rumours of Houdini 19?
- drew
- 117 posts
- Offline
PDG/TOPs » Python Script TOP node will only cook on a single HQ client
- drew
- 117 posts
- Offline
Check what python executable is set. If it's hython you may be limited by houdini licenses.
Technical Discussion » VDB files that will not load into Houdini
- drew
- 117 posts
- Offline
Technical Discussion » Why is CPU and GPU not fully utilized in OpenCL simulations?
- drew
- 117 posts
- Offline
It could be as simple as the task being memory bandwidth limited, to the CPU and/or GPU. And for the GPUs in particular many tasks have components that are inherently scalar and hence can't take advantage of the parallelism of OpenCl. The more complicated the task the less likely it can be made to run efficiently on modern systems.
Edited by drew - Jan. 29, 2021 22:30:05
Technical Discussion » How to create geometry in standalone hython script?
- drew
- 117 posts
- Offline
Something like this maybe.
import hou import sys def main(output_hip): geo_node = hou.node('/obj').createNode('geo') pysop = geo_node.createNode('python') code = \ ''' node = hou.pwd() geo = node.geometry() geo.createNURBSSurface(10,10) ''' pysop.parm('python').set(code) hou.hipFile.save(file_name=output_hip) if __name__ == "__main__": if len(sys.argv) == 2: main(output_hip=sys.argv[1])
PDG/TOPs » How to debug a pdg scheduler type?
- drew
- 117 posts
- Offline
PDG/TOPs » How to debug a pdg scheduler type?
- drew
- 117 posts
- Offline
How does one go about developing a new scheduler type? At the moment if there is a problem with the python code the only feedback seems to be this error.
Load warnings for /home/drw900/HoudiniProjects/pbs/pbs_scheduler.hip
Warning: Bad node type found: pdg_drw900_pbsscheduler in /tasks/topnet1.
Is there some way to see the python interpreter stdout/err, stack trace etc?
Cheers,
Drew
Load warnings for /home/drw900/HoudiniProjects/pbs/pbs_scheduler.hip
Warning: Bad node type found: pdg_drw900_pbsscheduler in /tasks/topnet1.
Is there some way to see the python interpreter stdout/err, stack trace etc?
Cheers,
Drew
Technical Discussion » Rendering very large volumes / mantra / OpenVDB ?
- drew
- 117 posts
- Offline
I have some quite large volumes (~40-120GB uncompressed) that I'd like to render and would appreciate any pointers to the current state of the art?
Before I go to the work of getting the data into OpenVDB format, I'm trying to find out if mantra (or any other production renderer) utilise out of core delayed loading of subsets of an OpenVDB volume? I note that the openvdb::File class supports delayed loading of volume chunks, but I don't know if this functionality is enabled and accessible from houdini/mantra.
Thanks.
Before I go to the work of getting the data into OpenVDB format, I'm trying to find out if mantra (or any other production renderer) utilise out of core delayed loading of subsets of an OpenVDB volume? I note that the openvdb::File class supports delayed loading of volume chunks, but I don't know if this functionality is enabled and accessible from houdini/mantra.
Thanks.
PDG/TOPs » TOP Deadline updates in Houdini 18.0.399 (new MQ)
- drew
- 117 posts
- Offline
A bit of extra info to the last post. Strace'ing indicates that a thread is being woken up, very often. Maybe that is the cause of the idle cpu load?
nanosleep({tv_sec=0, tv_nsec=100}, NULL) = 0
PDG/TOPs » TOP Deadline updates in Houdini 18.0.399 (new MQ)
- drew
- 117 posts
- Offline
Looking forward to trying this new MQ with HQueue, coming soon?
BTW I just got it (linux 18.0.401) up and running and I notice it sits at about 8-9% CPU while idle which seems excessive?
> mqserver -p 4999 -s -i 0.0.0.0
BTW I just got it (linux 18.0.401) up and running and I notice it sits at about 8-9% CPU while idle which seems excessive?
> mqserver -p 4999 -s -i 0.0.0.0
Edited by drew - March 10, 2020 01:51:41
Technical Discussion » Houdini 18 HQueue Error
- drew
- 117 posts
- Offline
Grrrr….
After spending a few days investigating what was going on with H18 HQueue and submitting bug reports detailing how hqnode.ini files were being overwritten on startup, it's really frustrating to find out this has been moved into the web server. Why was this done? Why was nothing put into the configuration files mentioning the fact that they were now were being ignored. Nothing in the Whats New about HQueue changes.
I've spent a good deal of time building automated tools for:
- spinning up new linux VMs
- rolling out new versions of HQueue, keeping versions and configurations up to date
- installing hqnode clients that start on machine reboot, and restart on errors
- running up the web server on boot, _not_ as the root user
- creating a hquser on all the machines with the same uid/gid that allows a team to use HQueue without having the network mount completely open from a security standpoint
- not requiring someone to put passwords in for every client they add, frankly it's scary that the web server wants to ssh into machines and do stuff behind my back, and doesn't scale to a large number of nodes
So the new changes just seem to be going in the opposite direction. It's obviously not testable at the moment as evidenced by the fact that it was completely broken on day one of the H18 release. Philosophically I just don't think that HQueue should be developed in this direction, it seems to me un-Houdini like. When administering multiple machines there are much better tools for system orchestration than buggy web servers holding user passwords. Configuration should be in one place, clearly documented, updateable, and automatable. At least give system admins a chance to do things the right way. Sorry for the rant but I had to get this off my chest!
BTW sometimes we have to nuke the server and database and start from scratch due to large render jobs being nearly impossible to delete. The server goes into 100% cpu and hours go by without a successful delete operation. I'm assuming that would mean putting the network shares back into the database by hand through the web GUI?
Maybe I'm expecting too much of HQueue? It's been a really useful, albeit fragile, tool that has rendered hundreds of thousands of frames for my small group over the years. We're hardware rich, but software poor so it has filled a gap when we couldn't afford Deadline, Tractor etc. But maybe now we should be focusing on developing a custom PDG scheduler for task distribution in our environment, something that I'm seriously considering?
-Drew
After spending a few days investigating what was going on with H18 HQueue and submitting bug reports detailing how hqnode.ini files were being overwritten on startup, it's really frustrating to find out this has been moved into the web server. Why was this done? Why was nothing put into the configuration files mentioning the fact that they were now were being ignored. Nothing in the Whats New about HQueue changes.
I've spent a good deal of time building automated tools for:
- spinning up new linux VMs
- rolling out new versions of HQueue, keeping versions and configurations up to date
- installing hqnode clients that start on machine reboot, and restart on errors
- running up the web server on boot, _not_ as the root user
- creating a hquser on all the machines with the same uid/gid that allows a team to use HQueue without having the network mount completely open from a security standpoint
- not requiring someone to put passwords in for every client they add, frankly it's scary that the web server wants to ssh into machines and do stuff behind my back, and doesn't scale to a large number of nodes
So the new changes just seem to be going in the opposite direction. It's obviously not testable at the moment as evidenced by the fact that it was completely broken on day one of the H18 release. Philosophically I just don't think that HQueue should be developed in this direction, it seems to me un-Houdini like. When administering multiple machines there are much better tools for system orchestration than buggy web servers holding user passwords. Configuration should be in one place, clearly documented, updateable, and automatable. At least give system admins a chance to do things the right way. Sorry for the rant but I had to get this off my chest!
BTW sometimes we have to nuke the server and database and start from scratch due to large render jobs being nearly impossible to delete. The server goes into 100% cpu and hours go by without a successful delete operation. I'm assuming that would mean putting the network shares back into the database by hand through the web GUI?
Maybe I'm expecting too much of HQueue? It's been a really useful, albeit fragile, tool that has rendered hundreds of thousands of frames for my small group over the years. We're hardware rich, but software poor so it has filled a gap when we couldn't afford Deadline, Tractor etc. But maybe now we should be focusing on developing a custom PDG scheduler for task distribution in our environment, something that I'm seriously considering?
-Drew
Edited by drew - Dec. 5, 2019 23:46:27
Technical Discussion » render farm linux houdini 17.5
- drew
- 117 posts
- Offline
So i suggest you
> mkdir /opt/hqueue/shared/houdini_distros
Then install a full distro of linux houdini into this, ie something like the following
> tar xvfz houdini-17.5.360-linux_x86_64_gcc6.3.tar.gz
> cd houdini-17.5.360-linux_x86_64_gcc6.3
> . houdini.install # note the space after the period here
You shouldn't need to be the root user to do this.
… then from the menus you're going to select option D and change the installation directory to be something like /opt/hqueue/shared/houdini_distros/hfs17.5.360 at which point go ahead and install.
Now
> cd /opt/hqueue/shared/houdini_distros
> ln -sf hfs17.5.360 hfs.linux-x86_64
Then you should be on your way.
> mkdir /opt/hqueue/shared/houdini_distros
Then install a full distro of linux houdini into this, ie something like the following
> tar xvfz houdini-17.5.360-linux_x86_64_gcc6.3.tar.gz
> cd houdini-17.5.360-linux_x86_64_gcc6.3
> . houdini.install # note the space after the period here
You shouldn't need to be the root user to do this.
… then from the menus you're going to select option D and change the installation directory to be something like /opt/hqueue/shared/houdini_distros/hfs17.5.360 at which point go ahead and install.
Now
> cd /opt/hqueue/shared/houdini_distros
> ln -sf hfs17.5.360 hfs.linux-x86_64
Then you should be on your way.
Edited by drew - Dec. 5, 2019 18:53:30
Technical Discussion » render farm linux houdini 17.5
- drew
- 117 posts
- Offline
On your linux machine, do this and tell us what you see.
> ls /opt/hqueue/shared
Also,
> ls /opt/hqueue/shared/houdini_distros
> ls /opt/hqueue/shared
Also,
> ls /opt/hqueue/shared/houdini_distros
Technical Discussion » render farm linux houdini 17.5
- drew
- 117 posts
- Offline
These things happen …
1. The Hqueue server is installed somewhere, either windows or linux. The server does not need to mount the shared filesystem.
2. The Hqueue clients are installed on the machines you want doing the work, windows and/or linux. The clients _must_ all be able to see the shared filesystem. Note: this means if want your server machine to also do work, you'll need a Hqueue client installed on it as well and hence the shared network mount to be present. I'm guessing from what you've desrcribed this is what you'll be doing.
3. A full Houdini distro must be installed on all the clients machines, and the easiest way to do this is to install it once onto the shared filesystem that is accessible to all. ie into /opt/hqueue/shared/houdini_distros/ directory like I detailed above.
You may also eventually need a Windows distro installed on that shared mount as well, but I'm not a Windows user so others will need to jump in here for the detalis. While you're getting things set up I'd just have linux be the client. One you get that running proprely you can think about adding Windows as a client as well.
Hopefully this is a bit clearer. BTW I don't recommend going to H18 yet.
-D
1. The Hqueue server is installed somewhere, either windows or linux. The server does not need to mount the shared filesystem.
2. The Hqueue clients are installed on the machines you want doing the work, windows and/or linux. The clients _must_ all be able to see the shared filesystem. Note: this means if want your server machine to also do work, you'll need a Hqueue client installed on it as well and hence the shared network mount to be present. I'm guessing from what you've desrcribed this is what you'll be doing.
3. A full Houdini distro must be installed on all the clients machines, and the easiest way to do this is to install it once onto the shared filesystem that is accessible to all. ie into /opt/hqueue/shared/houdini_distros/ directory like I detailed above.
You may also eventually need a Windows distro installed on that shared mount as well, but I'm not a Windows user so others will need to jump in here for the detalis. While you're getting things set up I'd just have linux be the client. One you get that running proprely you can think about adding Windows as a client as well.
Hopefully this is a bit clearer. BTW I don't recommend going to H18 yet.
-D
bgood
Under windows when I install the server it does it to me alone why under linux it did not do it to me?
I have to reinstall houdini in this directory or just the server I don't understand?
Edited by drew - Dec. 4, 2019 18:23:45
-
- Quick Links