FUSION: Unable to Map to xi users (no mapping)

This support forum board is for questions relating to Nagios Fusion.
User avatar
inversecow
Posts: 44
Joined: Wed Sep 25, 2019 4:17 pm

Re: FUSION: Unable to Map to xi users (no mapping)

Post by inversecow »

Good morning and thank you for your continued review.

Happy to run the query (looks like the tail end was missing so I made a "leap").
The original syntax returned an error, but I guessed at what you were after, and checked the API docs.
Do let me know if you had something different in mind.

NOTE: This did return all 117 LDAP user records from xi (no errors apparent), I trimmed and sanitized it for general consumption.

Code: Select all

[user@fusionnode ~]
# curl  --cacert /usr/local/nagiosfusion/var/certs/ca_root.cer \
> -XGET "http://xi_node_name/nagiosxi/api/v1/system/user?fusekey=FUSE_KEY_HERE&outputtype=xml&user=nagiosadmin"
{"records":117,"users":[{"user_id":"117","username":"user1","name":"One, User","email":"user1@domain.tld","enabled":"1"},{"user_id":"116","username":"user2","name":"Two, User","email":"user2@domain.tld","enabled":"1"},{"user_id":"1","username":"nagiosadmin","name":"Nagios Administrator","email":"admin@domain.tld","enabled":"1"}]}
Indeed, I had previously set the FUSION instance to DEBUG logging level (via the WebGUI: Admin > System Configuration > System Settings).
As an aside I did note "odd behavior" when checking the Fusion logs via the WebGUI (page numbers seem to change in order, etc.)
Good to know where they live on the FS to check instead.

I do observe a number of the below sort of WARN message in the fusion log (perhaps this is relevant?)
Otherwise there did not appear to be much of note.

# /usr/local/nagiosfusion/var/log/fusion.log

Code: Select all

...
[2019-10-03 07:46:01] [SYSTEM] [WARN] [xi_node_name]: poll_subsys(): Lock exists for user:nagiosadmin, bailing out
...
# /usr/local/nagiosfusion/var/log/fusion.debug

Code: Select all

...
[2019-10-03 09:18:03] [SYSTEM] [DEBUG] [xi_node_name]: poll_master(): Not yet time to poll server, polled_time: 1570119478
[2019-10-03 09:18:03] [SYSTEM] [DEBUG] [xi_node_name]: poll_master(): executing: /usr/local/nagiosfusion/cron/poll_subsys.php --server="4" --user="user1" >/usr/local/nagiosfusion/var/log/poll_subsys.4.user1.log 2>&1 &
[2019-10-03 09:18:03] [SYSTEM] [DEBUG] [xi_node_name]: poll_master(): Not yet time to poll server, polled_time: 1570119427
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: poll_subsys() called at 1570119484
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: poll_subsys(): using php memory limit: 1024M
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/bpi?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/hoststatus?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:0?brevity=1
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/hoststatus?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:1000&brevity=1
[2019-10-03 09:18:04] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/servicestatus?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:0?brevity=1
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: runtime: 1 seconds
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/servicestatus?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:1000&brevity=1
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/logentries?logentry_type=in:1024,2048,4096,8192,32768,65536,16384&fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&starttime=1570119423&endtime=1570119484
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/hostgroupmembers?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:0
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/hostgroupmembers?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:1000
[2019-10-03 09:18:05] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/hostgroup?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:0
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: runtime: 1 seconds
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/hostgroup?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:1000
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: IOSTAT: ( [user] => 3.81, [nice] => 0.00, [system] => 3.21, [iowait] => 0.15, [steal] => 0.00, [idle] => 92.83 )
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/servicegroup?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:0
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/servicegroup?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:1000
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: IOSTAT: ( [user] => 2.20, [nice] => 0.00, [system] => 1.95, [iowait] => 0.15, [steal] => 0.00, [idle] => 95.69 )
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/servicegroupmembers?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:0
[2019-10-03 09:18:06] [SYSTEM] [DEBUG]: runtime: 0 seconds
[2019-10-03 09:18:07] [SYSTEM] [DEBUG]: live_data_timeout: 45
[2019-10-03 09:18:07] [SYSTEM] [DEBUG]: URL: https://xi_node_name/nagiosxi/api/v1/objects/servicegroupmembers?fusekey=FUSE_KEY_HERE&outputtype=xml&user=user1&records=1000:1000
[2019-10-03 09:18:07] [SYSTEM] [DEBUG]: runtime: 1 seconds
[2019-10-03 09:18:07] [SYSTEM] [DEBUG] [xi_node_name]: poll_master(): Server using polling interval 60
[2019-10-03 09:18:07] [SYSTEM] [DEBUG] [xi_node_name]: poll_master(): Not yet time to poll server, polled_time: 1570119449
...
“And who better understands the Unix-nature?” Master Foo asked.
“Is it he who writes the ten thousand lines, or he who, perceiving the emptiness of the task, gains merit by not coding?”
Master Foo - The ten thousand Lines
Unix Koans of Master Foo
Top
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: FUSION: Unable to Map to xi users (no mapping)

Post by benjaminsmith »

Hello,

Thank you for the logs and running the last command.
curl --cacert /usr/local/nagiosfusion/var/certs/ca_root.cer \
What we're noticing is the use of the --cacert option when running the commands. Are you able to run the same query without this option and get a response as this would not be utilized by Fusion?

It would also be helpful to see the Apache log from the xi server. Would you be able to retrieve this from the xi server ( you could also just send over the system profile if that's easier)? Thanks.

Code: Select all

/var/log/httpd/error_log
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!
Top
User avatar
inversecow
Posts: 44
Joined: Wed Sep 25, 2019 4:17 pm

Re: FUSION: Unable to Map to xi users (no mapping)

Post by inversecow »

Good afternoon,

Thanks for the continued eyes on this matter.

Apologies, I had enabled HTTPS some time back and "got used" to using that string as part of API calls when doing things on the CLI.
I will be mindful of this when executing further syntax.

As requested, I re-ran without the "--cacert" part of the syntax, and received successful output (same as was posted previously).

With regards to the Apache log (nothing exciting that I observed).
Do let me know if you want any other logs or levels adjusted (EG: debugging).

# current rotation

Code: Select all

[user@xi_node_name ~]
# cat /var/log/httpd/error_log
[Sun Sep 29 03:42:02.128915 2019] [auth_digest:notice] [pid 77927] AH01757: generating secret for digest authentication ...
[Sun Sep 29 03:42:02.129808 2019] [lbmethod_heartbeat:notice] [pid 77927] AH02282: No slotmem from mod_heartmonitor
[Sun Sep 29 03:42:02.186532 2019] [mpm_prefork:notice] [pid 77927] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Sun Sep 29 03:42:02.186556 2019] [core:notice] [pid 77927] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
# last rotation

Code: Select all

[user@xi_node_name ~]
# cat /var/log/httpd/error_log-20190929
[Mon Sep 23 12:08:07.842144 2019] [suexec:notice] [pid 5895] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Sep 23 12:08:07.877807 2019] [auth_digest:notice] [pid 5895] AH01757: generating secret for digest authentication ...
[Mon Sep 23 12:08:07.878485 2019] [lbmethod_heartbeat:notice] [pid 5895] AH02282: No slotmem from mod_heartmonitor
[Mon Sep 23 12:08:07.940644 2019] [mpm_prefork:notice] [pid 5895] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Mon Sep 23 12:08:07.940693 2019] [core:notice] [pid 5895] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon Sep 23 12:08:09.608717 2019] [mpm_prefork:notice] [pid 5895] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Sep 23 12:08:10.705437 2019] [suexec:notice] [pid 6105] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Sep 23 12:08:10.741322 2019] [auth_digest:notice] [pid 6105] AH01757: generating secret for digest authentication ...
[Mon Sep 23 12:08:10.741994 2019] [lbmethod_heartbeat:notice] [pid 6105] AH02282: No slotmem from mod_heartmonitor
[Mon Sep 23 12:08:10.802317 2019] [mpm_prefork:notice] [pid 6105] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Mon Sep 23 12:08:10.802354 2019] [core:notice] [pid 6105] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon Sep 23 12:08:34.571947 2019] [mpm_prefork:notice] [pid 6105] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Sep 23 12:08:35.687051 2019] [suexec:notice] [pid 8327] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Sep 23 12:08:35.722058 2019] [auth_digest:notice] [pid 8327] AH01757: generating secret for digest authentication ...
[Mon Sep 23 12:08:35.722706 2019] [lbmethod_heartbeat:notice] [pid 8327] AH02282: No slotmem from mod_heartmonitor
[Mon Sep 23 12:08:35.786106 2019] [mpm_prefork:notice] [pid 8327] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Mon Sep 23 12:08:35.786142 2019] [core:notice] [pid 8327] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon Sep 23 12:08:43.144962 2019] [mpm_prefork:notice] [pid 8327] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Sep 23 12:08:44.243805 2019] [suexec:notice] [pid 8538] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Sep 23 12:08:44.280319 2019] [auth_digest:notice] [pid 8538] AH01757: generating secret for digest authentication ...
[Mon Sep 23 12:08:44.281017 2019] [lbmethod_heartbeat:notice] [pid 8538] AH02282: No slotmem from mod_heartmonitor
[Mon Sep 23 12:08:44.344038 2019] [mpm_prefork:notice] [pid 8538] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Mon Sep 23 12:08:44.344077 2019] [core:notice] [pid 8538] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon Sep 23 12:08:49.369941 2019] [mpm_prefork:notice] [pid 8538] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Sep 23 12:08:50.467725 2019] [suexec:notice] [pid 8908] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Sep 23 12:08:50.504466 2019] [auth_digest:notice] [pid 8908] AH01757: generating secret for digest authentication ...
[Mon Sep 23 12:08:50.505193 2019] [lbmethod_heartbeat:notice] [pid 8908] AH02282: No slotmem from mod_heartmonitor
[Mon Sep 23 12:08:50.567596 2019] [mpm_prefork:notice] [pid 8908] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Mon Sep 23 12:08:50.567630 2019] [core:notice] [pid 8908] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon Sep 23 12:09:44.727280 2019] [mpm_prefork:notice] [pid 8908] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Sep 23 12:10:29.496128 2019] [suexec:notice] [pid 2303] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Sep 23 12:10:29.539459 2019] [auth_digest:notice] [pid 2303] AH01757: generating secret for digest authentication ...
[Mon Sep 23 12:10:29.540188 2019] [lbmethod_heartbeat:notice] [pid 2303] AH02282: No slotmem from mod_heartmonitor
[Mon Sep 23 12:10:30.190553 2019] [mpm_prefork:notice] [pid 2303] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Mon Sep 23 12:10:30.190599 2019] [core:notice] [pid 2303] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon Sep 23 12:15:43.541618 2019] [mpm_prefork:notice] [pid 2303] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Sep 23 12:15:49.638196 2019] [suexec:notice] [pid 4788] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Sep 23 12:15:49.674924 2019] [auth_digest:notice] [pid 4788] AH01757: generating secret for digest authentication ...
[Mon Sep 23 12:15:49.675608 2019] [lbmethod_heartbeat:notice] [pid 4788] AH02282: No slotmem from mod_heartmonitor
[Mon Sep 23 12:15:49.737421 2019] [mpm_prefork:notice] [pid 4788] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Mon Sep 23 12:15:49.737472 2019] [core:notice] [pid 4788] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon Sep 23 12:15:49.829681 2019] [mpm_prefork:notice] [pid 4788] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Sep 23 12:15:50.926326 2019] [suexec:notice] [pid 4815] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Sep 23 12:15:50.962781 2019] [auth_digest:notice] [pid 4815] AH01757: generating secret for digest authentication ...
[Mon Sep 23 12:15:50.963455 2019] [lbmethod_heartbeat:notice] [pid 4815] AH02282: No slotmem from mod_heartmonitor
[Mon Sep 23 12:15:51.026239 2019] [mpm_prefork:notice] [pid 4815] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Mon Sep 23 12:15:51.026289 2019] [core:notice] [pid 4815] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon Sep 23 12:31:34.000709 2019] [mpm_prefork:notice] [pid 4815] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Sep 23 13:14:02.590458 2019] [suexec:notice] [pid 2299] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Sep 23 13:14:02.734815 2019] [auth_digest:notice] [pid 2299] AH01757: generating secret for digest authentication ...
[Mon Sep 23 13:14:02.735538 2019] [lbmethod_heartbeat:notice] [pid 2299] AH02282: No slotmem from mod_heartmonitor
[Mon Sep 23 13:14:03.837016 2019] [mpm_prefork:notice] [pid 2299] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Mon Sep 23 13:14:03.837077 2019] [core:notice] [pid 2299] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon Sep 23 14:21:28.405877 2019] [mpm_prefork:notice] [pid 2299] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Sep 23 14:22:11.059510 2019] [suexec:notice] [pid 2414] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Sep 23 14:22:11.112985 2019] [auth_digest:notice] [pid 2414] AH01757: generating secret for digest authentication ...
[Mon Sep 23 14:22:11.114100 2019] [lbmethod_heartbeat:notice] [pid 2414] AH02282: No slotmem from mod_heartmonitor
[Mon Sep 23 14:22:11.198586 2019] [mpm_prefork:notice] [pid 2414] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Mon Sep 23 14:22:11.198631 2019] [core:notice] [pid 2414] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Thu Sep 26 13:22:04.317170 2019] [mpm_prefork:notice] [pid 2414] AH00170: caught SIGWINCH, shutting down gracefully
[Thu Sep 26 13:22:05.415546 2019] [suexec:notice] [pid 77927] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Sep 26 13:22:05.452873 2019] [auth_digest:notice] [pid 77927] AH01757: generating secret for digest authentication ...
[Thu Sep 26 13:22:05.453596 2019] [lbmethod_heartbeat:notice] [pid 77927] AH02282: No slotmem from mod_heartmonitor
[Thu Sep 26 13:22:05.520051 2019] [mpm_prefork:notice] [pid 77927] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Thu Sep 26 13:22:05.520099 2019] [core:notice] [pid 77927] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Sun Sep 29 03:42:01.973941 2019] [mpm_prefork:notice] [pid 77927] AH00171: Graceful restart requested, doing restart
“And who better understands the Unix-nature?” Master Foo asked.
“Is it he who writes the ten thousand lines, or he who, perceiving the emptiness of the task, gains merit by not coding?”
Master Foo - The ten thousand Lines
Unix Koans of Master Foo
Top
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: FUSION: Unable to Map to xi users (no mapping)

Post by benjaminsmith »

Hello,

Those look normal. One of the team members here has figured out a way to repeat this condition, and this maybe what is happening in this situation.

Once there is a mapped user registered in the database for you account, it will not populate the list of users. Follow the steps below and let us know if this is the issue.

1. Go to Edit User and select the No Mapping option from the list (the list the doesn't populate), and then select Update User/

2. Go back to Edit from the Actions menu, and select the Mapping menu. Do you see the list of users now? Please let us know.
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!
Top
User avatar
inversecow
Posts: 44
Joined: Wed Sep 25, 2019 4:17 pm

Re: FUSION: Unable to Map to xi users (no mapping)

Post by inversecow »

Thank you once again for your efforts on this.

Indeed I just tried this, but no dice on this end.
"No Mapping" persists as the displayed selection (and the only selection in the drop-down, when I check various users at random).

Happy to collect further data / try things on this end as suits to enable the investigation.
“And who better understands the Unix-nature?” Master Foo asked.
“Is it he who writes the ten thousand lines, or he who, perceiving the emptiness of the task, gains merit by not coding?”
Master Foo - The ten thousand Lines
Unix Koans of Master Foo
Top
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: FUSION: Unable to Map to xi users (no mapping)

Post by benjaminsmith »

Hello,

Thank you for your patience and providing all the details. At this point, I'd like you to open a support ticket for this issue and reference this thread. We'll most likely need to take a look a the server in a remote session to troubleshoot further.

Let me know if you have any questions.

Nagios Support Tickets
https://support.nagios.com/tickets/
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!
Top

Return to “Nagios Fusion”