Installation of Linux agent failed

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
mmoser
Posts: 7
Joined: Thu Aug 13, 2020 4:03 am

Installation of Linux agent failed

Post by mmoser »

I had downloaded the nagios-5.7.2-64.ova image and I am running that on a Windows 10 Enterprise laptop using VMware Workstation.

After initial setup I was trying to deploy my first agent on a Linux box running SUSE Enterprise. I entered the address, selected the OS type, entered my root credentials into the form but then I only got an error page stating:

FAILED - MODULE FAILURE See stdout/stderr for the exact error.

The console of the NagiosXI VM shows nothing. What stdout/stderr is meant here? How can I find out, why that agent installation failed?
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: Installation of Linux agent failed

Post by cdienger »

Run the following while you try to deploy again:

Code: Select all

tail -f  /usr/local/nagiosxi/var/cmdsubsys.log
It should show you something like:

Code: Select all

CMDLINE=php /usr/local/nagiosxi/scripts/deploy_run_job.php -j '3'
OUTPUT=
RETURNCODE=4
Try running the CMDLINE directly on the command line of the XI machine as nagios:

Code: Select all

su - nagios 
php /usr/local/nagiosxi/scripts/deploy_run_job.php -j '3'
The number passed with the -j argument will likely be different. Make sure to use whatever was logged int he cmdsubsys.log file.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
mmoser
Posts: 7
Joined: Thu Aug 13, 2020 4:03 am

Re: Installation of Linux agent failed

Post by mmoser »

Already the tail fails. There *is* no such file. Which - I presume - indicates, that already the login fails. Even though I am sure to pass it the exact credentials I am using myself to ssh into the box. And - yes - that's a login using uid&pwd, not using any keys.

Can one trigger the script (or whatever is executed by that form) manually? I tried to peek into the .php script and wanted to single-step it but that seems to be compiled or something. It's not readable text...

I then found the following summary:

Code: Select all

                   "hosts": {
                        "hostname_here": {
                            "_ansible_no_log": false, 
                            "action": "zypper", 
                            "changed": false, 
                            "exception": "Traceback (most recent call last):\r\n  
							File \"/root/.ansible/tmp/ansible-tmp-1597307430.26-17558-199103016661433/AnsiballZ_zypper.py\", line 102, in <module>\r\n
							_ansiballz_main()\r\n
							File \"/root/.ansible/tmp/ansible-tmp-1597307430.26-17558-199103016661433/AnsiballZ_zypper.py\", line 94, in _ansiballz_main\r\n
							invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\r\n
							File \"/root/.ansible/tmp/ansible-tmp-1597307430.26-17558-199103016661433/AnsiballZ_zypper.py\", line 40, in invoke_module\r\n
							runpy.run_module(mod_name='ansible.modules.packaging.os.zypper', init_globals=None, run_name='__main__', alter_sys=True)\r\n
							File \"/usr/lib64/python2.7/runpy.py\", line 176, in run_module\r\n
							fname, loader, pkg_name)\r\n  File \"/usr/lib64/python2.7/runpy.py\", line 82, in _run_module_code\r\n
							mod_name, mod_fname, mod_loader, pkg_name)\r\n
							File \"/usr/lib64/python2.7/runpy.py\", line 72, in _run_code\r\n
							exec code in run_globals\r\n
							File \"/tmp/ansible_zypper_payload_w5Pfyo/ansible_zypper_payload.zip/ansible/modules/packaging/os/zypper.py\", line 195, in <module>\r\n
							ImportError: No module named xml\r\n", 
                            "failed": true, 
                            "module_stderr": "Shared connection to hostname_here closed.\r\n", 
                            "module_stdout": "Traceback (most recent call last):\r\n
							File \"/root/.ansible/tmp/ansible-tmp-1597307430.26-17558-199103016661433/AnsiballZ_zypper.py\", line 102, in <module>\r\n
							_ansiballz_main()\r\n
							File \"/root/.ansible/tmp/ansible-tmp-1597307430.26-17558-199103016661433/AnsiballZ_zypper.py\", line 94, in _ansiballz_main\r\n
							invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\r\n
							File \"/root/.ansible/tmp/ansible-tmp-1597307430.26-17558-199103016661433/AnsiballZ_zypper.py\", line 40, in invoke_module\r\n
							runpy.run_module(mod_name='ansible.modules.packaging.os.zypper', init_globals=None, run_name='__main__', alter_sys=True)\r\n
							File \"/usr/lib64/python2.7/runpy.py\", line 176, in run_module\r\n
							fname, loader, pkg_name)\r\n  File \"/usr/lib64/python2.7/runpy.py\", line 82, in _run_module_code\r\n
							mod_name, mod_fname, mod_loader, pkg_name)\r\n  File \"/usr/lib64/python2.7/runpy.py\", line 72, in _run_code\r\n
							exec code in run_globals\r\n
							File \"/tmp/ansible_zypper_payload_w5Pfyo/ansible_zypper_payload.zip/ansible/modules/packaging/os/zypper.py\", line 195, in <module>\r\n
							ImportError: No module named xml\r\n", 
                            "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", 
                            "rc": 1
                        }
                    }, 
Does that bring us any further?
Sigh! I though I was going to install a monitoring tool, not debug a monitoring tool...
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: Installation of Linux agent failed

Post by benjaminsmith »

HI,

Looking over that log output, you might be hitting this issue:

https://lists.opensuse.org/opensuse-bug ... 04383.html

Let's try to install python-xml on this host, and let me know if that resolves the issues.

https://software.opensuse.org/package/python-xml

Otherwise, let us know what version of Enterprise SUSE you're using so we can try to replicate this on our end.

Thanks,
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!
Locked