FCP FAQ

Q: What is the current version of Computing Provider, and are there any tutorials?

A:

The latest version is v0.6.4

Check the dashboard here : https://orchestrator.swanchain.io/provider-status

Tutorials

Q: How can I know if the status of the computing provider is normal?

A:

Set the [HUB].VerifySign in the $CP_PATH/config.toml file 

[HUB]
VerifySign = false

Run the following command:

*Note: Please replace <YOUR_MULTI_ADDRESS_IP>:<PORT> with your actual multi-address IP and port.

curl -k --location --request POST 'https://<YOUR_MULTI_ADDRESS_IP>:<PORT>/api/v1/computing/lagrange/jobs' \
--header 'Content-Type: application/json' \
--data-raw '{
"uuid": "5641877b-dc94-469a-bb3b-ecab6d10f7dd",
"name": "Job-5641877b-dc94-469a-bb3b-ecab6d10f7dd",
"status": "Submitted",
"duration": 900,
"job_source_uri": "https://api.lagrangedao.org/spaces/51d6abbb-f928-43e4-91fd-79e93e2b276f",
"storage_source": "lagrange",
"task_uuid": "92cd5595-9789-4af3-9100-7c7e4aacb456"
}'

After running this command, wait for 3-5 minutes, and then execute 

kubectl get ing -n ns-0x6091b2f5678952cafbf02755d78973ebff302e11

Find the hosts corresponding to the name ing-minesweeper and ensure that the domain can be accessed in a browser to confirm its normal status.

Q: My node has been running for so long, yet the uptime is 0%.

A:

1. Run the following command:

Ensure that <YOUR_MULTI_ADDRESS_IP> is the Public IP.

curl -k https://<YOUR_MULTI_ADDRESS_IP>:<PORT>/api/v1/computing/host/info

2. Compare the returned result with the example provided below. If they are different, you should review your port mappings.

Example result:

{"status":"success","code":"","data":{"swan_miner_version":"","operating_system":"linux","architecture":"amd64","cpu_cores":48}}

3. If your port mappings are correct and the result matches the example, then proceed to check the configuration file of the computing provider.

Ensure that the MultiAddress is set exactly as "/ip4/<public_ip>/tcp/<port>".

Q: How can I verify if my Computing Provider is set up to receive UBI tasks?

A:

  1. Replace the UbiEnginePk in the $CP_PATH/config.toml file with the ownerAddress:

    [UBI]
UbiEnginePk ="0xxxxx"

  2. Restart computing-provider.

  3. Generate the signature using the following command:

    computing-provider wallet sign <ownerAddress> <nodeid+contract_addr>

    For example, if nodeid is abcd and task contract_addr is 11:

    computing-provider wallet sign <ownerAddress> abcd11

  4. Prepare raw data for the ubi-task test task:

    {

"id": 26384,
"name": "1000-0-7-26381",
"type": 1,
"resource_type": 0,
"deadline": 2000000,
"check_code": "check_code-demo",
"input_param": "https://286cb2c989.acl.swanipfs.com/ipfs/QmTgoX6LkzZTsTjSjXvujzgJEHBLTEg3KMUadQGnyTrNFG",
"verify_param": "https://286cb2c989.acl.swanipfs.com/ipfs/QmTgoX6LkzZTsTjSjXvujzgJEHBLTEg3KMUadQGnyTrNFG.verify",
"resource":{"cpu":"10","memory":"5.00 GiB","storage":"10.00 GiB"}
"signature":"Signing_cpAccountAddress_and_id_with_ownerAddress"

}

  5. Submit the ubi-task using the following command(using your public IP and port ):

    curl --location --request POST 'http://<public_IP>:<port>/api/v1/computing/cp/ubi' \
--header 'Content-Type: application/json' \
--data-raw '{
    "id": 26384,
    "name": "1000-0-7-26381",
    "type": 1,
    "resource_type": 0,
    "deadline": 2000000,
    "check_code": "check_code-demo",
    "input_param": "https://286cb2c989.acl.swanipfs.com/ipfs/QmTgoX6LkzZTsTjSjXvujzgJEHBLTEg3KMUadQGnyTrNFG",
    "verify_param": "https://286cb2c989.acl.swanipfs.com/ipfs/QmTgoX6LkzZTsTjSjXvujzgJEHBLTEg3KMUadQGnyTrNFG.verify",
    "resource":{"cpu":"10","memory":"5.00 GiB","storage":"10.00 GiB"}
    "signature":"Signing_cpAccountAddress_and_id_with_ownerAddress"
}'

  6. After running ubi-task, check if the task status is success:

    computing-provider ubi list

  7. If the test is successful, restore the UbiEnginePk in the config.toml file to its original value

Q: Which ports need to be mapped?

A: Here are the ports you need to map

1. You need to map the CP's internal IP and its port (default 8085), as well as the public IP and port.

2. Map your wildcard domain (*.example.com) to your public IP.

3. Additionally, you need to map port 80 of your internal IP to port 80 of your public IP, as well as port 443 of your internal IP to port 443 of your public IP.

Q: Where should I create the API key?

A: you must use the API of https://multichain.storage, and login in it using Polygon mainnet wallet.

Q: What are the requirements for SSL certificates needed in CP?

A: Please use certificates issued by trusted Certificate Authorities (CA). Currently, certificates generated by Certbot are not functioning properly.

Otherwise, the application won't be displayed correctly on the Space App page.

Q: Is it possible to use a port other than 80 and 443 in the wildcard domain(*.exmaple.com)?

A: No, it is not possible.

Q: Is the "pod" used for communication, and "Calico" is used to manage this communication within the cluster?

A: Both are used for intra-cluster communication. You can use one of these approaches.

Q: If someone didn't apply for early bird, can they still join and run the computing provider tasks?

A: Of course, they can also follow the instruction to set up a Computing Provider.

Q: Can I move my computing provider to a new one while maintaining my previous server? Will this reset my uptime?

A: Yes, you need to move .swan_node to the new server. The uptime will not be reset.

Q: How can I migrate my CP (Computing Provider) to a new environment?

A: To migrate your CP to a new environment, follow these steps:

  1. Backup CP Repo: Copy all files under the old CP directory ($CP_PATH) to a directory on the new server, for example: /data/swan.

  2. Set Environment Variable: Set the environment variable CP_PATH to the directory where you copied the CP files on the new server. For example, you can do this by running the command: export CP_PATH=/data/swan.

  3. Start CP Service: Once the files are copied and the environment variable is set, start the CP service process on the new server.

By following these steps, you'll successfully migrate your CP to the new environment, ensuring that it operates smoothly in the new environment.

Q: How can I resolve the error “(error) MISCONF Redis is configured to save RDB snapshots” seen in the FCP logs?

A: MISCONF Redis is configured to save RDB snapshots but is currently not able to persist on disk, Commands that may modify the data set are disabled.

You can try to change the setting:

$ redis-cli
> config set stop-writes-on-bgsave-error no

Q: How do I withdraw collateral from FCP?

To withdraw collateral from FCP, use the following command:

computing-provider --repo <YOUR_CP_PATH> collateral withdraw --fcp --owner <YOUR_OWNER_WALLET_ADDRESS> --account <YOUR_CP_ACCOUNT> <AMOUNT>

Q: How to Upgrade Resource-Exporter in FCP

A:

Step 1: Stop the computing-provider service.

Step 2: Delete the current resource-exporter component:

kubectl delete ds -n kube-system resource-exporter-ds

Step 3: Reinstall the resource-exporter by using the following command:

cat <<EOF | kubectl apply -f -
apiVersion: apps/v1
kind: DaemonSet
metadata:
  namespace: kube-system
  name: resource-exporter-ds
  labels:
    app: resource-exporter
spec:
  selector:
    matchLabels:
      app: resource-exporter
  template:
    metadata:
      labels:
       app: resource-exporter
    spec:
      containers:
      - name: resource-exporter
        image: filswan/resource-exporter:v11.2.9
        imagePullPolicy: IfNotPresent
        securityContext:
          privileged: true
EOF

Step 4: Check the version of the resource-exporter:

kubectl describe po -n kube-system resource-exporter-ds | grep "Image:"

It should display:

Image:          filswan/resource-exporter:v11.2.9

Ensure the resource-exporter is running by executing:

kubectl get po -n kube-system

Step 5: Start the computing-provider with the latest version.

PreviousFCP Funding Operations GuideNextEdge Computing Provider (ECP)

Last updated