[ERROR] in line 930: exit code 0: while executing command timezone=$(cat /etc/timezone) #1684

Closed
opened 2026-02-05 01:57:10 +03:00 by OVERLORD · 9 comments
Owner

Originally created by @madIlama on GitHub (Sep 27, 2025).

Have you read and understood the above guidelines?

yes

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

komodo

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📈 Which Proxmox version are you on?

pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-2-pve)

📝 Provide a clear and concise description of the issue.

cat: /etc/timezone: No such file or directory

[ERROR] in line 930: exit code 0: while executing command timezone=$(cat /etc/timezone)

seems falling at build.func,930

  NEXTID=$(pvesh get /cluster/nextid)
  timezone=$(cat /etc/timezone)
  header_info
  while true; do

🔄 Steps to reproduce the issue.

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

Paste the full error output (if available).

cat: /etc/timezone: No such file or directory

[ERROR] in line 930: exit code 0: while executing command timezone=$(cat /etc/timezone)

🖼️ Additional context (optional).

No response

Originally created by @madIlama on GitHub (Sep 27, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? komodo ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-komodo.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📈 Which Proxmox version are you on? pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-2-pve) ### 📝 Provide a clear and concise description of the issue. cat: /etc/timezone: No such file or directory [ERROR] in line 930: exit code 0: while executing command timezone=$(cat /etc/timezone) seems falling at build.func,930 ``` NEXTID=$(pvesh get /cluster/nextid) timezone=$(cat /etc/timezone) header_info while true; do ``` ### 🔄 Steps to reproduce the issue. bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-komodo.sh)" ### ❌ Paste the full error output (if available). cat: /etc/timezone: No such file or directory [ERROR] in line 930: exit code 0: while executing command timezone=$(cat /etc/timezone) ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 01:57:10 +03:00
Author
Owner

@MickLesk commented on GitHub (Sep 27, 2025):

https://github.com/community-scripts/ProxmoxVE/issues/7904

This is largely the same answer, only for tz.
Why your system doesn't have a time zone is up to you. Check your host.

@MickLesk commented on GitHub (Sep 27, 2025): https://github.com/community-scripts/ProxmoxVE/issues/7904 This is largely the same answer, only for tz. Why your system doesn't have a time zone is up to you. Check your host.
Author
Owner

@rayjaymor85 commented on GitHub (Sep 27, 2025):

I had the same issue, I just fired off timedatectl and then copied and pasted the Timezone line (minus the brackets) into nano /etc/timezone

So for example my output for timedatectl was

Local time: Sat 2025-09-27 16:40:50 AEST
Universal time: Sat 2025-09-27 06:40:50 UTC
RTC time: Sat 2025-09-27 06:40:51
Time zone: Australia/Melbourne (AEST, +1000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

I just made a file called /etc/timezone with Australia/Melbourne

No idea why the host doesn't create it properly, my guess is something changed in Proxmox 9 as I had no trouble installing the same container I found this issue on a few weeks ago on my old host.

@rayjaymor85 commented on GitHub (Sep 27, 2025): I had the same issue, I just fired off `timedatectl` and then copied and pasted the Timezone line (minus the brackets) into `nano /etc/timezone` So for example my output for timedatectl was > Local time: Sat 2025-09-27 16:40:50 AEST > Universal time: Sat 2025-09-27 06:40:50 UTC > RTC time: Sat 2025-09-27 06:40:51 > Time zone: **Australia/Melbourne** (AEST, +1000) > System clock synchronized: yes > NTP service: active > RTC in local TZ: no I just made a file called /etc/timezone with `Australia/Melbourne` No idea why the host doesn't create it properly, my guess is something changed in Proxmox 9 as I had no trouble installing the same container I found this issue on a few weeks ago on my old host.
Author
Owner

@deutrino commented on GitHub (Oct 27, 2025):

This was also a problem attempting to install alpine-adguard on a relatively recent Proxmox 9.0.11 install.

Edit:

/etc/timezone appears to have been removed in Debian 13 (or earlier?)

See also:

@deutrino commented on GitHub (Oct 27, 2025): This was also a problem attempting to install `alpine-adguard` on a relatively recent Proxmox 9.0.11 install. Edit: `/etc/timezone` appears to have been removed in Debian 13 (or earlier?) See also: * https://github.com/MichaIng/DietPi/issues/6482 * https://web.archive.org/web/20250510235704/https://tracker.debian.org/news/1424576/accepted-systemd-2526-1-source-into-unstable/
Author
Owner

@namadori commented on GitHub (Nov 20, 2025):

Same error here on a clean install of Proxmox 9.1 trying to setup Proxmox Datacenter Manager. @tremor021 I think this should not be closed.

[ERROR] in line 930: exit code 0: while executing command timezone=$(cat /etc/timezone)

@namadori commented on GitHub (Nov 20, 2025): Same error here on a clean install of Proxmox 9.1 trying to setup Proxmox Datacenter Manager. @tremor021 I think this should not be closed. `[ERROR] in line 930: exit code 0: while executing command timezone=$(cat /etc/timezone)`
Author
Owner

@moodyblue commented on GitHub (Nov 22, 2025):

@tremor021 @MickLesk this is a problem that should be addressed. Several other scripts suffer from this, such as mariadb and glpi. My suggestion is to modify the pve post install script to to create the /etc/timezone file required by several install scripts (or else identify and modify such scripts).

@moodyblue commented on GitHub (Nov 22, 2025): @tremor021 @MickLesk this is a problem that should be addressed. Several other scripts suffer from this, such as mariadb and glpi. My suggestion is to modify the pve post install script to to create the /etc/timezone file required by several install scripts (or else identify and modify such scripts).
Author
Owner

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

Why should we create an Timezone? Whats Happen If i create an static utc, but the Guy lives in India? Its an User fault.

@MickLesk commented on GitHub (Nov 22, 2025): Why should we create an Timezone? Whats Happen If i create an static utc, but the Guy lives in India? Its an User fault.
Author
Owner

@namadori commented on GitHub (Nov 22, 2025):

Why should we create an Timezone? Whats Happen If i create an static utc, but the Guy lives in India? Its an User fault.

The timezone file is not created because with Trixie is obsolete. See https://git.gsi.de/chef/cookbooks/sys/-/issues/54
It's not a user's duty to create a file that's obsolete, scripts must be updated to use timedatectl show --value --property=Timezone instead.

@namadori commented on GitHub (Nov 22, 2025): > Why should we create an Timezone? Whats Happen If i create an static utc, but the Guy lives in India? Its an User fault. The timezone file is not created because with Trixie is obsolete. See https://git.gsi.de/chef/cookbooks/sys/-/issues/54 It's not a user's duty to create a file that's obsolete, scripts must be updated to use `timedatectl show --value --property=Timezone` instead.
Author
Owner

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

The timezone will be generated by Proxmox Setup. If i spend time, i create an new VM and See -> timezone is available.

If you are other opinion, make an functional PR in ProxmoxVED, the complete core is different to live.

Edit: an affected user Tell me, that the VED core Work smooth.

@MickLesk commented on GitHub (Nov 22, 2025): The timezone will be generated by Proxmox Setup. If i spend time, i create an new VM and See -> timezone is available. If you are other opinion, make an functional PR in ProxmoxVED, the complete core is different to live. Edit: an affected user Tell me, that the VED core Work smooth.
Author
Owner

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

you can try it in 5-10min in live, ive hotfixed it, because the proxmox guys drunk. 9.0.17 (latest 9.0) work fine (as VM), but 9.1.x not. (VM)

@MickLesk commented on GitHub (Nov 22, 2025): you can try it in 5-10min in live, ive hotfixed it, because the proxmox guys drunk. 9.0.17 (latest 9.0) work fine (as VM), but 9.1.x not. (VM)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1684