Fresh install of Ubuntu 20.04 and fresh install of Opennebula 6.0, using sqlite3. Everything worked great, setup networks, created VMs, etc. Then I powered down to move the server. Now after the sever has booted up I can’t login to Sunstone. I’m getting a 404 error saying “Sinatra doesn’t know this ditty”. What broke between power down and power back up???
Hi @cstory777 ,
You should check the log files after login: sunstone.error and oned.log.
More information in Sunstone configuration doc
After move you commented, It’s probably your sunstone-server configuration file needs a review.
Best,
Sergio
There is no sunstone.error log and oned.log has nothing regarding the error. The only thing I see in a log is in sunstone.log and it is really no help.
oned.log:
Wed Jun 2 08:22:58 2021 [Z0][ReM][D]: Req:5344 UID:0 IP:127.0.0.1 one.zone.raftstatus invoked
Wed Jun 2 08:22:58 2021 [Z0][ReM][D]: Req:5344 UID:0 one.zone.raftstatus result SUCCESS, “<SERVER_ID>-1<…”
Wed Jun 2 08:22:58 2021 [Z0][ReM][D]: Req:6976 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Wed Jun 2 08:22:58 2021 [Z0][ReM][D]: Req:6976 UID:0 one.vmpool.infoextended result SUCCESS, “<VM_POOL>6</…”
Wed Jun 2 08:22:58 2021 [Z0][ReM][D]: Req:5408 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Wed Jun 2 08:22:58 2021 [Z0][ReM][D]: Req:5408 UID:0 one.vmpool.infoextended result SUCCESS, “<VM_POOL>6</…”
Wed Jun 2 08:23:07 2021 [Z0][ReM][D]: Req:3088 UID:0 IP:127.0.0.1 one.zone.raftstatus invoked
Wed Jun 2 08:23:07 2021 [Z0][ReM][D]: Req:3088 UID:0 one.zone.raftstatus result SUCCESS, “<SERVER_ID>-1<…”
Wed Jun 2 08:23:07 2021 [Z0][ReM][D]: Req:6672 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Wed Jun 2 08:23:07 2021 [Z0][ReM][D]: Req:6672 UID:0 one.vmpool.infoextended result SUCCESS, “<VM_POOL>6</…”
Wed Jun 2 08:23:07 2021 [Z0][ReM][D]: Req:3888 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Wed Jun 2 08:23:07 2021 [Z0][ReM][D]: Req:3888 UID:0 one.vmpool.infoextended result SUCCESS, “<VM_POOL>6</…”
Wed Jun 2 08:23:13 2021 [Z0][ReM][D]: Req:7808 UID:0 IP:127.0.0.1 one.zone.raftstatus invoked
Wed Jun 2 08:23:13 2021 [Z0][ReM][D]: Req:7808 UID:0 one.zone.raftstatus result SUCCESS, “<SERVER_ID>-1<…”
Wed Jun 2 08:23:13 2021 [Z0][ReM][D]: Req:5968 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Wed Jun 2 08:23:13 2021 [Z0][ReM][D]: Req:5968 UID:0 one.vmpool.infoextended result SUCCESS, “<VM_POOL>6</…”
Wed Jun 2 08:23:13 2021 [Z0][ReM][D]: Req:9632 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Wed Jun 2 08:23:13 2021 [Z0][ReM][D]: Req:9632 UID:0 one.vmpool.infoextended result SUCCESS, “<VM_POOL>6</…”
sunstone.log:
Wed Jun 02 08:22:57 2021 [I]: 10.100.255.88 - - [02/Jun/2021:08:22:57 -0400] “GET / HTTP/1.1” 200 - 0.0477
Wed Jun 02 08:22:57 2021 [I]: 10.100.255.88 - - [02/Jun/2021:08:22:57 -0400] “GET /dist/login.js HTTP/1.1” 200 - 0.0137
Wed Jun 02 08:22:57 2021 [I]: 10.100.255.88 - - [02/Jun/2021:08:22:57 -0400] “GET /dist/login.js HTTP/1.1” 200 - 0.0127
Wed Jun 02 08:23:12 2021 [I]: 10.100.255.88 - - [02/Jun/2021:08:23:12 -0400] “POST / HTTP/1.1” 404 - 0.0010
Wed Jun 02 08:23:12 2021 [I]: 10.100.255.88 - - [02/Jun/2021:08:23:12 -0400] “GET /sinatra/404.png HTTP/1.1” 401 - 0.0007
As I said in my initial post Sunstone was running just fine for hours while I setup the server. Only after I powered it down to move it did it stop working. I made no changes to /etc/one/sunstone-server.conf.
Also of note, whenever I go to http://x.x.x.x:9869 there’s a spinning wheel to the left of the “Login” button that never stops spinning.
anyone have anything on this? I can’t be the first, after all the Sinatra thing is an image that is part of OpenNebula so someone has to have had this happen before.
Just tried a fresh install of Ubuntu 18.04, OpenNebula 6 and MariaDB 10.1.48 on a different server. Sunstone immediately gives the same Sinatra error. And this is following the docs here: Single Front-end Installation — OpenNebula 6.0.2 documentation.
Hello @cstory777 ,
I have never seen this error before, but I found this ticket in github.
I hope it helps you 
Best,
Sergio