Page 1 of 1
Upgrade error again!
Posted: Wed Jan 04, 2017 10:49 am
by BanditBBS
Code: Select all
Starting nagios: done.
NDOUTILS UPGRADED!
Saving old crontab to /tmp/nagios.crontab.orig...
Removing XI cron jobs...
Saving old crontab to /tmp/root.crontab.orig...
Removing XI cron jobs...
mv: cannot move `/etc/sudoers.new' to `/etc/sudoers': Operation not permitted
We really need to find a new way to do the sudoers stuff in the upgrade and I cna't be the only user with that stuff protected and not allowed to be edited. What do I need to do to get around this issue?
Re: Upgrade error again!
Posted: Wed Jan 04, 2017 11:52 am
by SteveBeauchemin
Suggestion from Steve...
run the update from the command line - always...
Look at the files. You will notice 5-sudoers
If you look at the file you can see that you can fool it into thinking that it already ran. If installed.sudoers exists, it skips this step. It thinks it is already done.
I have custom sudo from Quest installed, and our sudoers is centrally controlled. I have to always do this.
Steve B
Re: Upgrade error again!
Posted: Wed Jan 04, 2017 12:09 pm
by dwhitfield
Thanks again
@SteveBeauchemin!
@ BanditBBS, we've kept around what I suppose could be called crufty code due to CentOS 5. Now that CentOS 5 is going out of support, I am thinking we will have a fix. Unfortunately, I don't have an ETA at present, but I did bring it to the attention of other members of the team since CentOS 5 is officially off our QA board.
If you'd like, I can try to get a little more detail on when we should have a fix in place.
Re: Upgrade error again!
Posted: Wed Jan 04, 2017 12:14 pm
by avandemore
BanditBBS wrote:and I cna't be the only user with that stuff protected and not allowed to be edited
No, not the only one. It's just very rare and depending on the amount of system modifications the target system has, it can make the XI install out of scope.
This page contains instructions about editing sudoers to allow Nagios privileges needed to operate normally.
https://support.nagios.com/kb/article.php?id=34
If you do that process ahead of time, you can comment out the sudoers stuff in the upgrade script or do as
@SteveBeauchemin suggested.
Just by the end of it, you'll need your sudoers or whatever your equivalent is to have the appropriate entries.