Any idea why I am getting :
Error: Unable to connect to linstor://localhost:3370: [Errno 99] Cannot assign requested address
I installed linstor with replication as 2 and the VM is running fine. I am executing this command from dom0 of Pool Master.
Are there any other packages in xcp-ng requiring python2 ?
Would it be advisable to change default python to python3 (by adding alias in bashrc) ?
Or do you think I should create a script which in-turn runs python3 command only for linstor ?
PS: By executing :
python3 /usr/bin/linstor
Result :
Error: Unable to connect to linstor://localhost:3370: [Errno 99] Cannot assign requested address
Although through XO, I can see the VM on Linstor SR running fine,
Can you try installing ipv4 only and alternatively ipv6 only to see if it works ?
(Just wanted to confirm something)
@ronan-a said in XOSTOR hyperconvergence preview:
@gb-123 What command and error exactly?
I was referring to the our earlier conversation :
@gb-123 said in XOSTOR hyperconvergence preview:
running linstor command on both hosts gives the following error :
Traceback (most recent call last):
File "/usr/bin/linstor", line 21, in <module>
import linstor_client_main
ImportError: No module named linstor_client_main@ronan-a said in XOSTOR hyperconvergence preview:
Regarding this error, can you say me what's your XCP-ng version? And what's the output of:
yum list installed | grep -i linstor?Output of
yum list installed | grep -i linstor:drbd.x86_64 9.22.0-1.el7 @xcp-ng-linstor drbd-bash-completion.x86_64 9.22.0-1.el7 @xcp-ng-linstor drbd-pacemaker.x86_64 9.22.0-1.el7 @xcp-ng-linstor drbd-reactor.x86_64 1.0.0-1 @xcp-ng-linstor drbd-udev.x86_64 9.22.0-1.el7 @xcp-ng-linstor drbd-utils.x86_64 9.22.0-1.el7 @xcp-ng-linstor drbd-xen.x86_64 9.22.0-1.el7 @xcp-ng-linstor kmod-drbd.x86_64 9.2.2+ptf.1_4.19.0+1-1 @xcp-ng-linstor linstor-client.noarch 1.18.0-1 @xcp-ng-linstor linstor-common.noarch 1.21.1-1.el7 @xcp-ng-linstor linstor-controller.noarch 1.21.1-1.el7 @xcp-ng-linstor linstor-satellite.noarch 1.21.1-1.el7 @xcp-ng-linstor python-linstor.noarch 1.18.0-1 @xcp-ng-linstor xcp-ng-linstor.noarch 1.2-1.xcpng8.3 @xcp-ng-linstor xcp-ng-release-linstor.noarch 1.4-1.xcpng8.3 @xcp-ng-base@ronan-a said in XOSTOR hyperconvergence preview:
Do you have a XCP-ng 8.3? And did you run the beta installation script on it?
I installed XCP-ng 8.3 beta from ISO and then applied all the patches that were available. To install linstor, I followed the 1st Post of this topic.
@BenjiReis said in XOSTOR hyperconvergence preview:
@gb-123 are you using XOA or XO from sources?
If from sources the issue might come from having a different openssl when creating the sdn-controller certificates.
You can either try with an XOA or generate manually your certificates.
Using XO from sources. I just turned on "Over-ride certificates" and reinstalled the whole XO virtual machine. Seems to work fine now.
My only problem was that why it suddenly stopped working when I installed Linstore as installing Linstor should not impact upon this. So thats why I reported this on this thread. 
@ronan-a said in XOSTOR hyperconvergence preview:
@gb-123 said in XOSTOR hyperconvergence preview:
running linstor command on both hosts gives the following error :
Traceback (most recent call last):
File "/usr/bin/linstor", line 21, in <module>
import linstor_client_main
ImportError: No module named linstor_client_main
Regarding this error, can you say me what's your XCP-ng version? And what's the output of:
yum list installed | grep -i linstor?
Output of yum list installed | grep -i linstor :
drbd.x86_64 9.22.0-1.el7 @xcp-ng-linstor
drbd-bash-completion.x86_64 9.22.0-1.el7 @xcp-ng-linstor
drbd-pacemaker.x86_64 9.22.0-1.el7 @xcp-ng-linstor
drbd-reactor.x86_64 1.0.0-1 @xcp-ng-linstor
drbd-udev.x86_64 9.22.0-1.el7 @xcp-ng-linstor
drbd-utils.x86_64 9.22.0-1.el7 @xcp-ng-linstor
drbd-xen.x86_64 9.22.0-1.el7 @xcp-ng-linstor
kmod-drbd.x86_64 9.2.2+ptf.1_4.19.0+1-1 @xcp-ng-linstor
linstor-client.noarch 1.18.0-1 @xcp-ng-linstor
linstor-common.noarch 1.21.1-1.el7 @xcp-ng-linstor
linstor-controller.noarch 1.21.1-1.el7 @xcp-ng-linstor
linstor-satellite.noarch 1.21.1-1.el7 @xcp-ng-linstor
python-linstor.noarch 1.18.0-1 @xcp-ng-linstor
xcp-ng-linstor.noarch 1.2-1.xcpng8.3 @xcp-ng-linstor
xcp-ng-release-linstor.noarch 1.4-1.xcpng8.3 @xcp-ng-base
Do you have a XCP-ng 8.3? And did you run the beta installation script on it?
I installed XCP-ng 8.3 beta from ISO and then applied all the patches that were available. To install linstor, I followed the 1st Post of this topic.
Also, your SSL/VLAN issue is not caused by LINSTOR, @BenjiReis do you have any idea?
Yeah, even I thought so, but nothing changed for me before I installed Linstor.
There is also a very peculiar thing I am noticing:
Backup from Thin (Ext4) SR to another Thin (Ext4) SR has a transfer of 120KiBs over network(WAN). I thought this is maybe due to a 'slow' network, but however, I started another backup at the same time while the previous one was running slowly, this time from Thick (LVM) SR to Thin SR and the speed I got was around 16 MiB/s (which seems to be OK). I did write a post regarding this but deleted it since I need to dig deeper into this before I report this as an issue to you.
I will be conducting tests for a few more days just to be sure. (I am talking about Continuous Backup btw.)
Update :
After a week of continuous testing, I am getting mixed results on the backup speed as mentioned in the above paragraph. I can now say that the issue may not be related to Linstor.
running linstor command on both hosts gives the following error :
Traceback (most recent call last):
File "/usr/bin/linstor", line 21, in <module>
import linstor_client_main
ImportError: No module named linstor_client_main
I have installed the XOSTOR with replica count of 2.
I have tried running one E-mail Server (PostFix) and one Web-Server (Nginx), with their VHD on XOSTOR. They seem to run fine. I have not done any benchmarks for now.
After installing, I noticed that the VxLAN (Encrypted) has stopped working.
Update:
I managed to fix the VxLAN by :
Previous Error Details (Now Solved as mentioned in the update above):
So this is how I was using:
1 VM on Node 1 which runs pfSense Router
VxLan (encrypted) on the pool.
Other VMs on Node 1 & Node 2.
VMs on Node1 are connecting to the pfSense which is running on the same node.
VMs on Node2 have stopped connecting.
I have not changed any settings. All I did for installing XOSTOR, was remove the previous SR (after migrating vhd to another sr using XO) edit partition (using fdisk) and then create 2 SRs (One for EXT4 and the Other for XOSTOR) and migrate all VHDs back to EXT4 and XOSTOR (as per requirement). I did this for both nodes.
I am not sure if installing XOSTOR has something to do with this or not so this is not a bug report (yet).
So far I have tried :
Do you think XOSTOR would have an impact on the MTU in the host Network Card ?
Any direction you can give me to diagnose the problem ?
I am planning to remove the VxLAN and re-create it. Do you think it would help ?
Update : Checked XO Logs:
I get :
2023-08-11T14:00:17.907Z xo:xo-server:sdn-controller:tls-connect ERROR TLS connection failed {
xen-orchestra-docker-orchestra-1 | error: [Error: 58EBD01E7F7F0000:error:0A000418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1586:SSL alert number 48]
{
| library: 'SSL routines',
| reason: 'tlsv1 alert unknown ca',
| code: 'ERR_SSL_TLSV1_ALERT_UNKNOWN_CA'
| },
Though earlier, the connection between Node1 and Node 2 were still being made despite this warning. So this is not new.
Further Update:
I deleted the previous VxLAN and now when I try to create it, it gives me the following error :
sdnController.createPrivateNetwork
{
"poolIds": [
"b990a09e(*removed*)"
],
"pifIds": [
"68fc6193(*removed*)"
],
"name": "VxLAN",
"description": "Private Lan Network",
"encapsulation": "vxlan",
"encrypted": true,
"mtu": 1500
}
{
"library": "SSL routines",
"reason": "tlsv1 alert unknown ca",
"code": "ERR_SSL_TLSV1_ALERT_UNKNOWN_CA",
"message": "582B645BC47F0000:error:0A000418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1586:SSL alert number 48
",
"name": "Error",
"stack": "Error: 582B645BC47F0000:error:0A000418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1586:SSL alert number 48
"
}
Is it possible to change replication factor later on the fly eg. after adding a new host (without loosing data) ?