PDG "Could not find output file for job..." Error
3823 11 2- adrianmeyerart
- Member
- 36 posts
- Joined: July 2013
- Offline
Hi,
I have the following issue.
I have a Topnet that outputs wedge variations with a Ropfetch TOP.
Everything has been cooked and saved to disk.
Now I added another Ropgeometry TOP with some polyreducing procedures inside, and want to take the original result, process it and save it next to the original geo.
The “Expected Output” looks correct, the Python expression to rename the files seems to work as well (in theoery).
All files are on present on disk and the initial ropfetch TOP “loads” detects that they are already cooked, thus creating a green dot.
If I send this to my HQueue Farm I get the follwing Log and nothing happens.
“Could not find output file for job ‘xxxxx’”
I also tried using a Local Scheduler, there it sometimes worked, but not really reproducable, sometimes same error.
Any ideas to help me there?
Much appreciated
Thanks
Adrian
PS.
Another annyoing thing is that if I shift-v to abort it, Houdini freezes and crashes.
Houdini 17.5.229
Windows 10 64Bit
I have the following issue.
I have a Topnet that outputs wedge variations with a Ropfetch TOP.
Everything has been cooked and saved to disk.
Now I added another Ropgeometry TOP with some polyreducing procedures inside, and want to take the original result, process it and save it next to the original geo.
The “Expected Output” looks correct, the Python expression to rename the files seems to work as well (in theoery).
All files are on present on disk and the initial ropfetch TOP “loads” detects that they are already cooked, thus creating a green dot.
If I send this to my HQueue Farm I get the follwing Log and nothing happens.
“Could not find output file for job ‘xxxxx’”
I also tried using a Local Scheduler, there it sometimes worked, but not really reproducable, sometimes same error.
Any ideas to help me there?
Much appreciated
Thanks
Adrian
PS.
Another annyoing thing is that if I shift-v to abort it, Houdini freezes and crashes.
Houdini 17.5.229
Windows 10 64Bit
Edited by adrianmeyerart - June 4, 2019 07:04:44
- chrisgreb
- Member
- 603 posts
- Joined: Sept. 2016
- Offline
- adrianmeyerart
- Member
- 36 posts
- Joined: July 2013
- Offline
Hi,
alright, I'll try with Houdini 17.5.258 production build, as I have to use this in production and include it in the pipeline i'm not to keen to use a daily build. I saw there is quite some fixes in 17.5.258.
Or do you think there are major enhancements in PDG from 17.5.258 that could adress exactly this problem?
Thanks
alright, I'll try with Houdini 17.5.258 production build, as I have to use this in production and include it in the pipeline i'm not to keen to use a daily build. I saw there is quite some fixes in 17.5.258.
Or do you think there are major enhancements in PDG from 17.5.258 that could adress exactly this problem?
Thanks
- chrisgreb
- Member
- 603 posts
- Joined: Sept. 2016
- Offline
- adrianmeyerart
- Member
- 36 posts
- Joined: July 2013
- Offline
- adrianmeyerart
- Member
- 36 posts
- Joined: July 2013
- Offline
I found something out though, meanwhile.
I think it happens when I use a split TOP to extract some of the work items with an expression like “@wedgenum<2”.
Lets say I have wedge Top with 8 work items above.
That leaves me with all work items with a wedgenum below 2.
If I try to execute that, this gives me “Could not find output file for job ‘xxxxx’”
I think it happens when I use a split TOP to extract some of the work items with an expression like “@wedgenum<2”.
Lets say I have wedge Top with 8 work items above.
That leaves me with all work items with a wedgenum below 2.
If I try to execute that, this gives me “Could not find output file for job ‘xxxxx’”
- adrianmeyerart
- Member
- 36 posts
- Joined: July 2013
- Offline
- chrisgreb
- Member
- 603 posts
- Joined: Sept. 2016
- Offline
- adrianmeyerart
- Member
- 36 posts
- Joined: July 2013
- Offline
Havent tried that.
But it now works with Houdini 17.5.278 daily build. That was lucky.
I was so bold to dare and try to only upgrade to 17.5.278 on my PDG Host machine (which is also running HQueue Server).
The client machines on the farm still run 17.5.229 production build.
And somehow it works. I just hardcoded the “Universal HFS” on the Hqueue Scheduler to “CProgram Files/Side Effects Software/Houdini 17.5.229”.
Because it is such a pain to setup Hqueue on Windows on all farm machines, I would try a lot to avoid upgrading that every couple of days :-P
Thanks a lot though!
But it now works with Houdini 17.5.278 daily build. That was lucky.
I was so bold to dare and try to only upgrade to 17.5.278 on my PDG Host machine (which is also running HQueue Server).
The client machines on the farm still run 17.5.229 production build.
And somehow it works. I just hardcoded the “Universal HFS” on the Hqueue Scheduler to “CProgram Files/Side Effects Software/Houdini 17.5.229”.
Because it is such a pain to setup Hqueue on Windows on all farm machines, I would try a lot to avoid upgrading that every couple of days :-P
Thanks a lot though!
Edited by adrianmeyerart - June 5, 2019 17:46:22
- adrianmeyerart
- Member
- 36 posts
- Joined: July 2013
- Offline
- chrisgreb
- Member
- 603 posts
- Joined: Sept. 2016
- Offline
- adrianmeyerart
- Member
- 36 posts
- Joined: July 2013
- Offline
-
- Quick Links