unable to lock shared memory data lock

[Adrian Wyer]

getting this error note

new 9,1.26 install, trying to render in houdini 21.0.729 with rs 2026.7.0

maya seemed to work just fine, but since then the client app just keeps restarting....

any ideas?

[Adrian Wyer]

farm/clients restart 'seems' to  have fixed it for now....

[Adrian Wyer]

ok, more in the ongoing saga....

got a second machine updated... it picks up the houdini/rs job in the farm 

in viewer it shows that the new machine (fluid001) is rendering frames, but when the frame completes, the label changes to fluid002 (this machine is currently disabled)

small issue, but will be a problem in future when trouble shooting renders

[RR, Schoenberger]

Hi

Lock Error:

The lock error might be caused by thew GPU info app.
But if there is an incompatibility, then the GPU Info should be restarted and not the rrClient.
The issue will be investigated.

 

Client name:

I have to take a look at the job.

Please select the job (or multiple) in rrControl.

Then execute "Export debug info - selected job(s)" via the menu "Debug".

Please upload via www.RoyalRender.de/upload/

 

 

 

regards,
Holger Schönberger

Craftsman and Keeper of the Royal Render Flame

Please use the rrKnights Tavern
or our support system for new questions.

 

[RR, Schoenberger]

Hi

 

The lock issue  should not happen any more.
It was related to a log message in rrClientWatch, which should not show a dialog, but did.
The main download was updated.
Quickfix: www.RoyalRender.de/download/RoyalRender__9.1.26__updateFrom_9.1.26+.zip

[Adrian Wyer]

having updated more machines, we're noticing that the clients are constantly restarting, switching between demo/licensed.. losing connection to server then restarting, then sitting idle, then repeating the sequence

it's not job specific as there's currently nothing really in the farm

what log files do you need me to export to see why they are constantly restarting?

in the meantime i'll update from the quickfix

thanks

[Adrian Wyer]

also the earlier issue with jobs in the viewer reporting having been rendered by the wrong machine is still happening, have uploaded a job debug for that one

[Adrian Wyer]

ok, latest, the new quickfix seems to have sorted the constant restarting of clients and the LOCK error

i have 2 machines out of 7 that will not pick up jobs, they are installed/configured and appear in the control app

the weird thing is, if a submit a job to all the clients, the job shows up in control UNASSIGNED to those two machines....

i figured it could be something to do with the machine list in config, so uninstalled the client from both, and removed the machines from the client list in config

then reinstalled the client app.. waited until the machine again showed up in the farm, but again it won't let me assign jobs

[RR, Schoenberger]

Hi

> but again it won't let me assign jobs
Two possible reasons:
The render app is not listed for the client.
It is a GPU job,  but the client has not found the GPU.

You can verify both in rrConfig, menu Clients, tab Per Client.
On the first tab on the right you can see the GPU count.
On the last tab the installed render apps.

[Adrian Wyer]

thanks!! it was the GPUs... both machines have 2 but RR config said 0... set it to two and the machines picked up straight away!

great stuff

a

[Adrian Wyer]

any thoughts on how to get the farm to recognise the gpus and clock them ?

noticed that even if i force it to use 2 gpus on a machine, the GPU Speed field is zero...

a

[RR, Schoenberger]

Hi

 

Which machines have the issue?
Then I can take a look in the app logs that you send with the Job debug export.

Which GPUs do they have?

 

 

Note:

The new application that should detect all GPUs can be run via

%RR_ROOT%/bin/win64/rrGpuInfo -v -single

[RR, Schoenberger]

GPU issue:
I found it in the logs.
Machine no 006.
It was a problem that it tried to benchmark the GPU while another process was trying to retrieve the GPU usage at the same time. Will be fixed.

 

Houdini client name issue.
The job was reset, therefore I do not have access to all information any more.
At the moment it states that frames have been assigned to Fluid005.

Do you know if the issue Fluid001/Fluid001 happened after an older reset?
If it was after the reset, then the issue was perhaps that some old information was not reset.

[Adrian Wyer]

good to know about the gpu issue, will run the rrgpuinfo when nothing else is running

will keep an eye on renders and see if i can replicate the client name issue, nothing rendering currently and the farm has been swept clean of logs/jobs

will report back next week

thanks!