Tips To Resolve The Nmo Not Setuid-root Unix-only Error Log Error

September 16, 2021 By Lucas Nibbi Off

Table of Contents

Over the past few days, some of our readers have encountered a known bug related to the nmo not setuid-root unix-only error log error. This problem occurs for a number of reasons. We will discuss this below.

Recommended: Fortect

1. Download and install Fortect

2. Open the program and click "Scan"

3. Click "Repair" to start the repair process

Download this software and fix your PC in minutes.

NMO is less than setuid-root (Unix only). Run root.Script sh to fix this problem. The next job submitted by the operating system command will suppress this warning.

The permissions for all nm files are the same as for other agents. Note. 1465278.1 was being used to re-run root.sh, re-evaluation generated by the crash did not resolve this issue. The agent has also been restarted. This was not the last incident.

Recommended: Fortect

Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for Fortect is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download Fortect today!

1. Download and install Fortect

2. Open the program and click "Scan"

3. Click "Repair" to start the repair process

 APPLIES TO:Enterprise Manager base platform - version 12.1.0.1.0 and higherUniversal UNIXGeneral LinuxSYMPTOMS:The Cloud Management Agent was installed from a Unix machine. Attempting to perform certain operations on a target controlled by this agent from the Cloud, all Controls result in an error:ERROR: NMO not setuid-root (Unix only).Examples of operations that can lead to permanent failure:- Performing installation work: it can be an OS command, a SQLPlus script, etc.- Set or check the preferred credentials for this host- Configure database backup options for the primary database on this host.- Try itYou can clone to the Oracle source home directory by running our own patch wizard or the target deployment process from that host.- Run a new custom metric for the target on this host, etc.To summarize, we can say that any operation where the agent needs to log in as a path to the host and execute the training result can lead to excessive error.FIRST REASON:Reason 1: The script  /root.sh did not even run after installing the agent.Activity of executable files nmo, nmb to nmo is not the main user:$ cd  / sbin$ ls -ltr nm *For example:$ cd / u03 / cloud12c / agent12c / sbin$ ls -al nm *-rwxr-xr-x Oracle 1 Oracle 22754 Feb 9 11:08 nmb-rwxr-xr-x oracle 1 oracle 57835 February 11, 11:10 nmhs-rwxr-xr-x oracle special oracle 40478 Jan 31 16:57 nmo...Patch permissions must be set by running the  /root.sh file as a base when installing / deploying the agent.You should get:$ ls -al nm *-rwxr-xr-x 1 Oracle core 585242 Jul 6, 2013-rws - x --- 1 root oracle 40007 Some July 2013 1 nmo-rws - x --- oracle root 57835 Jul 6, 2013 by nmhs-rws - x --- 1 large oracle 22754 6  July 2013 nmb-rwxr-xr-x 1 oracle root 43494, best July 6, 2013Reason 2: The root.sh program may have been executed, but the mount point type for  is usually set to "nosuid" rather than "nosetuid" / "noatime" / "nodiratime".This can be verified by running the following command:CollectWherecollect | grep nosuidandcollect | grepWhereCheck the entries in the files: / etc / vfstab, / etc / fstabThe nosetuid parameter prevents connected parameters that have setuid permissions from also using their administrator's permissions, regardless of who runs them. Without this option, a setuid program with its own root cause will run with root read / write access regardless of who runs it.Sometimes the "nosuid" policy is used to protect the system as a whole from programs that are likely to run setuid as root and damage a specific system.Note that the Solaris zone may report incorrect mount options:If the actual setuid is set to global quality for the ZFS filesystem, the Lofs type that mounts this tmount point when you need a directory in a zone is usually setuid = true to always get a specific setting from the global Pass scope.If you mount | grep /  'full for zone out of zone, device still returns' setuid' incorrectly.If a person prints a pry bar | grep 'in the global scope, you will see the correct settingthis is also seen when noatime, nodiratime processing is enabled on the filesystem.SOLUTION:A solution is available for Reason 1:1) Log in to the host of the Cloud Control Agent as root.2) Go to the Oracle Home / u01 / app / oracle / product / Middleware / agent / core / 12 Cloud Control Agent directory.Example: .1.0.1.03) Run our own root.sh script:# ./root.sh4) Connect to your Cloud Control agent host as many times as the owner of the agent binaries (Oracle for many examples).5) Check if the permissions are currently correct:$ ls -ltr....-rwxr-xr-x 1 root them 58524 July 2, 2013 6 nm-rws - x --- 7 root em 4000 7 July 2013 fifty percent nmo-rws - x --- 1 root em 57835 Jul 2013 6 nmhs-rws - x --- 1 root them 22754 July 2013 6 nmb-rwxr-xr-x some root em 43494 July 2013 five nmgsshe6) Stop and restart the Cloud Control agent:Example$ cd /u01 / app / oracle / product / Middleware / agent / core / 12.1.0.1.0 / binQuit agent $ ./emctl.Launcher $ ./emctlSolution for Reason 2:If the mount point has practically set the options ('nosuid' and 'nosetuid' / 'noatime' / 'nodiratime'), your problem should be resolved by the Unix system sysadmins:1) Save, edit and save the / etc / vfstab or / etc / fstab entry for the checkpoint where the agent was installed and remove the 'nosuid' for each 'nosetuid' / 'noatime' / 'nodiratime' option. AixOn the operating system, edit the / etc / filesystems.(u01 in our example)2) Stop the agent, mount the mount point again and restart the computer using the EM agent.Example(As the owner associated with the binaries agent :)$ cd $ ORACLE_HOME / bacPrevent agent $ ./emctl(As root user):# umount # mount (As a dog owner, binary agent :)$ cd $ ORACLE_HOME / bac$ ./emctl starts agent process