root account?

Today I was looking for my active process and I find the root account (Xwindows server, networks and other account), and I never got it before today...

Is this dangerous? Should I change it?

All the processes of the system are managed by 'root '. What you describe is normal. My guess is that you normally activity monitor together to see ' process of my ' but today you have involuntarily (by using the view menu) changed to display "all processes".

C.

Tags: Mac OS & System Software

Similar Questions

  • the root account not working for vSphere Client 5.5, for SSH works fine

    Hey.

    I got this:

    I can connect to vCenter 5.5 by SSH and the root user and password works fine

    I can connect to vCenter 5.5 by vSphere Client and use domain user and everything works fine

    I cant't connection 5.5 by user of vSphere vCenter Client and use of root and the password. I have information on

    "Cannot complete the connection because username or password incorect.

    IM shure I use the right password for root.

    A suggestion?

    Screenshot_6.png

    Ok. Thank you community vExpert and Lukasz of my team, we found easy reason perhaps, but not at the first glance for me

    We had the installer by default "Source of identity" for Active Directory then when I used only root for connection I got the error with wrong password.

    In this possible case is just to connect to vcenter using root@localos credintials.

    But in addition we sam of similar mistakes inside the SSO connects:

    Location of the vCenter Single Sign-On log files for vCenter Server 5.1 and 5.5 (2033430) | VMware KB

    /var/log/VMware/SSO/VMware-STS-idmd.log

    2016 06-21 13:57:31, ERROR 142 [IdentityManager] could not authenticate [root] main tenant [vsphere.local]

    javax.security.auth.login.LoginException: failed connection

    at com.vmware.identity.idm.server.provider.ldap.LdapWithAdMappingsProvider.authenticate(LdapWithAdMappingsProvider.java:327)

    at com.vmware.identity.idm.server.IdentityManager.authenticate(IdentityManager.java:2412)

    at sun.reflect.GeneratedMethodAccessor24.invoke (unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

    at java.lang.reflect.Method.invoke (unknown Source)

    at sun.rmi.server.UnicastServerRef.dispatch (unknown Source)

    to sun.rmi.transport.Transport$ 1.run (unknown Source)

    to sun.rmi.transport.Transport$ 1.run (unknown Source)

    at java.security.AccessController.doPrivileged (Native Method)

    at sun.rmi.transport.Transport.serviceCall (unknown Source)

    at sun.rmi.transport.tcp.TCPTransport.handleMessages (unknown Source)

    to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run0 (unknown Source)

    to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run (unknown Source)

    at java.util.concurrent.ThreadPoolExecutor.runWorker (unknown Source)

    to java.util.concurrent.ThreadPoolExecutor$ Worker.run (unknown Source)

    at java.lang.Thread.run (unknown Source)

    Caused by: com.vmware.identity.idm.InvalidPrincipalException: could not find the main id: {name: root domain: OurAdDomain.local}

    at com.vmware.identity.idm.server.provider.BaseLdapProvider.findAccountLdapEntry(BaseLdapProvider.java:543)

    at com.vmware.identity.idm.server.provider.ldap.LdapWithAdMappingsProvider.getUserDN(LdapWithAdMappingsProvider.java:1715)

    at com.vmware.identity.idm.server.provider.ldap.LdapWithAdMappingsProvider.authenticate(LdapWithAdMappingsProvider.java:323)

    ... 15 more

    2016-06-21 13:57:31, 144 ERROR [IdentityManager] failed to main checkUserAccountFlags [root] for tenant [vsphere.local]

    "2016-06-21 13:57:31, 144 exception ERROR [ServerUtils] ' com.vmware.identity.idm.IDMLoginException: the connection has failed.

    com.vmware.identity.idm.IDMLoginException: failed connection

    at com.vmware.identity.idm.server.IdentityManager.authenticate(IdentityManager.java:2481)

    at sun.reflect.GeneratedMethodAccessor24.invoke (unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

    at java.lang.reflect.Method.invoke (unknown Source)

    at sun.rmi.server.UnicastServerRef.dispatch (unknown Source)

    to sun.rmi.transport.Transport$ 1.run (unknown Source)

    to sun.rmi.transport.Transport$ 1.run (unknown Source)

    at java.security.AccessController.doPrivileged (Native Method)

    at sun.rmi.transport.Transport.serviceCall (unknown Source)

    at sun.rmi.transport.tcp.TCPTransport.handleMessages (unknown Source)

    to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run0 (unknown Source)

    to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run (unknown Source)

    at java.util.concurrent.ThreadPoolExecutor.runWorker (unknown Source)

    to java.util.concurrent.ThreadPoolExecutor$ Worker.run (unknown Source)

    at java.lang.Thread.run (unknown Source)

    2016-06-21 13:57:31, 144 INFO [IdentityManager] authentication failed for user [root] the tenant [vsphere.local] in milliseconds [4]

    When I used the credentials with appropriate domain name:

    root@localos we received newspapers below:

    2016-06-21 14:11:58, 971 INFO [LinuxNativeAuthDbAdapter] [root] user authentication

    2016-06-21 14:11:58, 974 INFO [IdentityManager] authentication successful for the user [root@localos] [vsphere.local] tenant in milliseconds [3]

    2016-06-21 14:11:58, 984 INFO [LinuxNativeAuthDbAdapter] to get local groups for the [root] user. Recursive? [Yes]

    When I temporary switch the source of identity - "localos" and use the root account to log logs below, we received and I connected without problem:

    2016-06-21 14:14:37, 545 INFO [LinuxNativeAuthDbAdapter] [root] user authentication

    2016-06-21 14:14:37, 549 INFO [IdentityManager] authentication successful for the user [root] the tenant [vsphere.local] in milliseconds [4]

    2016-06-21 14:14:37, 564 INFO [LinuxNativeAuthDbAdapter] to get local groups for the [root] user. Recursive? [Yes]

    Now, for me, more clearly

    Once again thank you

    Sebastian

  • Can access VCSA with the root account, but cannot access vSphere with the same root account

    I am able to connect to the VCSA (: 5480) with the created password for root, but I can't log in vSphere (: 9443) with this same root account).  It seems that the password has been correctly set, but weird that I can connect to one and not the other.  I recently improved bed and breakfast ESXi and VCSA version 5.5 Update 2, but don't think that should have an effect on.  Any suggestions?  Help, please.

    Understand the problem.  When you change the field by default to another identity source, you must type root@localos as the user name to use the root account.

  • Determine the IP address of local login using the root account

    How can I determine the IP address of a person who connects to an ESXi host using the root account? (I don't know if the connection was via ssh or vSphere Client)

    Hello

    connects him with the address IP can be found here:

    SSH: /var/log/auch.log

    vSphere Client: /var/log/hostd.log

    Concerning

    Tim

  • Definition of root account ESXi expire after 60 days

    Is there a way to define the local root account on an ESXi host expire after 60 days?

    I already use AD authentication, but the root account is always available for use if the ad is not available to authenticate.  However, I don't want to just leave the root with the same password forever account to comply with the security policy.

    Thank you-

    ESXi does not support the password aging as well at the ESXi hosts with State and stateless.

  • Creative Cloud Desktop only works in the root account

    10.10.3 Mac

    Cannot open the VAC Office. nothing happened to the screen after clicking on the icon. only a CAC logo (in gray) appeared in the status bar at the top, but it disappeared quickly. Have you tried:

    1. creation of cloud cleanser

    2. safe Mode

    3. clean the OOBE, AAMUpdater records

    4. connect with the administered user another

    Installed and opened successfully to the root account, but don't always works is not in my account (which is an administrator).

    Please help me solve the problem. Thank you!

    I fixed this problem in my environment (Yosemite 10.10.3) after a day and a half, tinker with it.

    Open launchpad / look for the disk utility / click on verify disk permissions / repair disk permissions.

    It worked for me. Adobe CC now works again and the applications are broken no longer.

  • After Effects will be not updated for MAC 10.9.4 even on the Root account.

    I've already updated my Mac OS to 10.9.4 and it was only until today that I wanted to use After Effects. I opened After Effects and I get an error, after some googling I am taken to a download page for the update of After Effects. I downloaded the update, but when I ran it, it said I had no sufficient privileges. After a long chain of events that involved trick my computer into thinking that it was all new to an admin account, I made an admin account and from there had access to the root account. Once the root account, I thought that all the permissions would be open, but no, I still receive the same error message, "please contact your system administrator if you want to apply updates on your machine. Updates have been removed by your administrator. »

    Is there an I need to press the button or command that I need to type in the root account, which will allow me to update the AE? Any help would be appreciated.

    Thank you.

    This is not the administrator of the computer; rather, it is the administrator of your software licenses. Who distributed your Adobe software seems to have chosen the option in this distribution to disable updates. You will need to talk with them.

  • Cannot access the vCSA 5.5 with the local root account

    We are upgrading from 5.0 to 5.5 U2 ESXi. By the checklist, I first upgraded vCSA to 5.5.

    The vCSA 5.5 upgrade gives me connection problems. I can connect to the admin of vSphere GUI (port 5480) and web client (port 9443) using the local account "root". However if I try to access it from an application (IE VUM or Backup Exec) vCSA credentials of the root get rejected (as if I use the username/password wrong name). No idea why? FYI, we are using Active Directory and embedded DB & SSO. I attach a screenshot of the summary page.

    Thank you! :-)

    If it was working earlier and you have changed the domain by default to a good AD/LDAP, you can try with the username "root@localos".

    Concerning

    Girish

  • I accidentally run the environment using the root account

    Hello

    I am trying to restart the concurrent Manager but accidentally into account root then also EPS of DB and APPS

    the solution I did was change the owner chown-r applmgr:dba apps / and inst and also for the DB chown-r: dba oracle db.
    After that, I run the DB env and it has been successfully wihtout exisitng errors or addbctl.sh: exit with status 0

    but in applications when I run ENV then go to ADMIN_SCRIPTS_HOME/sid_name.
    then adstrtal.sh the APPS ask me a username and password which is entered without having to enter because I'm on the side of the APPS

    error message:

    adstrtal.sh: the base connection could not be established. The database is out of service or applications provided credentials are wrong

    USE: adstrtal.sh < appsusername/appspassword >

    adstrtal.sh: leave with the State 1



    Help, please

    Thank you

    Published by: cheesewizz on November 23, 2010 22:05

    Hello

    If please run AutoConfig on node layer (as user oracle and database after the database of supply env file) and make sure that it ends successfully. Then, run AutoConfig on the node application layer (as user applmgr and after the supply env file) and see if it returns any errors.

    Thank you
    Hussein

  • ORA-12154 as user oracle, Pentecost root account, it works very well

    Hello

    I have a problem with a client installation, if I try to connect to the database. I have the following configuration:

    1 database: running on an Ubuntu Jeos VM, Oracle 11 g (11.1.0.6.0 version 64 bit)
    2. customer: running on a CentOS 5.2 VM, Oracle 10 g Linux 32-bit Client

    I have configured the tnsnames.ora and stored in the directory of $ORACLE_HOME/network/admin. The content of the tnsnames.ora file is the following:
    ORCL64 = (Description = (ADDRESS_LIST = (Address = (Protocol = TCP)(host=192.168.12.128) (port = 1521))) (CONNECT_DATA = (SID = ORCL)))

    If I try to connect to the database as the user oracle with the following command sqlplus SYS@ORCL64 AS SYSDBA, I will get the ORA-12154 TNS: could not resolve the connect identifier specified error message. If I try the same as the root user, it works fine and I can make the connection. I have the same result if I try the command tnsping ORCL64. As user root the tnsnames adapter can resolve the alias, as the oracle user this appears not possible and I will get the error message: TNS-03505: failed to resolve the name. In both it uses the setting from the file u01/app/oracle/network/admin/sqlnet.ora. The content of the sqlnet.ora file is the following:
    NAMES of . DIRECTORY_PATH = (TNSNAMES, EZCONNECT).

    Do you have any suggestions how can I solve this problem of having a connection with the oracle user.
    Thanks in advance
    Sven

    user10252169 wrote:
    Hello

    Thanks for your replies. On the CentOS machine, where the client is installed, there is no directory $ORACLE_HOME/bin/oracle and $ORACLE_HOME/bin/lsnrctl. The output of the $ORACLE_HOME/network/admin / * ora is:

    -rw - r - 1 oracle oinstall 171 28. Apr 21:25 /u01/app/oracle/network/admin/sqlnet.ora
    WX - 1 root root 118 5. May 11:33 /u01/app/oracle/network/admin/tnsnames.ora

    The 'client' reads the tnsnames.ora to determine where the database. Looking at t he above, you have a configuration in which the user name only client able to read the tnsnames.ora is the root user. Which means that you have run the netca or netmgr as root.

    Change the tnsnames.ora to provide the appropriate, perms and then try again.

  • Not able to connect with the root via putty ssh account

    Hello

    I activated the lock mode and activated ssh as well.but I am still unable to log in using PuTTY says access denied. At the same time, I can able to connect to esxi console using the root account. Help, please.

    In the locked mode, you will only be able to connect through vCenter, not via SSH.

    See http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.security.doc/GUID-F8F105F7-CF93-46DF-9319-F8991839D265.html

  • How to change a user account non-root on multiple esx hosts 4

    We currently use the script below to change the root password, but we need a to change a non-root user account that does not have access to the root of how.

    So if the script could be changed to connect to each server with root and then change the password of the root no account that might be useful.

    Any help would be appreciated.

    -Steve

    #
    # This script changes the password to root on all ESX host in the esxservers.txt text file
    #

    # Add toolkit-VI #.
    Add-PSsnapin VMware.VimAutomation.Core
    Initialize - VIToolkitEnvironment.ps1

    # Get old credential root
    $oldrootPassword = "Enter the old root password" Read-Host - AsSecureString
    $oldrootCredential = new-object - typename System.Management.Automation.PSCredential - argumentlist 'root', $oldrootPassword

    # New information for the identification of root
    $newrootPassword = "Enter the new root password" Read-Host - AsSecureString
    $newrootCredential = new-object - typename System.Management.Automation.PSCredential - argumentlist 'root', $newrootPassword
    $newrootPassword2 = Read-Host "Retype new root password" - AsSecureString
    $newrootCredential2 = new-object - typename System.Management.Automation.PSCredential - argumentlist 'root', $newrootPassword2
    $WarningPreference = "SilentlyContinue".

    # Compare passwords
    If ($newrootCredential.GetNetworkCredential ().) Password - ceq $newrootCredential2.GetNetworkCredential (). {Password)

    # Create the new object of root account
    $rootaccount = new-Object VMware.Vim.HostPosixAccountSpec
    $rootaccount.id = 'root '.
    $rootaccount.password = $newrootCredential.GetNetworkCredential (). Password
    $rootaccount.shellAccess = ' / bin/bash ".

    # The list of text file host servers to change the root password on
    Get-Content esxservers.txt | %{
    SE connect-VIServer $_-user root - password $oldrootCredential.GetNetworkCredential (). Password - ErrorAction SilentlyContinue - ErrorVariable ConnectError. Out-Null
    If ($ConnectError - not $Null) {}
    Write-Host "ERROR: unable to connect to the ESX Server: ' $_
    }
    Else {}
    $si = get-view ServiceInstance
    $acctMgr = get-view-Id $si.content.accountManager
    $acctMgr.UpdateUser ($rootaccount)
    Write-Host "Root password changed successfully on ' $_
    Disconnect-VIServer-confirm: $False | Out-Null
    }
    }
    }
    Else {}
    Write-Host "ERROR: new root passwords do not match." Smooth... »
    }

    Try something like that.

    First, it prompts you for the password for root servers ESX (i).

    And then the account name, followed by the 2 times the new password

    #
    # This script changes the password of an account on all ESX hosts in the esxservers.txt textfile#
     # Add VI-toolkit # Add-PSsnapin VMware.VimAutomation.CoreInitialize-VIToolkitEnvironment.ps1
    
    # Get root password$rootPassword = Read-Host "Enter root password" -AsSecureString$rootCredential = new-object -typename System.Management.Automation.PSCredential -argumentlist "root",$rootPassword
    # Get account to change$account = Read-Host "Enter account"# Get new account credential$newaccountPassword = Read-Host "Enter new password" -AsSecureString$newaccountCredential = new-object -typename System.Management.Automation.PSCredential -argumentlist $account,$newaccountPassword$newaccountPassword2 = Read-Host "Retype new password" -AsSecureString$newaccountCredential2 = new-object -typename System.Management.Automation.PSCredential -argumentlist $account,$newaccountPassword2$WarningPreference = "SilentlyContinue"
    # Compare passwordsIf ($newaccountCredential.GetNetworkCredential().Password -ceq $newaccountCredential2.GetNetworkCredential().Password) {
    
        # Create new root account object    $accountSpec = New-Object VMware.Vim.HostPosixAccountSpec    $accountSpec.id = $account    $accountSpec.password = $newaccountCredential.GetNetworkCredential().Password
        $accountSpec.shellAccess = "/bin/bash"
        # Get list of Host servers from textfile to change account password on    Get-Content esxservers.txt | %{
            Connect-VIServer $_ -User root -Password $rootCredential.GetNetworkCredential().Password -ErrorAction SilentlyContinue -ErrorVariable ConnectError | Out-Null        If ($ConnectError -ne $Null) {
                Write-Host "ERROR: Failed to connect to ESX server:" $_        }
            Else {
                $si = Get-View ServiceInstance            $acctMgr = Get-View -Id $si.content.accountManager
                $acctMgr.UpdateUser($accountSpec)
                Write-Host "$account password successfully changed on" $_            Disconnect-VIServer -Confirm:$False | Out-Null        }
        }
    }
    Else {
    Write-Host "ERROR: New $account passwords do not match. Exiting..."}
    
  • How to restore the root permission administrator account

    on a test lab, a host ESX 4, I accidentally changed permission to the root account to the Administrator role to the role of read-only on one of the virtual machines.  This is why, when I connect to the host as root via vSphere Client, I have read-only access to one of the virtual machines.  What is the best way to fix that and go back to the root to have the role of administrator?

    Thanks in advance.

    Hello

    Moved to the Security Forum.

    You must log in as root on the ESX or ESXi console and modify the /etc/vmware/hostd/authorizations.xml and the ACEDataRoleID to-1 instead of what it is.

    Best regards
    Edward L. Haletky VMware communities user moderator, VMware vExpert 2009, 2010

    Now available: url = http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security'VMware vSphere (TM) and Virtual Infrastructure Security' [/ URL]

    Also available url = http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"VMWare ESX Server in the enterprise" [url]

    Blogs: url = http://www.virtualizationpractice.comvirtualization practice [/ URL] | URL = http://www.astroarch.com/blog Blue Gears [url] | URL = http://itknowledgeexchange.techtarget.com/virtualization-pro/ TechTarget [url] | URL = http://www.networkworld.com/community/haletky Global network [url]

    Podcast: url = http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcastvirtualization security Table round Podcast [url] | Twitter: url = http://www.twitter.com/TexiwillTexiwll [/ URL]

  • . VMDK copy with the non-root user account

    Hello

    On a machine of ESXi 3.5, I try to copy the files with a non-root account created

    I have same asigned this account non-root Administrator role

    I activated the SSH on the ESXi host

    The virtual machine is turned off

    With the non-root using winscp or plink with cp account I can copy the .log files and .vmx files but no other files

    When I log in to the root account can I copy all the files belonging to the virtual machine.

    Does anyone know what is the reason for this behavior?

    Any help greatly appreciated

    This is a permission problem.

    If you see the permission (for example with ls - l), you will see that only root has rw - for these files.

    You can change the permissions chmod g + rw File_List and add you're your root in Group (add entry in/etc/group).

    André

  • Find root password

    Upgrade to Mac OS Sierra and all my accounts now have Standard permissions, i.e. without administrator permissions.

    How I either upgrade my administrator account or find the password for Root?

    There is no root password. This is a disabled account. For good reasons.

    You can enable the root account, but that increases your risk of being hacked much, because the root is a known account that has unlimited privileges. Enabling root makes your Mac a rich target environment.

    But if that's how you want to live your life, Google "enable OS X root" and you will find several approaches.

Maybe you are looking for