[ANSWERED]Stop Indigo Server

How do you discover a plugin's ID?

You can also use this python code:

Code: Select all

indigo.server.log(indigo.devices[12345678].pluginId)

Have tried to just restart all plugins? That's pretty simple And should fix the memory leaks too.

Out of curiosity, are you guys reporting memory leaks and runaway CPU processes to the plugin developers? I ask because everyone always assumes the developers are aware of the issues when sometimes they have no clue and would be happy to investigate/fix if possible. I understand the immediate need to get things up-and-running again, but honestly restarting a plugin (all plugins?) or Indigo Server every so often is not a good long-term solution.

Adam

[jay (support)]

We encourage plugin developers to publish the IDs (we do for our plugins) but it's a bit spotty.

And, we completely agree with Adam - if a plugin is requiring frequent restart you really need to report it to the developer so they can investigate. Scheduling restarts is really a hack that isn't really scalable.

Code: Select all

import os

listOFAllFiles= os.listdir("/Library/Application Support/Perceptive Automation/Indigo 6/Preferences/Plugins")

for file in listOFAllFiles:           # loop over all files
   if file.find(".") ==0: continue     # skip system files
   pluginName= file.strip(".indiPref")   # strip ".indiPref"
   ID= indigo.server.getPlugin(pluginName)
   if ID.isEnabled():
      indigo.server.log("restarting plugin: "+ pluginName)
      try:
         ID.restart(waitUntilDone=False)
      except:
         indigo.server.log("failed")


This litte python script will restart ALL plugins for indigo 6 (if you have 5 replace the "6" with a "5"
see the attached screen shot how to enter it.

and yes I agree issues should be posted to be able to fix them.

Karl