When you click on the link received via text or email we get this (see attached).
We used to get straight to the device.
Thank you
Invalid Token, Rapid Response
Invalid Token, Rapid Response
You do not have the required permissions to view the files attached to this post.
----------------------------------
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: Invalid Token, Rapid Response
Hi @rbuckle
In Nagios 5.5, the rapid response URL is set to expire in 30 minutes. Can you verify that URL has not expired?
In Nagios 5.5, the rapid response URL is set to expire in 30 minutes. Can you verify that URL has not expired?
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!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Invalid Token, Rapid Response
That time it was, but i have also received that when i just got the message... is there a way that that 30 minutes can be extended?
I will test that
I will test that
----------------------------------
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: Invalid Token, Rapid Response
Hi @rbuckle,
In the xi_options table in nagiosxi, you can increase the rr_valid_link_timeout setting. Please make a backup or take a VM snapshot before making any changes.
If you're running a MySQL database, you can increase the time to 1 week with the following command:
Backing Up And Restoring Your Nagios XI System
https://assets.nagios.com/downloads/nag ... ios-XI.pdf
In the xi_options table in nagiosxi, you can increase the rr_valid_link_timeout setting. Please make a backup or take a VM snapshot before making any changes.
If you're running a MySQL database, you can increase the time to 1 week with the following command:
Code: Select all
echo "INSERT INTO xi_options (name, value) VALUES ('rr_valid_link_timeout', '604800');"|mysql -pnagiosxi nagiosxi
https://assets.nagios.com/downloads/nag ... ios-XI.pdf
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!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Invalid Token, Rapid Response
Update,
I have not altered anything yet to do with the timeout... I just received an Alert and the link was already expired (not even 30 minutes). Could this be just a plain expired cert issue?
My SSL cert had expired... i feel stupid... let me see if that fixes it
I have not altered anything yet to do with the timeout... I just received an Alert and the link was already expired (not even 30 minutes). Could this be just a plain expired cert issue?
My SSL cert had expired... i feel stupid... let me see if that fixes it
----------------------------------
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
Re: Invalid Token, Rapid Response
Nope that didnt fix my issue... even with a valid ssl cert i still get the same error
----------------------------------
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: Invalid Token, Rapid Response
Hello @rbuckle,
It's a single use url, is it possible another user has clicked on the URL?
If that's not the case, please repeat the error (click on the url) and either PM the Apache log files or run the following command and post the output to this thread:
The log files are located in /var/log/httpd.
Nagios XI Log Locations and Descriptions
https://assets.nagios.com/downloads/nag ... ptions.pdf
It's a single use url, is it possible another user has clicked on the URL?
If that's not the case, please repeat the error (click on the url) and either PM the Apache log files or run the following command and post the output to this thread:
Code: Select all
tail /var/log/httpd/error_log
tail /var/log/httpd/access_log
Nagios XI Log Locations and Descriptions
https://assets.nagios.com/downloads/nag ... ptions.pdf
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!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Invalid Token, Rapid Response
Looks to me like nothing 
Code: Select all
[root@nagios2 rbuckle]# tail /var/log/httpd/error_log
[Sun Jan 20 03:12:13.239926 2019] [auth_digest:notice] [pid 5338] AH01757: generating secret for digest authentication ...
[Sun Jan 20 03:12:13.240691 2019] [lbmethod_heartbeat:notice] [pid 5338] AH02282: No slotmem from mod_heartmonitor
[Sun Jan 20 03:12:13.292957 2019] [mpm_prefork:notice] [pid 5338] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Sun Jan 20 03:12:13.292975 2019] [core:notice] [pid 5338] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'Code: Select all
[root@nagios2 rbuckle]# tail /var/log/httpd/access_log -f
127.0.0.1 - - [21/Jan/2019:07:28:59 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"
127.0.0.1 - - [21/Jan/2019:07:33:57 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"
127.0.0.1 - - [21/Jan/2019:07:38:56 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"
127.0.0.1 - - [21/Jan/2019:07:43:54 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"
127.0.0.1 - - [21/Jan/2019:07:48:52 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"
127.0.0.1 - - [21/Jan/2019:07:53:50 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"
127.0.0.1 - - [21/Jan/2019:07:58:48 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"
127.0.0.1 - - [21/Jan/2019:08:03:47 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"
127.0.0.1 - - [21/Jan/2019:08:08:45 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"
127.0.0.1 - - [21/Jan/2019:08:13:43 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"
::1 - - [21/Jan/2019:08:15:51 -0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 (internal dummy connection)"
127.0.0.1 - - [21/Jan/2019:08:18:41 -0800] "GET / HTTP/1.0" 200 2968 "-" "check_http/v2.2.1 (nagios-plugins 2.2.1)"----------------------------------
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: Invalid Token, Rapid Response
Hi @rbuckle,
I have tested the rapid response URL on the latest version with SSL and without and it's working on my system. Let's verify your settings and also check the apache ssl log files:
1. Make sure you have correctly set the Program URL and the External URL (if required) in the General Program Settings ( see attached image).
2. Got to Admin > System Settings > Session Timeout and make sure this has not been set too low. The default is 30 minutes.
3. Also Check the Admin > System Settings > Rapid Response URL Settings. If you have this secured, please try and test without requiring login.
4. Can you tail the Apache ssl log files for errors as well?
I have tested the rapid response URL on the latest version with SSL and without and it's working on my system. Let's verify your settings and also check the apache ssl log files:
1. Make sure you have correctly set the Program URL and the External URL (if required) in the General Program Settings ( see attached image).
2. Got to Admin > System Settings > Session Timeout and make sure this has not been set too low. The default is 30 minutes.
3. Also Check the Admin > System Settings > Rapid Response URL Settings. If you have this secured, please try and test without requiring login.
4. Can you tail the Apache ssl log files for errors as well?
Code: Select all
tail /var/log/httpd/ssl_error_log
tail /var/log/httpd/ssl_access_log
You do not have the required permissions to view the files attached to this post.
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!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Invalid Token, Rapid Response
Code: Select all
[root@nagios2 rbuckle]# tail /var/log/httpd/ssl_access_log
208.94.80.132 - - [21/Jan/2019:15:07:20 -0800] "GET /nagiosxi/includes/components/statusmap/map.php?layout=7 HTTP/1.1" 200 3505
208.94.80.132 - - [21/Jan/2019:15:07:20 -0800] "GET /nagiosxi/ajaxhelper.php?cmd=getxicoreajax&opts=%7B%22func%22%3A%22get_service_status_tac_summary_html%22%2C%22args%22%3A%7B%22ignore_soft_states%22%3A%220%22%2C%22nsp%22%3A%2274526a6d71c4c13527665d8c674eaaac1fa1f8d5a8410636c657f5be8a261e2c%22%2C%22iframe_width%22%3A%22438%22%2C%22iframe_height%22%3A%22161%22%2C%22mode%22%3A%22inboard%22%7D%7D&nsp=f7e002d2724fcf702df42d50d4730d70223d6a0b01481f792df76469a324997c HTTP/1.1" 200 2590
208.94.80.132 - - [21/Jan/2019:15:07:23 -0800] "GET /nagiosxi/ajaxhelper.php?cmd=getxicoreajax&opts=%7B%22func%22%3A%22get_network_health_html%22%2C%22args%22%3A%7B%22host_warning_threshold%22%3A%2280%22%2C%22host_critical_threshold%22%3A%2260%22%2C%22service_warning_threshold%22%3A%2280%22%2C%22service_critical_threshold%22%3A%2260%22%2C%22ignore_soft_states%22%3A%220%22%7D%7D&nsp=d8e1b726726ecc7777ab1c7a7fc9dc415e06246538fd77af18996ca8f00c94c4 HTTP/1.1" 200 836
208.94.80.132 - - [21/Jan/2019:15:07:24 -0800] "GET /nagiosxi/ajaxhelper.php?cmd=getxicoreajax&opts=%7B%22func%22%3A%22get_tray_alert_html%22%2C%22args%22%3A%22%22%7D&nsp=d8e1b726726ecc7777ab1c7a7fc9dc415e06246538fd77af18996ca8f00c94c4 HTTP/1.1" 200 662
208.94.80.132 - - [21/Jan/2019:15:07:24 -0800] "GET /nagiosxi/ajaxhelper.php?cmd=getxicoreajax&opts=%7B%22func%22%3A%22get_host_status_tac_summary_html%22%2C%22args%22%3A%7B%22ignore_soft_states%22%3A%220%22%2C%22mode%22%3A%22outboard%22%7D%7D&nsp=d8e1b726726ecc7777ab1c7a7fc9dc415e06246538fd77af18996ca8f00c94c4 HTTP/1.1" 200 1056
208.94.80.132 - - [21/Jan/2019:15:07:23 -0800] "GET /nagiosxi/includes/components/statusmap/infobox.php HTTP/1.1" 200 341
208.94.80.132 - - [21/Jan/2019:15:07:24 -0800] "GET /nagiosxi/includes/components/nagioscore/ui/objectjson.php?&details=true&formatoptions=enumerate+bitmask&query=hostlist HTTP/1.1" 200 481302
208.94.80.132 - - [21/Jan/2019:15:07:25 -0800] "GET /nagiosxi/ajaxhelper.php?cmd=getxicoreajax&opts=%7B%22func%22%3A%22get_service_status_tac_summary_html%22%2C%22args%22%3A%7B%22ignore_soft_states%22%3A%220%22%2C%22mode%22%3A%22outboard%22%7D%7D&nsp=d8e1b726726ecc7777ab1c7a7fc9dc415e06246538fd77af18996ca8f00c94c4 HTTP/1.1" 200 2510
208.94.80.132 - - [21/Jan/2019:15:07:24 -0800] "GET /nagiosxi/includes/components/statusmap/map-popup.php HTTP/1.1" 200 1784
208.94.80.132 - - [21/Jan/2019:15:07:25 -0800] "GET /nagiosxi/includes/components/nagioscore/ui/statusjson.php?query=programstatus HTTP/1.1" 200 985Code: Select all
[root@nagios2 rbuckle]# tail /var/log/httpd/ssl_error_log
[Mon Jan 21 14:41:24.284827 2019] [:error] [pid 13035] [client 208.94.80.132:52490] PHP Warning: simplexml_load_string(): ^ in /usr/local/nagiosxi/html/includes/utils-systat.inc.php on line 17, referer: https://nagios2.intermax.network/nagiosxi/views/index.php?
[Mon Jan 21 14:41:32.585144 2019] [:error] [pid 20153] [client 208.94.80.132:56849] PHP Warning: simplexml_load_string(): Entity: line 25: parser error : StartTag: invalid element name in /usr/local/nagiosxi/html/includes/utils-systat.inc.php on line 17, referer: https://nagios2.intermax.network/nagiosxi/admin/
[Mon Jan 21 14:41:32.585190 2019] [:error] [pid 20153] [client 208.94.80.132:56849] PHP Warning: simplexml_load_string(): ax.network;Load;STOPPED; Service appears to have stopped flapping (3.9% change < in /usr/local/nagiosxi/html/includes/utils-systat.inc.php on line 17, referer: https://nagios2.intermax.network/nagiosxi/admin/
[Mon Jan 21 14:41:32.585201 2019] [:error] [pid 20153] [client 208.94.80.132:56849] PHP Warning: simplexml_load_string(): ^ in /usr/local/nagiosxi/html/includes/utils-systat.inc.php on line 17, referer: https://nagios2.intermax.network/nagiosxi/admin/
[Mon Jan 21 14:41:32.592161 2019] [:error] [pid 8864] [client 208.94.80.132:56850] PHP Warning: simplexml_load_string(): Entity: line 25: parser error : StartTag: invalid element name in /usr/local/nagiosxi/html/includes/utils-systat.inc.php on line 17, referer: https://nagios2.intermax.network/nagiosxi/admin/
[Mon Jan 21 14:41:32.592195 2019] [:error] [pid 8864] [client 208.94.80.132:56850] PHP Warning: simplexml_load_string(): ax.network;Load;STOPPED; Service appears to have stopped flapping (3.9% change < in /usr/local/nagiosxi/html/includes/utils-systat.inc.php on line 17, referer: https://nagios2.intermax.network/nagiosxi/admin/
[Mon Jan 21 14:41:32.592205 2019] [:error] [pid 8864] [client 208.94.80.132:56850] PHP Warning: simplexml_load_string(): ^ in /usr/local/nagiosxi/html/includes/utils-systat.inc.php on line 17, referer: https://nagios2.intermax.network/nagiosxi/admin/
[Mon Jan 21 15:02:41.582866 2019] [:error] [pid 13045] [client 208.94.80.132:57279] PHP Warning: Division by zero in /usr/local/nagiosxi/html/includes/components/graphexplorer/templates/perfdata.inc.php on line 99, referer: https://nagios2.intermax.network/nagiosxi/includes/components/xicore/status.php?show=servicedetail&host=kvm01.intermax.network&service=APT+Updates&dest=auto
[Mon Jan 21 15:03:46.264279 2019] [:error] [pid 13046] [client 208.94.80.132:57331] PHP Warning: Division by zero in /usr/local/nagiosxi/html/includes/components/graphexplorer/templates/perfdata.inc.php on line 99, referer: https://nagios2.intermax.network/nagiosxi/includes/components/xicore/status.php?show=servicedetail&host=kvm01.intermax.network&service=APT+Updates&dest=auto
[Mon Jan 21 15:05:10.233314 2019] [:error] [pid 30434] [client 208.94.80.132:57367] PHP Warning: _() expects exactly 1 parameter, 0 given in /usr/local/nagiosxi/html/includes/components/xicore/status.php on line 645, referer: https://nagios2.intermax.network/nagiosxi/config/configobject.php----------------------------------
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License
Running:
Installed Version: 5.8.3
OS: CentOS 7
Nagios XI
Enterprise License