Unable to write to check_result_path
-
pratik.patel
- Posts: 77
- Joined: Wed Apr 19, 2017 10:51 am
Re: Unable to write to check_result_path
I run the commands but same issue..
Re: Unable to write to check_result_path
Can you PM me your system profile?
To send us your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and email it back to us.
Also, run these commands as root and email in the /tmp/info.txt file
ls -lR /usr/local/nagios >/tmp/info.txt
getenforce >>/tmp/info.txt
Has the server recently been configured to use SSL?
If so, can you email in these files.
To send us your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and email it back to us.
Also, run these commands as root and email in the /tmp/info.txt file
ls -lR /usr/local/nagios >/tmp/info.txt
getenforce >>/tmp/info.txt
Has the server recently been configured to use SSL?
If so, can you email in these files.
Code: Select all
/etc/httpd/conf/httpd.conf
/etc/httpd/conf.d/nagiosxi.conf
/etc/httpd/conf.d/nagios.conf
/etc/httpd/conf.d/ssl.confBe sure to check out our Knowledgebase for helpful articles and solutions!
-
pratik.patel
- Posts: 77
- Joined: Wed Apr 19, 2017 10:51 am
Re: Unable to write to check_result_path
I have send you PM and I am not able to download profile
getting below message:
PROFILE BUILD FAILED
Array
(
)
CODE: 1
I have attached the system info.
getting below message:
PROFILE BUILD FAILED
Array
(
)
CODE: 1
I have attached the system info.
Re: Unable to write to check_result_path
The Build profile error is a /etc/sudoers configuration issue and what you did PM to me had more permission errors as well which confirmed the error.
What you have in your /etc/sudoers file will have to be changed and the easiest way to fix it is to replace your file with the default one that is attached to this post and that should fix the issues for you.
Remove the .txt extension.
If not, remove the following entries in the /etc/sudoers file
And replace them with the following
Try that and post back is it works or not.
What you have in your /etc/sudoers file will have to be changed and the easiest way to fix it is to replace your file with the default one that is attached to this post and that should fix the issues for you.
Remove the .txt extension.
If not, remove the following entries in the /etc/sudoers file
Code: Select all
nagios ALL=(root) NOPASSWD: /sbin/service httpd configtest, /usr/sbin/apachectl -S, /opt/continuent/tungsten/cluster-home/bin/check_tungsten_services, /opt/continuent/tungsten/cluster-home/bin/check_tungsten_online, /opt/continuent/tungsten/cluster-home/bin/check_tungsten_latency, /opt/continuent/tungsten/cluster-home/bin/check_tungsten_latency_mod, /opt/continuent/tungsten/cluster-home/bin/check_tungsten_progress
apache ALL=(root) NOPASSWD: /usr/bin/virsh list
Code: Select all
Defaults !visiblepw
Defaults:nagios !requiretty
Defaults:apache !requiretty
You do not have the required permissions to view the files attached to this post.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
pratik.patel
- Posts: 77
- Joined: Wed Apr 19, 2017 10:51 am
Re: Unable to write to check_result_path
I don't think so tungsten is the issue.
I can not remove it as we have these on all servers.
I can not remove it as we have these on all servers.
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: Unable to write to check_result_path
Well, you could try removing everything except tungsten. Modified sudoers is a known issue: https://support.nagios.com/kb/article.p ... ategory=44
-
pratik.patel
- Posts: 77
- Joined: Wed Apr 19, 2017 10:51 am
Re: Unable to write to check_result_path
I removed what you mention and replaced with that but same issue. 
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: Unable to write to check_result_path
Did you also add the following, as was suggested?
Code: Select all
Defaults !visiblepw
Defaults:nagios !requiretty
Defaults:apache !requiretty
-
pratik.patel
- Posts: 77
- Joined: Wed Apr 19, 2017 10:51 am
Re: Unable to write to check_result_path
Yes I added those 3 lines too.
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: Unable to write to check_result_path
Do you still have your XI install in /tmp/nagiosxi? If so, run the following comamnds:
If you do not still have that, download your current version from https://assets.nagios.com/downloads/nag ... rsions.php (or just decide to upgrade and get the latest), unpack it and then run the ./upgrade. It's highly likely there are still some permissions issues, and the upgrade will not work, but if it works it may resolve the issue. Also, if it doesn't work, it will give us some additional data on the issue. Please attach the upgrade.log if it fails.
Also, what's the output of sestatus? That will disabled, possibly permissive.
UPDATE: Upgrade log received and shared with techs
Code: Select all
cd /tmp/nagiosxi
./upgrade
Also, what's the output of sestatus? That will disabled, possibly permissive.
UPDATE: Upgrade log received and shared with techs
Last edited by dwhitfield on Thu May 11, 2017 4:43 pm, edited 1 time in total.
Reason: pm received
Reason: pm received