starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 01:06:06 +03:00

[GH-ISSUE #11173] Tautulli update doesn't work #2387

New issue

Closed

opened 2026-02-26 12:52:17 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 12:52:17 +03:00

Owner

Originally created by @jnsn on GitHub (Jan 25, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11173

Originally assigned to: @vhsdream on GitHub.

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

Tautulli

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

update

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.4-2-pve)

📝 Provide a clear and concise description of the issue.

When trying to update Tautulli to the latest version, the virtual environment seems to be removed and cannot be re-activated resulting in an update error.

I believe this is the same issue as fixed in this paperless-ai PR: https://github.com/community-scripts/ProxmoxVE/pull/9987

🔄 Steps to reproduce the issue.

$ update

❌ Paste the full error output (if available).

Updating Tautullienvironment: line 39 /opt/tautulli/venv/bin/activate: No such file or directory

🖼️ Additional context (optional).

I saw in the paperless PR that also the data folder is now backed up. Tautulli has a .db file, my data folder seems to be empty. I'm not sure these are now properly backed up and restored if the entire folder is removed and re-created.

Originally created by @jnsn on GitHub (Jan 25, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11173 Originally assigned to: @vhsdream on GitHub. ### ✅ 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? Tautulli ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.4-2-pve) ### 📝 Provide a clear and concise description of the issue. When trying to update Tautulli to the latest version, the virtual environment seems to be removed and cannot be re-activated resulting in an update error. I believe this is the same issue as fixed in this paperless-ai PR: https://github.com/community-scripts/ProxmoxVE/pull/9987 ### 🔄 Steps to reproduce the issue. `$ update` ### ❌ Paste the full error output (if available). Updating Tautullienvironment: line 39 /opt/tautulli/venv/bin/activate: No such file or directory ### 🖼️ Additional context (optional). I saw in the paperless PR that also the data folder is now backed up. Tautulli has a .db file, my data folder seems to be empty. I'm not sure these are now properly backed up and restored if the entire folder is removed and re-created.

kerem

2026-02-26 12:52:17 +03:00

closed this issue
added the
bug

bugfix
labels

kerem commented

2026-02-26 12:52:17 +03:00

Author

Owner

@vhsdream commented on GitHub (Jan 25, 2026):

Hey @jnsn - I don't run Tautulli, can you tell me where your db file was located, so I can ensure it's preserved during updates? And if the db location is typically configurable (for example in the config.ini file), please let me know that as well.

@vhsdream commented on GitHub (Jan 25, 2026): Hey @jnsn - I don't run Tautulli, can you tell me where your db file was located, so I can ensure it's preserved during updates? And if the db location is typically configurable (for example in the `config.ini` file), please let me know that as well.

kerem commented

2026-02-26 12:52:17 +03:00

Author

Owner

@jnsn commented on GitHub (Jan 25, 2026):

Hey @jnsn - I don't run Tautulli, can you tell me where your db file was located, so I can ensure it's preserved during updates? And if the db location is typically configurable (for example in the config.ini file), please let me know that as well.

By default it seems to be inside the Tautulli folder itself:

root@tautulli:~# ls -la /opt/Tautulli/
total 937
drwxr-xr-x 16 root root      34 Jan 25 16:44 .
drwxr-xr-x  3 root root       3 Aug  9 20:50 ..
-rw-r--r--  1 root root     144 Aug  9 20:51 API.md
drwxr-xr-x  2 root root      22 Jan 25 16:44 backups
drwxr-xr-x  4 root root       7 Sep  9 06:42 cache
-rw-r--r--  1 root root  121450 Sep 12 22:19 CHANGELOG.md
-rw-r--r--  1 root root    4570 Jan 25 16:44 config.ini
drwxr-xr-x  2 root root       5 Aug  9 20:51 contrib
-rw-r--r--  1 root root    1539 Aug  9 20:51 CONTRIBUTING.md
drwxr-xr-x  3 root root       3 Aug  9 20:51 data
-rw-r--r--  1 root root     637 Aug  9 20:51 Dockerfile
-rw-r--r--  1 root root      97 Aug  9 20:51 .dockerignore
drwxr-xr-x  2 root root       2 Aug  9 20:51 exports
drwxr-xr-x  8 root root      15 Sep 12 22:19 .git
drwxr-xr-x  4 root root       9 Aug  9 20:51 .github
-rw-r--r--  1 root root    1085 Aug  9 20:51 .gitignore
drwxr-xr-x  2 root root       6 Aug  9 20:51 init-scripts
drwxr-xr-x 68 root root      78 Sep 12 22:19 lib
-rw-r--r--  1 root root   35147 Aug  9 20:51 LICENSE
drwxr-xr-x  2 root root      11 Jan 23 08:59 logs
drwxr-xr-x  2 root root       2 Aug  9 20:51 newsletters
drwxr-xr-x  4 root root       8 Aug  9 20:51 package
drwxr-xr-x  3 root root      43 Sep 12 22:19 plexpy
-rwxr-xr-x  1 root root     812 Aug  9 20:51 PlexPy.py
-rw-r--r--  1 root root    9251 Aug  9 20:51 pylintrc
-rw-r--r--  1 root root   12075 Aug  9 20:51 README.md
-rw-r--r--  1 root root       7 Jan 25 10:44 release.lock
-rw-r--r--  1 root root    1063 Sep 12 22:19 requirements.txt
drwxr-xr-x  2 root root       3 Aug  9 20:51 snap
-rwxr-xr-x  1 root root      25 Aug  9 20:51 start.bat
-rwxr-xr-x  1 root root    1007 Aug  9 20:51 start.sh
-rw-r--r--  1 root root 5332992 Jan 25 13:39 tautulli.db
-rwxr-xr-x  1 root root   11797 Aug  9 20:51 Tautulli.py
-rw-r--r--  1 root root      40 Jan 25 10:44 version.lock

I guess that's also because the working directory is set to /opt/Tautulli in the LXC install script: github.com/community-scripts/ProxmoxVE@2a234829b8/install/tautulli-install.sh (L40)

I've also got some information displayed in Tautulli itself:

Info	Value
Git Branch:	master
Git Commit Hash:	cc0150a1b2b745980467003a73aa1be51c1e426a
Configuration File:	/opt/Tautulli/config.ini
Database File:	/opt/Tautulli/tautulli.db
Log File:	/opt/Tautulli/logs/tautulli.log
Backup Directory:	/opt/Tautulli/backups
Cache Directory:	/opt/Tautulli/cache
Export Directory:	/opt/Tautulli/exports
Newsletter Directory:	/opt/Tautulli/newsletters
Platform:	Linux 6.17.4-2-pve (#1 SMP PREEMPT_DYNAMIC PMX 6.17.4-2 (2025-12-19T07:49Z) - Debian GNU/Linux 12 bookworm)
System Timezone:	Europe/Brussels (UTC+0100)
System Language:	en_US
Python Version:	3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0]
SQLite Version:	3.40.1

It doesn't look like the database path or file is set explicitly in the config.ini, and I don't see an entry that might hold this value to be overwritten.

It should be possible somehow, as the lxs.io Docker container has it somewhere else, but I guess they don't use the systemd service.

In the official documentation there is a parameter to specify the data directory, my guess is it's taking that as the root to move everything else too: github.com/Tautulli/Tautulli@cc0150a1b2/init-scripts/init.systemd (L55)

@jnsn commented on GitHub (Jan 25, 2026): > Hey [@jnsn](https://github.com/jnsn) - I don't run Tautulli, can you tell me where your db file was located, so I can ensure it's preserved during updates? And if the db location is typically configurable (for example in the `config.ini` file), please let me know that as well. By default it seems to be inside the Tautulli folder itself: ```bash root@tautulli:~# ls -la /opt/Tautulli/ total 937 drwxr-xr-x 16 root root 34 Jan 25 16:44 . drwxr-xr-x 3 root root 3 Aug 9 20:50 .. -rw-r--r-- 1 root root 144 Aug 9 20:51 API.md drwxr-xr-x 2 root root 22 Jan 25 16:44 backups drwxr-xr-x 4 root root 7 Sep 9 06:42 cache -rw-r--r-- 1 root root 121450 Sep 12 22:19 CHANGELOG.md -rw-r--r-- 1 root root 4570 Jan 25 16:44 config.ini drwxr-xr-x 2 root root 5 Aug 9 20:51 contrib -rw-r--r-- 1 root root 1539 Aug 9 20:51 CONTRIBUTING.md drwxr-xr-x 3 root root 3 Aug 9 20:51 data -rw-r--r-- 1 root root 637 Aug 9 20:51 Dockerfile -rw-r--r-- 1 root root 97 Aug 9 20:51 .dockerignore drwxr-xr-x 2 root root 2 Aug 9 20:51 exports drwxr-xr-x 8 root root 15 Sep 12 22:19 .git drwxr-xr-x 4 root root 9 Aug 9 20:51 .github -rw-r--r-- 1 root root 1085 Aug 9 20:51 .gitignore drwxr-xr-x 2 root root 6 Aug 9 20:51 init-scripts drwxr-xr-x 68 root root 78 Sep 12 22:19 lib -rw-r--r-- 1 root root 35147 Aug 9 20:51 LICENSE drwxr-xr-x 2 root root 11 Jan 23 08:59 logs drwxr-xr-x 2 root root 2 Aug 9 20:51 newsletters drwxr-xr-x 4 root root 8 Aug 9 20:51 package drwxr-xr-x 3 root root 43 Sep 12 22:19 plexpy -rwxr-xr-x 1 root root 812 Aug 9 20:51 PlexPy.py -rw-r--r-- 1 root root 9251 Aug 9 20:51 pylintrc -rw-r--r-- 1 root root 12075 Aug 9 20:51 README.md -rw-r--r-- 1 root root 7 Jan 25 10:44 release.lock -rw-r--r-- 1 root root 1063 Sep 12 22:19 requirements.txt drwxr-xr-x 2 root root 3 Aug 9 20:51 snap -rwxr-xr-x 1 root root 25 Aug 9 20:51 start.bat -rwxr-xr-x 1 root root 1007 Aug 9 20:51 start.sh -rw-r--r-- 1 root root 5332992 Jan 25 13:39 tautulli.db -rwxr-xr-x 1 root root 11797 Aug 9 20:51 Tautulli.py -rw-r--r-- 1 root root 40 Jan 25 10:44 version.lock ``` I guess that's also because the working directory is set to `/opt/Tautulli` in the LXC install script: https://github.com/community-scripts/ProxmoxVE/blob/2a234829b8c0f0e3811a0161a7e369f75cc29724/install/tautulli-install.sh#L40 I've also got some information displayed in Tautulli itself: | Info | Value | | ------------- | ------------- | | Git Branch: | master | | Git Commit Hash: | cc0150a1b2b745980467003a73aa1be51c1e426a | | Configuration File: | /opt/Tautulli/config.ini | | Database File: | /opt/Tautulli/tautulli.db | | Log File: | /opt/Tautulli/logs/tautulli.log | | Backup Directory: | /opt/Tautulli/backups | | Cache Directory: | /opt/Tautulli/cache | | Export Directory: | /opt/Tautulli/exports | | Newsletter Directory: | /opt/Tautulli/newsletters | | Platform: | Linux 6.17.4-2-pve (#1 SMP PREEMPT_DYNAMIC PMX 6.17.4-2 (2025-12-19T07:49Z) - Debian GNU/Linux 12 bookworm) | | System Timezone: | Europe/Brussels (UTC+0100) | | System Language: | en_US | | Python Version: | 3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0] | | SQLite Version: | 3.40.1 | It doesn't look like the database path or file is set explicitly in the config.ini, and I don't see an entry that might hold this value to be overwritten. It should be possible somehow, as the lxs.io Docker container has it somewhere else, but I guess they don't use the systemd service. In the official documentation there is a parameter to specify the data directory, my guess is it's taking that as the root to move everything else too: https://github.com/Tautulli/Tautulli/blob/cc0150a1b2b745980467003a73aa1be51c1e426a/init-scripts/init.systemd#L55

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2387

No description provided.

Rows
Columns