Beka Gelashvili Posted April 15, 2021 Report Posted April 15, 2021 I have built the kazoo from the source.When I'm performing command - kazoo-applications status it displays this: Because of that, I can't use various functions of the kazoo. Is there a way to activate whApps manually?
Administrators mc_ Posted April 15, 2021 Administrators Report Posted April 15, 2021 Hard to say why the other apps aren't starting offhand. Consult the logs from startup. You can manually start with 'sup kapps_controller start_app {APP_NAME}'
Beka Gelashvili Posted April 15, 2021 Author Report Posted April 15, 2021 @mc Thanks for your help, I had to start all apps manually and now everything works good. Is there any command to start all available apps? So, when performing command - "make release" inside kazoo's source directory, normal behaviour is that, all that apps will start automatically right? @mc you mean kazoo logs located inside /var/log/kazoo/console.log file?
Administrators mc_ Posted April 15, 2021 Administrators Report Posted April 15, 2021 If this is a new system, yes, KAZOO should initialize relevant databases and configure the default list of apps to start automatically. You'll want to bump log level (typically syslog) in /etc/kazoo/core/config.ini to debug, then restart the VM and see what happens, why the default apps weren't started. Could be a temporary issue too (though I routinely reset my database cluster for dev and don't have issues with the default apps starting).
Beka Gelashvili Posted April 16, 2021 Author Report Posted April 16, 2021 (edited) @mc_ I couldn't find out what is happening, when starting the system (I think the system is not trying to load apps, because there are no logs which describe that process), but when I manually run - "sup kapps_controller start_default_apps" command, I can see logs. https://pastebin.com/LkW4pXH5 Edited April 16, 2021 by Beka Gelashvili (see edit history)
Administrators mc_ Posted April 16, 2021 Administrators Report Posted April 16, 2021 If you built this from source, make sure all the deps/ built properly (should be listed in make/deps.mk). You can stop the release, do `make sparkly-clean compile build-dev-release` to clean everything out, fetch all deps, recompile everything, and build a development release. Then `make release` will start the dev release. Other things to check are that you're compiling with the correct version of Erlang (see make/erlang_version).
Recommended Posts