ACDC sup command output device

106 views
Skip to first unread message

Mike Montgomery

unread,
Jun 16, 2017, 10:18:52 AM6/16/17
to 2600hz...@googlegroups.com
We are gradually figuring out how to implement ACDc.

During the debug we are attempting to use the acdc_agent_maintenance and acdc_maintenance sup commands from the console and find that the only output we get from these commands is an “ok”.

Looking into it further we find that the command outputs to kazoo.log instead of the console.

How can we redirect the output of these commands to the console?

Example:

console
[user@kazoo ~]# sup acdc_maintenance agents_detail
ok

kazoo.log
Jun 16 12:58:28 kazoo 2600hz[23116]: |016aead0-8ec8-421b-8fe3-7f6b5b6602d3|kz_nodes:570 (<0.1155.0>) VM sup_...@kazoo.example.com is now connected:
Jun 16 12:58:28 kazoo 2600hz[23116]: |016aead0-8ec8-421b-8fe3-7f6b5b6602d3|kz_nodes:571 (<0.1155.0>) node_type: hidden
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agents_sup:49 (<0.2956.7>) ACDc Agents Status
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:66 (<0.2957.7>) Agent 531e1058608d6d17bc61173356ed19e6 (Account 542d2a397a248001738957bc766f952a)
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:67 (<0.2957.7>) Supervisor: <0.26447.0>
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:68 (<0.2957.7>) Listener: <0.26448.0> (kazoo...@kazoo.example.com-<0.26448.0>-884f70e0)
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:69 (<0.2957.7>) FSM: <0.26449.0>
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:87 (<0.2957.7>) first_name: B
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:87 (<0.2957.7>) last_name: User
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:87 (<0.2957.7>) username: bu...@example.com
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:87 (<0.2957.7>) email: bu...@example.com
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:87 (<0.2957.7>) state: ready
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:66 (<0.2957.7>) Agent 2455133708d6ce051e813ba03ffa799e (Account 542d2a397a248001738957bc766f952a)
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:67 (<0.2957.7>) Supervisor: <0.2757.0>
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:68 (<0.2957.7>) Listener: <0.2758.0> (kazoo...@kazoo.example.com-<0.2758.0>-2a7dbafa)
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:69 (<0.2957.7>) FSM: <0.2764.0>
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:87 (<0.2957.7>) first_name: New
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:87 (<0.2957.7>) last_name: User
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:87 (<0.2957.7>) username: new...@example.com
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:87 (<0.2957.7>) email: new...@example.com
Jun 16 12:58:28 kazoo 2600hz[23116]: |acdc_maintenance|acdc_agent_sup:87 (<0.2957.7>) state: ready
Jun 16 12:58:28 kazoo 2600hz[23116]: |016aead0-8ec8-421b-8fe3-7f6b5b6602d3|kz_nodes:563 (<0.1155.0>) VM sup_...@kazoo.example.com is no longer connected:
Jun 16 12:58:28 kazoo 2600hz[23116]: |016aead0-8ec8-421b-8fe3-7f6b5b6602d3|kz_nodes:564 (<0.1155.0>) nodedown_reason: connection_closed


Best Regards,

Mike Montgomery
919 539 6133




James Aimonetti

unread,
Jun 16, 2017, 10:43:15 AM6/16/17
to 2600hz...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I suspect your console log level is info or higher and these are debug
messages. You'll either need to set console to debug (and the flood of
messages that entails) or you can change the lager:debug(...) to
lager:info(...). The log lines below have the module and line numbers of
where the lager lines are.
- --
James Aimonetti

Lead Systems Architect
"If Dialyzer don't care, I don't care"
2600HzPDX | http://2600hz.com
sip:ja...@2600hz.com
tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEvSh+xZ5hP1H8lVIU1Mpr4k9cJWAFAllD7ncACgkQ1Mpr4k9c
JWBqxQf/QtJS9w6nk074fwoZ0pZ/TNaKfHPM2eLEPN6616XSgd+s019UguXcMSCC
7m8RNJS19xKjzPwUkA0dDqsbg7XEqNVoOxqdKVPD/n1q8yrNRZN8c9aNEC3II07T
vs4vz63JY58nVhHwySGXKqtpv3TSr+DD0PHnOiPQ9SDxt9y3HGYF+3loa4SJr0zr
VvaoooWw1PS6n8P6qQPDLIZph3V1YTC8Kfx6FCetCnWa8I4wKOc2fTwzW4KSaZYB
PUVgMfsjRkAIMruw2R6nUInTtTwO68EFcQfwHaGLU2u33DC1qND3Rp0X5a/3aD91
j0YhWT+SXFYyTYPbdVT4CSxrxL83eg==
=qf2V
-----END PGP SIGNATURE-----

pierre

unread,
Jun 28, 2017, 3:23:44 PM6/28/17
to 2600hz-users
Reply all
Reply to author
Forward
0 new messages