Comparing MeshCentral 2 to ScreenConnect

FATeknollogee

MeshCentral HTTP redirection server running on port 80.
MeshCentral v0.3.2-z, WAN mode.
{ Error: Command failed: /usr/bin/node /opt/meshcentral/node_modules/meshcentral --launch
internal/modules/cjs/loader.js:584
    throw err;
    ^

Error: Cannot find module './amt/amt-ider.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
    at Function.Module._load (internal/modules/cjs/loader.js:508:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.module.exports.CreateWebServer (/opt/meshcentral/node_modules/meshcentral/webserver.js:60:27)
    at AsyncWrap.<anonymous> (/opt/meshcentral/node_modules/meshcentral/meshcentral.js:767:59)
    at AsyncWrap.wrap.ondone (internal/crypto/random.js:57:8)

    at ChildProcess.exithandler (child_process.js:294:12)
    at ChildProcess.emit (events.js:194:15)
    at maybeClose (internal/child_process.js:970:16)
    at Socket.stream.socket.on (internal/child_process.js:389:11)
    at Socket.emit (events.js:189:13)
    at Pipe._handle.close (net.js:597:12)
  killed: false,
  code: 1,
  signal: null,
  cmd:
   '/usr/bin/node /opt/meshcentral/node_modules/meshcentral --launch' }
ERROR: MeshCentral failed with critical error, check MeshErrors.txt. Restarting in 5 seconds...

scottalanmiller

@FATeknollogee there you go, it has an error and isn't starting.

scottalanmiller

When did you update to "z"? I'm not on that yet, we are on "y".

FATeknollogee

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

When did you update to "z"? I'm not on that yet, we are on "y".

I have auto-updates enabled.

FATeknollogee

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

When did you update to "z"? I'm not on that yet, we are on "y".

Anyone know how to rollback?

CloudKnight

@FATeknollogee I've had this happend once with auto updates on, I turned it off and have since updated manually.

FATeknollogee

I'll go post this on MC github page.

FATeknollogee

@StuartJordan said in Comparing MeshCentral 2 to ScreenConnect:

@FATeknollogee I've had this happend once with auto updates on, I turned it off and have since updated manually.

C'mon, what fun is that...updating by hand :grinning_face_with_smiling_eyes:

CloudKnight

@FATeknollogee very true, but I'm not in your position now lol

FATeknollogee

@StuartJordan You got me there!

FATeknollogee

Per @Ylian "Update to latest version to fix this. MeshCentral v0.3.3-b is current."

FATeknollogee

v0.3.3-b update fixed the problem.
Thanks to @dafyre @scottalanmiller for chiming in.

FATeknollogee

What do you do when you connect back & a bunch of your hosts (agents) are greyed out?

scottalanmiller

@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:

What do you do when you connect back & a bunch of your hosts (agents) are greyed out?

Wait till they check in.

FATeknollogee

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:

What do you do when you connect back & a bunch of your hosts (agents) are greyed out?

Wait till they check in.

:thumbs_up:

scottalanmiller

They have a check in cycle, it can take a little bit.

scottalanmiller

For those not aware, MeshCentral standard install now requires make.

So on Ubuntu ....

sudo apt-get install make

And on Fedora...

dnf install make

scottalanmiller

Ylian

MeshCentral should not require make. If it does, this is a bug. I don't want the MeshCentral server to depend on anything but node itself. If you get an error during install, please post it here or better yet on GitHub, I will work to fix it. MeshCentral should remain super easy to install.

In other news, back to requests and fixing bugs this week. Last two weeks saw lots of work on Intel AMT IDER, but finally back to more normal tasks.

scottalanmiller

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

MeshCentral should not require make. If it does, this is a bug.

It threw an error for me and couldn't NPM install 0.3.3-b for me without adding make.