SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Jotty: OOM during update and migration issue #2244

New Issue
Closed
opened 2025-11-20 05:26:02 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:26:02 -05:00
Owner
Copy Link

Originally created by @vhsdream on GitHub (Nov 5, 2025).

Originally assigned to: @vhsdream on GitHub.

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

jotty

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jotty.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

During update (and perhaps during a new install), jotty will fail during the build phase due to running out of memory. Increasing RAM to 4GB fixes this, will make a PR.

Also, for those upgrading from an earlier version, due to a change in how sharing is implemented, there is a migration process that may get "stuck" for users who do not have any shared items.

🔄 Steps to reproduce the issue.

  1. Run update in the LXC console
  2. Observe RAM usage in the Summary tab
  3. Observe build failure

❌ Paste the full error output (if available).

Didn't grab a screenshot

🖼️ Additional context (optional).

For the migration issue, I opened an issue and the dev is on it, so it's likely there's a fix incoming. But there's a simple manual fix:

cd /opt/jotty/data/sharing
rm shared-items.json
touch ../../notes/.sharing.json
touch ../../checklists/.sharing.json
systemctl restart jotty

Only perform the above steps if you find you are stuck on the migration needed/migration success page on the web. This is only for those who had a shared-items.json file that looked like this:

Image
Originally created by @vhsdream on GitHub (Nov 5, 2025). Originally assigned to: @vhsdream on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? jotty ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jotty.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. During update (and perhaps during a new install), jotty will fail during the build phase due to running out of memory. Increasing RAM to 4GB fixes this, will make a PR. Also, for those upgrading from an earlier version, due to a change in how sharing is implemented, there is a migration process that may get "stuck" for users who do not have any shared items. ### 🔄 Steps to reproduce the issue. 1. Run `update` in the LXC console 2. Observe RAM usage in the Summary tab 3. Observe build failure ### ❌ Paste the full error output (if available). Didn't grab a screenshot ### 🖼️ Additional context (optional). For the migration issue, I opened [an issue](https://github.com/fccview/jotty/issues/197) and the dev is on it, so it's likely there's a fix incoming. But there's a simple manual fix: ``` cd /opt/jotty/data/sharing rm shared-items.json touch ../../notes/.sharing.json touch ../../checklists/.sharing.json systemctl restart jotty ``` Only perform the above steps if you find you are stuck on the migration needed/migration success page on the web. This is only for those who had a `shared-items.json` file that looked like this: <img width="689" height="107" alt="Image" src="https://github.com/user-attachments/assets/35555969-6ac1-4243-a55a-263f29371930" />
saavagebueno added the bug label 2025-11-20 05:26:02 -05:00
saavagebueno commented 2025-11-20 05:26:02 -05:00
Author
Owner
Copy Link

@fccview commented on GitHub (Nov 5, 2025):

This should all be fixed in 1.10.1 ❤️
Sorry about it friends!

@fccview commented on GitHub (Nov 5, 2025): This should all be fixed in [1.10.1](https://github.com/fccview/jotty/releases/tag/1.10.1) ❤️ Sorry about it friends!
saavagebueno commented 2025-11-20 05:26:02 -05:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Nov 5, 2025):

I can confirm that 1.10.1 fixes the migration issue - so there's likely no need for manual intervention anymore 👍🏼

However the increase in RAM is still needed, so I will make a PR to increase to 4GB.

@vhsdream commented on GitHub (Nov 5, 2025): I can confirm that 1.10.1 fixes the migration issue - so there's likely no need for manual intervention anymore 👍🏼 However the increase in RAM is still needed, so I will make a PR to increase to 4GB.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#2244
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?