Isilon Error: isi_visudo does not edit the correct sudoers configuration file


Error: isi_visudo does not edit the correct sudoers configuration file.

Issue: When issuing the command isi_visudo to add sudo privileges to a user, the command opens and edits the wrong configuration file /usr/local/etc/sudoers instead of the correct one /etc/mcp/override/sudoers. This issue affects OneFS version 8.0.0.6+, 8.0.1.2+, and 8.1.0.1+

Resolution: As a workaround, issue the following command to force isi_visudo to edit the correct sudoers configuration file which is /etc/mcp/override/sudoers. The changes would propagate across all nodes in the cluster 
# isi_visudo -f /etc/mcp/override/sudoers

How to Collect API response generated on the Isilon Cluster

How to Collect API response generated on the Isilon Cluster

Process:
1. Use the below URL in the browser
2. Enter the Login Credentials
3. Prompt to Downloaded the File, ex: eventlists.json
4. Open the file in Notepad and view the generated last 1000 Events

https://<Isilon IP>:8080/platform/3/event/eventlists?limit=1000

ViPR SRM - License Upload - Error: An unexpected error occured: 'Unable to upload license. License is invalid or expires.'


Issue: Unable to upload the ViPR SRM License Ley from GUI or CLI
Error: An unexpected error occured: 'Unable to upload license. License is invalid or expires.'
Cause: This error is caused because the ELMS license SWID is referring to a product that is already using the other licenses.
Fix: Uninstall the conflicted ELMS license SWID

Steps to Fix Issue:
1. Upload the New License File (.lic) to the Frontend Server, maybe to tmp directory/folder; using tools like WinSCP.
Ex: file name: <SRMS_XXXXX_exp>.lic

2. Login to the Frontend Server with root Credentials
<FrontendServer>:~ # cd /tmp/
<FrontendServer>:/tmp # ls -l | grep -i SRMS
-rw-r--r-- 1 root    root       694 May 21 18:42 <SRMS_XXXXX_exp>.lic

3. Test the issue by trying to install the new License (Can be Skipped)
<FrontendServer>:/tmp # /opt/APG/bin/manage-licenses.sh install "<SRMS_XXXXX_exp>.lic"
Installing APG license key (SRMS_XXXXX_exp.lic)... SEVERE  -- [2018-05-22 11:47:40 EDT] -- BinaryDecoder$AbstractBagDecorator::getHashCodeBuilder(): ELMS license swid refers to a product that is already in use by other license(s).  If the current license is correct, please remove the installed license(s) that conflict,  otherwise contact SRM support about the current conflicting license(s). candidate swid: ELMSRM0XXXXXXX, candidate product: ViPR SRM, conflicting swid(s): [CB885L7VXXXXXX], installed license(s) swid-to-product-mapping: {CB885L7VXXXXXX=[ViPR SRM]}
 failed!
**** Unable to modify Java system preferences.
**** You may need to be root in order to perform this operation.

4. Uninstall the conflicted ELMS license SWID
<FrontendServer>:/tmp # /opt/APG/bin/manage-licenses.sh remove "ELMS Features: CB885L7VXXXXXX"
Removing license for ELMS Features: CB885L7VXXXXXX... done.
<FrontendServer>:/tmp # /opt/APG/bin/manage-licenses.sh remove "ELMS Features: ELMSRM0XXXXXXX"
Removing license for ELMS Features: ELMSRM0XXXXXXX... done.

5. After uninstalling all the license causing interruption for the fresh license we need to update the license-manager by using the following command:
<FrontendServer>:/tmp # /opt/APG/bin/manage-modules.sh update license-manager Default
Required dependencies, in processing order:
   [1]   java '8.0.151' v8.0.151
   [2] U license-manager 'Default' v5.7u2 => v5.7u2
> 1 not modified, 1 to update
> 2.2 MB space required / 346.9 GB available
 ? Enter the step to modify, 'yes' to accept them, or 'no' to cancel the operation [yes] > yes

Starting update of license-manager Default from v5.7u2 to v5.7u2...
 * Gathering information...
 * Module found in '/opt/APG/Tools/License-Manager/Default'.
 * It will now be updated using 'license-manager-5.7u2-linux-x64.pkg'.
 * Unpacking files...
 * Updating files... 100%
 * 19 files have been updated.
 * Finalizing update...
Update complete.

6. Now you can then install the fresh license using the following command
<FrontendServer>:/tmp # /opt/APG/bin/manage-licenses.sh install "SRMS_XXXXXXX_DD-MMM-YYYY_exp.lic"
Installing APG license key (SRMS_XXXXXXX_DD-MMM-YYYY_exp.lic)... done.

7. You can then verify the installed license by using the below command:
<FrontendServer>:/tmp # /opt/APG/bin/manage-licenses.sh check

Note: Moreover, if it’s a distributed environment you will need to go to the >> ViPR SRM centralized management > License Management > and then click on Synchronize so that the new license is copied on all the hosts.

Hope this would help :)