Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UniFi AP Retries Reporting Stopped Working Again #129

Open
jordanwmcdonald opened this issue Feb 13, 2025 · 1 comment
Open

UniFi AP Retries Reporting Stopped Working Again #129

jordanwmcdonald opened this issue Feb 13, 2025 · 1 comment

Comments

@jordanwmcdonald
Copy link

Separate, but similar issue to my previous report.

CONFIGURATION

  • VM: Ubuntu 24.04.2 LTS Server x86_x64 6.8.0-53-generic
  • Zabbix Server: 7.0.9
  • UniFi Dream Machine Pro: 4.1.1.3
  • UniFi Network Application: 9.0.114

ISSUE

  • Everything works except for the Wi-Fi Retries Items across all three U6 Enterprise APs.
  • /var/log/zabbix/zabbix_server.log and /tmp/mcaDumpShort.err are both empty.

ATTEMPTED RESOLUTIONS

  • Observed the previously mentioned log files
  • Manually ran mca dumps while directly SSH'd into each AP -- it appears that UniFi has changed the way the pertinent information is presented within the dump. The current JSONPath of $.vap_table[?(@.radio == '{#RADIO_NAME}')].tx_retries.first() accurately returns the value 0 as it is first in dump, but there are now additional values returned. I tried multiple times to modify the JSONPath into something that would take the highest value (not sure if that is even the correct value), but failed. I contemplated making a custom preprocessing script and, separately, making an awk/grep script, but figured I should reach out to you first. See below:

mca-dump | jq '.vap_table[] | {type: type, radio, tx_retries}?'
{
"type": "object",
"radio": "6e",
"tx_retries": 0
}
{
"type": "object",
"radio": "6e",
"tx_retries": 158673
}
{
"type": "object",
"radio": "na",
"tx_retries": 0
}
{
"type": "object",
"radio": "na",
"tx_retries": 136969
}
{
"type": "object",
"radio": "ng",
"tx_retries": 0
}
{
"type": "object",
"radio": "ng",
"tx_retries": 51768
}
{
"type": "object",
"radio": "ng",
"tx_retries": 1684
}

@patricegautier
Copy link
Owner

good catch - what model of AP is this, and what firmware is it running?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants