Discourse installer broken again

hello

When I install discourse, I get the following error:
ERROR: Lararia\Jobs\Job::handle(): Job failed – fatal error: fatal(): `discourse_install’ crashed or ran into a serious issue.

I’ve tried updating to edge, but the same error still occurs. It might help to add an install checker on your side and either disable apps that don’t work or lock them to a specific version, because this problem keeps coming back.

Fixed in edge. If you’re still experiencing issues installing, then it’d be necessary to examine storage/logs/start.log to determine the underlying cause.

If you’d like to disallow this app from being installed, you may blacklist it:

cpcmd scope:set cp.config webapps blacklist 'magento,discourse'

Hello

It still doesn’t work on edge. There is a new error now. Can you please check this and confirm that the installer is functional as there may be more errors once this one is fixed.

2025-01-27 08:01:25][36511] Failed: Lararia\Jobs\InstallAppJob
(Lararia\Jobs\JobException) EXCEPTION: DataStream::pipeline(): Discourse_Module::install(): A MaxMind GeoLite2 key is required.

Said key is specified.

FYI key has the following format: QyHi2p_XXXXXXXXXXXXXXXX_mmk

If you’d like to disallow this app from being installed, you may blacklist it:

What I meant is that it should automatically blacklist them once the installer breaks as it happens every few updates.

Thanks for the information. Maxmind updated their key format, which now includes underscores. This has been amended in edge.

A Maxmind key is no longer required to install but will use it for GeoIP lookups if present.

Hello,

On edge the install still fails if I specify the license key.

If I remove it, it doesn’t fail with the same error however it still fails and site displays:
*** ERROR ***: cannot assign to cgroup site144: Cgroup is not mountedno cgroup set! errno=1 errmsg=Cgroup is not mounted
*** ERROR ***: Cannot execute 2.5.8: No such file or directory (2)

Passenger is no longer used to directly launch Discourse. It’s a separate launcher script within the app root (launch.sh).

Check with the latest release on edge. Looks good on my end with the newer key format.

Okay. Do you have any instructions for starting the discorse application after it’s installed? Am I cronjobbing this shell file or is it managed by the web app?

It starts automatically by invoking launch.sh located within its app root. If you’d need to kill the application, it can be killed from the terminal or UI but that’s managed directly, including on boot.

That’s strange. For me it does not start automatically even on reinstall I get the same error,
*** ERROR ***: cannot assign to cgroup site144: Cgroup is not mountedno cgroup set! errno=1 errmsg=Cgroup is not mounted
*** ERROR ***: Cannot execute 2.5.8: No such file or directory (2)

Does it boot automatically for you?

If I click on restart app it gives:
Internal Server Error

No sentient programmers detected
¯_(ツ)_/¯

Additionally, there is no launch.sh file at the document root.

What do you think about my idea of locking certain apps to minor version until you have the time to test the next major version to prevent things like this from breaking again in the future? Or how do you recommend we resolve this permanently going forward as some change in the future is sure to break any web app - it’s just a matter of time.

I’m not able to reproduce with either 2.8.14 or 3.3.3 using Redis 6.2. Run the installer from the shell (cpcmd -d DOMAIN discourse:install DOMAIN '' '[version:VERSION-NUMBER,maxmind:API-KEY]') and PM me the log.

Proper .htaccess looks like,

# Enable caching
UnsetEnv no-cache
DirectoryIndex disabled
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ http://localhost:ACCOUNT-PORT/$1 [P,L,QSA]

Zero Passenger directives are used.

PM’d. For your own information the Laravel installer is broken for me too :confused:

18.18.0 is the minimum Node engine now. Presently 18.12.1 is installed on the site (nvm uninstall 18.12.1 to remove). I’ve raised the requirement for 3.2+, which should clear this up going forward.

lgtm. Note that newer Laravel frameworks require newer PHP versions.

# cpcmd -d ssss.test php:pool-get-version
8.2

# cpcmd -d ssss.test laravel:install ssss.test '' '[empty:1]'
DEBUG  : Property verlock deferred until installation
DEBUG  : Property fortify deferred until installation
INFO   : Relocated primary document root from `/var/www/html' to `/var/www/html-laravel'
INFO   : created database `ssss_sssstest'
INFO   : added database backup task for `ssss_sssstest'
DEBUG  : Cancelling rollback queue
INFO   : Laravel installed - confirmation email with login info sent to blackhole@apnscp.com
----------------------------------------
MESSAGE SUMMARY
Reporter level: SUCCESS
SUCCESS: detected `laravel'; updating records
DEBUG: Property verlock deferred until installation
DEBUG: Property fortify deferred until installation
INFO: Relocated primary document root from `/var/www/html' to `/var/www/html-laravel'
INFO: created database `ssss_sssstest'
INFO: added database backup task for `ssss_sssstest'
DEBUG: Cancelling rollback queue
INFO: Laravel installed - confirmation email with login info sent to blackhole@apnscp.com
----------------------------------------
1