MeshCentral - Unable to update
-
@DustinB3403 said in MeshCentral - Unable to update:
@scottalanmiller said in MeshCentral - Unable to update:
Non-MongoDB install here. Update went smoothly.
Didn't mongoDB just change their license too, to something so practically insane that using MongoDB for even free and open source projects makes it worthless to consider?
Nope. They just made it only make sense for open source projects.
-
Thanks, I will keep digging.
-
Any guides for installing MeshCentral?
I looked under:
https://mangolassi.it/tags/meshcentralI didn't see anything.
-
@Curtis none written yet.
-
I was hoping I could (finally) contribute one but that is now shot to shit!
-
@pmoncho why is it shot?
-
Well, I cannot figure out how to update and I tried to get Let's Encrypt setup but that is blowing up with errors also.
May not be totally shot just delayed.
-
@pmoncho said in MeshCentral - Unable to update:
Well, I cannot figure out how to update and I tried to get Let's Encrypt setup but that is blowing up with errors also.
May not be totally shot just delayed.
What errors?
-
I would get the following after enabling the letsencrypt setting.
This is from syslog.Jan 4 16:12:42 host_mesh1 systemd[1]: Stopping MeshCentral Server... Jan 4 16:12:42 host_mesh1 systemd[1]: Stopped MeshCentral Server. Jan 4 16:12:49 host_mesh1 systemd[1]: Started MeshCentral Server. Jan 4 16:12:50 host_mesh1 node[10024]: Installing greenlock... Jan 4 16:12:51 host_mesh1 node[10024]: ERROR: Unable to install missing package 'greenlock', make sure npm is installed. Jan 4 16:13:02 host_mesh1 systemd[1]: meshcentral.service: Service RestartSec=1 0s expired, scheduling restart. Jan 4 16:13:02 host_mesh1 systemd[1]: meshcentral.service: Scheduled restart jo b, restart counter is at 1. Jan 4 16:13:02 host_mesh1 systemd[1]: Stopped MeshCentral Server.I'm contemplating installing again without the increased security or MongoDB and go from there.
-
@pmoncho Oh, I saw this happen. I got around it by firing it off manually, it installed what was needed, then it could go back to running automatically.
-
Are you saying you just installed greenlock on its own or ran the letsencrypt part on its own?
-
@pmoncho said in MeshCentral - Unable to update:
Are you saying you just installed greenlock on its own or ran the letsencrypt part on its own?
Neither. I just ran MechCentral manually, rather than with the systemctl script. It takes care of everything on its own otherwise. You can see it install GreenLock when you do that.
-
I installed generic instance of MC without secure install and with NeDB.
It still doesn't update properly but running it manually like you did, it did install the greenlock and le-acme-core.
-
@pmoncho said in MeshCentral - Unable to update:
I installed generic instance of MC without secure install and with NeDB.
It still doesn't update properly but running it manually like you did, it did install the greenlock and le-acme-core.
You only need to do that when you are "updating" with new code. It's not the updating that does it, it's the changing of features in the config file. Had you rebooted, it would have done the same thing. It just happened to be an attempt to update that triggered the restart that caught the issue.
-
@scottalanmiller said in MeshCentral - Unable to update:
@DustinB3403 said in MeshCentral - Unable to update:
@scottalanmiller said in MeshCentral - Unable to update:
Non-MongoDB install here. Update went smoothly.
Didn't mongoDB just change their license too, to something so practically insane that using MongoDB for even free and open source projects makes it worthless to consider?
Nope. They just made it only make sense for open source projects.
Yes, they fucked it all up. But as long as everything is open source, it seems to still be ok to use.
-
@JaredBusch said in MeshCentral - Unable to update:
@scottalanmiller said in MeshCentral - Unable to update:
@DustinB3403 said in MeshCentral - Unable to update:
@scottalanmiller said in MeshCentral - Unable to update:
Non-MongoDB install here. Update went smoothly.
Didn't mongoDB just change their license too, to something so practically insane that using MongoDB for even free and open source projects makes it worthless to consider?
Nope. They just made it only make sense for open source projects.
Yes, they fucked it all up. But as long as everything is open source, it seems to still be ok to use.
Yeah. For open source, it works fine. The physical product is good, but just not the license.
Have to say, we've been testing Atlas, their "paid" service and it is unstable. So even their paid for product, if you pay to make it okay for non-open source projects, isn't viable. Like seriously unstable. We've had more outages in three weeks of testing with Atlas on Amazon AWS, then we've had with our in house MongoDB on Linode in five years!
