vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you change the traceSpecification configuration for one instance, the change doesn't apply to other instances of the same app. For example, your app uses log4j and you have 2 instances for this app. You can change the log level of instance 0 from info to debug, but the log level of instance 1 remains as info.



 How to fix it 

No action is required. This behavior is expected.





 Disk quota exceeded 

You might see, in your app log, that your disk quota is exceeded.

 What’s happening 

You see the Disk quota exceeded error message in the log of your app.

 Why it’s happening 

This problem occurs for one of the following reasons:



* The dump files are generated with the running app instances, and the files use up the allocated disk quota. By default, the disk quota for one app instance is 1 GB. You can check your disk usage by clicking Dashboard > Application > App Runtime. The following example shows the runtime information, including disk usage, for two instances of an app:



Instance	State	CPU	Memory Usage	Disk Usage

0		Running	1.0%	344.8MB/512MB	236.8MB/1GB
2		Running	2.3%	361.2MB/512MB	235.7MB/1GB



* The disk quota is limited by the current organization quota.



 How to fix it 

Use one of the following methods:



* Delete dump files after they are downloaded.
* Redeploy the app with a bigger disk quota by including the following entry in the deployment manifest:

disk_quota: 2048









 Liberty for Java 



 App fails to start accepting connections 

 What’s happening 

A Liberty app fails to start with a "Failed to start accepting connections" error. For example, the error in the logs might look like the following:
The [Reject unauthorized](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-add-destdest-user-auth) of the destination is enabled and the CN in the certificate presented is the IP address of the gateway, but the certificate does not have a SAN matching the IP address and the client fails to connect.

Due to hostname resolution issues we are using the IP address in our destination. The CN in the certificate presented is the IP address of the gateway, but the certificate does not have a SAN matching the IP address and the client fails to connect

You have created a destination using TLS, but instead of using the destination's hostname you have used it's IP address. When connecting the client the following error is being thrown.

[2015-10-15 13:00:04.866] [INFO] Connection 0 is being established to 10.3.20.31:443
[2015-10-15 13:00:05.426] [ERROR] Connection 0 to destination 10.3.20.31:443 had error: IP: 10.3.20.31 is not in the cert's list:
[2015-10-15 13:00:05.427] [INFO] Connection 0 to 10.3.20.31:443 was closed





 Why it is happening 

What is going on is that the SSL verification code in the gateway client is treating this destination differently because it uses an IP address rather than a hostname. Instead of matching with the cert's CN, it is looking in the cert's SAN for a match of the IP address. Since there is no SAN in the cert, it sees it as a bad connection and fails the SSL handshake.





 How to fix it 

You can disable the Reject unauthorized of the destiantion, or upload the correct certificate as mentioned below:

If you look at the error message it does not say CN, (e.g. [ERROR] Connection ## had error: Host: . is not cert's CN: ), but the cert's list, which leads me to believe you have generated your self-signed cert incorrectly.
See also [different ways to run VMware workloads in IBM Cloud](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-v2t-migrationfaq-v2t-migration-vmware-platforms).





 If I am using BYOL on my VMware Solutions - vCenter Server hosts how does this impact the upgrade? 

Upgrading vSphere software is your responsibility. However, with Bring Your Own License (BYOL) you access VMware Support directly by using your license agreement. IBM Cloud provides support for your bare metal servers infrastructure on the IBM Cloud. For more information, see [Upgrading vCenter Server vSphere software from vSphere 6.5 or 6.7 to 7.0](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vsphere_70_upgrade). If your vCenter Server instance is running NSX-V, consider moving to vCenter Server with NSX-T. This lift and shift upgrade approach might be more beneficial due to the end of support of NSX-V.

See also [different ways to run VMware workloads in IBM Cloud](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-v2t-migrationfaq-v2t-migration-vmware-platforms).





 What product is it running in the VMware Solutions - vCenter Server instance? 

For a vCenter Server instance, the following information is displayed on the VMware Solutions user interface.



* VMware NSX networking solution - NSX-T
* NSX for vSphere - 3.1.1.0
* NSX license edition - VMware NSX Advanced



What product is it running in the vCenter Server instance?

This vCenter Server instance is running NSX-T version 3.1.1. Due to the licensing agreement between IBM Cloud and VMware, NSX-V licenses were being used for NSX-T instances.
In CouchDB version 2 onwards, you are allowed to [specify the replica count](https://docs.couchdb.org/en/stable/cluster/databases.htmlcreating-a-database) when you create a database. However, you are not allowed to change the replica count value from the default of 3. In particular, it is not possible to specify a different replica count value when you create a database. For further help, go to the [IBM Cloud Support portal](https://www.ibm.com/cloud/support).





 What are the R and W arguments? 

Some requests can have arguments that affect the coordinator's behavior when it answers the request. These arguments are known as R and W after their names in the request query string. They can be used for single document operations only. They have no effect on general 'query style' requests.

In practice, it is rarely useful to specify R and W values. For example, specifying either R or W does not alter consistency for the read or write.



 What is R? 

The R argument can be specified on single document requests only. R affects how many responses must be received by the coordinator before it replies to the client. The responses must come from the nodes that host the replicas of the shard that contains the document.

Setting R to 1 might improve the overall response time because the coordinator can return a response more quickly. The reason is that the coordinator must wait only for a single response from any one of the replicas that host the appropriate shard.

If you reduce the R value, it increases the likelihood that the returned response is not based on the most up-to-date data. This state occurs because of the [eventual consistency](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-cap-theorem) model used by IBM Cloudant. Using the default R value helps mitigate this effect.

The default value for R is 2. This value corresponds to most of the replicas for a typical database that uses three shard replicas. If the database has multiple replicas that are greater than or less than 3, the default value for R changes correspondingly.





 What is W?
The custom IBM Watson™ Knowledge Studio model overrides the default Relation extraction enrichment.

Only one IBM Watson™ Knowledge Studio model can be assigned to an enrichment.







 Keyword extraction 

Important topics in your content that are typically used when indexing data, generating tag clouds, or when searching. Discovery automatically identifies supported languages in your input content, and then identifies and ranks keywords in that content.

Example portion of a document enriched with Keyword Extraction:

{
"text": "The stockholders were pleased that Acme Corporation plans to build a new factory in Atlanta, Georgia.",
"enriched_text": {
"keywords": [
{
"text": "Acme Corporation",
"sentiment": {
"score": 0
},
"relevance": 0.985203
},
{
"text": "new factory",
"sentiment": {
"score": 0
},
"relevance": 0.821033
},
{
"text": "stockholders",
"sentiment": {
"score": 0
},
"relevance": 0.66497
},
{
"text": "title",
"sentiment": {
"score": 0
},
"relevance": 0.332438
},
{
"text": "Atlanta",
"sentiment": {
"score": 0
},
"relevance": 0.307723
},
{
"text": "Georgia",
"sentiment": {
"score": 0
},
"relevance": 0.306485
}
]
}
}
Show more

In the preceding example, you could query the keyword text by accessing enriched_text.keywords.text

sentiment is calculated for keywords even if the sentiment enrichment is not selected.
See also [account](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2012863).





 entitlement 

In software licensing, the maximum allowed allocation of capacity as determined by a license agreement.





 entity 



* A set of details that are held about a real-world object such as a person, location, or bank account. An entity is a kind of item.
* A person, object, or concept about which information is stored.
* A mention that is annotated by an entity type.







 entity type 

The type of entity that a mention represents without consideration for context. For example, the mention IBM might be annotated by the entity type ORGANIZATION. In an entity-relationship model, an entity type is the thing that is being modeled or the thing that a mention refers to, such as the name of a person or place. Different entity types have different sets of attributes such as "surname" or "home town", and are connected through relationships like "lives in". An entity type exists independently and can be uniquely identified.





 envelope encryption 

The process of encrypting data with a data encryption key and then encrypting the key with a root key that can be fully managed.





 evidence 

The collected raw data to support an assessment for auditing purposes.





 experimental product 

A product that IBM makes available solely for evaluation and testing purposes, and might be unstable or not compatible with previous versions. An experimental product can be discontinued with short notice. There are no warranties, SLAs or support provided, and experimental products are not intended for production use.





 explainability 

The ability of human users to trace, audit, and understand predictions that are made in applications that use AI systems.







 F 



 F1 score 

A measure of a test's accuracy that considers both precision and recall to compute the score. The F1 score can be interpreted as a weighted average of the precision and recall values. An F1 score reaches its best value at 1 and worst value at 0.





 false negative 

An answer or annotation that is correct, but was predicted to be incorrect.





 false positive 

An answer or annotation that is incorrect, but was predicted to be correct.
-i, --new-iops INTEGER Performance Storage IOPS, between 100 and 6000
in multiples of 100 [only for performance
volumes] If no IOPS value is specified, the
original IOPS value of the volume will be
used.
Requirements: [If original IOPS/GB
for the volume is less than 0.3, new IOPS/GB
must also be less than 0.3. If original
IOPS/GB for the volume is greater than or
equal to 0.3, new IOPS/GB for the volume must
also be greater than or equal to 0.3.]
-t, --new-tier [0.25|2|4|10] Endurance Storage Tier (IOPS per GB) [only for
endurance volumes] If no tier is specified,
the original tier of the volume will be
used.
Requirements: [If original IOPS/GB
for the volume is 0.25, new IOPS/GB for the
volume must also be 0.25. If original IOPS/GB
for the volume is greater than 0.25, new
IOPS/GB for the volume must also be greater
than 0.25.]
-h, --help Show this message and exit.





 Adjusting the IOPS on your Storage with the API 

You can adjust the IOPS by using an API call to the SOAP web service. The following sample API calls can be called from the scripting language of your choice.

For more information about the SLAPI, see the [SLDN](http://sldn.softlayer.com/reference/softlayerapi).



* Adjust IOPS on Performance storage volume.

<?xml version="1.0" encoding="UTF-8"?>
If the cumulative score of all the matched OWASP rules exceeds that threshold, rule 981176 is triggered and blocks the request.

This means that all requests blocked by OWASP show on your Security Events as blocked by 981176. Expand the event details and view the Event Triggers section to see the individual OWASP rules that matched to increase the request’s threat score.





 What do I do if valid traffic is blocked? 

Expand each event to see event details. The Event Triggers section displays all the individual OWASP rules that matched for OWASP rule-triggered events. Decide whether this traffic looks normal for your website, or if it was appropriately blocked. If you decide that this block is a false positive, you can go back to your WAF configuration and disable individual OWASP rules until this request no longer exceeds your sensitivity threshold.





 Security event retention policy 

Enterprise plans retain security events for 90 days. Standard plans retain security events for 30 days.
volumes] If no IOPS value is specified, the
original IOPS value of the volume will be
used.
Requirements: [If original IOPS/GB
for the volume is less than 0.3, new IOPS/GB
must also be less than 0.3. If original
IOPS/GB for the volume is greater than or
equal to 0.3, new IOPS/GB for the volume must
also be greater than or equal to 0.3.]
-t, --new-tier [0.25|2|4|10] Endurance Storage Tier (IOPS per GB) [only for
endurance volumes] If no tier is specified,
the original tier of the volume will be
used.
Requirements: [If original IOPS/GB
for the volume is 0.25, new IOPS/GB for the
volume must also be 0.25. If original IOPS/GB
for the volume is greater than 0.25, new
IOPS/GB for the volume must also be greater
than 0.25.]
-h, --help Show this message and exit.

The Operating system must rescan the storage and reload the multipath device map to reflect the expanded volume size. Resizing of the partition and file system are also required. For more information about expanding the file system, see your OS Documentation. For example, [RHEL 8 - Modifying Logical Volume](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_logical_volumes/modifying-the-size-of-a-logical-volume_configuring-and-managing-logical-volumes) or [Microsoft® - Extend a basic volume](https://docs.microsoft.com/en-us/windows-server/storage/disk-management/extend-a-basic-volume).





 Resizing storage with the API 

You can increase your storage capacity by using an API call to the SOAP web service. The following sample API calls can be called from the scripting language of your choice.
A % B All number types Returns the remainder after dividing A by B. For example, 13.7 % 3 returns 1.7. The type of the result is the same as the type of the operand that is highest in the type hierarchy. For example, if A is of type FLOAT and B is of type INT, the result is of type FLOAT. 
 A DIV B Integer types Returns the integer part of the result of dividing A by B. For example, 13.7 DIV 3 returns the integer 4. 
 A & B All number types Returns the result of bitwise AND of A and B. The type of the result is the same as the type of the operand that is highest in the type hierarchy. 
 `A B` All number types 
 A ^ B All number types Returns the result of bitwise XOR of A and B. The type of the result is the same as the type of the operand that is highest in the type hierarchy. 







 String operator 



Table 52. String operator.

 Operator Operand types Description 

 `A B` 







 Comparison operators 



Table 53. Comparison operators.

 Operator Operand types Description 

 A = B All primitive types Returns TRUE if A is equal to B, FALSE otherwise. 
 A == B All primitive types Synonym for the equal (=) operator. 
 A <> B All primitive types Returns NULL if A or B is NULL, TRUE if A is not equal to B, FALSE otherwise. 
 A != B All primitive types Synonym for the not equal (<>) operator. 
 A < B All primitive types Returns NULL if A or B is NULL, TRUE if A is less than B, FALSE otherwise. 
 A <= B All primitive types Returns NULL if A or B is NULL, TRUE if A is less than or equal to B, FALSE otherwise. 
 A !> B All primitive types Returns NULL if A or B is NULL, TRUE if A is not greater than B, FALSE otherwise. 
 A > B All primitive types Returns NULL if A or B is NULL, TRUE if A is greater than B, FALSE otherwise. 
 A >= B All primitive types Returns NULL if A or B is NULL, TRUE if A is greater than or equal to B, FALSE otherwise.
Many IT organizations document their operational procedures in a runbook. A runbook is a set of standardized documents, references and procedures that explain common recurring IT tasks. IT staff refer to the runbook for an optimal way to get their work done. Runbooks improve organizational efficiency through standardization and they assist with onboarding employees more effectively. The following are the two typical types of runbooks.



1. General documentation used to capture procedures, guides, and tasks. They tend to be general in nature, and refer to existing documentation provided by vendors.
2. Specialized documentation written for the enterprise. This documentation is specific to a system, an application, or suite of applications and is not covered by vendors documentation. When you document your specialized documentation, the following structure is recommended:



* Overview - An overview of the service with sections that describes:



* What is the service and why is the service needed by the enterprise?
* Who are the primary contacts for the service?
* How to report issues with the service.



* Build - Focused on the development teams and the main software components of the service and how the service is constructed. Information on software products, locations of OVAs, distribution media, or the location of the source code. The required steps for packaging or distributing the release. It includes any required instructions for how a new developer gets started.
* Deployment - Focused on the operations team and how to deploy the software. It includes details of the hardware and virtualized infrastructure and how to build the virtual machines (VMs) including vCPU, RAM and disk requirements, OS version and configuration, what middleware or packages to install.
* Procedures - Step-by-step instructions for common tasks like add, change and delete, common issues and their solutions, troubleshooting advice.
* Troubleshooting - A list of common alerts from the monitoring system that include step-by-step tasks for these alerts, and generic guidance on troubleshooting the service.
* Disaster recovery plans and procedures - Details on how to recover the service at another location due to a disaster at the primary location.
* Service level agreement - The agreed service parameters such as operational level agreements, key point indicators, availability goals, recovery point objectives, recovery time objective.
* VMware NSX networking solution - NSX-T
* NSX for vSphere - 3.1.1.0
* NSX license edition - VMware NSX Advanced



What product is it running in the vCenter Server instance?

This vCenter Server instance is running NSX-T version 3.1.1. Due to the licensing agreement between IBM Cloud and VMware, NSX-V licenses were being used for NSX-T instances. Newer vCenter Server instances use NSX-T licenses, so the instance is correctly licensed.





 Can I do an in place vSphere upgrade for my vSphere 6.7 with NSX-T VMware Solutions - vCenter Server instance? 

Yes, but we strongly advise deploying a new vCenter Server instance and then use the lift and shift migration approach. For more information about the in place vSphere upgrade, see [Upgrading vCenter Server vSphere software from vSphere 6.5 or 6.7 to 7.0](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vsphere_70_upgrade) and the [important considerations](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vsphere_70_upgradevc_vsphere_70_upgrade-considerations).

Also, review the following key considerations:



* At the end of the documented process, your vCenter Server instance is running vSphere 7.0 Update 1c with N-VDS distributed switches. This configuration is different than the currently supported [Software BOM for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bomvc_bom-software), which is vSphere 7.0 Update 3c with Distributed vSwitch 7.0.0.
Why do I see a certificate warning with OpenVPN Connect v2 or v3? 

When the authentication mode is user ID and passcode only, a client certificate is not required. However, this approach is less secure than using both certificate and user ID and passcode authentication.

  What’s happening 

OpenVPN Connect V2 displays the error Missing External PKI alias.

OpenVPN Connect V3 displays the error Miss external certificate.

  Why it’s happening 

For v2, this message is a bug. For v3, this message is a warning that you can ignore.

  How to fix it 

Try the following options to resolve this issue:



1.  Select one of the following steps:



*  For OpenVPN Connect v2, edit the VPN client profile by adding a random client private key and certificate, then reimport the client profile into the OpenVPN Connect V2 client.
*  

*  For OpenVPN Connect v3, select to continue and skip the warning message.





2.  Use another VPN client, such as Tunnelblick. For OpenVPN Connect version 2 users, you can upgrade to version 3.
Also referred to as hostname.
* protocol: Protocol used to set up services. Can be HTTP, HTTPS, or a combination of the two, HTTP_AND_HTTPS.
* cname: Canonical name record aliases the hostname. Can be provided by the user, or system-generated. If user-provided, it should be less than 64 alphanumeric characters and must be unique. If not provided, one is generated when the mapping is created.
* certificateType: Type of certificate being used by a mapping. Can be WILDCARD_CERT or SHARED_SAN_CERT. Value is 0 for HTTP mappings.
* respectHeaders: A Boolean value that, if set to 'true', causes TTL settings in the origin to override CDN TTL settings.
* header: Specifies host header information that is used by the origin.



The following attributes are related to Cloud Object Storage (COS):



* bucketName: Unique name of your bucket for S3 object storage.
* fileExtension: File extensions that are allowed.



The following attribute is related to configuring Hotlink Protection:



* hotlinkProtection: See the [hotlink protection class](https://cloud.ibm.com/docs/CDN?topic=CDN-hotlink-protection-class) for more details.



The following attribute is related to Dynamic Content Acceleration (DCA):



* dynamicContentAcceleration: See the [Dynamic Content Acceleration class](https://cloud.ibm.com/docs/CDN?topic=CDN-dynamic-content-acceleration-container) for more details.