Posts made by bberndt

@benjireis
So..... I ran
journalctl -u xo-server -f -n 50 on XO machine
and then created a netwokr, and got the same second error, not the first one. and it created the network on the XCP 7.6 machine. They both seem to have the sdn service running, but only the 8.2 machine has a firewall rule for 6640.
do I need one for the XO machine as well? Im not completely sure, but I think im cool other than the weird (erroneous?) messages.

Nov 19 10:17:36 xo1.logistics.int xo-server[654246]: 2021-11-19T17:17:36.827Z xo:xo-server:sdn-controller INFO Private network registered { privateNetwork: '42b5f6da-e06a-4801-84ae-[redacted]' }
Nov 19 10:17:36 xo1.logistics.int xo-server[654246]: 2021-11-19T17:17:36.889Z xo:xo-server:sdn-controller INFO New network created {
Nov 19 10:17:36 xo1.logistics.int xo-server[654246]:   privateNetwork: '42b5f6da-e06a-4801-84ae-[redacted]',
Nov 19 10:17:36 xo1.logistics.int xo-server[654246]:   network: 'temp',
Nov 19 10:17:36 xo1.logistics.int xo-server[654246]:   pool: ''
Nov 19 10:17:36 xo1.logistics.int xo-server[654246]: }
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]: 2021-11-19T17:17:39.700Z xo:xo-server:sdn-controller:tls-connect ERROR TLS connection failed {
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:   error: Error: Client network socket disconnected before secure TLS connection was established
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:       at connResetException (internal/errors.js:639:14)
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:       at TLSSocket.onConnectEnd (_tls_wrap.js:1570:19)
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:       at TLSSocket.emit (events.js:412:35)
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:       at TLSSocket.emit (domain.js:475:12)
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:       at TLSSocket.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202111011545/@xen-orchestra/log/configure.js:118:17)
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:       at endReadableNT (internal/streams/readable.js:1334:12)
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:       at processTicksAndRejections (internal/process/task_queues.js:82:21) {
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:     code: 'ECONNRESET',
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:     path: undefined,
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:     host: '172.16.[redacted]',
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:     port: 6640,
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:     localAddress: undefined
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:   },
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:   address: '172.16.[redacted]',
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]:   port: 6640
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]: }
Nov 19 10:17:39 xo1.logistics.int xo-server[654246]: 2021-11-19T17:17:39.703Z xo:api WARN bberndt | sdnController.createPrivateNetwork(...) [3s] =!> Error: Client network socket disconnected before secure TLS connection was established

I went back to my XCP-ng 8.2 pool. It looks like its been creating these networks all along, despite the error.

So, I guess the question remains why the error on XCP-ng 7.6? (somewhat rhetorical, I know its old, and outa support)

@benjireis said in Can't create Private Network, on XO 5.83:

@bberndt can you try to set on in the settings of sdn-controller plugin override-certs to on?
And then try again.

In XCP-Center, Co-worker used something like this, and it created it, but Im not sure its actually working yet, he's still working on it, AFAIK and a Win7, and 2 WinXP VMs.

In XCP-ng Center you can create an Internal network which only works for the VMs on the SAME hosts. this is different than XO private neworks which work across hosts and even pools.

It does show as a regular network in XO, not under the Private list.

This is another thing, the private network you're trying to create is accessible by the VMs so it won't be listed here either.

Same error as above. I looked in the iptables of the (second)host, and it does appear to have this 6640 in it.
Im only looking for a Private Network on the same host, no need to across hosts yet. And these are all single-host-pools, no multiple host pools.

@benjireis

Im not ruling out user error, either.

But here is the log when trying on a different pool. This one happens to be 8.2 XCP-ng, the previous is 7.6 (yes, I know, but it is hardware limited). its a different error.

In XCP-Center, Co-worker used something like this, and it created it, but Im not sure its actually working yet, he's still working on it, AFAIK and a Win7, and 2 WinXP VMs.
https://computingforgeeks.com/create-internal-network-in-xenserver-xcp-ng/
It does show as a regular network in XO, not under the Private list.

sdnController.createPrivateNetwork
{
  "poolIds": [
    "8e059584-1d7b-b674-1fe4-ef5cd08d2550"
  ],
  "pifIds": [
    "566e0925-72d9-f3c3-6c06-b05ab7035018"
  ],
  "name": "dsf",
  "description": "sdf",
  "encapsulation": "gre",
  "encrypted": false,
  "mtu": 1546
}
{
  "code": "ECONNRESET",
  "host": "172.16.64.2",
  "port": 6640,
  "message": "Client network socket disconnected before secure TLS connection was established",
  "name": "Error",
  "stack": "Error: Client network socket disconnected before secure TLS connection was established
    at connResetException (internal/errors.js:639:14)
    at TLSSocket.onConnectEnd (_tls_wrap.js:1570:19)
    at TLSSocket.emit (events.js:412:35)
    at TLSSocket.emit (domain.js:475:12)
    at TLSSocket.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202111011545/@xen-orchestra/log/configure.js:118:17)
    at endReadableNT (internal/streams/readable.js:1334:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)"

@benjireis
No, there is no error on the servers page. In XCP-Center, it seemed to create the private network fine, but not sure my co-worker got it to actually work yet
I can also get to the console of the host in question as well.

@benjireis

yeah, I think its connected. I mean its connected as much as any other pool. I can connect to it and do anything else, in XO.

Can't create Private Network, on XO 5.83

I got to the Pool page, and select Network tab, and then, Select Manage. Add a network, and then hit the Private button. It makes me select a PIF, but anyone I select, and hit go, gives me an error.

I've seen instructions, and they seem pretty easy, so not sure what im doing wrong here.

Doing so in XCP-Center worked fine.

sdnController.createPrivateNetwork
{
  "poolIds": [
    "8e059584-1d7b-b674-1fe4-ef5cd08d2550"
  ],
  "pifIds": [
    "566e0925-72d9-f3c3-6c06-b05ab7035018"
  ],
  "name": "dfg",
  "description": "dfg",
  "encapsulation": "gre",
  "encrypted": false
}
{
  "message": "no connection found for object 8e059584-1d7b-b674-1fe4-ef5cd08d2550",
  "name": "Error",
  "stack": "Error: no connection found for object 8e059584-1d7b-b674-1fe4-ef5cd08d2550
    at default.getXenServerIdByObject (file:///opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server/src/xo-mixins/xen-servers.mjs:197:13)
    at default.getXapi (file:///opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server/src/xo-mixins/xen-servers.mjs:478:29)
    at default.getXapiObject (file:///opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server/src/xo-mixins/xen-servers.mjs:484:17)
    at Xo.getXapiObject (/opt/xo/xo-builds/xen-orchestra-202111011545/node_modules/lodash/_createBind.js:23:15)
    at map (/opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server-sdn-controller/src/index.js:716:46)
    at Array.map (<anonymous>)
    at SDNController._createPrivateNetwork (/opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server-sdn-controller/src/index.js:716:27)
    at Object.call (/opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server-sdn-controller/src/index.js:363:12)
    at Api.callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server/src/xo-mixins/api.mjs:304:33)"
} 

Looks like Citrix is on the case, but no idea when.

https://www.windowscentral.com/citrix-will-run-windows-11

@darkbeldin

Hopefully you've been looking, if not this is a friendly reminder

i've had operators already using Win 11, the pre-release, it looks like tho. Looks like Hyper-V obviously has support for it, and maybe VmWare. I've not seen anything from Citrix, nor Oracle yet.

Updated xcp-ng-pv-tools on my one XCP 8.2 server. (We have mostly (citrix)7.1 and (xcp)7.6 because of hardware RAID limitations)
Found the ISO located at /opt/xensource/packages/iso. (verison 8.2.0-9)
Moved this to my local workstation, and then to my ISO-repo file server.
Went to my XCP 7.6 server, and then to the Rocky Linux 8.4 VM i just set up.
Removed the EPEL xe-guest-utilities-latest package. (7.21.0-1)
Mounted the XCP ISO from the ISO-repo and installed the guest tools from that. (7.20.0-9)

Agent detected! and the service seems to run without error.

And this would only be on hardware that has TPM on board (and passed through to VM), or some sort of emulated TPM? We still have many hosts on Citrix 7.1, and XCP 7.6 because the RAID hardware doesn't work (monitoring software) doesn't work in XCP 8+.

Has anyone mentioned support for Windows 11, and TPM 2 yet?
I should clarify, meeting the requirements of TPM 2 for Windows 11 guests. Does XCP have the ability to pass through the features of TPM 2, or emulate them?

@deoccultist
Sadly, none of this seemed to make any difference.

Hello.
I understand this has been discussed a little bit, but nothing I've seen is pointing me in the right direction. Was wondering if anyone has this Active Directory business working?

Basically I have a group that is 3 OU's deep in my AD, and want to let those users, in that group, log in, so I can set them permissions. Nothing seems to work.

If I try to log in, (and the notation? or style isn't mentioned anywhere, that I can see) user@domain.ext, domain\user, and user just don't authenticate.

On the Test Plugin part, its not clear if I need to use the LDAP read-user or any intended AD user, nor notation. But if I do, all I get is:

0000208D: NameErr: DSID-03100288, problem 2001 (NO_OBJECT), data 0, best match of:
'OU=OULevel2,OU=OULevel1,DC=domain,DC=ext'

Note, the error doesn't mention OU Level 3, where group of users are.

Im using a brand new install with the XenOrchestraInstallerUpdater script, which went perfect.
My LDAP URI is ldap://host.domain.ext
check certificate and TLS is off.
The LDAP user is user@domain.ext.
User Filter: (sAMAccountName={{name}})

Is there a way to export out a list of VM and what host they live on, in Xen Ochestra? maybe as CSV, or Excel?

I concentrated here, after upgrading my second server:
Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /root/xen-orchestra/node_modules/argon2/lib/binding/napi-v3/argon2.node)

I've found circumstantial evidence that this depends on libraries found in newer gcc than is in the Cent OS 7 repo at this time.

strings /usr/lib64/libstdc++.so.6 | grep CXXABI
CXXABI_1.3
CXXABI_1.3.1
CXXABI_1.3.2
CXXABI_1.3.3
CXXABI_1.3.4
CXXABI_1.3.5
CXXABI_1.3.6
CXXABI_1.3.7
CXXABI_TM_1

so argon2.node requires something newer than centos7 can provide?!
and upgrading gcc does the trick? I may have to try when I have more time.
https://stackoverflow.com/questions/63374392/node-module-argon2-usr-lib-x86-64-linux-gnu-libstdc-so-6-version-cxxabi-1

Indeed here is Centos 8.
$ strings /usr/lib64/libstdc++.so.6 | grep CXXABI
CXXABI_1.3
CXXABI_1.3.1
CXXABI_1.3.2
CXXABI_1.3.3
CXXABI_1.3.4
CXXABI_1.3.5
CXXABI_1.3.6
CXXABI_1.3.7
CXXABI_1.3.8
CXXABI_1.3.9
CXXABI_1.3.10
CXXABI_1.3.11
CXXABI_TM_1
CXXABI_FLOAT128

and yes, I understand that XO doesn't target CentOS, but its our 'standard' right now.

Well, you are right, There wasn't explicit support for Cent I don't think. The installer script that I mentioned, did mention it (but not a primary target), and I thought it looked like it dropped 7. We've been standardizing on Cent, thats why I chose it. And am skittish on using 8 now that Redhat dropped it, hard. In fact I've been backtracking the couple machines I used 8 on.

In any case, I have two XO machines on different VLANs, one in the colocation facility. I attempted to update Cent, like I usually do, when you all release a version, and then update XO, with the git command, and the yarn, yarn build command. None of that seemed to error out at all.

After the error, and XO wouldn't start, I rolled back to the previous folder, and it started. So good news there. I looked at the other XO server, that I didn't upgrade, and it has gcc and gcc-g++ installed, and the first one does NOT. Weird that XO works at all, I guess. Not sure thats the key, but I'll have to do some testing with that.

Thanks all for the reply, and happy new year. Hope it gets better.

Did something break with CentOS 7, and XO?

I run mine, built from source, and went to update CentOS 7, and XO today, and it broke badly. An error is below, from the /var/log/orchestra.log. Also some mention at (which i don't use, currently)
https://github.com/ronivay/XenOrchestraInstallerUpdater/issues/59

that CentOS 7 support is gone!?
thanks.

2020-12-30T22:42:59.610Z xo:xo-server ERROR uncaught exception { error:
Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /root/xen-orchestra/node_modules/argon2/lib/binding/napi-v3/argon2.node)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:807:18)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object.<anonymous> (/root/xen-orchestra/node_modules/argon2/argon2.js:9:56)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object.<anonymous> (/root/xen-orchestra/node_modules/hashy/index.js:124:4)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18) }
error: Forever detected script exited with code: 0

ronivay created this issue in ronivay/XenOrchestraInstallerUpdater

closed Remove support for CentOS 7 #59

pulled and rebuilt and plugins have returned!

Running XO 5.60, installed ages ago, and have been updating since. This last upgrade, using the command 'git pull --ff-only', then 'yarn', and 'yarn build', I noticed errors, that necessitated me upgrading from Node 8 to Node 10.
But I've noticed all my plugins are gone. I do recall making a symbolic link somewhere to get them to work initially, a way long time ago, but can't recall what I did, or if thats related.
XO 5.60, on CentOS 7.

anyone have any ideas or thoughts? thanks.red