Upgrading to 2.0 - memory issue with CLI

boohoo

My version 1.8 forum finally works. Yeah! Thanks to some wonderful people on the site. Since I'm just starting out, I thought I'd upgrade to 2.0 because I'm having issues with email and I wouldn't want to start using and become dependent on extensions that will become obsolete.

I didn't get far on my installation:

npm install -g @flarum/cli@3

#

Fatal process out of memory: Failed to reserve virtual memory for CodeRange

#
----- Native stack trace -----

1: 0x9457d1 [node]
2: 0x26819d5 v8::base::FatalOOM(v8::base:😮OMType, char const) [node]
3: 0xba1b6f [node]
4: 0xba1c0f [node]
5: 0xe47dfe [node]
6: 0xd7823e [node]
7: 0x1351d33 [node]
8: 0xbcbda6 v8::Isolate::Initialize(v8::Isolate, v8::Isolate::CreateParams const&) [node]
9: 0x7835f0 node::NewIsolate(v8::Isolate::CreateParams, uv_loop_s, node::MultiIsolatePlatform, node::SnapshotData const, node::IsolateSettings const&) [node]
10: 0x903309 node::NodeMainInstance::NodeMainInstance(node::SnapshotData const, uv_loop_s, node::MultiIsolatePlatform*, std::vector<std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, std::vector<std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&) [node]
11: 0x843076 node::Start(int, char**) [node]
12: 0x7fd031a50610 [/lib64/libc.so.6]
13: 0x7fd031a506c0 __libc_start_main [/lib64/libc.so.6]
14: 0x77a92e _start [node]
Trace/breakpoint trap (core dumped)

using: node --max-old-space-size=256 npm install -g @flarum/cli@3

same thing

I have limited knowledge of most of what my terminal prints. What exactly is wrong? How much memory does this thing need?

Post your output of php flarum info here. Without this information providing support will take longer! >Flarum core: 1.8.12 PHP version: CLI: 8.3.30, Web: 8.3.30 PHP memory limit: CLI: 512M, Web: unable to detect MySQL version: 5.7.44-48 Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, pcntl, random, readline, Reflection, SPL, session, standard, bcmath, bz2, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, gmp, iconv, imap, intl, exif, mysqlnd, odbc, PDO, pgsql, Phar, posix, pspell, SimpleXML, soap, sockets, sodium, sqlite3, tidy, tokenizer, xml, xmlwriter, xsl, zip, mysqli, pdo_mysql, PDO_ODBC, pdo_pgsql, pdo_sqlite, xmlreader, apcu, imagick, Zend OPcache +--------------------------+---------+--------+-------+ | Flarum Extensions | | | | +--------------------------+---------+--------+-------+ | ID | Version | Commit | Notes | +--------------------------+---------+--------+-------+ | flarum-flags | v1.8.2 | | | | flarum-approval | v1.8.2 | | | | flarum-tags | v1.8.6 | | | | nauhyuh-migration-tool | 2.4.1 | | | | flarum-suspend | v1.8.5 | | | | flarum-subscriptions | v1.8.1 | | | | flarum-sticky | v1.8.2 | | | | flarum-statistics | v1.8.1 | | | | flarum-pusher | v1.8.1 | | | | flarum-mentions | v1.8.5 | | | | flarum-markdown | v1.8.1 | | | | flarum-lock | v1.8.2 | | | | flarum-likes | v1.8.1 | | | | flarum-lang-english | v1.8.0 | | | | flarum-extension-manager | v1.0.7 | | | | flarum-emoji | v1.8.1 | | | | flarum-bbcode | v1.8.0 | | | +--------------------------+---------+--------+-------+ Base URL: https://brainchildforum.com Installation path: /home2/mwkclamy/public_html/website_60ff95db/flarum Queue driver: sync Session driver: file Mail driver: smtp Debug mode: off

KBExit

boohoo thought I'd upgrade to 2.0 because I'm having issues with email and I wouldn't want to start using and become dependent on extensions that will become obsolete.

Email is not by extension and instead it is built into core. There can be many reasons to why your email doesn't work. Seeing that you're on shared hosting, you're extremely limited to what you can do. I suggest using Mailgun for email delivery since it's the simplest setup with just 1 API Key. Additionally, your host may be blocking the email ports to prevent spam / abuse. This is why it's crucial you research your hosting provider and set up with a VPS instead of shared hosting.

Moreover, that argument is not valid since 2.0 is beta and is not stable. It's a huge liability to push 2.0 on a production site especially when you don't understand the fundamentals of the stable builds that are out currently.

Long story short. As long as you're on shared hosting, you will always have issues and obstacles left and right.

boohoo

Mailgun costs money after 100 emails a month. I am thinking of my site being a big site because I am hopelessly optimistic! I am trying symfony.

Cool. I got it to work once I searched for my web host's details for smtp.

Okay, thanks for the info about Flarum 2.0. I saw that someone said it was beta last year in January 2025, and I assumed it certainly couldn't be beta now. I guess my site is done. Now I just have to do a million posts to incite people to post and add extensions and finessing.

Is there anywhere where you can "trade" posts to populate a baby site? Like I'll post on your site if you post on mine.

boohoo

Once again my topic took an unexpected turn and ended up having nothing to do with the title. Is there a way to change the title to help people find the right topics by title?

KBExit

boohoo Is there anywhere where you can "trade" posts to populate a baby site? Like I'll post on your site if you post on mine.

You'd have to review the Community Guidelines and make that judgement. https://discuss.flarum.org/p/3-guidelines

luceos

KBExit This is why it's crucial you research your hosting provider and set up with a VPS instead of shared hosting.

I know you mean well, but this is simply untrue.

Especially for people struggling with technical matters, shared hosting or managed hosting is much better in many ways:

no need to (learn to) configure a server
no need to (learn how to) keep your own server updated, secured and patched
no need to (learn how to) monitor your server for downtime, security patches, volumes running full etc

A lot of people on the internet suggest running your own vps and this is usually a reason why sites get defaced or hacked. It's not as simply as you make it believe, and this understanding will only hit once problems arise for that person.

boohoo MultiIsolatePlatform

From what I understand it seems your hosting provider isolates the javascript processes using something called isolated-vm. You could ask them for help, that's what they are for.

Also, upgrading to 2 because your email doesn't work, likely won't help you as the same issue will again exist. Also here, I would recommend asking your hosting provider by providing them with the given error. As @KBExit points out, usually hosting providers block commonly used email ports to prevent spam.

boohoo you can flag a post or topic to request help from @Moderators .

KBExit

luceos a lot of support requests lately have hit roadblocks because of shared hosting restrictions. I am only pointing out the common pattern I am seeing lately.
Shared hosting all have their own flavors, and you're right that misconfigured servers are dangerous. But seeing shared host after shared host limiting their customers, the path of least resistance is to set up a VPS. It's not impossible and I think we should encourage those to learn. It has been rewarding to me to be challenged and try something new. But I completely understand your stance. But as I have said, shared host after shared host, have been a common hard block recently here.

boohoo

Okay, smtp didn't work for sending passwords. I had to use mailgun, and it didn't work for sending passwords until a day or two after I set it up. Everything is good now...until...

KBExit

boohoo Everything is good now...until...

Until what?

boohoo

It was just a hypothetical. I'm assuming something will go wrong, and it did. Messaging extension didn't work, but I don't need that for sure. I did all the troubleshooting things, and now I'm going to wait and do some other stuff, and hopefully the new stuff I do will help the Messaging extension.