Page 20 of 256. Showing 2,557 results (0.015 seconds)

1. Restarting the Worker

   Linux % sudo /sbin/service worker restart OSX % sudo launchctl stop com.pipelinefx.worker % sudo launchctl start com.pipelinefx.worker Windows (Administrative Tools…
   Qube 6.5 • Jan 09, 2013

2. Restarting the Worker

   Linux $ sudo /sbin/service worker restart OS X $ sudo launchctl stop com.pipelinefx.worker $ sudo launchctl start com.pipelinefx.worker Windows Administrative Tools…
   Qube 6.6 • Sep 10, 2015

3. Restarting the Worker

   Linux $ sudo /sbin/service worker restart OS X $ sudo launchctl stop com.pipelinefx.worker $ sudo launchctl start com.pipelinefx.worker Windows Administrative Tools…
   Qube 7.0 • Nov 04, 2020

4. Restarting the Worker

   Linux $ sudo /sbin/service worker restart OS X $ sudo launchctl stop com.pipelinefx.worker $ sudo launchctl start com.pipelinefx.worker Windows Administrative Tools…
   Qube 6.9 • Jul 05, 2017

5. Restarting the Worker

   Linux $ sudo /sbin/service worker restart OS X $ sudo launchctl stop com.pipelinefx.worker $ sudo launchctl start com.pipelinefx.worker Windows Administrative Tools…
   Qube 6.10 • May 23, 2018

6. Restarting the Worker

   Linux $ sudo /sbin/service worker restart OS X $ sudo launchctl stop com.pipelinefx.worker $ sudo launchctl start com.pipelinefx.worker Windows Administrative Tools…
   Qube 6.7 • Jan 11, 2016

7. Restarting the Worker

   Linux $ sudo /sbin/service worker restart OS X $ sudo launchctl stop com.pipelinefx.worker $ sudo launchctl start com.pipelinefx.worker Windows Administrative Tools…
   Qube 6.8 • Oct 06, 2016

8. Windows Workers in Service Mode: operations such as killing/blocking jobs or locking workers do not take effect immediately; aggressive preemption does not seem to work properly.

   If your workers are: Windows-based configured to be in service mode (either "proxy" or "user" mode, and NOT "Desktop User mode") use Active Directory's GPO (Group Policy…
   Qube • Aug 16, 2018

9. Windows Workers in Service Mode: operations such as killing/blocking jobs or locking workers do not take effect immediately; aggressive preemption does not seem to work properly.

   If your workers are: Windows-based configured to be in service mode (either "proxy" or "user" mode, and NOT "Desktop User mode") use Active Directory's GPO (Group Policy…
   Qube 7.0 • Nov 04, 2020

10. Desktop worker service crashing on Windows

    desktop worker service is disappearing you can create a scheduled task of the below batch file to ensure that the machines always have the service running while logged in set…
    Qube 6.5 • Jul 17, 2013