-
btrachtinstalled kamailio from source, copied kazoo-kamailio configs...
-
btrachtgetting "/etc/kazoo/kamailio/db_scripts/db_extra_check.sql: line 21: KazooDB: command not found" when attempting to start kazoo-kamailio
-
btrachtany ideas?
-
gontranit's a binary on `/usr/sbin/KazooDB` when deploying from RPM
-
gontrananyone ever have an experience where the API believes an account no longer exists and shows `"message": "bad identifier"` but you can see the account and detail in the bigcouch backend?
-
BadRequestgontran: Make sure that accounts/{ACCOUNT_ID} document and account/ac/co/unt-id database exist.
-
gontranthx BadRequest; yeah i'm in there. that's what's weird, the backend looks good. the account document looks fine, not disabled, and the correlary database exists.
-
gontrani'm grasping at straws and trying various sup commands for accounts
-
gontran`sup kapps_maintenance ensure_tree_account` did some fixup, but since I did `sup crossbar_maintenance enable_account ` I'm getting forbidden from the API when I try to get a listing - which was different than the `bad identifier`, heh.
-
gontranit's very confusing as I can see the data in the bigcouch futon, but when requesting via the API, the bc backend throws a 404 in the logs.
-
BadRequestLook at logs, and see why it is replying with 403.
-
BadRequestgontran: Maybe you are using another {ACCOUNT_ID} and/or Token when issuing the API request.
-
gontranyeah, good ideas. logs aren't giving me much. my api access is confirmed good for other parallel accounts. really a stumper.