- This topic has 5 replies, 2 voices, and was last updated 6 years, 7 months ago by
Leonardo Bernardini.
-
Posted in: Muster usage
-
5th September 2019 at 9:52 am #21393Currently, we are building a render farm using a Windows 10/7 client PC.
By registering Muster with Windows Service, the user can set it to run in the background without starting Renderclient Service.At this time, if you log in locally or remotely as a user other than the Renderclient Service user, you will not be treated as logged in on the Muster.
When setting Shutdown or Availability, it is necessary to use a judgment method other than the user login status.Because of this problem, for example, in the following cases, Shutdown control is not executed as desired.
〇 Sample Case
The user is using it during the day and wants to use it as a render node at night, but wants to shut it down if it is idle for a certain time (ex. 2hours).
In the case described above, it is considered that it can be realized by the following settings, but in actuality, the user is logged in, but is shut down without being determined to be logged in.
+ Shutdown
-Shutdown atcion: Shutdown
-Shutdown disabled with logged users
-Track remote accesses as local loggings
-Shutdown the host when idle for N minutes〇 Our environment
Muster Version: 9.0.13
Dispatcher : Linux Server (Centos 7.x)
RenderNode :
- Windows 10 Pro 1903
- Windows 7 Pro SP1
Process start method: Service (use domain user)Is this just a problem for us?
Or is it due to the current specification of Muster?
5th September 2019 at 10:01 am #21394Hi Gemba,
As far as we know there have been no feedbacks about this problem when using the Renderclient as a Windows service.
From what you report, seems the problem is quite different. Basically you get a shutdown even the user is logged, so it is not the service that counts as a logged user, but rather logged users not detected at all. Could you confirm this behaviour ? Could you also tell us if just enabling “make client unavailable on user login” puts the client in a “user locked” status ?
Depending on those, we can understand if it’s just the shutdown operation that’s skipping the logged status, or something else.
Also, and not less important, please tell us your Muster version actually installed.
5th September 2019 at 10:30 am #21395Hi Leonardo
When “make client unavailable on user login” is enabled, the client status is as follows.
– domain\render : User Locked # Account registered for service
– domain\userA : idle # Designer account
– admin : idle # Local Administrator accountThe version of Muster used is 9.0.13 for both Dispatcher and Client.
Best regards.
5th September 2019 at 10:55 am #21398Do you mind installing 9.0.14 on just one client and confirm me the behaviour is the same ? seems things are working in reverse order on your site, while a user running as service is detected as a logged user, interactively logged users are detected as unlogged user. Very weird, things are working in the right way here but our test farm is at 9.0.14 at the moment, so I would like to exclude is something happened on 9.0.13. If you get the same behaviour, you may need to get in touch with us directly by email and we need to send you a couple of test .exe to run on your site to gather further information on what’s going on.
5th September 2019 at 11:45 am #21401Hi Leonard.
Thanks for your reply.
One client was upgraded to 9.0.14 and it worked the same way, but the results were the same.
– domain\render : User Locked # Account registered for service
– domain\userA : idle # Designer account
– admin : idle # Local Administrator accountCan I send an email to “vinfo@vvertex.com”?
Best regards.
-
You must be logged in to reply to this topic.
