RE: SystemLink 2027 EAR Frequently Asked Questions & Getting Started

[adamarnesen]

There are some prerequisite requirements that will help you get started with the SystemLink 2027 EAR. We recommend you review the attached document so that you are successful in deploying the beta for our new edition of SystemLink.

SystemLink 2027 EAR Getting Started

As we receive feedback, the document will be updated. Feel free to respond to this post with questions and feedback.

If you would like to join the early access program, you can apply here: Sign up for NI SystemLink™ Software Early Access - NI

[S.C.V-JH]

Hello, Adamarnesen

I encountered multiple failures during the Deploying process while installing the SystemLink beta version (see attached screenshot).

I am contacting support because I couldn't find the root cause in the log files.

SCVJH_0-1787206010553.png

[Brad_Turpin]

Hey S.C.V-JH,

What hostname did you provide in the configuration dialog prior to the deployment?  The initial EAR version frequently suggested hostnames that were incompatible with the deployment expectations.  You can not use an ip address for the hostname.  It should just be the Windows computer name of the host Windows computer you're installing on.

I got a similar, vague error when I tried to deploy with an incorrect hostname.

Brad Turpin

Principal Technical Support Engineer

NI / Emerson

[T-REX$]

Yeah, just to back up what Brad said here, I took a look at the log you provided and the errors imply that the configured public hostname does not correctly route back to the new SystemLink instance, so the systemlink-webserver cannot retrieve Keycloak’s OIDC discovery document. The webserver then crashes, Kubernetes backs off restarting it, dependent services stay unhealthy, and Helm times out.

If you resolve the hostname issue, you should be unblocked. To make that easier - we just updated the installer to include some better suggestions and error handling in the installer.

You should uninstall SystemLink via NIPM, download the latest version (same download link where you got the initial EAR), and re-run the installer.

[S.C.V-JH]

Oh, thank you 🙂

It was resolved by entering the PC ID.