22:14:19 <btracht> installed kamailio from source, copied kazoo-kamailio configs...
22:14:39 <btracht> getting "/etc/kazoo/kamailio/db_scripts/db_extra_check.sql: line 21: KazooDB: command not found" when attempting to start kazoo-kamailio
22:14:47 <btracht> any ideas?
22:34:18 <gontran> it's a binary on `/usr/sbin/KazooDB` when deploying from RPM
22:37:14 <gontran> anyone 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?
22:54:04 <BadRequest> gontran: Make sure that accounts/{ACCOUNT_ID} document and account/ac/co/unt-id database exist.
22:55:50 <gontran> thx 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.
22:56:10 <gontran> i'm grasping at straws and trying various sup commands for accounts
22:56:45 <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.
23:01:54 <gontran> it'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.
23:04:20 <BadRequest> Look at logs, and see why it is replying with 403.
23:05:20 <BadRequest> gontran: Maybe you are using another {ACCOUNT_ID} and/or Token when issuing the API request.
23:07:20 <gontran> yeah, good ideas.  logs aren't giving me much. my api access is confirmed good for other parallel accounts.  really a stumper.