KDB Insights Core install on linux - can't find qce-X.Y.Z-install.sh on Nexus.

[krish240574]

Hello,
I was trying to install KDB Insights Core on Linux and was following the page at :
https://code.kx.com/insights/1.5/core/install.html#binary-installation-linux
However, I can't find the qce-X.Y.Z-install.sh(qce-4.0.2-install) file on Nexus. How may I procure it? Has the download location changed?

I could use the docker container, but was leaning more to using the qce command line so I could follow along the videos on the KX Academy.

Please advise,

Thanks,

Krishna

[rocuinneagain]

The file is there:

kx-insights-packages > kdbInsightsCore > 4.0.2

Are you signed in with username and password?

[krish240574]

Nope, I'm not - how do I sign up? I can only see a sign in link.
Thanks for the prompt response !

Krishna

[rocuinneagain]

Listed on https://code.kx.com/insights/1.5/core/install.html#license

A valid license is needed to run kdb Insights Core. For more information on licensing, please contact licadmin@kx.com.

[krish240574]

Yup, I've received my license via email and have q installed. I received the link to download l64.zip in an email.
When I click the Nexus link on the download instruction page at :

https://code.kx.com/insights/1.5/core/install.html#license , I get a popup message saying :
undefined (kx-insights-package) not found. Is this because I'm not signed in?

How do I sign up for Nexus access?

Thanks,

Krishna

[krish240574]

I have a new error now:
when I run $QHOME/l64/q, I get the following :

KDB+ 4.0 Cloud Edition 2023.01.20 Copyright (C) 1993-2023 Kx Systems
l64/ 2(24)core 5847MB root ubuntu 127.0.1.1 EXPIRE *****************************************************.com

'type
[2] (/root/q/q.k:261)

What could be causing this? This q came from the l64.zip that I downloaded from the link I got in an email.

Krishna

[krish240574]

Never mind, I think I got it running, there was a import from the gsutil distribute that was messing up things.
Lucky find !
Thank you for the kind advice.

Krishna

[rocuinneagain · Accepted solution]

Yes this can be solved by ensuring gcloud is up to date and initialised:

gcloud components update
gcloud init