Mod Gearman GUI problems after upgrade to 2026R1.1

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
occ
Posts: 43
Joined: Fri Jan 11, 2019 5:05 am

Mod Gearman GUI problems after upgrade to 2026R1.1

Post by occ »

after updating nagiosxi, mod gearman it still works but the changes made by the GUI have no effect, using the "sync" button does write logs to the/usr/local/nagiosxi/var/nmg.log file but stops on "TASK [Check if Oracle plugin file exists locally] ******************************".
bbahn
Posts: 379
Joined: Thu Jan 12, 2023 5:42 pm

Re: Mod Gearman GUI problems after upgrade to 2026R1.1

Post by bbahn »

Hello @occ,

What version of XI did you upgrade from?
Actively advancing awesome answers with ardent alliteration, aptly addressing all ambiguities. Amplify your acumen and avail our amicable assistance. Eagerly awaiting your astute assessments of our advice.
gwesterman
Posts: 268
Joined: Wed Aug 23, 2023 11:29 am

Re: Mod Gearman GUI problems after upgrade to 2026R1.1

Post by gwesterman »

Can you provide the full output to nmg.log when you run sync?

Try adding become: false to the ansible.builtin.stat jobs in /usr/local/nagiosxi/html/config/nmg/ansible, e.g.

Code: Select all

# Oracle config file
    - name: Check if Oracle plugin file exists locally
      ansible.builtin.stat:
        path: /usr/local/nagiosxi/etc/configwizards/oracle/oracle
      become: false
      delegate_to: localhost
      register: oracle_file
There's 4 of them.

Thank you!
deficientamend
Posts: 1
Joined: Wed Dec 17, 2025 11:28 pm
Contact:

Re: Mod Gearman GUI problems after upgrade to 2026R1.1

Post by deficientamend »

I’ve run into the same situation before: Ansible tries to escalate privileges on the stat task and just hangs. Adding become: false to those ansible.builtin.stat jobs in /usr/local/nagiosxi/html/config/nmg/ansible cleared it up for me.
DoubleDoubleA
Posts: 272
Joined: Thu Feb 09, 2017 5:07 pm

Re: Mod Gearman GUI problems after upgrade to 2026R1.1

Post by DoubleDoubleA »

We'll have this fixed in the next XI release.

Aaron
Post Reply