Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.12 update update fail over tteck #89

Closed
snickerweb opened this issue Apr 14, 2024 · 6 comments
Closed

0.12 update update fail over tteck #89

snickerweb opened this issue Apr 14, 2024 · 6 comments
Assignees
Labels
bug Something isn't working proxmox Anything to do with proxmox

Comments

@snickerweb
Copy link

snickerweb commented Apr 14, 2024

Update over tteck do this at the end:

`<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0xb84bd6 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xefec30 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xefef17 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x1110925 [/usr/bin/node]
5: 0x1110eb4 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x1127da4 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x11285bc v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10fe8c1 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]
9: 0x10ffa55 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]
10: 0x10dd0a6 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/bin/node]
11: 0x1537e36 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]
12: 0x1971ef6 [/usr/bin/node]
|Aborted
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[ERROR] in line 68: exit code 0: while executing command yarn build

root@mafl:~# nano /opt/mafl/data/config.yml`

@snickerweb snickerweb added the bug Something isn't working label Apr 14, 2024
@hywax
Copy link
Owner

hywax commented Apr 14, 2024

Hi, you don't have enough memory in the lxc container. This is because the application is build from source.

The solution would be to increase the RAM memory of the container.

@snickerweb
Copy link
Author

Now I make a new tteck lxc. Works fine.

Maybe tteck should give as standard more ram

@hywax
Copy link
Owner

hywax commented Apr 14, 2024

How much memory did you have at the time of the error?

@snickerweb
Copy link
Author

2gb

@hywax
Copy link
Owner

hywax commented Apr 14, 2024

That's a lot, 1gb should be enough.

The script is in another repository (tteck). Maybe something in it has changed, it used to require less to update.

I'll try to fix it or ask tteck for help.

@hywax hywax added the proxmox Anything to do with proxmox label Apr 15, 2024
hywax added a commit that referenced this issue Apr 15, 2024
@hywax
Copy link
Owner

hywax commented Apr 15, 2024

Added documentation on this error - https://mafl.hywax.space/guide/getting-started.html#proxmox

@hywax hywax closed this as completed Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working proxmox Anything to do with proxmox
Projects
None yet
Development

No branches or pull requests

2 participants