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