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

Access Points at high elevation are not being honored to represent site, random hosts within the site show instead #13

Open
squad1534 opened this issue Aug 2, 2020 · 3 comments

Comments

@squad1534
Copy link

squad1534 commented Aug 2, 2020

Debian Buster
Cacti 1.2.2
PHP 7.0
GPSMAP 2.1

As I've added more sites GPSMAP seems to behave less predictably. Devices templated as AP's no longer represent the site and hosts at high elevation. Hosts within the site now populate the high elevation map (see ms393 tooltip and red pin), and due to the various states those hosts could be in my map looks like a bowl of fruit loops. The only changes I've made to the system are periodic "apt-get updates" which pull the latest stable system updates, e.g. php, maria, kernel updates, etc. Any ideas?

I'd be happy to supply any additional info upon request.
Respectfully,
Chip

@TheWitness
Copy link
Member

I'm sorry, I'm still stuck on Fruit Loops. That was too funny. Can you do some mock-up of what you would like?

@squad1534
Copy link
Author

squad1534 commented Aug 5, 2020 via email

@squad1534
Copy link
Author

My AP's use the Map Template and designate facilities spread out across the US, when you drill down into a AP you see the hosts which belong to another Template. In the process of updating my Cacti hosts I deleted several that belonged to various AP's/Facilities, this action cleared up the issue I was having with gpsmap having a problem with just showing the AP/Facility at high elevation, host pins in their various up/down colored states would appear instead of the blue AP pin. Not sure what the issue was, it may have been related to hosts that had been 'down' for a long time, I have no way of knowing. Just following up here, in the end gpsmap is back working fine and behaving as expected.

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