Cannot use module with meshcentral deployed in orchestration solution #5922
Replies: 3 comments 1 reply
-
|
plugins are not offically supported so we cannot provide any help im afraid, you need to ask in the plugin repo for help |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
OK, thank you very much for your reply. I would have appreciated it if you could have answered at least one question about the organization of plugin data storage. I'll manage otherwise. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
thank you for this clarification |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
My meshcentral server (1.1.20 or 1.1.21) is running in an orchestration environment with the meshcentral-data folder as the only persistent volume. The installation of the latest 'script task' module (0.0.19) seems to go well, but when I tried to use it with a device, I had this error from the mesh node client:
TypeError: Cannot read properties of null (reading 'getScriptTree')
at obj.handleAdminReq (/opt/meshcentral/meshcentral-data/plugins/scripttask/scripttask.js:224:20)
at obj.handleAdminReq (/opt/meshcentral/meshcentral/pluginHandler.js:521:40)
at obj.handlePluginAdminReq (/opt/meshcentral/meshcentral/webserver.js:5993:34)
at Layer.handle [as handle_request] (/opt/meshcentral/meshcentral/node_modules/express/lib/router/layer.js:95:5)
at next (/opt/meshcentral/meshcentral/node_modules/express/lib/router/route.js:144:13)
at Route.dispatch (/opt/meshcentral/meshcentral/node_modules/express/lib/router/route.js:114:3)
at Layer.handle [as handle_request] (/opt/meshcentral/meshcentral/node_modules/express/lib/router/layer.js:95:5)
at /opt/meshcentral/meshcentral/node_modules/express/lib/router/index.js:284:15
at Function.process_params (/opt/meshcentral/meshcentral/node_modules/express/lib/router/index.js:346:12)
at next (/opt/meshcentral/meshcentral/node_modules/express/lib/router/index.js:280:10)
Did you get this issue before? What would be your advice for meshcentral storage infrastructure as part of an orchestration project? Would it be necessary to create additional persistent volumes to store module data? If so, would you have details of the folders involved?
Beta Was this translation helpful? Give feedback.
All reactions