adding a map in "view"

[mskufca]

Moderator Edit: This thread has been split from another - https://support.nagios.com/forum/viewto ... =6&t=45787
In the future, please create a new thread and link to the old one instead of adding on.

Hi,

Same problem here.
Happened after upgrade of NagiosXI to latest stable last week. (Did not notice it at once )
Only happens if you click link to views linked to nagvis maps.
Rotation is working ok even with those problematic nagvis views.

Something similar is mentioned here
https://monitoring-portal.org/index.php ... us-issues/

Hope this helps you to troubleshoot this issue.

br
m.

[kyang]

Is the issue specifically for adding a map in views?

Only happens if you click link to views linked to nagvis maps.

Could you explain this a bit more or show us a screenshot? OR is it the same error.

What steps did you take when you received your issue? I would like to try to replicate this.

[mskufca]

Hi,

Sorry I cannot post image due business restrictions.
I had working NagiosXI setup with a few nagvis maps.
Those nagvis maps were posted as views inside NagiosXI.
I did an upgrade to latest version of NagiosXI and I got this issue (see attached picture).

Wierd thing is that if I open Views (top menu), the first view (nagvis map) is shown ok, but if I select (click) the same View from left menu I get an error.

Hope this explains the situation.

br
m.

[mskufca]

Hi,

I did a bit of troubleshooting and found that views somehow corrupt link:
Not working link I get from:
"https://host/nagvis/frontend/nagvis-js/ ... ow=mapname"

This is working link I made by hand from nagvis ini directions var "mapurl".
"https://host/nagvis/frontend/nagvis-js/ ... ow=mapname"

seems that there is a problem in "amp;" that are inserted two times and corrupts link.

Hope this helps.

br
m.

[dwhitfield]

The linked issue is almost 8 years old. I'd be surprised if there were related, but let's take a look at some things.

What's the outupt of php -v?

Also, can you PM me your Profile? You can download it by going to Admin > System Config > System Profile and click the ***Download Profile*** button towards the top. If for whatever reason you *cannot* download the profile, please put the output of View System Info (5.3.4+, Show Profile if older) in the thread (that will at least get us some info). This will give us access to many of the logs we would otherwise ask for individually. If security is a concern, you can unzip the profile take out what you like, and then zip it up again. We may end up needing something you remove, but we can ask for that specifically.

You can also generate a profile manually using the script at /usr/local/nagiosxi/html/includes/components/profile/getprofile.sh

That should generate a profile in /usr/local/nagiosxi/var/components/ which you can get off the server with an application such as FileZilla.

After you PM the profile, please update this thread. Updating this thread is the only way for it to show back up on our dashboard.

If you get an error that PROFILE BUILD FAILED, please see https://support.nagios.com/kb/article.p ... ategory=44

[mskufca]

Hi,

Here is output of "View System Info".
The rest is a bit problematic to get. Can you please specify more exactly what you need and I will try to get it.

Nagios XI - System Info
System:
Nagios XI Version : 5.4.10
realhostname.corp.company.biz 2.6.32-642.13.1.el6.x86_64 x86_64
CentOS release 6.9 (Final)
Gnome is not installed

Apache Information
PHP Version: 5.3.3
Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Server Name: upsn.corp.company.biz
Server Address: 172.17.x.x
Server Port: 443

Date/Time
PHP Timezone: Europe/Ljubljana
PHP Time: Fri, 27 Oct 2017 20:44:31 +0200
System Time: Fri, 27 Oct 2017 20:44:31 +0200

Nagios XI Data
License ends in: NUONMO

nagios (pid 129056) is running...
NPCD running (pid 1999).
ndo2db (pid 128143) is running...
CPU Load 15: 0.36
Total Hosts: 38
Total Services: 1010
Function 'get_base_uri' returns: https://upsn.corp.company.biz/nagiosxi/
Function 'get_base_url' returns: https://upsn.corp.company.biz/nagiosxi/
Function 'get_backend_url(internal_call=false)' returns: https://upsn.corp.company.biz/nagiosxi/ ... rofile.php
Function 'get_backend_url(internal_call=true)' returns: https://localhost/nagiosxi/backend/

Ping Test localhost
Running: /bin/ping -c 3 localhost 2>&1
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.030 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.029 ms

--- localhost ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.029/0.030/0.031/0.000 ms

Test wget To localhost
WGET From URL: https://localhost/nagiosxi/includes/components/ccm/
Running: /usr/bin/wget https://localhost/nagiosxi/includes/components/ccm/
--2017-10-27 20:44:33-- https://localhost/nagiosxi/includes/components/ccm/
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:443... connected.
ERROR: cannot verify localhost's certificate, issued by "/DC=biz/DC=company/DC=corp/CN=Company CA 2":
Self-signed certificate encountered.
ERROR: no certificate subject alternative name matches
requested host name "localhost".
To connect to localhost insecurely, use '--no-check-certificate'.

Network Settings
1: lo: mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever

2: eth0: mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:50:56:3f:00:11 brd ff:ff:ff:ff:ff:ff
inet 172.17.x.x/23 brd 172.17.7.255 scope global eth0
inet6 fe80::250:56ff:fe3f:11/64 scope link
valid_lft forever preferred_lft forever

172.17.x.0/23 dev eth0 proto kernel scope link src 172.17.x.x
169.254.0.0/16 dev eth0 scope link metric 1002
default via 172.17.x.1 dev eth0

br
m.

[dwasswa]

Hi @ mskufca,

Apparently, this is a security issue and is fixed in Nagios XI version 5.4.11 which is coming out next week.

I suggest that you upgrade your system from Nagios XI version 5.4.10 to Nagios XI version 5.4.11 and let me know if that issue persists.