http://bugzilla.opensuse.org/show_bug.cgi?id=1173919
Bug ID: 1173919
Summary: Hawk backend fails to start
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: High Availability
Assignee: ha-bugs@suse.de
Reporter: john.goutbeck@newsignal.ca
QA Contact: qa-bugs@suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0)
Gecko/20100101 Firefox/77.0
Build Identifier:
did another fresh clean server install of openSUSE Leap 15.2, use openSUSE
repositories
set IP
zypper in hawk2
zypper in ha-cluster-bootstrap
ha-cluster-init
- no sbd
systemctl restart hawk
systemctl restart hawk-backend
with the browser (from a Win 10 laptop) https://192.168.12.242:7630/
- get certificate error - accept
BLANK screen
--
systemctl status hawk
● hawk.service - HA Web Konsole
Loaded: loaded (/usr/lib/systemd/system/hawk.service; enabled; vendor preset>
Active: active (running) since Mon 2020-07-06 21:43:25 MDT; 17min ago
Main PID: 1903 (hawk-apiserver)
But not the hawk-backend
systemctl status hawk-backend
● hawk-backend.service - HA Web Konsole Backend
Loaded: loaded (/usr/lib/systemd/system/hawk-backend.service; static; vendor>
Active: failed (Result: exit-code) since Mon 2020-07-06 22:01:52 MDT; 5s ago
Process: 14663 ExecStart=/usr/bin/puma.ruby2.5 -C /usr/share/hawk/config/puma>
Main PID: 14663 (code=exited, status=1/FAILURE)
So, looking at the /var/log/messages file, this is what I get
---
2020-07-06T21:52:07.277099-06:00 nss-leap152 systemd[1]: Started HA Web Konsole
Backend.
2020-07-06T21:52:07.393681-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] Puma
starting in cluster mode...
2020-07-06T21:52:07.393886-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] *
Version 3.11.0 (ruby 2.5.8-p224), codename: Love Song
2020-07-06T21:52:07.393999-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Min
threads: 0, max threads: 1
2020-07-06T21:52:07.394113-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] *
Environment: production
2020-07-06T21:52:07.394231-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] *
Process workers: 1
2020-07-06T21:52:07.394350-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] *
Preloading application
2020-07-06T21:52:07.710011-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] !
Unable to load application: Gem::ConflictError: Unable to activate
sass-rails-5.1.0, because railties-5.1.4 conflicts with railties (>= 5.2.0)
2020-07-06T21:52:07.710267-06:00 nss-leap152 puma.ruby2.5[10033]:
/usr/lib64/ruby/2.5.0/rubygems/specification.rb:2327:in `raise_if_conflicts':
Unable to activate sass-rails-5.1.0, because railties-5.1.4 conflicts with
railties (>= 5.2.0) (Gem::ConflictError)
2020-07-06T21:52:07.710480-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/2.5.0/rubygems/specification.rb:1438:in `activate'
2020-07-06T21:52:07.710599-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:68:in `block in gem'
2020-07-06T21:52:07.710749-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `synchronize'
2020-07-06T21:52:07.710878-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
2020-07-06T21:52:07.710991-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/share/hawk/config/boot.rb:35:in `'
2020-07-06T21:52:07.711074-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711158-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711239-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/share/hawk/config/application.rb:4:in `'
2020-07-06T21:52:07.711320-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/share/hawk/config/environment.rb:5:in `require_relative'
2020-07-06T21:52:07.711400-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/share/hawk/config/environment.rb:5:in `'
2020-07-06T21:52:07.711477-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711573-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711650-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
config.ru:4:in `block in <main>'
2020-07-06T21:52:07.711726-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:55:in
`instance_eval'
2020-07-06T21:52:07.711804-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:55:in
`initialize'
2020-07-06T21:52:07.711880-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
config.ru:in `new'
2020-07-06T21:52:07.711957-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
config.ru:in `<main>'
2020-07-06T21:52:07.712037-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:49:in `eval'
2020-07-06T21:52:07.712114-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:49:in
`new_from_string'
2020-07-06T21:52:07.712186-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:40:in
`parse_file'
2020-07-06T21:52:07.712257-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/configuration.rb:318:in
`load_rackup'
2020-07-06T21:52:07.712327-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/configuration.rb:243:in
`app'
2020-07-06T21:52:07.712401-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/runner.rb:138:in
`load_and_bind'
2020-07-06T21:52:07.712472-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/cluster.rb:397:in `run'
2020-07-06T21:52:07.712540-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/launcher.rb:183:in `run'
2020-07-06T21:52:07.712611-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/cli.rb:77:in `run'
2020-07-06T21:52:07.712680-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/bin/puma:10:in `'
2020-07-06T21:52:07.712772-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/bin/puma.ruby2.5:23:in `load'
2020-07-06T21:52:07.712848-06:00 nss-leap152 puma.ruby2.5[10033]: #011from
/usr/bin/puma.ruby2.5:23:in `<main>'
2020-07-06T21:52:07.713821-06:00 nss-leap152 systemd[1]: hawk-backend.service:
Main process exited, code=exited, status=1/FAILURE
2020-07-06T21:52:07.714104-06:00 nss-leap152 systemd[1]: hawk-backend.service:
Unit entered failed state.
2020-07-06T21:52:07.714242-06:00 nss-leap152 systemd[1]: hawk-backend.service:
Failed with result 'exit-code'.
---
query the rpm
nss-leap152:~ # rpm -qa | grep railties
ruby2.5-rubygem-railties-5_1-5.1.4-lp152.3.3.x86_64
ruby2.5-rubygem-railties-5.2-5.2.3-lp152.2.3.x86_64
nss-leap152:~ # rpm -qa | grep sass
ruby2.5-rubygem-sass-3.5.3-lp152.3.3.x86_64
ruby2.5-rubygem-sass-rails-5.1-5.1.0-lp152.1.1.x86_64
ruby2.5-rubygem-sass-listen-4.0.0-lp152.3.3.x86_64
---
nss-leap152:~ # zypper up
Loading repository data...
Reading installed packages...
Nothing to do.
nss-leap152:~ # zypper in -force hawk
The flag o is not known.
nss-leap152:~ # update-alternatives --config rails
There are 2 choices for the alternative rails (providing /usr/bin/rails).
Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/bin/rails.ruby2.5-5.2.3 50203 auto mode
1 /usr/bin/rails.ruby2.5-5.1.4 50104 manual mode
2 /usr/bin/rails.ruby2.5-5.2.3 50203 manual mode
- I chose option 1, 2 and back to 0, still no joy
- restart hawk and hawk-backend in-between options.
---
zypper in -f hawk2
Loading repository data...
Reading installed packages...
Forcing installation of 'hawk2-2.1.1+git.1585238036.fab19246-lp152.1.9.x86_64'
from repository 'Main Repository'.
Resolving package dependencies...
The following package is going to be reinstalled:
hawk2
1 package to reinstall.
Overall download size: 9.3 MiB. Already cached: 0 B. No additional space will
be used or freed after the operation.
Continue? [y/n/v/...? shows all options] (y):
Retrieving package hawk2-2.1.1+git.1585238036.fab19246-lp152.1.9.x86_64 (1/1),
9.3 MiB ( 20.6 MiB unpacked)
Retrieving: hawk2-2.1.1+git.1585238036.fab19246-lp152.1.9.x86_64.rpm
..............................................[done (3.7 MiB/s)]
Checking for file conflicts:
..................................................................................................[done]
(1/1) Installing: hawk2-2.1.1+git.1585238036.fab19246-lp152.1.9.x86_64
........................................................[done]
Additional rpm output:
Updating /etc/sysconfig/hawk ...
systemctl restart hawk
systemctl restart hawk-backend
- still BLANK whit screen - no joy
Reproducible: Always
Steps to Reproduce:
1. Install Server based openSUSE Leap 15.2
2. zypper in hawk2
3. zypper in ha-cluster-bootstrap
4. ha-cluster-init
with the browser (from a Win 10 laptop) https://192.168.12.242:7630/
- get certificate error - accept
BLANK white screen
Actual Results:
BLANK whit screen
no HAWK2 login
Expected Results:
HAWK2 Login screen & HAWK 2 UI
--
You are receiving this mail because:
You are on the CC list for the bug.
