OTD Error on Node - OTD-63617 Instance has not been stopped because failover could not be stopped due to insufficient privileges. Execute the stop-failover command

(Doc ID 2065139.1)

Last updated on NOVEMBER 14, 2016

Applies to:

Oracle Traffic Director - Version 11.1.1.6 to 11.1.1.9.0 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

It is observed that the OTD servers are Not usable after instance restart.

This happens after two configuration parameters are changed on 2 OTD instances and then a restart of one instance from the Admin Console.  The following error is seen:

Error on Node xxxx-xxxx: OTD-63617 Instance has not been stopped because failover could not be stopped due to insufficient privileges. Execute the stop-failover command on the node 'xxxxx-xxxx' as a privileged user.

  
After getting the above error,  an access of the 2 virtual servers hosting the OTD instances will result in the following Error:

-bash: fork: retry: Resource temporarily unavailable
-bash: fork: retry: Resource temporarily unavailable
-bash: fork: retry: Resource temporarily unavailable
-bash: fork: retry: Resource temporarily unavailable

Therefore it's impossible to use the servers.  The admin console is also not able to restart the instances.

Changes

The changed parameters are:

Maximum Threads = from default to 1024
Minumum Threads = from default to 1024
Acceptor Threads = from default to 4
 

  

- for the otd user, the number of minimum threads have been increased to 1024.
- each thread has a stack size of 262144 bytes.
- 1024 * 262144  == 256MB

  
  

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms