Fresh install cannot finish - right denied core_coresettings table #1720
Replies: 2 comments 2 replies
-
troubleshooting and all the other stuff you did is only for after install, not during. wipe the vm, run the install script again and look for any errors, there probably would have been errors before you got to the "meshcentral not ready yet". if you don't see any errors and still get stuck, then leave the script running, open another terminal and run |
Beta Was this translation helpful? Give feedback.
-
found the issue, for some reason in the last few days, something with https://github.com/nodesource/distributions changed and installing nodejs 18 on Debian is no longer installing |
Beta Was this translation helpful? Give feedback.
-
Server Info (please complete the following information):
Installation Method:
Describe the bug
when I install tactical rmm with a self-signed certificate (./install --insecure) the script gets stuck with this message (Mesh Central not ready yet...).
When I ran the troubleshooting script, it told me that nats, nats-api and mesh were not running. I then used the systemctl status command to check what was happening. I noticed that the configuration file (nats-rmm.conf) didn't exist, so I ran the following command, which solved the problem (/rmm/api/env/bin/python /rmm/api/tacticalrmm/manage.py reload_nats) and I was able to start nats. As for nats-api, it just wasn't started.
Then I looked at mesh and did the following command as indicated in the documentation (/rmm/api/env/bin/python /rmm/api/tacticalrmm/manage.py check_mesh). This is where it gets tricky: I get the error i put in attachement file
tactical_rmm_django_error.txt
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The result of this command (/rmm/api/env/bin/python /rmm/api/tacticalrmm/manage.py check_mesh) on the documentation
Additional context
I just want to install tactical rmm. I just have ssh on the server.
It is a fresh install
Beta Was this translation helpful? Give feedback.
All reactions