Comparing MeshCentral 2 to ScreenConnect
-
All good.
-
0.3.3-e now
-
v0.3.3-i is out
-
I love this software... it updates faster than I can can install them.
-
@dafyre said in Comparing MeshCentral 2 to ScreenConnect:
I love this software... it updates faster than I can can install them.
Turn on automatic updates, silly person.
-
@travisdh1 said in Comparing MeshCentral 2 to ScreenConnect:
@dafyre said in Comparing MeshCentral 2 to ScreenConnect:
I love this software... it updates faster than I can can install them.
Turn on automatic updates, silly person.
Nah... I just update when I hear about it here... That way if yours breaks I know to wait.
-
@travisdh1 said in Comparing MeshCentral 2 to ScreenConnect:
@dafyre said in Comparing MeshCentral 2 to ScreenConnect:
I love this software... it updates faster than I can can install them.
Turn on automatic updates, silly person.
That's how people run into the "I came back and it wasn't working" problem.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@travisdh1 said in Comparing MeshCentral 2 to ScreenConnect:
@dafyre said in Comparing MeshCentral 2 to ScreenConnect:
I love this software... it updates faster than I can can install them.
Turn on automatic updates, silly person.
That's how people run into the "I came back and it wasn't working" problem.
Right, with fast updating Alpha (maybe beta) software, automatic updates are fucking stupid.
-
@scottalanmiller @JaredBusch
Y'all a bunch of scaredy (sp) cats, c'mon, don't be a party pooper, we got to live on the bleeding edge!! :face_with_tears_of_joy:
Turn on the auto updates... -
I switched my auto updates off, it's not too hard to click the update button in the GUI is it? lol..
-
Fedora auto updates = check
MeshCentral auto update = check
Automatic backup before MeshCentral auto update = ? -
Automatic backup is a good idea. If you have any suggestions, don't hesitate to add them to the GitHub issues list. By the way, last batch of updates includes support for ARMv8 64bit, Web Notifications, some improvements to multi-display selection, working on better tracking of relay sessions. Plenty more bug fixes of course.
-
Charts. I need to add a inactivity timeout for one-sided relays sessions to fix the green line.
-
Up to 0.3.3-n
-
Anyone here run into an issue out of the blue on day where meshcentral won't start? Running on linux.
mesherrors.txt says
/home/mordyt/node_modules/nedb/lib/datastore.js:77
if (err) { throw err; }
^Error: "toString()" failed
at stringSlice (buffer.js:560:43)
at Buffer.toString (buffer.js:633:10)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:506:23)Google brings me to: https://github.com/louischatriot/nedb/issues/389
I have like 10 PCs in MC.
How do I save my install? -
@MordyT likely this is related to a failed update. Did you update recently before this happened? Often a manual update will fix this.
-
Up to 0.3.3-q here now.
-
@MordyT Interesting. I have never seen this error before. Yes, it's safe to re-install, but backup "meshcentral-data" and "meshcentral-files" first. "meshcentral-data" contains the critical certificates that make your server unique. Agents will not reconnect unless you have the right certs. At any time, you can re-install your server and put the "data" and "files" folder back and restart and you should be fine. If you are using MongoDB, make sure to backup the database on a regular bases. If you are not using MongoDB, NeDB will be used and all ".db" files will be in the "meshcentral-data" folder.
Basically, should be easy to recover. Please don't hesitate to ask if you need help.
-
@MordyT One more thing. If you can go in "MeshCentral-Data" and look at the size of the ".db" files... Is any of the files really big (Megabytes)? If so, what is the name of the file that is big and how big is it? With only 10 PC's, I can't expect any of the files in that folder to be of any significant size. - Thanks.
-
How do you enable automatic server update?
For me, checking box and clicking OK to start server self update causes server to disconnect, automatically reconnect after 30 seconds or so, yet the server version remains the same.
To update, I must log in to server, stop MC, npm install meshcentral, and restart MC.
I am obviously doing it wrong.
