45 OTD-63026 to OTD-68881

OTD-63026: Cannot delete the configuration ''{0}''. It has been deployed to ''{1}'' node(s).

Cause: Cannot delete a configuration which has instances.

Action: Delete all the instances of the configuration before deleting the configuration.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63030: Cannot create instance of configuration ''{0}'' as an instance ''{1}'' of the same configuration already exists on host ''{2}''.

Cause: Multiple instances of a configuration are not supported on the same host.

Action: Create instance of the configuration on a different host after creating the OTD managed domain on the same.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63113: Error copying the configuration ''{0}''. For details, see the administration server log.

Cause: The admin server process may not have write permissions for <domain home>/config/fmwconfig/components/OTD or the disk may be full.

Action: Fix any permission or disk space related issues. Look at otd_admin.log for more details.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63114: Could not create a new configuration directory: {0}

Cause: The admin server process may not have write permissions for <domain home>/config/fmwconfig/components/OTD or the disk may be full.

Action: Fix any permission or disk space related issues. Look at otd_admin.log for more details.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63145: Configuration file ''{0}'' could not be saved. For details, see the administration server log.

Cause: The admin server process may not have write permissions for the file or the disk may be full.

Action: Fix any permission or disk space related issues. Look at otd_admin.log for more details.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63147: An error occurred while reading configuration file ''{0}''. For details, see the administration server log.

Cause: The file may not exist or the admin server process may not have permissions to read the file.

Action: Look at otd_admin.log for more details.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-67751: An error occurred while starting the instance. For details, see the server log.

Cause: Common causes are errors in server configuration and bind errors (Address already in use) on listener ports.

Action: Check if any other process is listening on any of the listener ports. Look at the instance's server log for more details.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-67753: An error occurred while restarting the instance. For details, see the server log.

Cause: Common causes are errors in server configuration and bind errors (Address already in use) on listener ports.

Action: Check if any other process is listening on any of the listener ports. Look at the instance's server log for more details.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-67762: Cannot stop instance ''{0}'' as failover is still running. Stop failover by running the WLST command 'otd_stopFailover' as a privileged user before stopping the instance.

Cause: If the instance is stopped while failover is still running, the VIP will not failover to the backup and any subsequent requests to the instance will fail.

Action: Stop failover before stopping the instance.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68108: Failover is not supported on the system due to missing prerequisites: ''{0}''

Cause: The failover feature depends on keepalived on Linux and vrrpd on Solaris.

Action: Install keepalived RPM on Linux or vrrp package on Solaris.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68153: The virtual IP ''{0}'' either has an invalid format or is an unknown hostname.

Cause: This could either be due to an invalid format for the IP address or the domain name resolution failed for the specified hostname. Failover will not work if the specified VIP cannot be resolved to a valid IP address.

Action: Specify a valid IP address or ensure that the hostname can be resolved to a valid IP address.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68154: The router ID is already in use for the failover group with virtual IP ''{0}'' in the configuration ''{1}''

Cause: The specified router ID is already in use. Router ID must be unique across all the failover groups.

Action: Choose a different router ID (should be between 1 and 255).

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68176: Failover cannot be started until the instance ''{0}'' has been started.

Cause: While starting failover will make the VIP accessible, the requests to the instance will fail if it is not running.

Action: Start failover only after starting the corresponding instance.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68213: Could not create the configuration directories.

Cause: The admin server process may not have write permissions for <domain home>/config/fmwconfig/components/OTD or the disk may be full.

Action: Fix any permission or disk space related issues. Look at otd_admin.log for more details.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68301: HTTP listener ''{0}'' is being referred by virtual server(s): {1}

Cause: The HTTP listener cannot be deleted as long as there are virtual servers that are referring to it.

Action: Before deleting the HTTP listener, either modify the referring virtual server(s) to use a different HTTP listener or delete them. To force delete the HTTP listener, execute the WLST command 'otd_deleteHttpListener' with 'force' option.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68408: Cannot delete the origin-server pool. It is referred by virtual server(s): {0}

Cause: The origin server pool cannot be deleted as long as there are routes that are referring to it.

Action: Before deleting the origin server pool, either modify the referring routes to use a different origin server pool or delete them.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68411: Cannot delete the origin-server pool since it is being used by the TCP proxies: {0}

Cause: The origin server pool cannot be deleted as long as there are TCP proxies that are referring to it.

Action: Before deleting the origin server pool, either modify the referring TCP proxies to use a different origin server pool or delete them.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68663: The certificate alias ''{0}'' either does not exist or is not of type ''Certificate''.

Cause: The certificate identified by the specified alias must be present in the keystore and should not be of type 'TrustedCertificate'.

Action: If the alias does exist in the keystore, it is likely that the entire certificate chain has not been added correctly into the keystore. This can be verified by checking if the specified alias is listed to be of type 'Certificate'.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68666: Cannot delete certificate because it is being referred by OTD configuration ''{0}''.

Cause: There is likely to be a listener, virtual server or an origin server pool that has been configured to use this certificate for SSL communication.

Action: Ensure that no entity is using this certificate before attempting to delete it. You can either delete the reference or change it to use some other certificate.

Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68881: CRL management is not supported since crl-path ''{0}'' is external to the configuration.

Cause: CRL management is not supported since the configured crl-path is external to the configuration.

Action: To enable CRL management, reset crl-path to the default path or to any directory within the configuration.

Level: 1

Type: NOTIFICATION

Impact: ADMIN