Chat now with support
Chat with Support

One Identity Management Console for Unix 2.5.2 - Administration Guide

One Identity Privileged Access Suite for Unix Introducing One Identity Management Console for Unix Installing Management Console for Unix Preparing Unix hosts Working with host systems Managing local groups Managing local users Active Directory integration Authentication Services integration Privilege Manager integration Reporting Setting preferences Security Troubleshooting tips
Auto profiling issues Active Directory Issues Auditing and compliance Cannot create a service connection point Check Authentication Services agent status commands not available CSV or PDF reports do not open Database port number is already in use Elevation is not working Hosts do not display Import file lists fakepath Information does not display in the console License information in report is not accurate Out of memory error Post install configuration fails on Unix or Mac Privilege Manager feature issues Profile task never completes questusr account was deleted Readiness check failed Recovering from a failed upgrade Reports are slow Reset the supervisor password Running on a Windows 2008 R2 domain controller Service account login fails Setting custom configuration settings Single Sign-on (SSO) issues JVM memory tuning suggestions Start/stop/restart Management Console for Unix service Toolbar buttons are not enabled UID or GID conflicts
System maintenance Command line utilities Web services Database maintenance

Auto profiling issues

The following topics may help you resolve some problems related to Auto Profiling.

Auto profiling takes a long time

If auto-profiling multiple hosts does not complete within a reasonable amount of time and the host is configured for multiple consoles, make sure each console address is valid and available.

To validate the console addresses

  1. On the unresponsive host, open the <Service Account Home Dir>/.quest_autoprofile/notify.rc configuration file.

  2. Remove the entry for the unresponsive server.

Note: If the host continues to be unresponsive, here are some other things you can try:

  • Verify the network connection.
  • Verify the console address is correct in Settings | System Settings | General | Console information.

    If this has changed, re-configure the host for auto-profile.

  • Check the firewall settings. Make sure the non-SSL port is not blocked for incoming traffic on the host that has the Management Console for Unix software installation.

    The default is 9080.

    Note: If you have customized your HTTP or SSL/TLS ports, see Customizing HTTP and SSL/TLS ports for more information.

There could be any number of things that would prevent the host from communicating with the console.

Auto profiling returns an error

If you receive an error when auto-profiling a host after a recent upgrade from 1.0.x, verify the console host address in System Settings.

To validate the console host address

  1. From the Settings menu, navigate to System Settings | General | Console Information.
  2. Verify that the host address in the Console host address box is the Fully Qualified Domain Name address.

    The host address in the Console host address box on the Console Information settings may have been entered as a simple address in version 1.0. To perform some tasks in version 2.x without error, such as auto-profiling, the Console host address must be a Fully Qualified Domain Name.

Note: Setting up automatic profiling on a host with Security-Enhanced Linux (SELinux) enabled will fail due to the enhanced security-related restrictions on the system. Please contact Technical Support at for instructions on how to either work-around the issues or disable SELinux.

Active Directory Issues

The following topics may help you resolve some problems related to Active Directory.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating