starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Proxmox Server crashes while executing jotty installation script #2072

New Issue
Closed
opened 2026-02-05 03:39:42 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 03:39:42 +03:00
Owner
Copy Link

Originally created by @n0rrin on GitHub (Nov 25, 2025).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 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?

pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-16-pve)

📝 Provide a clear and concise description of the issue.

I tried three times to install jotty by the helper script.
Everytime the proxmox server crashed and rebooted.
After the reboot the jotty installation seems to be finish but the ui-website does not work "Unabel to connect".
A reboot of the lxc does not help.
Does anyone else have this problem?

🔄 Steps to reproduce the issue.

Just execute the jotty-script in your proxmox node.

❌ Paste the full error output (if available).

Don't know where to get useful logs after a crash.

🖼️ Additional context (optional).

No response

Originally created by @n0rrin on GitHub (Nov 25, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 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 - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-16-pve) ### 📝 Provide a clear and concise description of the issue. I tried three times to install jotty by the helper script. Everytime the proxmox server crashed and rebooted. After the reboot the jotty installation seems to be finish but the ui-website does not work "Unabel to connect". A reboot of the lxc does not help. Does anyone else have this problem? ### 🔄 Steps to reproduce the issue. Just execute the jotty-script in your proxmox node. ### ❌ Paste the full error output (if available). Don't know where to get useful logs after a crash. ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issue label 2026-02-05 03:39:42 +03:00
OVERLORD commented 2026-02-05 03:39:45 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 25, 2025):

The helper script itself only creates an LXC and installs Jotty inside the container. It does not touch any low-level Proxmox node settings (kernel, ZFS, sysctl, etc.), so a full node crash + reboot usually points to an underlying host issue (OOM, storage/driver problem, kernel panic, hardware), not the script itself.

To debug this you really need logs from the Proxmox node, not from the LXC:
On the Proxmox host, right after the reboot, you can run:

journalctl -b-1 -n 200
dmesg -T | tail -n 200

@MickLesk commented on GitHub (Nov 25, 2025): The helper script itself only creates an LXC and installs Jotty **inside** the container. It does not touch any low-level Proxmox node settings (kernel, ZFS, sysctl, etc.), so a *full node crash + reboot* usually points to an underlying host issue (OOM, storage/driver problem, kernel panic, hardware), not the script itself. To debug this you really need logs from the **Proxmox node**, not from the LXC: On the Proxmox host, right after the reboot, you can run: journalctl -b-1 -n 200 dmesg -T | tail -n 200
OVERLORD commented 2026-02-05 03:39:52 +03:00
Author
Owner
Copy Link

@n0rrin commented on GitHub (Nov 27, 2025):

Yes you are right.
This time i chose the other disk of my server to install jotty and everything seems fine.

@n0rrin commented on GitHub (Nov 27, 2025): Yes you are right. This time i chose the other disk of my server to install jotty and everything seems fine.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2072
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?