NCPA error on AIX 6.1

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: NCPA error on AIX 6.1

Post by benjaminsmith »

Hi @occ,

Sorry to hear that this is impacting your business and after discussing this in more depth, it's an issue with the underlying python packages used by NCPA. In particular, it's the disk partition/layout on this particular server that is causing the issue.

One suggestion would be to modify the main ncpa configuration file and set the following to:

Code: Select all

exclude_fs_types =
At this point, since AIX 6 is end-of-life, we are not providing continued bug fixes or new NCPA builds for this operating system. However, as Sean mentioned, there maybe are other workarounds here such as check_by_ssh or the NRPE agent we can explore.

Let me know if you have any questions.

Benjamin
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
occ
Posts: 43
Joined: Fri Jan 11, 2019 5:05 am

Re: NCPA error on AIX 6.1

Post by occ »

Since the error pointed out he was unable to get FS structure, we've figured out the problem could have been in /etc/filesystems structure.
Because of the error we had on out share source, the current entry in filesystems was commented like this :

Code: Select all

#/tmp:
#	dev		= /dev/hd3
#	vfs		= jfs2
#	log		= /dev/hd8
#	mount		= automatic
#	check		= false
#	vol		= /tmp
#	free		= false
After deleting all the commented rows the ncpa started succesfully.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: NCPA error on AIX 6.1

Post by scottwilkerson »

occ wrote:Since the error pointed out he was unable to get FS structure, we've figured out the problem could have been in /etc/filesystems structure.
Because of the error we had on out share source, the current entry in filesystems was commented like this :

Code: Select all

#/tmp:
#	dev		= /dev/hd3
#	vfs		= jfs2
#	log		= /dev/hd8
#	mount		= automatic
#	check		= false
#	vol		= /tmp
#	free		= false
After deleting all the commented rows the ncpa started succesfully.
Glad to hear you were able to get the agent to start successfully!

Locking thread
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
Locked