vania-janet/multiturn-rag-retrieval-data huggingface dataset:
TIMESTAMP Operation update with the Env(s) "virtuozzo01.softlayer.local" is finished with errors: Can not update packages: exec failed: Error: URL $RH_SERVER/download/mirrors/redhat-as4 contents undefined variable You can define this variable in /etc/vztt/url.map. See Virtuozzo Installation Guide for more details. . Failed 
 TIMESTAMP Click here to open/close the operation details.Update OS Template Cache Failed 
 TIMESTAMP Operation update with the Env(s) "virtuozzo01.softlayer.local" and package(s) .redhat-el5-x86_64 is started 
 TIMESTAMP Operation update with the Env(s) "virtuozzo01.softlayer.local" is finished with errors: Can not update packages: exec failed: Error: URL $RH_SERVER/download/mirrors/redhat-el5 contents undefined variable You can define this variable in /etc/vztt/url.map. . Failed 
 TIMESTAMP Click here to open/close the operation details.Update OS Template Cache Failed <br> <br>Oct 29, 2008 01:16:56 PM Operation update with the Env(s) "virtuozzo01.softlayer.local" and package(s) .sles-10-x86_64 is started 
 TIMESTAMP Operation update with the Env(s) "virtuozzo01.softlayer.local" is finished with errors: Can not update packages: exec failed: Error: URL $SLES_SERVER/download/mirrors/suse-es10 contents undefined variable . Failed 
 TIMESTAMP Completing the process Failed 



* Why can I ping my ServiceVE but cannot log in to via SSH (PIM/PMC)?

Make sure that the host node doesn't have any IP addresses assigned other than the IP addresses that are listed in the Portal (1 public IP and 1 private IP [located in 10.0.0.0/8]).

If you have any range files that are configured on the host node, then you need to remove these files and restart networking.
The nfsnotify resource sends FSv3 reboot notifications after the entire NFS deployment initializes.

On NODE1, run the following command.

pcs resource create nfs_notify nfsnotify source_host=${NFS_ip} --group nfsgroup

The NFS cluster setup is now complete.

On NODE1, run the following command to check the status.

pcs resource status

Sample output:

 pcs resource status
* Resource Group: nfsgroup:
* nfs_vg (ocf::heartbeat:LVM-activate): Started cl-nfs-1
* nfs_fs1 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_fs2 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_fs3 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_daemon (ocf::heartbeat:nfsserver): Started cl-nfs-1
* nfs_export (ocf::heartbeat:exportfs): Started cl-nfs-1
* nfs_ip (ocf::heartbeat:IPaddr2): Started cl-nfs-1
* nfs_notify (ocf::heartbeat:nfsnotify): Started cl-nfs-1









 Testing the NFS server cluster 

You can validate the NFS resource configuration in a high availability cluster by using the following procedures. You can mount the exported file system with either NFSv3 or NFSv4. Run the following tests to verify that the NFS cluster functions.



 Test1 - Testing the NFS export 

Use the following information to test the NFS export.

Run all the commands on an NFS client node outside the HA NFS cluster.

Verify the NFS exports.

showmount -e ${NFS_ip}

The showmount command displays information about file systems that are exported by an NFS Server (NFS v3).
![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) All peers on a channel must use the same state database. You cannot change databases after the peer is deployed. 
 Deployment zone selection When your Kubernetes cluster is configured across multiple zones, you can choose the zone where you want the node to be deployed. ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) Must be configured when the node is deployed. You cannot change zones for a node after the node is deployed. 
 Override node configuration Specify additional node configurations that are not available in the console panels. ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) Overrides can be configured when a node is deployed or updated. 







 Before you begin 

Before attempting to deploy a node, it is the network operator's responsibility to monitor the cluster CPU, memory, and storage usage, and ensure that adequate resources are available in the cluster for the node.



 Allocating resources 

Because your instance of the IBM Blockchain Platform console and your Kubernetes cluster do not communicate directly about the resources that are available, the process for deploying components by using the console must follow this pattern:



1. Size the deployment that you want to make.
If the new node was added in Console 1, you can skip down to [Adding the node to the application channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer-consenters-add).







 Console 2: export the Ordering Service_2 node 

After the Ordering Service_2 node has successfully been created and added to the system channel, Console 2 must export a JSON representing the node to every channel member (in this tutorial, this means exporting it to Console 1). This will allow all channel members to have an accurate record of the nodes in the ordering service (which will allow the node to be selected from drop down lists, for example when adding consenters to channels).

To do this, click on the node and then on the "download" button. This will download a JSON representing the node to your filesystem. This JSON can then be sent to other network members out of band.

Once the node has been exported to the consoles of other channel members, those members will be able to add the node as a consenter to existing channels (where desired), and be able to accurately monitor the health of the ordering service.

Note that adding a new node to the system channel does not automatically add the node to any application channels. If you want to add this node to any existing application channels, you will have to add them to the consenter set of each of those channels separately. For information about how to do that, see [Adding an ordering node to the consenter set](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer-update-channel1) of a channel.





 Console 1: add the Ordering Service_2 node to your console 

This step should be completed by every channel member.

To do this, click on the tile representing the ordering service, which in this tutorial is called Ordering Service. Then click on the Ordering nodes tab and then the Add another node tab.

Then click Import an existing node.
Upgrading and deleting deployed nodes 

ATTENTION!! IBM Blockchain Platform SaaS Edition is being replaced by IBM Support for Hyperledger Fabric!! IBM Blockchain Platform SaaS Edition will no longer be supported after July 31, 2023. Customers have been directed to migrate their networks by July 31, 2023. After this date, IBM Blockchain Platform SaaS networks that are not migrated to IBM Support for Hyperledger Fabric will be at risk for potential security vulnerabilities. A migration tool is provided from your console, and the disruption to your network is minimal. See [Migrating to IBM Support for Hyperledger Fabric](https://cloud.ibm.com/docs/blockchain?topic=blockchain-migrating-to-hlf-support) for details.

After creating CAs, peers, and ordering nodes, you need to monitor the resources used by the nodes and potentially reallocate resources.

Target audience: This topic is designed for network operators who are responsible for creating, monitoring, managing, and upgrading their components in the blockchain network.

After a node has been created, there are three main ways to update it.



1. Update its configuration. Just as it is possible to override configuration parameters when deploying a node, it is possible to edit many parameters and redeploy the node. For more information, see our topic on [Advanced deployment options](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deployment).
2. Increase the resources allocated to it. If you notice that the performance of a node is beginning to lag or that its storage is beginning to run out, you can choose whether to deploy a larger node and join it to channels or whether to increase the resources allocated to your existing node.
3. Upgrade its Fabric version. Every node is deployed using a release version of Hyperledger Fabric. When new versions of Fabric become available on IBM Blockchain Platform, Upgrade available is visible on the tile representing the node. While upgrading to a new version of Fabric is always recommended, unless is rendered necessary by the capabilities of channels you want to join, it is typically optional.
If dest:path doesn’t exist, it is created and the source:path contents go there.

rclone sync source:path dest:path [flags]



 Using rclone from multiple locations at the simultaneously 

You can use rclone from multiple places simultaneously if you choose different subdirectory for the output:

Server A> rclone sync /tmp/whatever remote:ServerA
Server B> rclone sync /tmp/whatever remote:ServerB

If you sync to the same directory than you can use rclone copy, otherwise the two processes might delete each other's others files:

Server A> rclone copy /tmp/whatever remote:Backup
Server B> rclone copy /tmp/whatever remote:Backup





 --backup-dir=DIR 

When using sync, copy or move any files that would have been overwritten or deleted are moved in their original hierarchy into this directory.

If --suffix is set, then the moved files have the suffix added to them. If there is a file with the same path (after the suffix has been added) in the directory, it is overwritten.

The remote in use must support server-side move or copy and you must use the same remote as the destination of the sync. The backup directory must not overlap the destination directory.

rclone sync /path/to/local remote:current --backup-dir remote:old

will sync/path/to/local to remote:current, but for any files that would have been updated or deleted will be stored in remote:old.

If running rclone from a script you might want to use today’s date as the directory name passed to --backup-dir to store the old files, or you might want to pass --suffix with today’s date.







 rclone daily sync 

Scheduling a backup is important to automating backups. Depending on your platform depends on how you do this. Windows can use Task Scheduler while MacOS and Linux can use crontabs.



 Syncing a Directory 

Rclone syncs a local directory with the remote container, storing all the files in the local directory in the container.
If the worker node that the NLB IP address is on is removed, a Keepalive daemon that constantly monitors the IP automatically moves the IP to another worker node. You can assign any port to your NLB. The NLB serves as the external entry point for incoming requests for the app. To access the NLB from the internet, you can use the public IP address of your NLB and the assigned port in the format <IP_address>:<port>. You can also create DNS entries for NLBs by registering the NLB IP addresses with subdomains.

When you expose an app with an NLB service, your app is automatically made available over the service's NodePorts too. [NodePorts](https://cloud.ibm.com/docs/openshift?topic=openshift-nodeport) are accessible on every public and private IP address of every worker node within the cluster. To block traffic to NodePorts while you are using an NLB, see [Controlling inbound traffic to network load balancer (NLB) or NodePort services](https://cloud.ibm.com/docs/openshift?topic=openshift-network_policiesblock_ingress).

Kubernetes 1.20 and later: Although the Kubernetes [SCTP protocol](https://kubernetes.io/docs/concepts/services-networking/service/sctp) is generally available in the Kubernetes community release, creating load balancers that use this protocol is not supported in IBM Cloud Kubernetes Service clusters.



 Comparison of basic and DSR load balancing in version 1.0 and 2.0 NLBs 

When you create an NLB, you can choose a version 1.0 NLB, which performs basic load balancing, or version 2.0 NLB, which performs direct server return (DSR) load balancing.

How are versions 1.0 and 2.0 NLBs similar?
: Version 1.0 and 2.0 NLBs are both Layer 4 load balancers that exist in the Linux kernel space. Both versions run inside the cluster, and use worker node resources. Therefore, the available capacity of the NLBs is always dedicated to your own cluster.
* nfs_fs3	(ocf::heartbeat:Filesystem):	 Started cl-nfs-2
* nfs_daemon	(ocf::heartbeat:nfsserver):	 Started cl-nfs-2
* nfs_export	(ocf::heartbeat:exportfs):	 Started cl-nfs-2
* nfs_ip	(ocf::heartbeat:IPaddr2):	 Started cl-nfs-2
* nfs_notify	(ocf::heartbeat:nfsnotify):	 Started cl-nfs-2

Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/enabled
Partition leadership 

Each partition has one server in the cluster that acts as the partition's leader and other servers that act as the followers. All produce and consume requests for the partition are handled by the leader. The followers replicate the partition data from the leader with the aim of keeping up with the leader. If a follower is keeping up with the leader of a partition, the follower's replica is in-sync.

When a message is sent to the partition leader, that message is not immediately available to consumers. The leader appends the record for the message to the partition, assigning it the next offset number for that partition. After all the followers for the in-sync replicas replicated the record and acknowledged that they wrote the record to their replicas, the record is now committed. The message is available for consumers.

If the leader for a partition fails, one of the followers with an in-sync replica automatically takes over as the partition's leader. In practice, every server is the leader for some partitions and the follower for others. The process of designating a new leader replica is called a leadership election. The leadership of partitions is dynamic and changes as servers come and go.

Applications do not need to take specific actions to handle the change in the leadership of a partition. The Kafka client library automatically reconnects to the new leader, although the latency increases while the cluster settles.
: For more information, see the change logs: [4.11](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_411), [4.10](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410), [4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49), [4.8](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48), [4.7](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_47), [4.6](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_46).

Worker node fix pack 4.11.9_1529_openshift, 4.10.37_1542_openshift, and 4.9.50_1562_openshift
: For more information, see the change logs: [4.11](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_411), [4.10](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410), and [4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49).

Cloud Image Key Synchronizer add-on version 1.0.0_1200
: For more information, see the [change log](https://cloud.ibm.com/docs/openshift?topic=openshift-image-key-synchronizer-changelog).





 26 October 2022
host-name asloma-tc1b-18-10g-pubpriv-dual-ha1-vsrx-vSRX-Node0;
}
}
node1 {
system {
host-name asloma-tc1b-18-10g-pubpriv-dual-ha1-vsrx-vSRX-Node1;
}
}
}
apply-groups "${node}";
system {
login {
class security {
permissions [ security-control view-configuration ];
}
user admin {
uid 2000;
class super-user;
authentication {
encrypted-password "xxx"; SECRET-DATA
}
}
}
root-authentication {
encrypted-password "xxx”; SECRET-DATA
}
services {
ssh {
root-login allow;
}
netconf {
ssh {
port 830;
}
}
web-management {
http {
interface fxp0.0;
}
https {
port 8443;
system-generated-certificate;
interface [ fxp0.0 reth1.0 reth0.0 ];
}
session {
session-limit 100;
}
}
}
name-server {
10.0.80.11;
10.0.80.12;
}
syslog {
user * {
any emergency;
}
file messages {
any any;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
ntp {
server 10.0.77.54;
}
}
chassis {
cluster {
control-link-recovery;
reth-count 4;
heartbeat-interval 2000;
heartbeat-threshold 8;
redundancy-group 0 {
node 0 priority 100;
node 1 priority 1;
command: ["/bin/sh", "-c"]
args:
- >
while true; do
sleep 100000;
done
volumes:
- name: modifysys
hostPath:
path: /sys
Show more
2. Apply the daemon set to your worker nodes. The changes are applied immediately.

oc apply -f worker-node-kernel-settings.yaml



To revert your worker nodes sysctl parameters to the default values, follow these steps.



1. Delete the daemon set. The initContainers that applied the custom settings are removed.

oc delete ds kernel-optimization
2. [Reboot all worker nodes in the cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_reboot). The worker nodes come back online with the default values applied.









 Optimizing network keepalive sysctl settings 

If a pod has long running TCP connections that are occasionally disconnected when they are idle for a period of time, it might help to change the sysctl keepalive settings for the pod.

These scenarios and suggested settings are also described in the [Troubleshooting Outgoing Connection Issues with IBM VPC Public and Service Gateways](https://www.ibm.com/cloud/blog/troubleshooting-outgoing-connection-issues-with-ibm-vpc-public-and-service-gateways) blog.

The following sysctl network values can be set on all worker nodes in a cluster by using the daemonset described in the [Modifying worker node kernel settings](https://cloud.ibm.com/docs/openshift?topic=openshift-kernelworker-kernel-ds) section. However, there currently isn't a way to set these sysctl keepalive settings on all pods by default in a cluster. The best way to modify the settings on all pods is to use a privileged initContainer.
set interfaces bonding bond0 vif 1000 vrrp vrrp-group 10 virtual-address 192.168.10.1/24

On the second Vyatta:

set interfaces bonding bond0 vif 1000 address 172.16.0.11/29
set interfaces bonding bond0 vif 1000 vrrp vrrp-group 10 sync-group vgroup10
set interfaces bonding bond0 vif 1000 vrrp vrrp-group 10 priority 199
set interfaces bonding bond0 vif 1000 vrrp vrrp-group 10 virtual-address 192.168.10.1/24

In this case, both Vyattas have their own IP that won't conflict with the subnet that is allocated. You can choose almost any private range you want. Just pick a small subnet that won't conflict with any other routes you might have, such as a subnet range over an IPsec tunnel, or an 10.0.0.0/8 address that conflicts with Softlayer's.

Also add a sync-group name. All VRRP addresses should be a part of the same sync-group. This is so that any failure on one interface causes all the interfaces in the same sync-group to fail over as well. Otherwise, you could end up with some being MASTER, and others in BACKUP. Use the same name in the bond0 and bond1 native VLAN configuration.

The bond0 and bond1 VRRP configuration might have a line for rfc3768-compatibility. This is not needed for VRRP on a VIF, only the native VLAN of bond0 and bond1.

On a newly provisioned gateway pair, config-sync only has a minimal configuration:

config-sync {
remote-router 10.28.94.195 {
password 
sync-map syncme
username vyatta
}

You must add rules to determine which configuration branches to migrate over. For example, if you want to have the firewall and IPsec configuration to be pushed, add these commands:

set system config-sync sync-map syncme rule 1 action include
set system config-sync sync-map syncme rule 1 location firewall
In addition, we revamped the App Management feature in the Node.js buildpack, which enables utilities like shell, node-inspector, IBM Cloud Live Sync, and more. See [Managing Liberty and Node.js apps](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_management) for details.





 14 June 2015 

Updated Liberty buildpack v1.19-20150608-1717
: The buildpack contains a number of app management enhancements that include support for the development console and web-based shell access. See the [app management documentation](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_management) for details.



* The buildpack also contains a fix for a problem where the Liberty feature for the Monitoring and Analytics service could not be found.







 27 May 2015 

Updated Liberty buildpack v1.18-20150519-1642
: The buildpack contains an updated version of the Liberty profile based on the [May beta](https://developer.ibm.com/wasdev/blog/2015/05/08/beta-liberty-and-tools-may-2015/).





 5 May 2015 

Updated Liberty buildpack v1.17-20150501-1729
: The buildpack contains an updated version of the Liberty profile based on the [April beta](https://developer.ibm.com/wasdev/blog/2015/04/10/announcing-liberty-beta-with-tools-aprilmay-2015/). With this update, the jsp-2.3, el-3.0, and jdbc-4.1 Liberty features, previously available as beta features, are now available as production-ready features. Also, additional Java EE 7 features such as jsf-2.2, javaMail-1.5, webProfile-7.0, and javaee-7.0 are now available as beta features.



* The buildpack also provides initial support for Java 8.
keyVersion / creationDate Date and time the key material was last updated 
 extractable A boolean that determines whether the key material can leave the service. If set to false, Key Protect designates the key as a nonextractable root key used for wrap and unwrap actions. If set to true, Key Protect designates the key as a standard key that you can store in your apps and services. Once set to false it cannot be changed to true. 
 state 1 - the key is active; 2 - the key is suspended; see [key states](https://cloud.ibm.com/docs/key-protect?topic=key-protect-key-states) 
 crn The cloud resource name (CRN) 









 Required parameters 



* KEY_ID_OR_ALIAS

The v4 UUID or alias of the root key that you want to show.
* -i, --instance-id

The IBM Cloud instance ID that identifies your Key Protect instance.

You can set an environment variable instead of specifying -i with the following command: $ export KP_INSTANCE_ID=<INSTANCE_ID>.







 Optional parameters 



* -o, --output

Set the CLI output format. By default, all commands print in table format. To change the output format to JSON, use --output json.
* --key-ring

A unique, human readable name for the key-ring. Required if the user doesn't have permissions on the default key ring.









 kp key sync 

This subcommand synchronizes the associated resources for a key.

ibmcloud kp key sync KEY_ID
-i, --instance-id INSTANCE_ID
[--key-ring KEY_RING_ID]
[-o, --output FORMAT]



 Examples 

This is an example of kp key sync.



 Example 

Synchronize a key and show the results.

 synchronize the associated resources for a given key
$ ibmcloud kp key sync 94c06f9c-a07a-4961-8548-553cf7431f18