Installation

webwork2 service start failing in WW 2.18

webwork2 service start failing in WW 2.18

by Sean Fitzpatrick -
Number of replies: 5

I've just upgraded a development server to 2.18 using the instructions in the release notes.

When I get to the last step, the new webwork2 service fails to start. Running `systemctl status webwork2.service` gives the following information:

webwork2.service - webwork2

     Loaded: loaded (/etc/systemd/system/webwork2.service; enabled; vendor preset: enabled)

     Active: failed (Result: exit-code) since Wed 2023-06-07 11:11:49 MDT; 36s ago

    Process: 44391 ExecStart=/usr/local/bin/hypnotoad /opt/webwork/webwork2/bin/webwork2 (code=exited, status=255/EXCEPTION)


Jun 07 11:11:49 webwork-dev hypnotoad[44391]: BEGIN failed--compilation aborted at /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator/Login.pm line 17.

Jun 07 11:11:49 webwork-dev hypnotoad[44391]: Compilation failed in require at /opt/webwork/webwork2/lib/WeBWorK.pm line 50.

Jun 07 11:11:49 webwork-dev hypnotoad[44391]: BEGIN failed--compilation aborted at /opt/webwork/webwork2/lib/WeBWorK.pm line 50.

Jun 07 11:11:49 webwork-dev hypnotoad[44391]: Compilation failed in require at /opt/webwork/webwork2/lib/Mojolicious/WeBWorK.pm line 27.

Jun 07 11:11:49 webwork-dev hypnotoad[44391]: BEGIN failed--compilation aborted at /opt/webwork/webwork2/lib/Mojolicious/WeBWorK.pm line 27.

Jun 07 11:11:49 webwork-dev hypnotoad[44391]: Compilation failed in require at (eval 90) line 1.

Jun 07 11:11:49 webwork-dev hypnotoad[44391]: Compilation failed in require at (eval 88) line 1.

Jun 07 11:11:49 webwork-dev systemd[1]: webwork2.service: Control process exited, code=exited, status=255/EXCEPTION

Jun 07 11:11:49 webwork-dev systemd[1]: webwork2.service: Failed with result 'exit-code'.

Jun 07 11:11:49 webwork-dev systemd[1]: Failed to start webwork2.



In reply to Sean Fitzpatrick

Re: webwork2 service start failing in WW 2.18

by Sean Fitzpatrick -
I noticed that the upgrade instructions are missing the step of copying the webwork2.mojolicious.dist.yml file to webwork2.mojolicious.yml, but including this step didn't help.
In reply to Sean Fitzpatrick

Re: webwork2 service start failing in WW 2.18

by Alex Jordan -

Does journalctl give more information?

In reply to Alex Jordan

Re: webwork2 service start failing in WW 2.18

by Sean Fitzpatrick -
It gave more or less the same info. Running the first command again gave more information, that Mojo/Base.pm was missing, and I needed to install the Mojo::Base module.
This wasn't included in the upgrade instructions, but I think it does get installed if you're on Ubuntu 22.04 and use the Ubuntu package manager to install mojolicious.

So I did a distribution upgrade to 22.04, and now I have new trouble: something happened during upgrade to wipe out the internet settings on my server!
In reply to Sean Fitzpatrick

Re: webwork2 service start failing in WW 2.18

by Sean Fitzpatrick -
I've only sort of solved my networking problems (I lose the network again after rebooting). But I was able to install the potentially missing package, and I still get the same sort of error when trying to start the webwork2 service. It might be easier to just scrap my VM and start from scratch.
In reply to Sean Fitzpatrick

Re: webwork2 service start failing in WW 2.18

by Sean Fitzpatrick -
Got it working (the ww service, not my networking). Upgrading Ubuntu wiped out half my perl modules.