Nagios Support Forum

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: 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

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 :
After deleting all the commented rows the ncpa started succesfully.

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