Unable to start on-premise demo server per "Getting Started" instructions

General Discussions
21

If I recall, there were 3 domains that I had to add to /etc/hosts to make it work in my virtual box VM. I think I looked through prod.yml for all listed domains that needed to be resolved to localhost. I believe a storage proxy domain was one of the domains added.

I’m away from office but I have a live running production ready instance of mender running on Ubuntu guest in virtual box, running on a Linux host using bridged networking. I don’t think I had to do anything special in virtual box to make it work.

1 Like
22

@0lmi The VM is currently in NAT mode for networking and has been since I started this thread. Is there another network configuration that I should be using?

@dellgreen That would be great if you could pass along the hosts modifications if that has an impact!

23

@Kris I installed latest Ubuntu 18.04.4 Desktop in VirtualBox v.6.0.16 (on MacOS 10.15.3) with only NAT network interface connected, applied all available updates, run the script mentioned above and it works.

The weirdness in api-gateway logs is that the following message is repetitive.

setting up automatic reload on host IP address changes for DNS names: mender-useradm mender-inventory mender-deployments mender-device-auth mender-device-adm mender-gui

Here in api-gateway entrypoint script this echo which prints the message and there are no any loops, so, it should not repeat.

Can you try stop everything by ./demo down and then in one terminal tab run the following:

docker run -it -p 8888:80 openresty/openresty:1.13.6.2-0-alpine

and in another terminal tab execute:

curl -X GET http://localhost:8888

And post the output from both terminals in addition to dmesg output.

24

I have suspicious that this is happening because sse4_2 CPU instruction is missing. The issue is described in official openresty github project - here. Symptoms are the same - container exits with 132 code. So, let’s check by executing above commands and if this is the case then the case is just in the CPU, and it has nothing to do with VirtualBox, network configuration, docker, Mender, etc…

25

@0lmi I am absolutely speechless. I think that is absolutely the problem and thank you so much for your help.

The docker command does return 132:

karl@mender-test:~/integration-2.2.1$ sudo docker run -it -p 8888:80 openresty/openresty:1.13.6.2-0-alpine
karl@mender-test:~/integration-2.2.1$ echo $?
132

And dmesg snip shows the same opcode error:

[  688.851186] traps: openresty[3560] trap invalid opcode ip:7f986ae17448 sp:7ffe09c479b0 error:0 in libluajit-5.1.so.2.1.0[7f986ae0f000+277000]
[  689.326609] docker0: port 1(veth7b49596) entered disabled state
[  689.328498] vethd100f45: renamed from eth0
[  689.397711] docker0: port 1(veth7b49596) entered disabled state
[  689.402546] device veth7b49596 left promiscuous mode
[  689.402551] docker0: port 1(veth7b49596) entered disabled state

Seriously though, great catch, never would have expected that.