-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getScriptTree error #23
Comments
Same error for me too. Was working perfectly until recent upgrade to 0.9.47 version of MC (or perhaps the previous version). Have updated the plugin to 0.0.17. I'm getting a similar error on your other plugins Ryan. Cheers. |
Same issue here. Running 0.9.38 in Docker.
|
I also tried 0.9.47 and got the same. |
Hi again! Anyone found a workaround for this? All Ryan's plugins are unusable for me currently. |
Getting the same error, there is also a message pre-ceeding the message posted above here relating to "nedb"
|
The clue to a fix was in the error message, if anybody else wants a fix it is published here, |
Thanks @OvrAp3x . Working here with your fix. |
Thanks @OvrAp3x . Unfortunately, this didn't work in my case - and I don't see the error relating to nedb. Can I ask what version of MC you are using? |
@SpookOz Just as an FYI: I have 0.9.56 running here. |
Yeah, i also running that version |
fixes problems with plugins as referenced here ryanblenis/MeshCentral-ScriptTask#23
I'm also getting a 'getScriptTree' error that is not related to NeDB. TypeError: Cannot read property 'getScriptTree' of null
at Object.obj.handleAdminReq (/root/meshcentral/meshcentral-data/plugins/scripttask/scripttask.js:224:20)
at Object.obj.handleAdminReq (/root/meshcentral/node_modules/meshcentral/pluginHandler.js:522:40)
at obj.handlePluginAdminReq (/root/meshcentral/node_modules/meshcentral/webserver.js:5452:34)
at Layer.handle [as handle_request] (/root/meshcentral/node_modules/express/lib/router/layer.js:95:5)
at next (/root/meshcentral/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/root/meshcentral/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/root/meshcentral/node_modules/express/lib/router/layer.js:95:5)
at /root/meshcentral/node_modules/express/lib/router/index.js:281:22
at Function.process_params (/root/meshcentral/node_modules/express/lib/router/index.js:335:12)
at next (/root/meshcentral/node_modules/express/lib/router/index.js:275:10) |
Same here... latest MC and Plugin-Version. TypeError: Cannot read property 'getScriptTree' of null |
Same problem. It had worked for a while, but recently it stopped. |
I can also confirm this issue running on a Windows Server 2012 instance.
|
Updated to use MC's latest version of nedb (@yetzt/nedb), and remove the promise requirement which has gone away in the latest MC in lieu of later versions of Node. |
Thanks Ryan! It's working again. Really appreciate you taking the time to look into this and resolve it. These plugins add so much functionality to MC! |
Solved for ma as well. Many thanks!! |
I was able to install the plugin but when I go to the plugins tab for the remote machine I get the following error:
TypeError: Cannot read property 'getScriptTree' of null at Object.obj.handleAdminReq (/home/ec2-user/meshcentral-data/plugins/scripttask/scripttask.js:224:20) at Object.obj.handleAdminReq (/home/ec2-user/node_modules/meshcentral/pluginHandler.js:522:40) at obj.handlePluginAdminReq (/home/ec2-user/node_modules/meshcentral/webserver.js:5376:34) at Layer.handle [as handle_request] (/home/ec2-user/node_modules/express/lib/router/layer.js:95:5) at next (/home/ec2-user/node_modules/express/lib/router/route.js:137:13) at Route.dispatch (/home/ec2-user/node_modules/express/lib/router/route.js:112:3) at Layer.handle [as handle_request] (/home/ec2-user/node_modules/express/lib/router/layer.js:95:5) at /home/ec2-user/node_modules/express/lib/router/index.js:281:22 at Function.process_params (/home/ec2-user/node_modules/express/lib/router/index.js:335:12) at next (/home/ec2-user/node_modules/express/lib/router/index.js:275:10) at /home/ec2-user/node_modules/meshcentral/webserver.js:5622:20 at Layer.handle [as handle_request] (/home/ec2-user/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/home/ec2-user/node_modules/express/lib/router/index.js:317:13) at /home/ec2-user/node_modules/express/lib/router/index.js:284:7 at Function.process_params (/home/ec2-user/node_modules/express/lib/router/index.js:335:12) at next (/home/ec2-user/node_modules/express/lib/router/index.js:275:10)
Any ideas why that is?
(Running on Amazon Linux)
The text was updated successfully, but these errors were encountered: