Jump to content

Recommended Posts

Hi guys, 

I've recently (finally) started to use hbatch for rendering/saving out my files and it's a blessing. 
So far everything has been running smoothly but last night one of my renders died on me.

I tried a slightly higher sim resolution and started it before leaving work, when I returned this morning I could see that slightly less than half had been simulated and real fast, only about 3-4 minutes each. 
But then I simply got the "killed" feedback in my terminal with no further information, even though the render command was set to verbose. 
Is there someway I can access why it was killed? Since they were running so quickly I don't believe the system ran out of resources but then again it is fully possible.

/ -> render -V obj/PYRO/explosionVdb
Rendering 54 frames ( from 1 to 54 by 1)
19:55:47 explosionVdb frame 1 (1 of 54)
19:55:47 explosionVdb frame 2 (2 of 54)
19:55:47 explosionVdb frame 3 (3 of 54)
19:57:18 explosionVdb frame 4 (4 of 54)
19:58:15 explosionVdb frame 5 (5 of 54)
19:59:34 explosionVdb frame 6 (6 of 54)
20:01:37 explosionVdb frame 7 (7 of 54)
20:04:52 explosionVdb frame 8 (8 of 54)
20:08:23 explosionVdb frame 9 (9 of 54)
20:11:32 explosionVdb frame 10 (10 of 54)
20:14:48 explosionVdb frame 11 (11 of 54)
20:18:12 explosionVdb frame 12 (12 of 54)
20:21:46 explosionVdb frame 13 (13 of 54)
20:25:28 explosionVdb frame 14 (14 of 54)
20:29:17 explosionVdb frame 15 (15 of 54)
20:33:19 explosionVdb frame 16 (16 of 54)
20:37:32 explosionVdb frame 17 (17 of 54)
20:42:00 explosionVdb frame 18 (18 of 54)
20:46:43 explosionVdb frame 19 (19 of 54)
Killed

 

I'm running Houdini Indie 17.5.258 on Linux Mint  19.1 Cinnamon.

Any and all help would be appreciated! 

Share this post


Link to post
Share on other sites
On 15/7/2019 at 5:14 AM, Digistruct said:

Hi guys, 

I've recently (finally) started to use hbatch for rendering/saving out my files and it's a blessing. 
So far everything has been running smoothly but last night one of my renders died on me.

I tried a slightly higher sim resolution and started it before leaving work, when I returned this morning I could see that slightly less than half had been simulated and real fast, only about 3-4 minutes each. 
But then I simply got the "killed" feedback in my terminal with no further information, even though the render command was set to verbose. 
Is there someway I can access why it was killed? Since they were running so quickly I don't believe the system ran out of resources but then again it is fully possible.

/ -> render -V obj/PYRO/explosionVdb
Rendering 54 frames ( from 1 to 54 by 1)
19:55:47 explosionVdb frame 1 (1 of 54)
19:55:47 explosionVdb frame 2 (2 of 54)
19:55:47 explosionVdb frame 3 (3 of 54)
19:57:18 explosionVdb frame 4 (4 of 54)
19:58:15 explosionVdb frame 5 (5 of 54)
19:59:34 explosionVdb frame 6 (6 of 54)
20:01:37 explosionVdb frame 7 (7 of 54)
20:04:52 explosionVdb frame 8 (8 of 54)
20:08:23 explosionVdb frame 9 (9 of 54)
20:11:32 explosionVdb frame 10 (10 of 54)
20:14:48 explosionVdb frame 11 (11 of 54)
20:18:12 explosionVdb frame 12 (12 of 54)
20:21:46 explosionVdb frame 13 (13 of 54)
20:25:28 explosionVdb frame 14 (14 of 54)
20:29:17 explosionVdb frame 15 (15 of 54)
20:33:19 explosionVdb frame 16 (16 of 54)
20:37:32 explosionVdb frame 17 (17 of 54)
20:42:00 explosionVdb frame 18 (18 of 54)
20:46:43 explosionVdb frame 19 (19 of 54)
Killed

 

I'm running Houdini Indie 17.5.258 on Linux Mint  19.1 Cinnamon.

Any and all help would be appreciated! 

Any news? I have the same problem

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×