Comparing MeshCentral 2 to ScreenConnect
-
I'm using the Vultr instance with 1GB RAM and 25GB SSD, with Ubuntu 18.10 and with only 8 agent sessions connected, RAM usage is at 62 Mb free, 983 Mb total.
Is this normal?
-
@Scott said in Comparing MeshCentral 2 to ScreenConnect:
I'm using the Vultr instance with 1GB RAM and 25GB SSD, with Ubuntu 18.10 and with only 8 agent sessions connected, RAM usage is at 62 Mb free, 983 Mb total.
Is this normal?
Yup, that's normal. Agents really use just about no RAM. Doesn't change as you go to hundreds of agents. At least not for us.
-
Cool. Thanks mate.
-
This is what I have on a 19.04 install...
119 Mb free, 983 Mb total
I think 19.04 is a little lighter than 18.04, so not surprised.
-
I just upgraded to the latest release (sorry, don't remember the ver,) but I get this now. I rebooted the server, and still the same. any ideas?
Error: ENOENT: no such file or directory, open '/home/wscheele/views/layouts/main.handlebars'
-
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
Error: ENOENT: no such file or directory, open '/home/wscheele/views/layouts/main.handlebars'
You are trying to run something from your home directory for your user. Try installing under /opt as root.
-
@scottalanmiller not that i know of (remember, I don't use or care for linux, but will use it if need).. I only use this for MC. I followed the directions for auto start I believe from the MC website.. I'll try find that.
All other updates went without issues. Just this last one.
-
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller not that i know of (remember, I don't use or care for linux, but will use it if need).. I only use this for MC. I followed the directions for auto start I believe from the MC website.. I'll try find that.
All other updates went without issues. Just this last one.
Try re-running your NPM update manually.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller not that i know of (remember, I don't use or care for linux, but will use it if need).. I only use this for MC. I followed the directions for auto start I believe from the MC website.. I'll try find that.
All other updates went without issues. Just this last one.
Try re-running your NPM update manually.
OK, let me find the directions again. or do u know the command off the top of you head?
-
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller not that i know of (remember, I don't use or care for linux, but will use it if need).. I only use this for MC. I followed the directions for auto start I believe from the MC website.. I'll try find that.
All other updates went without issues. Just this last one.
Try re-running your NPM update manually.
OK, let me find the directions again. or do u know the command off the top of you head?
npm install meshcentral -
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller not that i know of (remember, I don't use or care for linux, but will use it if need).. I only use this for MC. I followed the directions for auto start I believe from the MC website.. I'll try find that.
All other updates went without issues. Just this last one.
Try re-running your NPM update manually.
OK, let me find the directions again. or do u know the command off the top of you head?
npm install meshcentralThanks, get this
-
@smartkid808 you need to run that in the location where MeshCentral is installed.
-
@scottalanmiller Not sure if this is the right location, I followed the steps in the install manual during initial install.. But I assume its this location " ./node_modules/meshcentral"
I switch to that directory and then get these errors
-
@smartkid808 that's a relative location, relative to where you are at the time. Do this...
find / -name meshcentral -
It's no different than on Windows, if you don't start at the root (like c:) when doing something, it is relative to where you are. But it is way simpler than Windows because everything starts from the central root and you don't have separate roots for each physical device.
-
@scottalanmiller Hi scott, so this is what it pulls up.. sorry for being so dumb lol
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
This is what I have on a 19.04 install...
@scottalanmiller using Ubuntu
-
@smartkid808 I too had trouble with MC on Linux because I am not a regular Linux user.
scottalanmiller has helped me a great deal. The man has the patience of a saint.
-
@Scott said in Comparing MeshCentral 2 to ScreenConnect:
@smartkid808 I too had trouble with MC on Linux because I am not a regular Linux user.
scottalanmiller has helped me a great deal. The man has the patience of a saint.
Yes sir.. He sure is. and has been since I met him in SW. Hopefully I can get mines working again..lol
-
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller Hi scott, so this is what it pulls up.. sorry for being so dumb lol
This is weird folder structure for sure. Go into node_modules and run from there...
cd node_modules
