Nagios XI 2024 installation error

[schadalawada]

When I am trying to install NAgiosXI2024 on new RHEL 9 VM, I got the following error

Running './D-chkconfigalldaemons'...
Error: Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/firewall/client.py", line 50, in _impl
return func(*args, **kwargs)
File "/usr/lib/python3.9/site-packages/firewall/client.py", line 3141, in get_property
return dbus_to_python(self.fw_properties.Get(
AttributeError: 'NoneType' object has no attribute 'Get'

Created symlink /etc/systemd/system/multi-user.target.wants/nagios.service → /usr/lib/systemd/system/nagios.service.
Created symlink /etc/systemd/system/multi-user.target.wants/npcd.service → /etc/systemd/system/npcd.service.
Created symlink /etc/systemd/system/multi-user.target.wants/mysqld.service → /usr/lib/systemd/system/mysqld.service.
Created symlink /etc/systemd/system/multi-user.target.wants/httpd.service → /usr/lib/systemd/system/httpd.service.
Created symlink /etc/systemd/system/multi-user.target.wants/php-fpm.service → /usr/lib/systemd/system/php-fpm.service.
Created symlink /etc/systemd/system/multi-user.target.wants/postfix.service → /usr/lib/systemd/system/postfix.service.
Job for postfix.service failed because the control process exited with error code.
See "systemctl status postfix.service" and "journalctl -xeu postfix.service" for details.
RESULT=1

===================
INSTALLATION ERROR!
===================
Installation step failed - exiting.
Check for error messages in the install log (install.log).

If you require assistance in resolving the issue, please include install.log
in your communications with Nagios XI technical support.

Please take a look and suggest a solution to overcome this.Thanks

The script that failed was: './D-chkconfigalldaemons'

[danderson]

Thanks for reaching out @schadalawada

What is the output from journalctl -xeu postfix.service?

[schadalawada]

Jan 10 14:28:19 dp01nagios01 systemd[1]: postfix.service: Control process exite>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ An ExecStart= process belonging to unit postfix.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jan 10 14:28:19 dp01nagios01 systemd[1]: postfix.service: Failed with result 'e>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit postfix.service has entered the 'failed' state with result 'exit-co>
Jan 10 14:28:19 dp01nagios01 systemd[1]: Failed to start Postfix Mail Transport>
░░ Subject: A start job for unit postfix.service has failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ A start job for unit postfix.service has finished with a failure.
░░
░░ The job identifier is 6790 and the job result is failed.

[jmichaelson]

Coming back to this, what happens if you run /usr/sbin/postfix start in a shell prompt?

[schadalawada]

# /usr/sbin/postfix start
postfix: fatal: parameter inet_interfaces: no local interface found for ::1

[cnorell]

schadalawada,

I believe that error indicates the postfix service can't find an interface for the IP (in this case the loopback interface) it's configured to listen on. It might be worth looking into the postfix config, found at:

Code: Select all

/etc/postfix/main.cf

. I can't speak to the security of this solution, but you may be able to change:

Code: Select all

inet_interfaces = localhost

To:

Code: Select all

inet_interfaces = any

To see if that will get you past the error. However, if it's a brand new server you haven't changed any configs on it seems unlikely that the config file would be malformed.

Best Regards,

Cory Norell