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 13 Packages Projects Releases 10 Wiki Activity

Technitium Update Script - technitium.service not found. #2214

New Issue
Closed
opened 2026-02-05 04:14:06 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-05 04:14:06 +03:00
Owner
Copy Link

Originally created by @kevdogg on GitHub (Dec 23, 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?

Technitium

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/technitiumdns.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/9.1.2/9d436f37a0ac4172 (running kernel: 6.5.13-5-pve)

📝 Provide a clear and concise description of the issue.

So I'm updating the technitium dns server from the LXC container itself. The original technitium script used to install a service called dns.service at /etc/systemd/system. This service file is still located within this directory. I noticed however when I run the updated scripts within the technitium LXC container (bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/technitiumdns.sh)"), it tries to start a service called technitium.service. I looked at the source of the script at it has a command to cp /opt/technitium/dns/systemd.service /etc/systemd/system/technitium.service. For some reason when running this upgrade script, I don't get any technitium.service installed and it doesn't exist in the filesystem. If I manually restart dns.service the service will restart.

🔄 Steps to reproduce the issue.

see above

❌ Paste the full error output (if available).

see above

🖼️ Additional context (optional).

no other info.

Originally created by @kevdogg on GitHub (Dec 23, 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? Technitium ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/technitiumdns.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/9.1.2/9d436f37a0ac4172 (running kernel: 6.5.13-5-pve) ### 📝 Provide a clear and concise description of the issue. So I'm updating the technitium dns server from the LXC container itself. The original technitium script used to install a service called dns.service at /etc/systemd/system. This service file is still located within this directory. I noticed however when I run the updated scripts within the technitium LXC container (bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/technitiumdns.sh)"), it tries to start a service called technitium.service. I looked at the source of the script at it has a command to cp /opt/technitium/dns/systemd.service /etc/systemd/system/technitium.service. For some reason when running this upgrade script, I don't get any technitium.service installed and it doesn't exist in the filesystem. If I manually restart dns.service the service will restart. ### 🔄 Steps to reproduce the issue. see above ### ❌ Paste the full error output (if available). see above ### 🖼️ Additional context (optional). no other info.
OVERLORD added the bug label 2026-02-05 04:14:06 +03:00
OVERLORD commented 2026-02-05 04:14:12 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Dec 23, 2025):

You have a old installation, and you already answered your own question/problem
rename the dns.service to technitium.service and you're done

@tremor021 commented on GitHub (Dec 23, 2025): You have a old installation, and you already answered your own question/problem rename the `dns.service` to `technitium.service` and you're done
OVERLORD commented 2026-02-05 04:14:20 +03:00
Author
Owner
Copy Link

@kevdogg commented on GitHub (Dec 23, 2025):

Hey thanks for reply but I didn't answer my own question. The install script or update script is supposed to install technitium.service but it didn't. I'm not sure if that's a feature or a bug.

@kevdogg commented on GitHub (Dec 23, 2025): Hey thanks for reply but I didn't answer my own question. The install script or update script is supposed to install technitium.service but it didn't. I'm not sure if that's a feature or a bug.
OVERLORD commented 2026-02-05 04:14:24 +03:00
Author
Owner
Copy Link

@GoldenSpringness commented on GitHub (Dec 23, 2025):

Hey thanks for reply but I didn't answer my own question. The install script or update script is supposed to install technitium.service but it didn't. I'm not sure if that's a feature or a bug.

the new service is not created as update _script only restarts a created technitium.service. ill suggest manually changing the name of the file to tenitium.service as suggested above, it shouldn't happen again.

@GoldenSpringness commented on GitHub (Dec 23, 2025): > Hey thanks for reply but I didn't answer my own question. The install script or update script is supposed to install technitium.service but it didn't. I'm not sure if that's a feature or a bug. the new service is not created as update _script only restarts a created technitium.service. ill suggest manually changing the name of the file to tenitium.service as suggested above, it shouldn't happen again.
OVERLORD commented 2026-02-05 04:14:28 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Dec 23, 2025):

Fresh install:

Image Image

Service is there

@tremor021 commented on GitHub (Dec 23, 2025): Fresh install: <img width="840" height="695" alt="Image" src="https://github.com/user-attachments/assets/a6913e4e-d87a-483c-9727-f64e3f1b6cc7" /> <img width="631" height="204" alt="Image" src="https://github.com/user-attachments/assets/fd727cf8-f3c6-499c-8d46-e8db2afde845" /> Service is there
OVERLORD commented 2026-02-05 04:14:30 +03:00
Author
Owner
Copy Link

@djr747 commented on GitHub (Dec 24, 2025):

This issue was not completely fixed for me. Post file move operation the new technitium.service was not enabled. Manually enabling resolved. Only happened on one of my LXC upgrades both done at the same time today.

root@dns-server1:~# systemctl list-units --type=service
  UNIT                               LOAD   ACTIVE SUB     DESCRIPTION               >
  console-getty.service              loaded active running Console Getty
  container-getty@1.service          loaded active running Container Getty on /dev/tt>
  container-getty@2.service          loaded active running Container Getty on /dev/tt>
  cron.service                       loaded active running Regular background program>
  dbus.service                       loaded active running D-Bus System Message Bus
  ifupdown-pre.service               loaded active exited  Helper to synchronize boot>
  ifupdown-wait-online.service       loaded active exited  Wait for network to be con>
  networking.service                 loaded active exited  Raise network interfaces
  nftables.service                   loaded active exited  nftables
  postfix.service                    loaded active exited  Postfix Mail Transport Age>
  postfix@-.service                  loaded active running Postfix Mail Transport Age>
  ssh.service                        loaded active running OpenBSD Secure Shell server
  systemd-journal-flush.service      loaded active exited  Flush Journal to Persisten>
  systemd-journald.service           loaded active running Journal Service
  systemd-logind.service             loaded active running User Login Management
  systemd-modules-load.service       loaded active exited  Load Kernel Modules
  systemd-network-generator.service  loaded active exited  Generate network units fro>
  systemd-networkd.service           loaded active running Network Configuration
  systemd-remount-fs.service         loaded active exited  Remount Root and Kernel Fi>
  systemd-sysctl.service             loaded active exited  Apply Kernel Variables
  systemd-sysusers.service           loaded active exited  Create System Users
  systemd-tmpfiles-setup-dev.service loaded active exited  Create Static Device Nodes>
  systemd-tmpfiles-setup.service     loaded active exited  Create System Files and Di>
  systemd-update-utmp.service        loaded active exited  Record System Boot/Shutdow>
  systemd-user-sessions.service      loaded active exited  Permit User Sessions
  unattended-upgrades.service        loaded active running Unattended Upgrades Shutdo>

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
26 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

root@dns-server1:~# ls /etc/systemd/system/
ctrl-alt-del.target                     sysinit.target.wants
dbus-org.freedesktop.timesync1.service  sys-kernel-config.mount
getty.target.wants                      sys-kernel-debug.mount
multi-user.target.wants                 systemd-journald-audit.socket
network-online.target.wants             technitium.service
sockets.target.wants                    timers.target.wants
sshd.service
root@dns-server1:~# systemctl daemon-reload
root@dns-server1:~# systemctl list-units --type=service
  UNIT                               LOAD   ACTIVE SUB     DESCRIPTION               >
  console-getty.service              loaded active running Console Getty
  container-getty@1.service          loaded active running Container Getty on /dev/tt>
  container-getty@2.service          loaded active running Container Getty on /dev/tt>
  cron.service                       loaded active running Regular background program>
  dbus.service                       loaded active running D-Bus System Message Bus
  ifupdown-pre.service               loaded active exited  Helper to synchronize boot>
  ifupdown-wait-online.service       loaded active exited  Wait for network to be con>
  networking.service                 loaded active exited  Raise network interfaces
  nftables.service                   loaded active exited  nftables
  postfix.service                    loaded active exited  Postfix Mail Transport Age>
  postfix@-.service                  loaded active running Postfix Mail Transport Age>
  ssh.service                        loaded active running OpenBSD Secure Shell server
  systemd-journal-flush.service      loaded active exited  Flush Journal to Persisten>
  systemd-journald.service           loaded active running Journal Service
  systemd-logind.service             loaded active running User Login Management
  systemd-modules-load.service       loaded active exited  Load Kernel Modules
  systemd-network-generator.service  loaded active exited  Generate network units fro>
  systemd-networkd.service           loaded active running Network Configuration
  systemd-remount-fs.service         loaded active exited  Remount Root and Kernel Fi>
  systemd-sysctl.service             loaded active exited  Apply Kernel Variables
  systemd-sysusers.service           loaded active exited  Create System Users
  systemd-tmpfiles-setup-dev.service loaded active exited  Create Static Device Nodes>
  systemd-tmpfiles-setup.service     loaded active exited  Create System Files and Di>
  systemd-update-utmp.service        loaded active exited  Record System Boot/Shutdow>
  systemd-user-sessions.service      loaded active exited  Permit User Sessions
  unattended-upgrades.service        loaded active running Unattended Upgrades Shutdo>

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
26 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

root@dns-server1:~# systemctl enable technitium.service
Created symlink /etc/systemd/system/multi-user.target.wants/technitium.service → /etc/systemd/system/technitium.service.
root@dns-server1:~# systemctl start technitium.service
root@dns-server1:~# systemctl list-units --type=service
  UNIT                               LOAD   ACTIVE SUB     DESCRIPTION               >
  console-getty.service              loaded active running Console Getty
  container-getty@1.service          loaded active running Container Getty on /dev/tt>
  container-getty@2.service          loaded active running Container Getty on /dev/tt>
  cron.service                       loaded active running Regular background program>
  dbus.service                       loaded active running D-Bus System Message Bus
  ifupdown-pre.service               loaded active exited  Helper to synchronize boot>
  ifupdown-wait-online.service       loaded active exited  Wait for network to be con>
  networking.service                 loaded active exited  Raise network interfaces
  nftables.service                   loaded active exited  nftables
  postfix.service                    loaded active exited  Postfix Mail Transport Age>
  postfix@-.service                  loaded active running Postfix Mail Transport Age>
  ssh.service                        loaded active running OpenBSD Secure Shell server
  systemd-journal-flush.service      loaded active exited  Flush Journal to Persisten>
  systemd-journald.service           loaded active running Journal Service
  systemd-logind.service             loaded active running User Login Management
  systemd-modules-load.service       loaded active exited  Load Kernel Modules
  systemd-network-generator.service  loaded active exited  Generate network units fro>
  systemd-networkd.service           loaded active running Network Configuration
  systemd-remount-fs.service         loaded active exited  Remount Root and Kernel Fi>
  systemd-sysctl.service             loaded active exited  Apply Kernel Variables
  systemd-sysusers.service           loaded active exited  Create System Users
  systemd-tmpfiles-setup-dev.service loaded active exited  Create Static Device Nodes>
  systemd-tmpfiles-setup.service     loaded active exited  Create System Files and Di>
  systemd-update-utmp.service        loaded active exited  Record System Boot/Shutdow>
  systemd-user-sessions.service      loaded active exited  Permit User Sessions
  technitium.service                 loaded active running Technitium DNS Server
  unattended-upgrades.service        loaded active running Unattended Upgrades Shutdo>

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
27 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
lines 14-34/34 (END)
@djr747 commented on GitHub (Dec 24, 2025): This issue was not completely fixed for me. Post file move operation the new `technitium.service` was not enabled. Manually enabling resolved. Only happened on one of my LXC upgrades both done at the same time today. ``` root@dns-server1:~# systemctl list-units --type=service UNIT LOAD ACTIVE SUB DESCRIPTION > console-getty.service loaded active running Console Getty container-getty@1.service loaded active running Container Getty on /dev/tt> container-getty@2.service loaded active running Container Getty on /dev/tt> cron.service loaded active running Regular background program> dbus.service loaded active running D-Bus System Message Bus ifupdown-pre.service loaded active exited Helper to synchronize boot> ifupdown-wait-online.service loaded active exited Wait for network to be con> networking.service loaded active exited Raise network interfaces nftables.service loaded active exited nftables postfix.service loaded active exited Postfix Mail Transport Age> postfix@-.service loaded active running Postfix Mail Transport Age> ssh.service loaded active running OpenBSD Secure Shell server systemd-journal-flush.service loaded active exited Flush Journal to Persisten> systemd-journald.service loaded active running Journal Service systemd-logind.service loaded active running User Login Management systemd-modules-load.service loaded active exited Load Kernel Modules systemd-network-generator.service loaded active exited Generate network units fro> systemd-networkd.service loaded active running Network Configuration systemd-remount-fs.service loaded active exited Remount Root and Kernel Fi> systemd-sysctl.service loaded active exited Apply Kernel Variables systemd-sysusers.service loaded active exited Create System Users systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes> systemd-tmpfiles-setup.service loaded active exited Create System Files and Di> systemd-update-utmp.service loaded active exited Record System Boot/Shutdow> systemd-user-sessions.service loaded active exited Permit User Sessions unattended-upgrades.service loaded active running Unattended Upgrades Shutdo> LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 26 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. root@dns-server1:~# ls /etc/systemd/system/ ctrl-alt-del.target sysinit.target.wants dbus-org.freedesktop.timesync1.service sys-kernel-config.mount getty.target.wants sys-kernel-debug.mount multi-user.target.wants systemd-journald-audit.socket network-online.target.wants technitium.service sockets.target.wants timers.target.wants sshd.service root@dns-server1:~# systemctl daemon-reload root@dns-server1:~# systemctl list-units --type=service UNIT LOAD ACTIVE SUB DESCRIPTION > console-getty.service loaded active running Console Getty container-getty@1.service loaded active running Container Getty on /dev/tt> container-getty@2.service loaded active running Container Getty on /dev/tt> cron.service loaded active running Regular background program> dbus.service loaded active running D-Bus System Message Bus ifupdown-pre.service loaded active exited Helper to synchronize boot> ifupdown-wait-online.service loaded active exited Wait for network to be con> networking.service loaded active exited Raise network interfaces nftables.service loaded active exited nftables postfix.service loaded active exited Postfix Mail Transport Age> postfix@-.service loaded active running Postfix Mail Transport Age> ssh.service loaded active running OpenBSD Secure Shell server systemd-journal-flush.service loaded active exited Flush Journal to Persisten> systemd-journald.service loaded active running Journal Service systemd-logind.service loaded active running User Login Management systemd-modules-load.service loaded active exited Load Kernel Modules systemd-network-generator.service loaded active exited Generate network units fro> systemd-networkd.service loaded active running Network Configuration systemd-remount-fs.service loaded active exited Remount Root and Kernel Fi> systemd-sysctl.service loaded active exited Apply Kernel Variables systemd-sysusers.service loaded active exited Create System Users systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes> systemd-tmpfiles-setup.service loaded active exited Create System Files and Di> systemd-update-utmp.service loaded active exited Record System Boot/Shutdow> systemd-user-sessions.service loaded active exited Permit User Sessions unattended-upgrades.service loaded active running Unattended Upgrades Shutdo> LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 26 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. root@dns-server1:~# systemctl enable technitium.service Created symlink /etc/systemd/system/multi-user.target.wants/technitium.service → /etc/systemd/system/technitium.service. root@dns-server1:~# systemctl start technitium.service root@dns-server1:~# systemctl list-units --type=service UNIT LOAD ACTIVE SUB DESCRIPTION > console-getty.service loaded active running Console Getty container-getty@1.service loaded active running Container Getty on /dev/tt> container-getty@2.service loaded active running Container Getty on /dev/tt> cron.service loaded active running Regular background program> dbus.service loaded active running D-Bus System Message Bus ifupdown-pre.service loaded active exited Helper to synchronize boot> ifupdown-wait-online.service loaded active exited Wait for network to be con> networking.service loaded active exited Raise network interfaces nftables.service loaded active exited nftables postfix.service loaded active exited Postfix Mail Transport Age> postfix@-.service loaded active running Postfix Mail Transport Age> ssh.service loaded active running OpenBSD Secure Shell server systemd-journal-flush.service loaded active exited Flush Journal to Persisten> systemd-journald.service loaded active running Journal Service systemd-logind.service loaded active running User Login Management systemd-modules-load.service loaded active exited Load Kernel Modules systemd-network-generator.service loaded active exited Generate network units fro> systemd-networkd.service loaded active running Network Configuration systemd-remount-fs.service loaded active exited Remount Root and Kernel Fi> systemd-sysctl.service loaded active exited Apply Kernel Variables systemd-sysusers.service loaded active exited Create System Users systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes> systemd-tmpfiles-setup.service loaded active exited Create System Files and Di> systemd-update-utmp.service loaded active exited Record System Boot/Shutdow> systemd-user-sessions.service loaded active exited Permit User Sessions technitium.service loaded active running Technitium DNS Server unattended-upgrades.service loaded active running Unattended Upgrades Shutdo> LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 27 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. lines 14-34/34 (END)
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#2214
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?