LMA-Infrastructure-Alerting plugin nagios web returns 404 when combining roles
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel Plugins |
Fix Committed
|
High
|
Swann Croiset | ||
Bug Description
Description: When combining all LMA roles(influxdb_
Version found: Fuel 7.0 nightly build number: 131
Steps to reproduce:
1. Enable all LMA related plugins built with latest master branches (2015-09-15)
2. Create an environment with LMA collector with a single node containing all LMA roles
3. Deploy environment
Current result:
Accessing 10.20.0.10/nagios3/ returns a 404
Accessing 10.20.0.10:8001 shows the web ui, but documentation doesn't mention this.
Expected result:
10.20.0.10/nagios3 to be working or update the documentation
Inititial investigation
When combining the roles on a single node then nginx is already running on port 80 to serve kibana. Nagios is configured to use apache but apache can't bind to port 80 because nginx is already bound to 80?
| summary: |
- LMA-Infrastructure-Alerting plugin nagios web 404 + LMA-Infrastructure-Alerting plugin nagios web returns 404 when combining + roles |
| description: | updated |
| tags: | added: feature-plugins |
| Changed in fuel: | |
| assignee: | nobody → Fuel Plugins Bugs (fuel-plugins-bugs) |
| Changed in fuel: | |
| assignee: | Fuel Plugins Bugs (fuel-plugins-bugs) → LMA-Toolchain Fuel Plugins (mos-lma-toolchain) |
| status: | New → Confirmed |
| tags: | added: lma |
| affects: | fuel → fuel-plugins |
| Changed in fuel-plugins: | |
| assignee: | LMA-Toolchain Fuel Plugins (mos-lma-toolchain) → nobody |
| assignee: | nobody → LMA-Toolchain Fuel Plugins (mos-lma-toolchain) |
| Changed in fuel-plugins: | |
| importance: | Undecided → High |
| milestone: | none → 7.0 |
| Swann Croiset (swann-w) wrote | #1 |
| Swann Croiset (swann-w) wrote | #2 |
| Changed in fuel-plugins: | |
| status: | Confirmed → Fix Committed |
| assignee: | LMA-Toolchain Fuel Plugins (mos-lma-toolchain) → Swann Croiset (swann-w) |
Thanks for the report.
In fact the HTTP port is always 8001 even when deployed alone (w/o other LMA plugin roles).
I'll update the README . The user guide will contain the info as well.