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

Failing to create LXC with "flock: cannot set up timer" #1196

New Issue
Closed
opened 2026-02-04 23:34:11 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-04 23:34:11 +03:00
Owner
Copy Link

Originally created by @gmontard on GitHub (Jun 30, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Uptime Kuma

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

bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/uptimekuma.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Uptime Kuma requires to create an LXC, when it's trying to create it, it throws a very weird error about a timeout on the lockfile of the template.

🔄 Steps to reproduce the issue.

bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/uptimekuma.sh)"

❌ Paste the full error output (if available).

🧩 Using Advanced Settings on node pve-nas
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: Automatic Login
🆔 Container ID: 114
🏠 Hostname: uptimekuma
💾 Disk Size: 4 GB
🧠 CPU Cores: 1
🛠️ RAM Size: 1024 MiB
🌉 Bridge: vmbr0
📡 IPv4: DHCP
📡 IPv6: SLAAC/AUTO
📡 APT-Cacher IP Address: Default
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: Default
📡 Tags: community-script;analytics;monitoring
🔑 Root SSH Access: no
🗂️ Enable FUSE Support: no
🔍 Verbose Mode: yes
🚀 Creating a Uptime Kuma LXC using the above advanced settings
✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ Cluster is quorate
✔️ LXC Template List Updated
✔️ LXC Template 'debian-12-standard_12.7-1_amd64.tar.zst' is ready to use.
flock: cannot set up timer: Resource temporarily unavailable
✖️ Timeout while waiting for template lock

[ERROR] in line 1096: exit code 0: while executing command bash -c "(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/misc/create_lxc.sh)" ?

🖼️ Additional context (optional).

No response

Originally created by @gmontard on GitHub (Jun 30, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Uptime Kuma ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/uptimekuma.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Uptime Kuma requires to create an LXC, when it's trying to create it, it throws a very weird error about a timeout on the lockfile of the template. ### 🔄 Steps to reproduce the issue. `bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/uptimekuma.sh)"` ### ❌ Paste the full error output (if available). 🧩 Using Advanced Settings on node pve-nas 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: Automatic Login 🆔 Container ID: 114 🏠 Hostname: uptimekuma 💾 Disk Size: 4 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 1024 MiB 🌉 Bridge: vmbr0 📡 IPv4: DHCP 📡 IPv6: SLAAC/AUTO 📡 APT-Cacher IP Address: Default ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;analytics;monitoring 🔑 Root SSH Access: no 🗂️ Enable FUSE Support: no 🔍 Verbose Mode: yes 🚀 Creating a Uptime Kuma LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ✔️ Cluster is quorate ✔️ LXC Template List Updated ✔️ LXC Template 'debian-12-standard_12.7-1_amd64.tar.zst' is ready to use. flock: cannot set up timer: Resource temporarily unavailable ✖️ Timeout while waiting for template lock **[ERROR] in line 1096: exit code 0: while executing command bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/misc/create_lxc.sh)" $?** ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 23:34:11 +03:00
OVERLORD commented 2026-02-04 23:34:23 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 30, 2025):

https://community-scripts.github.io/ProxmoxVE/scripts?id=clean-orphaned-lvm

Try this

@MickLesk commented on GitHub (Jun 30, 2025): https://community-scripts.github.io/ProxmoxVE/scripts?id=clean-orphaned-lvm Try this
OVERLORD commented 2026-02-04 23:34:32 +03:00
Author
Owner
Copy Link

@gmontard commented on GitHub (Jul 1, 2025):

Thanks @MickLesk

Unfortunately it didn't work, btw here is the output of the clean orphaned script

🔍 Scanning for orphaned LVM volumes...

❗ The following orphaned LVM volumes were found:

LV Name                   VG         Size      
------------------------- ---------- ----------

✅ Cleanup process completed!```
@gmontard commented on GitHub (Jul 1, 2025): Thanks @MickLesk Unfortunately it didn't work, btw here is the output of the clean orphaned script ``` 🔍 Scanning for orphaned LVM volumes... ❗ The following orphaned LVM volumes were found: LV Name VG Size ------------------------- ---------- ---------- ✅ Cleanup process completed!```
OVERLORD commented 2026-02-04 23:34:37 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 1, 2025):

lsof /tmp/template.*

rm -f /tmp/template.*

ulimit -n

@MickLesk commented on GitHub (Jul 1, 2025): `lsof /tmp/template.*` `rm -f /tmp/template.*` `ulimit -n`
OVERLORD commented 2026-02-04 23:34:40 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 3, 2025):

can you give feedback? ive prepare an bigger PR for tomorrow and can fix it, if this is the case

@MickLesk commented on GitHub (Jul 3, 2025): can you give feedback? ive prepare an bigger PR for tomorrow and can fix it, if this is the case
OVERLORD commented 2026-02-04 23:34:44 +03:00
Author
Owner
Copy Link

@gmontard commented on GitHub (Jul 3, 2025):

Very weird — but I had to reboot due to a power outage — and now it works...
I'll keep in mind the command above in case it comes back and report here.

Thanks again @MickLesk 🙏

@gmontard commented on GitHub (Jul 3, 2025): Very weird — but I had to reboot due to a power outage — and now it works... I'll keep in mind the command above in case it comes back and report here. Thanks again @MickLesk 🙏
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 bug
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#1196
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?