vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Why does my Linux Backup Agent appear offline? 

The Linux® backup agent might appear offline in the portal for multiple reasons. Follow the steps to rule out issues with firewall port settings, registration, and the buagent process on the server.

 What’s happening 

Linux® agent shows as offline in Portal.



 Possible firewall issue 

 Why it’s happening 

Currently, at minimum, your servers must allow access to the 10.200.86.0/24 and 10.2.118.0/24 subnets for TCP ports 8086, 8087. If the port settings are incorrect, traffic is blocked, and the agent cannot communicate with the Cloud Backup Portal.

 How to fix it 

Check firewall ports - 8086 & 8087. For more information, see [Configuring Ports to allow communication between the backup agent and Cloud Backup Portal](https://cloud.ibm.com/docs/Backup?topic=Backup-portinfo).





 BUAgent service isn't running 

 Why it’s happening 

When BUAgent process is no longer active on the server, the Linux® Agent appears offline in the Cloud Backup Portal.

 How to fix it 

Ensure that the BUAgent is running by issuing the following command on the Linux® system.

/etc/init.d/vvagent status

The output shows whether the BUAgent is running.

VVAgent is running (PID: )
BUAgent is running (PID: )



* If the BUAgent is not running, start it with the following command.

/etc/init.d/vvagent start
* If the BUAgent appears to be running, restart the service with the following command.

/etc/init.d/vvagent restart







 Agent needs to be reregistered to the Cloud Backup portal 

 Why it’s happening 

If it still shows that the Agent is offline after a refresh of the Portal page, then the Agent needs to be registered again.

 How to fix it 

Registering an Agent to the Portal retains all existing jobs, schedules, and configurations as-is.
docker run --rm -v "$PWD:/tutorials" ibmcom/ibp-ansible /tutorials/build_network.sh -i destroy





 Hints and Tips 



Table 1. Hints and tips for using the Ansible collection

 Tip Action 

 Increasing the wait timeout Some clusters perform faster than others. The scripts use a default wait timeout of 600 seconds, which is sufficient for most environments. The wait timeout represents the maximum amount of time the playbook waits for the underlying transactions to complete before it logs a failure. If you need to increase the timeout, open the associated variables file (ordering-org-vars.yml, org1-vars.yml, or org2-vars.yml) and modify the value of the wait_timeout: parameter. 
 Customizing organization names The playbooks use the organization names that are defined in the common-vars.yml file. When you are ready to configure your own organizations, you can edit the file and specify the preferred organization names for your network. 
 Customizing the name of the ordering service The default ordering service name is defined in the common-vars.yml file in the ordering_service_name parameter. Edit this value to specify the preferred name of the ordering service. 
 Adjusting how many ordering nodes are created for an ordering service By default, the 01-create-ordering-organization-components.yml playbook is configured to create a single node ordering service. If your cluster has the resources to support additional ordering nodes in the ordering service, you can modify how many ordering nodes are created when the ordering service is deployed by editing the 01-create-ordering-organization-components.yml playbook and specifying the number of ordering nodes that you want to deploy in the ordering_service_nodes: parameter. 
 Adjusting node resources You can customize the resources that are allocated to a node by editing the resources block of its associated module. For example, to modify the CPU and memory that is allocated to a CA node, navigate to your clone of the [certificate_authority](https://github.com/IBM-Blockchain/ansible-collection/blob/main/plugins/modules/certificate_authority.py) module on your local system.
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. Rclone uses the syntax, rclone sync source destination, where source is the local folder and destination is the container within your IBM COS.

rclone sync /path/to/my/backup/directory RemoteName:newbucket

You might already have a destination that is created, but if you don't then you can create a new bucket by using the steps above.





 Scheduling a Job 

Before scheduling a job, make sure that you have done your initial upload and it has completed.



 Windows 



1. Create a text file that is called backup.bat somewhere on your computer and paste in the command you used in the section about [syncing a directory](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-rclonerclone-sync-directory). Specify the full path to the rclone.exe and don’t forget to save the file.



C:fullpathtorclone.exe sync "C:pathtomybackupdirectory" RemoteName:newbucket



2. Use schtasks to schedule a job. This utility takes a number of parameters.



* /RU – the user to run the job as. This is needed if the user you want to use is logged out.
* /RP – the password for the user.
* /SC – set to DAILY
* /TN – the name of the job. Call it backup
* /TR – the path to the backup.bat file you created.
* /ST – the time to start the task.
--------------------





 verifyDomainMapping 

Verifies the status of the CDN, and updates the status of the CDN mapping if it changed. When a CDN mapping is created initially, its status shows as CNAME_CONFIGURATION. At this point, you must update the DNS record so that the CDN mapping points the hostname to the CNAME. Check with your DNS provider if you have questions about how the update is done and how long it might take for the change to propagate on the internet. Typically, it takes 15 - 30 minutes. After that time, this verifyDomainMapping API must be called to verify whether the CNAME chain is complete. If the CNAME chain is complete, the CDN-mapping status changes to RUNNING.

This API can be called at any time to get the latest CDN-mapping status. The domain mapping must be in one of the following states: RUNNING or CNAME_CONFIGURATION.



* Parameters- uniqueId - (Required) The unique ID of the mapping that you want to verify.
* Return- A collection of type SoftLayer_Container_Network_CdnMarketplace_Configuration_Mapping.

[Mapping container](https://cloud.ibm.com/docs/CDN?topic=CDN-mapping-container)



--------------------





 startDomainMapping 

Starts a CDN domain mapping based on the uniqueId. To be started, the domain mapping must be in a STOPPED state.



* Parameters- uniqueId - (Required) Provide the unique ID of the mapping to be started.
* Return- A collection of type SoftLayer_Container_Network_CdnMarketplace_Configuration_Mapping.

[Mapping container](https://cloud.ibm.com/docs/CDN?topic=CDN-mapping-container)



--------------------





 stopDomainMapping 

Stops a CDN domain mapping based on the uniqueId.
When you deploy an app to IBM Cloud, the route of the app can't be created if the host name that you specified is already being used.

 What’s happening 

When you deploy an app to IBM Cloud, you see the following error message:

Creating route hostname.domainname ... FAILED Server error, status code: 400, error code: 210003, message: The host is taken: hostname

 Why it’s happening 

This problem occurs if the host name that you specified is already being used.

 How to fix it 

The host name that you specify must be unique within the domain that you are using. To specify a different host name, use one of the following methods:



* If you deploy your app by using the manifest.yml file, specify the host name in the host option.

host: host_name
* If you deploy your app from the command prompt, use the ibmcloud cf push command with the -n option.

ibmcloud cf push appname -p app_path -n host_name







 WAR apps can't be pushed by using the ibmcloud cf push command 

You might not be able to use the ibmcloud cf push command to deploy an archived web app to IBM Cloud if the app location isn't specified correctly.

 What’s happening 

When you upload a WAR app to IBM Cloud by using the ibmcloud cf push command, you see the following error message: Staging error: cannot get instances since staging failed.

 Why it’s happening 

This problem might happen if the WAR file isn't specified, or if the path to the WAR file isn't specified.

 How to fix it 

Use the -p option to specify a WAR file or add the path to the WAR file. For example:

ibmcloud cf push MyUniqueAppName01 -p app.war

ibmcloud cf push MyUniqueAppName02 -p "./app.war"

For more information about the ibmcloud cf push command, enter ibmcloud cf push -h.





 Node.js apps can't be deployed 

You might experience problems when you update a Node.js app or deploy a Node.js app to IBM Cloud.
A public gateway only provides virtual server instances outbound connectivity, whereas a floating IP address provides virtual server instances outbound and inbound connectivity. A floating IP address exposes a service on the internet to inbound activity.

For more information about how to create a public gateway, see [Creating Public Gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-create-public-gateways&interface=ui).





 Step 8: Connecting to your instance 

Using the floating IP address that you created, ping your instance to make sure it's up and running:

ping <public-ip-address>



 Connecting to Linux images 

Since you created your instance with a public SSH key, you can now connect to it directly by using your private key:

ssh -i <path-to-private-key-file> root@<public-ip-address>

The user login 'root' is disabled by default in Fedora Core OS. The user login 'core' can be used to log in to Fedora Core OS instances.

For more information about how to connect to your instance, see [Connecting to Linux instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_linux).

To connect to a Windows image, log in using its decrypted password. For instructions, see [Connecting to your Windows instance](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_windows).

To connect to your z/OS virtual server instance, see [Connecting to z/OS virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_zos).

You can now access your IBM Cloud® virtual server instance by connecting to a VNC or serial console. This is a quick-and-easy way for you to interact with the instance without using a Secure Shell. However, accessing your z/OS virtual server instance by using a VNC console on the IBM Cloud UI is not supported.
- connection ID is a client assigned connection number.
- host name is the host name for the connection.
- mycommonname is the FDQN or common name that is used in the certificate.





 Why it is happening 

The Common Name, for example, the server FQDN or YOUR name, between your on-premises application and the certificate that you uploaded into IBM Cloud for this destination do not match.



* Check the following items:
* You generated the certificate correctly and that you used the correct server FQDN or host name.
* You uploaded the correct certificate into your IBM Cloud destination for this client.







 How to fix it 



1. In the IBM Cloud UI, go to the Secure Gateway Dashboard.
2. Select your destination and click the Edit icon.
3. Disable Reject unauthorized or upload the correct certificate in Resource Authentication.
4. If you choose to upload certificate, upload the PEM certificate file that is to be used to connect to the on-premises system.





* You can verify your certificate file using following command:

openssl s_client -CAfile <CA> -connect <target_host>:<target_port>

Where: CA is the certificate file you uploaded, target is the on-premise endpoint.









 IP is not in the cert's list 



 What is happening 

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.
[DevSecOps CC evidence](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-cc-explore-evidence.png)

Figure 21. DevSecOps CC evidence

For more information, see [DevOps data aggregation](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-devops-data-aggregation).





 CI and CC pipeline comparison 

You might notice that the CI and CC pipeline have many common steps. The scans and checks that are run are similar in nature and details. The pipelines still have some significant differences as explained in the following table:



Table 1. Differences in the CI and CC pipelines

 CI pipeline CC pipeline 

 It is part of the CI toolchain. It is part of the CC toolchain. 
 It is triggered after a merge request is merged with the master branch It can be triggered manually or at predefined intervals that are independent of a deployment schedule. 
 An application URL and application code repo details are entered as part of the setup process. An application URL and application code repo details are provided after the CC toolchain is configured and before initiation of first pipeline run. 
 The incident issues that are created as part of various scans and checks during compliance checks do not carry a due date. The incident issues that are created as part of various scans and checks during compliance checks carry a due date. 
 The incident issues that are created are found during the build. The incident issues that are created are found during periodic scans of the staging or production environment. 
 The summary.json file is not generated at the end of each CI pipeline run. The summary.json file is not generated at the end of each CI pipeline run. 
 It includes steps like app image creation, image signing, and deploy to dev cluster. This in turn creates inputs for the CD pipeline. It runs only scans and checks that are needed for compliance testing.
However, when you create public networking services, a VPC load balancer is automatically created. The VPC load balancer can route public requests to your app by providing your app a public URL. When an app is publicly exposed, anyone that has the public URL can send a request to your app.

When an app is publicly exposed, anyone that has the public service IP address or the URL that you set up for your app can send a request to your app. For this reason, expose as few apps as possible. Expose an app to the public only when your app is ready to accept traffic from external web clients or users.

The public network interface for worker nodes is protected by [predefined Calico network policy settings](https://cloud.ibm.com/docs/openshift?topic=openshift-network_policiesdefault_policy) that are configured on every worker node during cluster creation. By default, all outbound network traffic is allowed for all worker nodes. Inbound network traffic is blocked except for a few ports. These ports are opened so that IBM can monitor network traffic and automatically install security updates for the Kubernetes master, and so that connections can be established to public networking services. For more information about these policies, including how to modify them, see [Network policies](https://cloud.ibm.com/docs/openshift?topic=openshift-network_policiesnetwork_policies).



 Public app networking for classic clusters 

To make an app publicly available to the internet in a classic cluster, choose an app exposure method that uses routes, NodePorts, NLBs, or setting up Ingress. The following table describes each possible method, why you might use it, and how to set it up. For basic information about the networking services that are listed, see [Understanding Kubernetes service types](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_network_planningexternal).

You can't use multiple app exposure methods for one app.



Characteristics of public app exposure methods

 Name Load-balancing method Use case Implementation
[Associate admin identity](/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-node-identity)

[Update MSP on application channel](/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-channel-peer)

[Share MSP with consortium members](/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-export-msp)

[Import MSP JSON](/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-import-msp)

[Update ordering service channel member](/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-os-channel-member)





Table 4. How to manage the peer organization admin certificate

 Certificate Description How generated Default Expiration How to view expiration How to renew Update MSP Update node admin Update channel Share with network Impact if expired What to do if expired 

 Peer organization admin certificate The admin certificate that is used to administer the peer and install smart contracts on the peer. It can also be configured to manage the application channel that the peer belongs to. The associated admin user is registered with the organization CA before the peer and organization MSP are created. Generated when you create the peer organization MSP and provide the admin identity enroll ID and secret. In addition to being part of the peer node configuration, this MSP certificate can also be included in the channel that the peer joins as a channel member or channel administrator. 1 year Wallet tab: Click the peer organization admin identity tile to view the expiration date of the certificate and private key. <br> <br>Peer node: If Node OU support is not enabled for the peer MSP, open peer tile and view the Admin Cert Expiration in the left column. <br> <br>MSP tab: Open peer organization MSP tile, the admin certificate expiration date is listed in left column. <br> <br>Channel details tab: Open channel and click member tile to view expiration date.
Procedure 



1. From the Rules page of your workspace, click the Add a class icon next to the Class heading in the right side panel.
2. Enter DictMonth as the class name, and then click Add.

The new class is displayed in the Class side panel.









 Lesson 4: Associating a dictionary with a class 

In this lesson, you will learn how to use a dictionary in the rule editor.



 Procedure 



1. Click Rule-based Model > Rules, and then click the Dictionaries tab.
2. Select Month dictionary that you created previously.
3. From the Class list, select DictMonth and then click Save.

The class is associated with the dictionary.

![Shows that the DictMonth class is associated with the Month dictionary in the Dictionaries panel of the Rules page.](https://cloud.ibm.com/docs-content/v1/content/148d3bd95f946aa1bb53ea1540475f522e6b61c9/watson-knowledge-studio-data/images/rule-dict-map2.png)







 Results 

For documents that are associated with the rule editor, any references to terms in the dictionary are annotated as DictMonth class mentions. You will see proof that these references have been annotated in the next lesson.







 Lesson 5: Finding class annotations in documents 

In this lesson, you will learn how to find class annotations in rule editor documents.



 Procedure 



1. Select Rule-based Model > Rules.
2. From the Class panel, find the DictMonth class that you defined earlier, and click the Search annotations in documents icon that's next to it.

The Find Annotations page is displayed and shows all the documents that contain text references to months.
3. Click the Technology - computerworld.com document to view the full document. Notice that the text February is highlighted, which means it was annotated as a mention of the DictMonth class.









 Lesson 6: Defining a regular expression
Typically the future date is returned as the @sys-date value. If there is ambiguity, the past date is saved as an alternative date. For example, for the input in January, a future date is returned. However, if it's February (January passed for this year), then the past January is returned also as an alternative date. An alternative date is also provided for weekdays when the weekday is specified without a modifier. For example, for the input Are you open Wednesday?, the future date is stored, but an alternative date with the date of the previous Wednesday is created also. Alternative dates are created for phrases that contain modifiers such as next, this, or last, which can have different meanings in different locales. The Watson Assistant service treats last and next dates as references to the most immediate last or next day that is referenced, which might be in either the same or a previous week. For some modifiers, an alternative date is created or not depending on the current day of the week. For example, maybe the input contains this Wednesday. If it's Monday, the future date is stored and no alternative date is created. However, if it's Wednesday, then the date is assumed to be the Wednesday of the coming week, but today's date is stored as an alternative date. Each alternative date is saved as an object that contains a value and confidence for each alternative date. The alternative date objects are stored in a JSON Array. To get an alternative value, use the syntax: @sys-date.alternative.
* .calendar_type: Specifies the calendar type for the timezone in use. GREGORIAN is the only supported type.
* .datetime_link: See [Date and time mentions](https://cloud.ibm.com/docs/assistant?topic=assistant-system-entitiessystem-entities-sys-date-time).
* .day: Helper method that returns the day in the date.
* .day_of_week: Returns the day of the week in the date as a lowercase string.
* .festival: Recognizes locale-specific holiday names and can return the date of the upcoming holiday, such as Thanksgiving, Christmas, and Halloween.