Good start (in openproject) seems to bring the CPU to 100%

[MWH-Rookie]

Hi there,

I just installed OpenProject under Ubuntu 24.04 LTS. My problem is that after a restart my system slows down to the bottom, because both CPUs (or cores) are dealing with 100% ruby processes. This immeadiately stops when I stop openproject with
"sudo systemctl stop openproject". However, this does not solve the problem. As it seems every few seconds one of the ruby processes ends and another comes up with 100% CPU usage again. Then I searched for more information:
ps -fp 17138
UID PID PPID C STIME TTY TIME CMD
openpro+ 17138 17111 99 11:35 ? 00:00:03 /opt/openproject/vendor/bundle/ruby/3.3.0/bin/good_job start
So, it seems that it has something to do with good_job. But I don't know how to handle that. I'm not a ruby developer.
I already switched from the apt version of ruby (3.2) to the snap version (3.3), but this did not make any difference.

In earlier attempts I also rebooted the system, restarted apache2, and restartet postgresql. However, nothing worked and as far as this cannot be solved I cannot use openproject.

Best regards
MH

[bensheldon]

Hi! I'm a GoodJob maintainer. I'm not familiar with openproject so you should probably open an issue with them first.

Just for brief background: GoodJob shares all of the same startup code as a Ruby on Rails web service in the same app. So from your description, it sounds like the problem of 100% CPU is likely unrelated specifically to GoodJob. And I imagine that the process restarting is related to some kind of process-monitor, again outside of GoodJob.

[MWH-Rookie]

Hi Ben
Thanks for your reply. So far I have sent an email to the administration of the OP community in order to also post my question there. In the meantime I could solve my problem, but rather by accident and I do not know how reliable it is. What I did:

1. sudo apt-get remove --purge openproject
2. sudo apt-get install openproject
3. sudo openproject configure
4. copy a modified version of a token file to /opt/openproject/app/models/

And then I did not restart anything. I just had to wait a short moment and the ruby processes' CPU usage went down. But I have no clue why and how this solved the issue.