search

ncbo / virtual_appliance

Bioportal Virtual Appliance
5 stars 7 forks source link

New appliance (3.2) UI get stuck on "initialize" #37

Closed jonquet closed 10 months ago

jonquet commented 10 months ago

We have @imadbourouche here at INRAE/Montpellier who recently used the latest release of the appliance. Will provide details.

alexskr commented 10 months ago

sometimes it can happen if appliance fails to get an IP address from the DHCP. Would you be able to provide a screen shot of the console of the appliance?

imadbourouche commented 10 months ago

yes, here are the screenshots.

ip_address ssh home_page rest_service

alexskr commented 10 months ago

when appliance is booted for the very first time it runs firstboot.rb script which resets secrets so that all deployed appliances have unique api keys and rails secrets. This script supposed to remove /srv/ontoportal/bioportal_web_ui/current/public/system/maintenance.html to disable the maintenance notification. This script is run only once so if something goes wrong then the maintenance page doesn't get disabled.

I have previously seen this behavior with the appliance when VM couldn't get the IP address so I would need to make the firstboot script less brittle.

In the mean time you can try to manually run this script:

sudo touch /srv/ontoportal/firstboot
sudo chown ontoportal:ontoportal /srv/ontoportal/firstboot

and reboot the appliance. If you are able to access console you would see something like image

imadbourouche commented 10 months ago

By running the firstboot.rb script it worked now. The scirpt firstboot.rb that i run was in /srv/ontoportal/virtual_appliance/utils/bootstrap Thank you.

ui

alexskr commented 10 months ago

We made a number of fixes to address initialization issues:

  1. The script for determines appliance's IP address fails in some edge cases which prevents starting ncbo_cron and unicorn services. This is addressed by https://github.com/ncbo/virtual_appliance/commit/104cd1f95b6aa2fc423bb737057cbdbe30ff1212

  2. firstboot script can fail for VMs that have low number of CPUs/RAM. This is addressed by https://github.com/ncbo/virtual_appliance/commit/49f81fb2d91017d2ad9ab63bb5b650456015ff5a

Virtual appliance v3.2.1 incorporates those fixes