snm
June 8, 2023, 11:18am
1
My YunoHost server
Hardware: Old computer at home
YunoHost version: 11.1.20
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
If your request is related to an app, specify its name and version: HedgeDoc 1.9.7~ynh3
Description of my issue
Hi,
I’m trying to upgrade HedgeDoc from Version 1.9.7~ynh3 to Version 1.9.8~ynh1. It fails with
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
.
This is the log: https://paste.yunohost.org/raw/uqasulebak
Here is a problem with the same error message where it was assumed that there was not enough memory:
Hello! I tried install misskey, but I see error:
2022-07-14 13:14:50,263: DEBUG - FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
2022-07-14 13:14:50,295: DEBUG - 1: 0xb09980 node::Abort() [webpack]
2022-07-14 13:14:50,297: DEBUG - 2: 0xa1c235 node::FatalError(char const*, char const*) [webpack]
2022-07-14 13:14:50,300: DEBUG - 3: 0xcf77be v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [webpack]
2022-07-14 13:14:50,302: DEBUG - 4…
But my server already uses an 8G swap file:
sudo swapon -s && echo && free
Filename Type Size Used Priority
/swapfile file 8388604 803384 -2
/dev/dm-1 partition 999420 0 -3
/dev/zram0 partition 262140 262132 100
total used free shared buff/cache available
Mem: 1938512 1486816 70588 21796 381108 279012
Swap: 9650164 1067828 8582336
Shouldn’t that be sufficient? Any ideas what I could try?
pqc
June 18, 2023, 5:02pm
2
I am having the same issue.
YunoHost version: 11.1.21.4
I just tried increasing my swap from 2GB to 4GB and it still failed, but it sounds like 8GB isn’t even enough!
Also wondering if anyone has any idea on how to fix this!
pqc
June 19, 2023, 4:49pm
3
I did a little digging into this, and it seems there have been issues in the past trying to run or install HedgeDoc with 2GB (or less) of memory. (I only have 2GB of physical memory.)
opened 06:06PM - 29 Jan 21 UTC
closed 08:34AM - 21 Mar 21 UTC
Hello,
**Describe the bug**
I was trying to install Hedgedoc on a sub-domain… . It didn't work and the application wasn't installed.
**Versions**
- Hardware: Kimsufi KS-3 Server
- YunoHost version: 4.1.6 (everything up-to-date)
- I have access to my server: *Through SSH | through the webadmin*
- Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: *no*
- Using, or trying to install package version/branch: 1.7.2
**To Reproduce**
I tried from the webadmin but it's the same from the CLI :
```sh
$ sudo yunohost app install hedgedoc
Choose the domain where this app should be installed [mydomain.be | cloud.mydomain.be | pad.mydomain.be] (default: mydomain.be): pad.mydomain.be
Choose the path where this app should be installed (default: /hedgedoc): /
Should this app be exposed to anonymous visitors? [yes | no] (default: yes): yes
Info: Installing hedgedoc...
Info: [....................] > Validating installation parameters...
Info: [....................] > Storing installation settings...
Info: [+...................] > Finding an available port...
Info: [#++++++.............] > Installing dependencies...
Info: Installation of N - Node.js version management
Info: '/etc/apt/trusted.gpg.d/hedgedoc.asc' wasn't deleted because it doesn't exist.
Info: [#######+............] > Creating a PostgreSQL database...
Info: [########+...........] > Setting up source files...
Info: [#########...........] > Configuring NGINX web server...
Info: [#########+..........] > Configuring system user...
Info: [##########++++++....] > Building HedgeDoc... (this will take some time and resources!)
Warning: error /var/www/hedgedoc/node_modules/sqlite3: Command failed.
Warning: Exit code: 1
(...)
```
**Expected behavior**
I expected Hedgedoc installation.
**Logs**
The logs are there : https://paste.yunohost.org/raw/egofapesoy
opened 02:52AM - 28 Dec 20 UTC
closed 07:08AM - 04 Jan 21 UTC
I tried installing HedgeDoc, but ran into an error.
It looks like it's an out… of memory error, here's a piece of the stacktrace:
> 2020-12-27 20:34:07,830: DEBUG - <--- JS stacktrace --->
> 2020-12-27 20:34:07,830: DEBUG -
> 2020-12-27 20:34:07,830: DEBUG - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
> 2020-12-27 20:34:07,830: DEBUG - 1: 0xa04200 node::Abort() [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,830: DEBUG - 2: 0x94e4e9 node::FatalError(char const*, char const*) [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,830: DEBUG - 3: 0xb7860e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,831: DEBUG - 4: 0xb78987 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,831: DEBUG - 5: 0xd33215 [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,831: DEBUG - 6: 0xd33d9f [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,831: DEBUG - 7: 0xd41e2b v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,831: DEBUG - 8: 0xd459ec v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,831: DEBUG - 9: 0xd140cb v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,831: DEBUG - 10: 0x105a06f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,832: DEBUG - 11: 0x1400039 [/opt/node_n/n/versions/node/14.15.3/bin/node]
> 2020-12-27 20:34:07,832: DEBUG - Aborted
> 2020-12-27 20:34:07,932: DEBUG - error Command failed with exit code 134.
> 2020-12-27 20:34:07,933: DEBUG - info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
> 2020-12-27 20:34:07,933: DEBUG - + ynh_exit_properly
> 2020-12-27 20:34:07,933: DEBUG - + local exit_code=134
> 2020-12-27 20:34:07,934: DEBUG - + '[' 134 -eq 0 ']'
> 2020-12-27 20:34:07,934: DEBUG - + trap '' EXIT
> 2020-12-27 20:34:07,934: DEBUG - + set +o errexit
> 2020-12-27 20:34:07,934: DEBUG - + set +o nounset
> 2020-12-27 20:34:07,935: DEBUG - + sleep 0.5
> 2020-12-27 20:34:08,436: DEBUG - + type -t ynh_clean_setup
> 2020-12-27 20:34:08,437: DEBUG - + ynh_clean_setup
> 2020-12-27 20:34:08,437: DEBUG - + ynh_clean_check_starting
> 2020-12-27 20:34:08,437: DEBUG - + '[' -n '' ']'
> 2020-12-27 20:34:08,437: DEBUG - + '[' -n '' ']'
> 2020-12-27 20:34:08,438: DEBUG - + exit 1
> 2020-12-27 20:34:08,627: ERROR - Could not install hedgedoc: An error occurred inside the app installation script
>
I'm on a VPS with 1 GB of RAM.
According to the YunoHost documentation, 1 GB of RAM should be enough:
> 512 MB RAM (recommended : 1 GB in order to run all the services and apps properly)
[https://yunohost.org/#/hardware](https://yunohost.org/#/hardware)
But it looks like it's possible that HedgeDoc could use 2 GB of RAM (not sure if the YunoHost version does this)?:
> For building the HedgeDoc frontend you need a machine with at least 2 GB RAM.
[https://github.com/hedgedoc/hedgedoc/blob/master/docs/setup/manual-setup.md](https://github.com/hedgedoc/hedgedoc/blob/master/docs/setup/manual-setup.md)
I can try upgrading the RAM, but before I do is there anything I can try to get it to install with 1 GB of RAM?
YunoHost 4.0.8.3 running on a VPS
Full logs: https://paste.yunohost.org/raw/urayaqoqun
1 Like
snm
June 30, 2023, 12:47pm
4
@pqc Thanks for your investigation!
There is also this:
opened 05:41PM - 13 Mar 23 UTC
closed 09:06PM - 17 Apr 23 UTC
### Describe the bug
upgrade to 1.9.7~ynh2 is failing
### Context
- Har… dware: *VPS bought online / Old laptop or computer / Raspberry Pi at home / Internet Cube with VPN / Other ARM board / ...*
- YunoHost version:
```
root@gourzoot:~# yunohost --version
yunohost:
repo: stable
version: 11.1.15
yunohost-admin:
repo: stable
version: 11.1.7
moulinette:
repo: stable
version: 11.1.4
ssowat:
repo: stable
version: 11.1.4
```
- I have access to my server: *Through SSH | through the webadmin *
- Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: *no *
- Using, or trying to install package version/branch: `1.9.7~ynh2`
- If upgrading, current package version: `1.9.6~ynh2`
### Steps to reproduce
- *If you performed a command from the CLI, the command itself is enough. For example:*
```sh
# yunohost app upgrade hedgedoc
```
### Expected behavior
i expect an upgrade to `1.9.7~ynh2`
### Logs
* first try:
https://paste.yunohost.org/raw/xoruxuzeha
i clean yarn cache and retry:
```
root@gourzoot:~# sudo yarn cache clean
yarn cache v1.22.19
success Cleared cache.
Done in 0.07s.
```
* second try is running
It seems adding more Swap doesn’t solve the problem while adding more RAM helps.
I don’t think, though, that adding more RAM is a good solution as long as this is only needed for upgrading an app. Everything is working well on my YunoHost except upgrading HedgeDoc. Using HedgeDoc works without any problems and I’m using it a lot.
Why isn’t it sufficient to add more Swap instead of RAM?
And why is HedgeDoc built on YunoHost instead of providing a prebuilt version?
Thanks in advance for any info / ideas / thoughts / workarounds …
1 Like
ericg
July 1, 2023, 12:24pm
5
Should be fixed in the next update
2 Likes
pqc
July 1, 2023, 10:06pm
6
Good find @snm ! Thanks for the update @ericg !
system
Closed
July 16, 2023, 10:06pm
7
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.