Page 1 of 1

NCPA 1.7.2 issue

Posted: Mon Mar 23, 2015 10:44 am
by mon-team
Hi guys,

We are using ncpa wizard version 1.3 on nagiosxi to monitor remoted servers.

We noticed that installing ncpa-1.7.2.el6.x86_64.rpm and ncpa-1.7.2.el7.centos.x86_64.rpm respectively on monitored machine cent0s6.x and Cent0s7.x, we don't see any information about services.
Having a look to the page http://host:5693/api/ , we get this:
{
"value": {
"root": {
"services": [],
"processes": [],

How can we overcome to this problem?

We also find this post https://github.com/NagiosEnterprises/ncpa/issues/140 about a bug with ncpa1.7.2 on cent0s7. Can we upgrade to 1.8?

Thank in advance for your quick response.

Best Regards

Re: NCPA 1.7.2 issue

Posted: Mon Mar 23, 2015 11:11 am
by ssax
Can you view them with this url? https://HOST:5693/api/services

Re: NCPA 1.7.2 issue

Posted: Mon Mar 23, 2015 11:21 am
by lmiltchev
We noticed that installing ncpa-1.7.2.el6.x86_64.rpm and ncpa-1.7.2.el7.centos.x86_64.rpm respectively on monitored machine cent0s6.x and Cent0s7.x, we don't see any information about services.
Are you having issues with CentOS 7 ONLY or with both, CentOS 6 and 7? I have ncpa 1.7.2 installed on CentOS 6 and I can see the services.

Code: Select all

{
  "value": {
    "services": {
      "blk-availability": "stopped", 
      "cgconfig": "stopped", 
      "lvm2-lvmetad": "stopped", 
      "mod_gearman_worker": "running", 
      "lvm2-monitor": "stopped", 
      "rdisc": "stopped", 
      "auditd": "running", 
      "ncpa_listener": "stopped", 
      "nagios": "running", 
      "udev-post": "stopped", 
      "netfs": "stopped", 
      "single": "stopped", 
      "rsyslog": "running", 
      "snmpd": "running", 
      "netconsole": "stopped", 
      "htcacheclean": "stopped", 
      "svnserve": "stopped", 
      "restorecond": "stopped", 
      "functions": "stopped", 
      "network": "stopped", 
      "ntpdate": "stopped", 
      "messagebus": "stopped", 
      "httpd": "running", 
      "npcd": "running", 
      "killall": "stopped", 
      "saslauthd": "stopped", 
      "ndo2db": "running", 
      "ntpd": "running", 
      "iptables": "stopped", 
      "halt": "stopped", 
      "sendmail": "running", 
      "nagiosxi": "running", 
      "qpidd": "running", 
      "ajaxterm": "running", 
      "xinetd": "running", 
      "snmptt": "stopped", 
      "dnxcld": "stopped", 
      "crond": "running", 
      "ktune": "stopped", 
      "sshd": "running", 
      "postgresql": "stopped", 
      "ip6tables": "stopped", 
      "cgred": "stopped", 
      "vsftpd": "running", 
      "postfix": "stopped", 
      "snmptrapd": "running", 
      "sysstat": "running", 
      "tuned": "stopped", 
      "sandbox": "stopped", 
      "mysqld": "running", 
      "ncpa_passive": "stopped"
    }
  }
}
Don't you see the services on the CentOS 6 box, when you go to:

Code: Select all

https://host:5693/api/services
I will talk to our developers to see when 1.8 for Linux will be available for download.

Re: NCPA 1.7.2 issue

Posted: Thu Mar 26, 2015 12:39 pm
by mon-team
You are right.
Anything ok with Cent0s 6 while the installation of ncpa1.7.2 fails on Cent0s 7.

Can you please tell us how long will it take to get available the latest version 1.8 for linux?

Thanks
BR

Re: NCPA 1.7.2 issue

Posted: Thu Mar 26, 2015 1:10 pm
by lmiltchev
Can you please tell us how long will it take to get available the latest version 1.8 for linux?
Unfortunately, I don't have an ETA. I believe NCPA 1.8 for LInux *should* be out in a few weeks but I could be wrong. It up to the developers.

Re: NCPA 1.7.2 issue

Posted: Mon May 11, 2015 2:55 am
by mon-team
Hello guys,

I installed version 1.8.1 NCPA on centos 7 but if I go to the url
https://HOST:5693/api/service or https://HOST:5693/api/services

I have this

{
   "value": {
     "services": {}
   }
}

ideas to solve?

Re: NCPA 1.7.2 issue

Posted: Mon May 11, 2015 10:24 am
by lmiltchev
I was able to recreate the issue, and I saw that it is already reported on GitHub:

https://github.com/NagiosEnterprises/ncpa/issues/176

Our developers are aware of it. I expect this to be fixed in the next version of NCPA.