Cannot see my Cluster in PX-CENTRAL

Portworx Essentials
1

Hello,
I have installed Portworx Essentials Free forever license on my kubernetes cluster. But i don’t see my cluster ID in PX-Central Panel.I have internet connection on all kubernetes nodes and storage is up nad running. Can you please help me ?

On a server i have this message: License: PX-Essential (lease renewal in 23h, 3m)

2

On central.portworx.com, you should be able to login and see the cluster under “check” mark symbol if connection is available.

@Tapas-Sharma FYI

3

Can you share the output of pxctl status and the essential entitlement id too.
Also, can you login to one of the portworx pods and check the following
curl -k https://pxessentials.portworx.com/osb/ping
As of writing this post the service is running and serving requests. Please update with the output of the above ping.
Also, what is the output of
/opt/pwx/bin/pxctl alerts show

4

[root@kubenode2 ~]# curl -k https://pxessentials.portworx.com/osb/ping
{“status”:“pong”,“message”:“PX-OSB is UP and running”}
(reverse-i-search)`s’: systemctl di^Cble firewalld
[root@kubenode2 ~]# sudo /opt/pwx/bin/pxctl status
Status: PX is operational
License: PX-Essential (lease renewal in 23h, 30m)
Node ID: 4e4f6c33-3123-4aef-9557-964e9af9a31d

5

increase the number of threads using pxctl cluster options
CLUSTER LicenseExpiring px-cluster-fc58ace4-2bc4-42c7-a82e-3ef03e49b70d WARN 1 Dec 9 16:29:28 UTC 2020 Dec 9 16:29:28 UTC 2020 PX-Essential license will expire in 0 days, 23:01
NODE CallHomeFailure 875b7576-c140-4ea1-b919-66532c6b539c ALARM 4 Dec 10 02:44:10 UTC 2020 Dec 9 20:32:10 UTC 2020 Error while calling home: node (10.130.90.132) node (10.130.90.132) Post http://logs-01.loggly.com/inputs/token/tag/http/: dial tcp 52.24.177.168:80: i/o timeout
CLUSTER MeteringAgentCritical ALARM 20 Dec 10 05:33:00 UTC 2020 Dec 9 10:30:02 UTC 2020 Unable to reach to billing server: Cannot send metric to the billing endpoint: Put https://pxessentials.portworx.com/osb/billing/v1/register: x509: certificate signed by unknown authority

6

can you run the curl command without the -k option. i.e
curl https://pxessentials.portworx.com/osb/ping

7

I know, but i don’t see anything there

8

[root@kubenode2 ~]# curl https://pxessentials.portworx.com/osb/ping
{“status”:“pong”,“message”:“PX-OSB is UP and running”}
[root@kubenode2 ~]#

9

this is from within the portworx pod right?

10

can you paste the entire output of pxctl status.

11

I run on the cluster, i didn;;t do kubectl exec -it and etc

12

you need to test the reach-ability from the pods, please refer PX-Essentials license is expired

13

[root@kubenode2 ~]# sudo /opt/pwx/bin/pxctl status
Status: PX is operational
License: PX-Essential (lease renewal in 23h, 23m)
Node ID: 4e4f6c33-3123-4aef-9557-964e9af9a31d
IP: 192.168.1.131
Local Storage Pool: 1 pool
POOL IO_PRIORITY RAID_LEVEL USABLE USED STATUS ZONE REGION
0 HIGH raid0 20 GiB 3.3 GiB Online default default
Local Storage Devices: 2 devices
Device Path Media Type Size Last-Scan
0:1 /dev/sdb STORAGE_MEDIUM_MAGNETIC 10 GiB 09 Dec 20 15:11 +04
0:2 /dev/sdc STORAGE_MEDIUM_MAGNETIC 10 GiB 09 Dec 20 15:11 +04
* Internal kvdb on this node is sharing this storage device /dev/sdc to store its data.
total - 20 GiB
Cache Devices:
* No cache devices
Cluster Summary
Cluster ID: px-cluster-fc58ace4-2bc4-42c7-a82e-3ef03e49b70d
Cluster UUID: 8cd23762-a515-466b-adda-d9f0f84583d5
Scheduler: kubernetes
Nodes: 2 node(s) with storage (2 online)
IP ID SchedulerNodeName StorageNode Used Capacity Status StorageStatus Version Kernel OS
192.168.1.132 875b7576-c140-4ea1-b919-66532c6b539c kubenode3 Yes 3.2 GiB 10 GiB Online Up 2.6.1.6-3409af2 4.18.0-193.el8.x86_64 CentOS Linux 8 (Core)
192.168.1.131 4e4f6c33-3123-4aef-9557-964e9af9a31d kubenode2 Yes 3.3 GiB 20 GiB Online Up (This node) 2.6.1.6-3409af2 4.18.0-193.el8.x86_64 CentOS Linux 8 (Core)
Warnings:
WARNING: Persistent journald logging is not enabled on this node.
WARNING: Internal Kvdb is not using dedicated drive on nodes [192.168.1.132 192.168.1.131]. This configuration is not recommended for production clusters.
Global Storage Pool
Total Used : 6.6 GiB
Total Capacity : 30 GiB
[root@kubenode2 ~]#

14

[root@kubenode1 ~]# kubectl exec -it -n kube-system px-cluster-fc58ace4-2bc4-42c7-a82e-3ef03e49b70d-q7l77 – curl -k https://pxessentials.portworx.com/osb/ping
{“status”:“pong”,“message”:“PX-OSB is UP and running”}
[root@kubenode1 ~]#

15

[root@kubenode1 ~]# kubectl exec -it -n kube-system px-cluster-fc58ace4-2bc4-42c7-a82e-3ef03e49b70d-q7l77 – curl https://pxessentials.portworx.com/osb/ping
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
command terminated with exit code 60

16

Can someone help me with my issue?

17

have you added a self-signed certificate to your k8s master or to the pods? it seems your pods do not have proper system certificates.
Please share your essential entitlement ID too.

18

On nodes i added,but in pods not.

Essentials ID: 388ede74-387b-11eb-a2c5-c24e499c7467

19

On nodes i added,but in pods not.

Essentials ID: 388ede74-387b-11eb-a2c5-c24e499c7467

20

Thanks, I can see your user with valid essential ID, please add the certificates to the pods, so that they can access the SSL endpoint, for reference : https://medium.com/@paraspatidar/add-self-signed-or-ca-root-certificate-in-kubernetes-pod-ca-root-certificate-store-cb7863cb3f87