Trouble with omnisci-ee-gpu-byol-5.5.3 AMI on AWS

Comments

9 comments

  • Avatar
    Candido Dessanti

    Hi @jmboehm,

    It looks like that in the AMI is installed a docker version of omnisci; I started with the usual syntax

    [centos@ip-172-31-24-0 var]$ sudo docker run --runtime=nvidia -v $HOME/omnisci-docker-storage:/omnisci-storage -p 6273-6280:6273-6280 omnisci/omnisci-ee-cuda:latest
    
    startomnisci 7 running
    WARN: config file does not exist, ignoring: --config /omnisci-storage/omnisci.conf
    Backend TCP:  localhost:6274
    Backend HTTP: localhost:6278
    Frontend Web: localhost:6273
    Calcite TCP:  localhost:6279
    - omnisci_server 112 started
    - omnisci_web_server 113 started
    ⇨ http server started on [::]:6273
    Navigate to: http://localhost:6273
    

    I used my free license, and it's working.

    image|690x158

    While the usage instructions give me the idea that a binary version of the software would be installed, you can, if you want, run with docker; in the meantime, I will ask internally if there a problem with the AMI or in the documentation.

    Regards, Candido

    1
    Comment actions Permalink
  • Avatar
    Candido Dessanti

    Hi @jmboehm,

    I asked internally and while the AMI is intended to be a docker one (that's because to run the jupyter notebook extension it's needed to use the docker), there are obviously issues on the AMI, so our dev-ops are looking into the issue, and we will update it ASAP.

    I want to thank you for your patience and for reporting the problem to us.

    Candido

    1
    Comment actions Permalink
  • Avatar
    Candido Dessanti

    Hi @jmboehm

    the problem as been isolated; it's a script that for whatever reason isn't starting when at the creation time of the AWS instance.

    as a workaround, I can suggest running this command with root privilege

    /home/mapd/cloud-init/run-once.sh

    this way you should get the complete experience.

    Thanks again for reporting problem, and have fun with Omnisci Free edition

    0
    Comment actions Permalink
  • Avatar
    Johannes Boehm

    Confirmed; running the script solves the problem. Thank you for your fast and competent response.

    0
    Comment actions Permalink
  • Avatar
    Candido Dessanti

    Well the most competent response come up from Pete Antosik 😎

    Mine was half-competent, anyway, we are in the process to release a better version that resolves some annoying bugs. I will reach you here when will be GA. We are on RC stage yet.

    0
    Comment actions Permalink
  • Avatar
    Johannes Boehm

    Hi Candido,

    Sorry to bother you again. I've terminated the old AWS instance to make use of the new AMI, and created a new instance from the new AMI. However, when pasting the license key, I now get a "License error: Failed to parse key". - Is that expected? Do licenses for Omnisci Free only apply to one AWS instance, even if the old one has been terminated? - If yes, is it possible to "free" a license to move it to another instance? - If no, any idea what's going on? :)

    Many thanks, as always.

    Best, Johannes

    0
    Comment actions Permalink
  • Avatar
    Candido Dessanti

    Hi Johannes,

    Don't worry, you are not bothering me at all. I am here to help and be helped by the community.

    AFAIK you can use the key more than once (how we could check....we are not Skynet... Luckily...Unluckily don't know 🤔)

    We faced that error when applied to OmniSci version older than 5.5.3...so if you are running a 5.5.2 you can use the free license (because the software isnt is aware of it).

    So the question is... Which version are you running (please tell me it's older than 5.5.3...you can also lie... Kidding).

    If you are on an older version you have to upgrade.

    Best, Candido

    0
    Comment actions Permalink
  • Avatar
    Johannes Boehm

    You're absolutely right, the AMI is on 5.5.2 (but it used to be 5.5.3 already, no? maybe it was removed). No worries, I'll wait until 5.5.3 is out on the AMI.

    Phew! ;)

    0
    Comment actions Permalink
  • Avatar
    Candido Dessanti

    Hi

    The 5.5.3 has been removed because of a bug, the 5.5.6 has been finalized yesterday and would be on AWS AMI today or tomorrow.

    Candido

    1
    Comment actions Permalink

Please sign in to leave a comment.