Comment # 7 on bug 1173919 from Alberto Bursi

same issue confirmed on Leap 15.3, 2 years later. Wtf people.

I have a workaround, this seems to be a package dependency issue.

by default hawk2 is installed with ruby2.5-rubygem-sass-rails-5.1 dependency,
but hawk-backend fails 

��������� hawk-backend.service - HA Web Konsole Backend
     Loaded: loaded (/usr/lib/systemd/system/hawk-backend.service; static)
     Active: failed (Result: exit-code) since Fri 2022-04-22 14:50:46 CEST;
994ms ago
    Process: 27451 ExecStart=/usr/bin/puma.ruby2.5 -C
/usr/share/hawk/config/puma.rb (code=exited, status=1/FAILURE)
   Main PID: 27451 (code=exited, status=1/FAILURE)

apr 22 14:50:46 susehost1 puma.ruby2.5[27451]:         from
/usr/lib64/ruby/gems/2.5.0/gems/puma-4.3.5/lib/puma/configuration.rb:246:in
`app'
apr 22 14:50:46 susehost1 puma.ruby2.5[27451]:         from
/usr/lib64/ruby/gems/2.5.0/gems/puma-4.3.5/lib/puma/runner.rb:155:in
`load_and_bind'
apr 22 14:50:46 susehost1 puma.ruby2.5[27451]:         from
/usr/lib64/ruby/gems/2.5.0/gems/puma-4.3.5/lib/puma/cluster.rb:413:in `run'
apr 22 14:50:46 susehost1 puma.ruby2.5[27451]:         from
/usr/lib64/ruby/gems/2.5.0/gems/puma-4.3.5/lib/puma/launcher.rb:172:in `run'
apr 22 14:50:46 susehost1 puma.ruby2.5[27451]:         from
/usr/lib64/ruby/gems/2.5.0/gems/puma-4.3.5/lib/puma/cli.rb:80:in `run'
apr 22 14:50:46 susehost1 puma.ruby2.5[27451]:         from
/usr/lib64/ruby/gems/2.5.0/gems/puma-4.3.5/bin/puma:10:in `<top (required)>'
apr 22 14:50:46 susehost1 puma.ruby2.5[27451]:         from
/usr/bin/puma.ruby2.5:23:in `load'
apr 22 14:50:46 susehost1 puma.ruby2.5[27451]:         from
/usr/bin/puma.ruby2.5:23:in `<main>'
apr 22 14:50:46 susehost1 systemd[1]: hawk-backend.service: Main process
exited, code=exited, status=1/FAILURE
apr 22 14:50:46 susehost1 systemd[1]: hawk-backend.service: Failed with result
'exit-code'.


it actually needs ruby2.5-rubygem-sass-rails to work properly.

If you try to uninstall ruby2.5-rubygem-sass-rails-5.1 zypper will try to
remove also hawk2 and other stuff, so we need to follow these steps:

install the new package
zypper install ruby2.5-rubygem-sass-rails

remove the old package (should remove ONLY this package)
zypper remove ruby2.5-rubygem-sass-rails-5.1 

restart hawk-backend service
systemctl restart hawk-backend

now the web interface is accessible at the IP configured.