Clarify that running main requires more than 2G of RAM, unlike versioned releases

[ebecaf]

Hi,

I have had a look at the other 4.x to 5.x update issues but they don't seem to apply.

I get:

Error running a subcommand of ./tools/update-prod-static: ./tools/webpack --quiet
Actual error output for the subcommand is just above this.

upgrade-zulip-stage-2: Failed to build static assets.
Zulip upgrade failed (exit code 1)!

Here is what is above the --quiet in the logs:

[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "swagger-parser > @apidevtools/swagger-parser@10.0.3" has unmet peer dependency "openapi-type>
[4/4] Building fresh packages...
warning Ignored scripts due to flag.
Done in 26.04s.
Using cached node modules from /srv/zulip-npm-cache/123456789/node_mod>
+ ./tools/setup/emoji/build_emoji
build_emoji: Using cached emojis from /srv/zulip-emoji-cache/123456789>
+ ./scripts/setup/inline_email_css.py
+ ./tools/setup/generate_zulip_bots_static_files.py
+ ./tools/setup/build_pygments_data
+ ./tools/setup/build_timezone_values
+ ./tools/webpack --quiet

I assume it has something to do with;

warning "swagger-parser > @apidevtools/swagger-parser@10.0.3" has unmet peer dependency

Ubuntu 20
PostgreSQL 14.1
Zulip 4.11 (obviously :) )

Thanks for your help

[andersk]

No, the swagger-parser warning is harmless. I think this is what happens when webpack runs out of RAM. Try adding more RAM or swap, or install using the tarball (which has pre-built webpack bundles) rather than Git.

[ebecaf]

No, the swagger-parser warning is harmless. I think this is what happens when webpack runs out of RAM. Try adding more RAM or swap, or install using the tarball (which has pre-built webpack bundles) rather than Git.

Will try that, thank you

[zulipbot]

Hello @zulip/server-production members, this issue was labeled with the "area: production installer" label, so you may want to check it out!

[timabbott]

@ebecaf were you able to complete this upgrade? I figure we should close the issue to clean up the tracker if so.

[alexmv]

I'm resolving this issue due to lack of response -- please re-open if you're still seeing an issue.

[oyale]

I am writing to confirm that we encountered the same problem (when upgrading the server using /home/zulip/deployments/current/scripts/upgrade-zulip-from-git main, as we are migrating from the cloud) and that it was indeed due to the machine not having enough RAM.

Maybe it is worth adding it to the documentation?

Thanks to everyone!

[alexmv]

How much RAM did you have before, and what version were you upgrading to main from?

[oyale]

We were running it on a 2 GB CX11 Hetzner's machine. Switching to a 4 GB's CX21 was enough to run the upgrade smoothly.

I didn't catch the exact patch, but it was a v5.6, the one provided by the latest installer (using this Ansible role).

[alexmv]

I believe this to be because when building from main, you need to have enough memory to run webpack, which has started requiring more than 2G of RAM. The pre-packaged releases with version numbers have the webpack output pre-generated and bundled in them.

The action here is likely to better document that the memory requirements for main are higher than those for versioned releases. @oyale and @ebecaf, when planning to upgrade to main, did you read https://zulip.readthedocs.io/en/latest/production/upgrade-or-modify.html#upgrading-from-a-git-repository -- such that if we added a note about expanded memory requirements in main there, you'd have seen it?

[alexmv]

We do say, in the "requirements and scalability" section of a different page:

• At least 2 GB RAM, and 10 GB disk space
  • If you expect 100+ users: 4 GB RAM, and 2 CPUs
  • If you intend to upgrade from Git: 3 GB RAM, or 2G and at least 1G of swap configured.

But that can be easily missed if one was on a release when it was first alled.

[oyale]

Yeah, I've seen it in the requirements section just after writing this issue, sorry.

We have indeed read the section Upgrading from a Git repository, following the link in the section Importing to a new Zulip server.

[timabbott]

@alexmv do you have an idea for where we might update documentation, or should we close this?

(I suppose another idea could be to have a check in the upgrade tool)