I'm running the KX Dashboards package through kdb-x. I have the Dashboards running, but I have noticed the Demo Dashboards running on port 6812 (html5evalcongroup) connection don't have data. Kickstarting a new kdb connection for port 6812 will activate the connection (q -p 6812), but none of the demo data tables are accessible on the connection. How are the sample data sets initiated in kdb-x for KX Dashboards?
3 Answers
3Are you following the docs here Standard Deploy - Dashboards ?
I tested this on version 2.20 and it's working for me
Hey Ian, did you have to start a second connection for port 6812? It might be because I haven't updated my version of kdb-x to take the latest version of Dashboards?
I was running my existing install that I did from a few months ago; if this is the case, there probably needs to be a user warning to get the latest version of kdb-x?
I have always used the Standard Install, using my local q, but this is no longer supported in that I'm unable to get a new kc.lic to replace my expired license? I'm having to use KDB-X, which is where the problem lies. How can I get a new, standard kc.lic? Trying a cut-and-paste for the one used by KDB-X didn't work. This is very frustrating....
– declan_fallon1Restart the two processes cleanly. The simplest, most reliable approach is to run each in its own terminal window, in the foreground: Terminal 1 (from your dashboards directory): q sample/demo.q -u 1 Terminal 2: q dash.q -p 10001 -u 1
– declan_fallon1
This isn't a versioning issue. As mentioned, following the Standard Deploy (or README.md inside the dashboards folder) will get the demo data populated, namely: q sample/demo.q -u 1 & q dash.q -p 10001 -u 1 If you look at the first few lines of sample/demo.q that is the process that binds to 6812. My guess is you only ran dash.q if you're not seeing the connection, and if starting a separate q process on that port didn't cause a fail on start with the port already being in use.
– sbruce12