search

MichaIng / DietPi

Lightweight justice for your single-board computer!
https://dietpi.com/
GNU General Public License v2.0
4.87k stars 496 forks source link

Multiple Issues updating buster to bullseye #5605

Closed ZiggyPi closed 2 years ago

ZiggyPi commented 2 years ago

@MichaIng @Joulinar

Hey Guys,

I recently came back from a vacation and came to the conclusion that setting up a reverse proxy in lighttpd for sonarr, radarr etc. would be a good idea. As i was setting this up and got it to work, i thought to myself "wouldn't it be nice the have Organizr running to have everything nicely accessable". Well that is when the problems started. Organizr website gave the error : Your Composer dependencies require a PHP version ">= 7.4.0". So i did some searching on the internet en installed PHP7.4. And after that everything went belly up.

So i have managed to get some stuff working again after some removes, reinstalls and installs. I have made a matrix of the issues i still have now.

i am running dietpi 8.6.1 (buster), PHP7.3, PHP7.2-fpm, Lighttpd 1.4.53 (ssl)

Hope you guys can help me out with getting everything working again. If you can help me with getting Organizr to work, that would be a great plus.

|   Service  |IP:port Result                |IP/service Result                                              |
-----------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------|
|Sonarr      |Perfect                   |Perfect                                                    |
|Radarr      |Perfect                   |Perfect                                                    |
|Lidarr      |Perfect                   |Perfect                                                    |
|Deluge      |Perfect                   |No Such Resource, No such child resource                                   |
|Jackett     |Perfect                   |Perfect                                                    |
|Plex        |Perfect                   |401 Unauthorized                                               |
|Webmin ssl=1    |Perfect                   |ERROR - DOCUMENT FOLLOWS - This web server is running in SSL mode. Try the URL https://localhost:10000/ instead|
|Webmin ssl=0    |This site can't provide a secure connection   |Basic text, no graphics, after Login : 404 Not Found                               |
|HTPC Manager    |Can't be reached              |Perfect                                                    |
|Dietpi Dashboard|Perfect                   |Blank Page                                                 |
|Ubooquity   |Perfect                   |Basic text, no graphics                                            |
|Ubooquity Admin |Perfect                   |HTTP ERROR 500 - Could not find matching provider (worng URL)                  
|Nextcloud   |-                     |404 Not Found                                                  |
MichaIng commented 2 years ago

Be careful with manually upgrading PHP to a version not natively shipped by the Debian version. The Nextcloud/webserver issues is most likely the result, as the webserver may still be configured to use PHP7.3, it can be however updated.

Every applications behaves different behind a reverse proxy, some are fine with base paths, others not, some request specific headers to be rewritten, others not. Especially Lighttpd seems to not work OOTB with very much applications, Nginx and Apache2 are simpler in that way, based on cases we saw.

Generally, if you need PHP 7.4, I suggest to upgrade your system to Bullseye instead, which has other benefits as well: https://dietpi.com/blog/?p=811

ZiggyPi commented 2 years ago

@MichaIng thanks for your quick reply, as always.

Will updating to bullseye fix the problems i am having now? I am a little hesitant to do a manual install as i have had issues after update in the past. And i rather would wait for a dietpi-update to bullseye

So what are my options if i want to fix things with this buster version? Will doing the following help > dietpi-software uninstall 81 82 and dietpi-software install 78 79? And maybe a reinstall of 114?<

And then i have to setup reverse proxy again for nginx.

If i can get everything to work with my current setup, what would have my preference. I would think a am just missing some php module or some other simple php thing

Joulinar commented 2 years ago

And i rather would wait for a dietpi-update to bullseye

DietPi will never update your system automatically, nor will it be a feature of dietpi-update. Something you need to do yourself. That's why we create the blog post nearly a year ago.

MichaIng commented 2 years ago

wait for a dietpi-update to bullseye

DietPi updates will never do Debian distro upgrades, that will always need to be done manually. EDIT: Ah Joulinar was faster 😄.

The guide includes some reinstalls, including PHP and webservers, which should fix the Nextcloud issue, if my assumption above regarding this is correct.

Everything else as said is a matter of configuring the backend software (e.g. a base path) and the proxy correctly. The distro upgrade won't fix this.

As always, check the logs for the individual services may give a hint why they are failing, respectively not answering requests correctly. And in case those fail behind the proxy only, their documentation pages may contain proxy setup guides. Worth to have a look there. The official individual software docs are always (at least mostly 😉) linked from our software docs: https://dietpi.com/docs/software/

ZiggyPi commented 2 years ago

@MichaIng @Joulinar Thanks for the input. EDIT: i have tried checking logs from lighttpd but no errors there. I am always having trouble locating log files for all the different services

I will try and update to bullseye this week and do what i sad to switch from lighttpd to nginx. And see if that solves al my problems.

I will keep you guys posted

ZiggyPi commented 2 years ago

@MichaIng @Joulinar

I am currently running the guide to update buster to bullseye. I have got some error messages, but nothing that stopped the process untill "apt full-upgrade".

This gives me the following error message.

``` root@DietPi-HTPC:/# apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages ```

EDIT : I tried to fix this by running "sudo apt install gcc-8-base" en this gave me another error

I tried to fix this by running "sudo apt install gcc-8-base" en this gave me another error

``` Errors were encountered while processing: mariadb-common libmariadb3:armhf coturn E: Sub-process /usr/bin/dpkg returned an error code (1) ```

Using "sudo rm -R /var/lib/mysql" and rerunning "sudo apt install gcc-8-base" gave me the following result

``` root@DietPi-HTPC:/# sudo apt install gcc-8-base Reading package lists... Done Building dependency tree Reading state information... Done gcc-8-base is already the newest version (8.4.0-7+rpi1). gcc-8-base set to manually installed. ```

Now trying to rerun "apt full-upgrade"

Okay all went well.... untill the "dietpi-software reinstall" it is reinstall software including PHP7.3-fpm ..... that shouldnt be right als bulleye was update to PHP7.4?

ZiggyPi commented 2 years ago

@MichaIng

I have rerun all the steps in the guide and this is the result But during reinstall it was still reinstalling PHP7.3

root@DietPi-HTPC:~# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

So a lot of stuff that i was used to isnt working any more and some stuff that still isnt working:

what still works :

I cant wrap my head around this as i have followed all the steps

Joulinar commented 2 years ago

did you followed all steps in section 2.2.4? Did you have done following before, as it is quite important to detect the correct OS version Bullseye, e.g. PHP7.4

/boot/dietpi/func/dietpi-obtain_hw_model
. /boot/dietpi/func/dietpi-globals

For SAMBA you might need to install WSDD service https://github.com/MichaIng/DietPi/discussions/5244 to have it visible on a Windows network

ZiggyPi commented 2 years ago

@Joulinar

Yes i followed the steps exactly as they are in the guide. Should i rerun a specific part of the guide to see if that fixes anything?

And for SAMBA...i installed WSDD. Now i can see the RPI and the folders (dietpi and HTPC), but cant access these folders.

EDIT : Distro is still on buster....

root@DietPi-HTPC:~# cat /boot/dietpi/.hw_model
G_HW_MODEL=4
G_HW_MODEL_NAME='RPi 4 Model B (armv7l)'
G_HW_ARCH=2
G_HW_ARCH_NAME='armv7l'
G_HW_CPUID=0
G_HW_CPU_CORES=4
G_DISTRO=5
G_DISTRO_NAME='buster'
G_ROOTFS_DEV='/dev/mmcblk0p2'
G_HW_UUID='b3e885d8-1893-40a5-b4ae-18eb722c81ab'
G_RASPBIAN=1
G_HW_ONBOARD_WIFI=1
G_HW_REVISION='c03112'
G_HW_PCB_REVISION=2
G_HW_MEMORY_SIZE=4096
G_HW_MANUFACTURER='Sony UK'
Joulinar commented 2 years ago

Could you run following

echo $G_DISTRO_NAME
rm /boot/dietpi/.hw_model
/boot/dietpi/func/dietpi-obtain_hw_model
. /boot/dietpi/func/dietpi-globals
cat /boot/dietpi/.hw_model
ZiggyPi commented 2 years ago

so nothing changed

root@DietPi-HTPC:~# echo $G_DISTRO_NAME
buster
root@DietPi-HTPC:~# rm /boot/dietpi/.hw_model
root@DietPi-HTPC:~# /boot/dietpi/func/dietpi-obtain_hw_model
root@DietPi-HTPC:~# . /boot/dietpi/func/dietpi-globals
root@DietPi-HTPC:~# cat /boot/dietpi/.hw_model
G_HW_MODEL=4
G_HW_MODEL_NAME='RPi 4 Model B (armv7l)'
G_HW_ARCH=2
G_HW_ARCH_NAME='armv7l'
G_HW_CPUID=0
G_HW_CPU_CORES=4
G_DISTRO=5
G_DISTRO_NAME='buster'
G_ROOTFS_DEV='/dev/mmcblk0p2'
G_HW_UUID='64c1c99e-b114-42e0-b03b-b44edfcf0ea5'
G_RASPBIAN=1
G_HW_ONBOARD_WIFI=1
G_HW_REVISION='c03112'
G_HW_PCB_REVISION=2
G_HW_MEMORY_SIZE=4096
G_HW_MANUFACTURER='Sony UK'
Joulinar commented 2 years ago

Did you tried to reboot?

ZiggyPi commented 2 years ago

@Joulinar reboot doesn't change a thing

Joulinar commented 2 years ago

Looks like the update did not completed fully. @MichaIng any ideas?

MichaIng commented 2 years ago

What does this show?

cat /etc/debian_version /etc/os-release

I saw some -dev packages causing issues with the upgrade in the path. They are only required for compiling, not for running software, so you can purge them. Any dietpi-software reinstall would reinstall them automatically when required:

G_AGP '*-dev'
apt full-upgrade

Why did you remove /var/lib/mysql? That was a symlink pointing to your database directory, so I'd recreate it:

rm -R /var/lib/mysql # in case there was a directory recreated
ln -s /mnt/dietpi_userdata/mysql /var/lib/mysql
ZiggyPi commented 2 years ago
cat /etc/debian_version /etc/os-release

``` root@DietPi-HTPC:~# cat /etc/debian_version /etc/os-release 10.2 PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" ```

Why did you remove /var/lib/mysql?

I found this on the internet to solve the problem i was having with ggc-8-base

rm -R /var/lib/mysql # in case there was a directory recreated ln -s /mnt/dietpi_userdata/mysql /var/lib/mysql

Okay did this, so that should be fine again

G_AGP '*-dev'

okay did this too

apt full-upgrade

``` root@DietPi-HTPC:~# apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ```

echo $G_DISTRO_NAME

Still returns "buster"

Joulinar commented 2 years ago

let's try to reinstall base files package as there is a mismatch between /etc/debian_version and /etc/os-release

apt install --reinstall base-files
ZiggyPi commented 2 years ago
apt install --reinstall base-files

``` root@DietPi-HTPC:~# apt install --reinstall base-files Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 70.3 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 https://mirror.netcologne.de/raspbian/raspbian bullseye/main armhf base-files armhf 11.1+rpi1+deb11u3 [70.3 kB] Fetched 70.3 kB in 0s (221 kB/s) (Reading database ... 135611 files and directories currently installed.) Preparing to unpack .../base-files_11.1+rpi1+deb11u3_armhf.deb ... Unpacking base-files (11.1+rpi1+deb11u3) over (11.1+rpi1+deb11u3) ... Setting up base-files (11.1+rpi1+deb11u3) ... Processing triggers for install-info (6.7.0.dfsg.2-6) ... ```

results after reboot

``` root@DietPi-HTPC:~# cat /etc/debian_version /etc/os-release 10.2 PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" root@DietPi-HTPC:~# echo $G_DISTRO_NAME buster root@DietPi-HTPC:~# cat /boot/dietpi/.hw_model G_HW_MODEL=4 G_HW_MODEL_NAME='RPi 4 Model B (armv7l)' G_HW_ARCH=2 G_HW_ARCH_NAME='armv7l' G_HW_CPUID=0 G_HW_CPU_CORES=4 G_DISTRO=5 G_DISTRO_NAME='buster' G_ROOTFS_DEV='/dev/mmcblk0p2' G_HW_UUID='233cb82c-0d0a-48ea-b2b4-18ab42d9dbb7' G_RASPBIAN=1 G_HW_ONBOARD_WIFI=1 G_HW_REVISION='c03112' G_HW_PCB_REVISION=2 G_HW_MEMORY_SIZE=4096 G_HW_MANUFACTURER='Sony UK' ```

MichaIng commented 2 years ago

Can you show:

ls -al /etc/debian_release.dpkg-{dist,new}
ZiggyPi commented 2 years ago

@MichaIng

ls -al /etc/debian_release.dpkg-{dist,new}

root@DietPi-HTPC:~# ls -al /etc/debian_release.dpkg-{dist,new} ls: cannot access '/etc/debian_release.dpkg-dist': No such file or directory ls: cannot access '/etc/debian_release.dpkg-new': No such file or directory

MichaIng commented 2 years ago

Okay, no idea why it is not updated, let's do it manually:

echo '11.3' > /etc/debian_version
/boot/dietpi/func/dietpi-obtain_hw_model
. /boot/dietpi/func/dietpi-globals
echo $G_DISTRO_NAME

And then continue/repeat at 2.2.4 from the guide.

ZiggyPi commented 2 years ago

@MichaIng

is this the outcome you expected and is this the outcome to pickup at 2.2.4?

root@DietPi-HTPC:~# echo '11.3' > /etc/debian_release
root@DietPi-HTPC:~# echo '11.3' > /etc/debian_release
root@DietPi-HTPC:~# /boot/dietpi/func/dietpi-obtain_hw_model
root@DietPi-HTPC:~# . /boot/dietpi/func/dietpi-globals
root@DietPi-HTPC:~# echo $G_DISTRO_NAME
buster
MichaIng commented 2 years ago

Ah sorry, my fault, wrong file name (edited it above as well) 😅:

rm /etc/debian_release
echo '11.3' > /etc/debian_version
/boot/dietpi/func/dietpi-obtain_hw_model
. /boot/dietpi/func/dietpi-globals
echo $G_DISTRO_NAME
ZiggyPi commented 2 years ago

@MichaIng

Okay now it's returning "bullseye". Gonna run the guide from 2.2.4 now.

Wish me luck

ZiggyPi commented 2 years ago

@MichaIng Reinstall is still running, but now i can see PHP7.4 lines going down the terminal window, so that's a good sign :+1:

EDIT : Result

root@DietPi-HTPC:~# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
ZiggyPi commented 2 years ago

@MichaIng

Okay so theses issues are still unresolved :

Organizr website is now not returning an error, but is keeps loading (turning loading wheel)

Joulinar commented 2 years ago

can you share following

dietpi-services status

ZiggyPi commented 2 years ago

@Joulinar

dietpi-services status

``` root@DietPi-HTPC:~# dietpi-services status DietPi-Services ───────────────────────────────────────────────────── Mode: status [ OK ] DietPi-Services | nmbd active (running) since Thu 2022-07-07 23:05:27 CEST; 9min ago [ OK ] DietPi-Services | smbd active (running) since Thu 2022-07-07 23:05:27 CEST; 9min ago [ OK ] DietPi-Services | nfs-kernel-server active (exited) since Thu 2022-07-07 23:05:29 CEST; 9min ago [ OK ] DietPi-Services | redis-server active (running) since Thu 2022-07-07 23:05:29 CEST; 9min ago [ OK ] DietPi-Services | mariadb active (running) since Thu 2022-07-07 23:05:30 CEST; 9min ago [ OK ] DietPi-Services | nginx active (running) since Thu 2022-07-07 23:05:31 CEST; 9min ago [ OK ] DietPi-Services | deluged active (running) since Thu 2022-07-07 23:05:31 CEST; 9min ago [ OK ] DietPi-Services | plexmediaserver active (running) since Thu 2022-07-07 23:05:31 CEST; 9min ago [ OK ] DietPi-Services | ubooquity active (running) since Thu 2022-07-07 23:05:31 CEST; 9min ago [ OK ] DietPi-Services | jackett active (running) since Thu 2022-07-07 23:05:31 CEST; 9min ago [ OK ] DietPi-Services | sonarr active (running) since Thu 2022-07-07 23:05:31 CEST; 9min ago [ OK ] DietPi-Services | radarr active (running) since Thu 2022-07-07 23:05:31 CEST; 9min ago [ OK ] DietPi-Services | lidarr active (running) since Thu 2022-07-07 23:05:31 CEST; 9min ago [ INFO ] DietPi-Services | deluge-web inactive (dead) [ OK ] DietPi-Services | rpimonitor active (running) since Thu 2022-07-07 23:05:34 CEST; 9min ago [ OK ] DietPi-Services | webmin active (running) since Thu 2022-07-07 23:05:41 CEST; 9min ago [FAILED] DietPi-Services | ● htpc-manager.service - HTPC Manager (DietPi) Loaded: loaded (/etc/systemd/system/htpc-manager.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2022-07-07 23:05:42 CEST; 9min ago Process: 961 ExecStart=/usr/bin/python3 -OO /mnt/dietpi_userdata/htpc-manager/Htpc.py (code=exited, status=1/FAILURE) Main PID: 961 (code=exited, status=1/FAILURE) CPU: 416ms Jul 07 23:05:42 DietPi-HTPC HTPC Manager[961]: Traceback (most recent call last): Jul 07 23:05:42 DietPi-HTPC HTPC Manager[961]: File "/mnt/dietpi_userdata/htpc-manager/Htpc.py", line 254, in Jul 07 23:05:42 DietPi-HTPC HTPC Manager[961]: main() Jul 07 23:05:42 DietPi-HTPC HTPC Manager[961]: File "/mnt/dietpi_userdata/htpc-manager/Htpc.py", line 172, in main Jul 07 23:05:42 DietPi-HTPC HTPC Manager[961]: from htpc.settings import Settings Jul 07 23:05:42 DietPi-HTPC HTPC Manager[961]: File "/mnt/dietpi_userdata/htpc-manager/htpc/settings.py", line 7, in Jul 07 23:05:42 DietPi-HTPC HTPC Manager[961]: import cherrypy Jul 07 23:05:42 DietPi-HTPC HTPC Manager[961]: ModuleNotFoundError: No module named 'cherrypy' Jul 07 23:05:42 DietPi-HTPC systemd[1]: htpc-manager.service: Main process exited, code=exited, status=1/FAILURE Jul 07 23:05:42 DietPi-HTPC systemd[1]: htpc-manager.service: Failed with result 'exit-code'. [ OK ] DietPi-Services | docker active (running) since Thu 2022-07-07 23:05:41 CEST; 9min ago [ OK ] DietPi-Services | cron active (running) since Thu 2022-07-07 23:05:41 CEST; 9min ago [ OK ] DietPi-Services | dropbear active (running) since Thu 2022-07-07 23:05:24 CEST; 9min ago [ INFO ] DietPi-Services | dietpi-vpn inactive (dead) [ INFO ] DietPi-Services | dietpi-cloudshell inactive (dead) [ OK ] DietPi-Services | dietpi-dashboard active (running) since Thu 2022-07-07 23:05:24 CEST; 9min ago [ INFO ] DietPi-Services | dietpi-ramlog inactive (dead) [ OK ] DietPi-Services | dietpi-preboot active (exited) since Thu 2022-07-07 23:05:24 CEST; 9min ago [ OK ] DietPi-Services | dietpi-postboot active (exited) since Thu 2022-07-07 23:05:24 CEST; 9min ago [ INFO ] DietPi-Services | dietpi-wifi-monitor inactive (dead) ```

MichaIng commented 2 years ago

Ah, HTPC-Manager needs to be reinstalled as well (like most Python software due to Python 3.7 => 3.9 upgrade):

dietpi-software reinstall 155

I added this to our guide.

Joulinar commented 2 years ago

just as of interest let's check ports

ss -tulpn | grep LISTEN
ZiggyPi commented 2 years ago
dietpi-services status after reinstall

``` root@DietPi-HTPC:~# dietpi-services status DietPi-Services ───────────────────────────────────────────────────── Mode: status [ OK ] DietPi-Services | nmbd active (running) since Thu 2022-07-07 23:25:07 CEST; 1min 37s ago [ OK ] DietPi-Services | smbd active (running) since Thu 2022-07-07 23:25:07 CEST; 1min 36s ago [ OK ] DietPi-Services | nfs-kernel-server active (exited) since Thu 2022-07-07 23:25:09 CEST; 1min 35s ago [ OK ] DietPi-Services | redis-server active (running) since Thu 2022-07-07 23:25:09 CEST; 1min 35s ago [ OK ] DietPi-Services | mariadb active (running) since Thu 2022-07-07 23:25:10 CEST; 1min 33s ago [ OK ] DietPi-Services | nginx active (running) since Thu 2022-07-07 23:25:11 CEST; 1min 33s ago [ OK ] DietPi-Services | deluged active (running) since Thu 2022-07-07 23:25:11 CEST; 1min 33s ago [ OK ] DietPi-Services | plexmediaserver active (running) since Thu 2022-07-07 23:25:11 CEST; 1min 33s ago [ OK ] DietPi-Services | ubooquity active (running) since Thu 2022-07-07 23:25:11 CEST; 1min 33s ago [ OK ] DietPi-Services | jackett active (running) since Thu 2022-07-07 23:25:11 CEST; 1min 33s ago [ OK ] DietPi-Services | sonarr active (running) since Thu 2022-07-07 23:25:11 CEST; 1min 33s ago [ OK ] DietPi-Services | radarr active (running) since Thu 2022-07-07 23:25:11 CEST; 1min 33s ago [ OK ] DietPi-Services | lidarr active (running) since Thu 2022-07-07 23:25:11 CEST; 1min 33s ago [ INFO ] DietPi-Services | deluge-web inactive (dead) [ OK ] DietPi-Services | rpimonitor active (running) since Thu 2022-07-07 23:25:13 CEST; 1min 31s ago [ OK ] DietPi-Services | webmin active (running) since Thu 2022-07-07 23:25:18 CEST; 1min 26s ago [ OK ] DietPi-Services | htpc-manager active (running) since Thu 2022-07-07 23:25:18 CEST; 1min 26s ago [ OK ] DietPi-Services | docker active (running) since Thu 2022-07-07 23:25:18 CEST; 1min 26s ago [ OK ] DietPi-Services | cron active (running) since Thu 2022-07-07 23:25:18 CEST; 1min 26s ago [ OK ] DietPi-Services | dropbear active (running) since Thu 2022-07-07 23:05:24 CEST; 21min ago [ INFO ] DietPi-Services | dietpi-vpn inactive (dead) [ INFO ] DietPi-Services | dietpi-cloudshell inactive (dead) [ OK ] DietPi-Services | dietpi-dashboard active (running) since Thu 2022-07-07 23:05:24 CEST; 21min ago [ INFO ] DietPi-Services | dietpi-ramlog inactive (dead) [ OK ] DietPi-Services | dietpi-preboot active (exited) since Thu 2022-07-07 23:05:24 CEST; 21min ago [ OK ] DietPi-Services | dietpi-postboot active (exited) since Thu 2022-07-07 23:05:24 CEST; 21min ago [ INFO ] DietPi-Services | dietpi-wifi-monitor inactive (dead) ```

ss -tulpn | grep LISTEN

``` root@DietPi-HTPC:~# ss -tulpn | grep LISTEN tcp LISTEN 0 64 0.0.0.0:2049 0.0.0.0:* tcp LISTEN 0 4096 0.0.0.0:33347 0.0.0.0:* users:(("rpc.mountd",pid=5868,fd=17)) tcp LISTEN 0 4096 0.0.0.0:60195 0.0.0.0:* users:(("rpc.mountd",pid=5868,fd=13)) tcp LISTEN 0 128 0.0.0.0:5252 0.0.0.0:* users:(("dietpi-dashboar",pid=503,fd=6)) tcp LISTEN 0 5 10.0.0.30%eth0:54405 0.0.0.0:* users:(("deluged",pid=6016,fd=13)) tcp LISTEN 0 5 127.0.0.1%lo:54405 0.0.0.0:* users:(("deluged",pid=6016,fd=11)) tcp LISTEN 0 80 127.0.0.1:3306 0.0.0.0:* users:(("mariadbd",pid=5953,fd=19)) tcp LISTEN 0 511 127.0.0.1:6379 0.0.0.0:* users:(("redis-server",pid=5891,fd=7)) tcp LISTEN 0 50 0.0.0.0:139 0.0.0.0:* users:(("smbd",pid=5852,fd=45)) tcp LISTEN 0 128 127.0.0.1:39341 0.0.0.0:* users:(("Plex Script Hos",pid=6389,fd=4)) tcp LISTEN 0 128 127.0.0.1:44077 0.0.0.0:* users:(("Plex Script Hos",pid=6184,fd=7)) tcp LISTEN 0 5 172.17.0.1:5357 0.0.0.0:* users:(("python3",pid=511,fd=18)) tcp LISTEN 0 5 10.0.0.30:5357 0.0.0.0:* users:(("python3",pid=511,fd=10)) tcp LISTEN 0 4096 0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=287,fd=4),("systemd",pid=1,fd=93)) tcp LISTEN 0 4096 0.0.0.0:10000 0.0.0.0:* users:(("miniserv.pl",pid=6256,fd=5)) tcp LISTEN 0 511 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=6002,fd=5),("nginx",pid=6001,fd=5),("nginx",pid=6000,fd=5),("nginx",pid=5998,fd=5),("nginx",pid=5996,fd=5)) tcp LISTEN 0 1024 127.0.0.1:32401 0.0.0.0:* users:(("Plex Media Serv",pid=6028,fd=57)) tcp LISTEN 0 10 127.0.0.1:8085 0.0.0.0:* users:(("python3",pid=6265,fd=5)) tcp LISTEN 0 64 0.0.0.0:35381 0.0.0.0:* tcp LISTEN 0 1000 0.0.0.0:22 0.0.0.0:* users:(("dropbear",pid=338,fd=4)) tcp LISTEN 0 128 127.0.0.1:32600 0.0.0.0:* users:(("Plex Tuner Serv",pid=6400,fd=10)) tcp LISTEN 0 5 0.0.0.0:8888 0.0.0.0:* users:(("rpimonitord",pid=6214,fd=5)) tcp LISTEN 0 4096 0.0.0.0:33145 0.0.0.0:* users:(("rpc.mountd",pid=5868,fd=9)) tcp LISTEN 0 500 0.0.0.0:8989 0.0.0.0:* users:(("mono",pid=6080,fd=8)) tcp LISTEN 0 50 0.0.0.0:445 0.0.0.0:* users:(("smbd",pid=5852,fd=44)) tcp LISTEN 0 50 0.0.0.0:58846 0.0.0.0:* users:(("deluged",pid=6016,fd=21)) tcp LISTEN 0 64 [::]:2049 [::]:* tcp LISTEN 0 4096 [::]:60769 [::]:* users:(("rpc.mountd",pid=5868,fd=11)) tcp LISTEN 0 512 *:7878 *:* users:(("Radarr",pid=6098,fd=192)) tcp LISTEN 0 511 [::1]:6379 [::]:* users:(("redis-server",pid=5891,fd=8)) tcp LISTEN 0 4096 [::]:46987 [::]:* users:(("rpc.mountd",pid=5868,fd=15)) tcp LISTEN 0 50 [::]:139 [::]:* users:(("smbd",pid=5852,fd=43)) tcp LISTEN 0 4096 [::]:41037 [::]:* users:(("rpc.mountd",pid=5868,fd=19)) tcp LISTEN 0 5 [fe80::dea6:32ff:fe55:2005]%eth0:5357 [::]:* users:(("python3",pid=511,fd=14)) tcp LISTEN 0 512 *:8686 *:* users:(("Lidarr",pid=6112,fd=233)) tcp LISTEN 0 4096 [::]:111 [::]:* users:(("rpcbind",pid=287,fd=6),("systemd",pid=1,fd=95)) tcp LISTEN 0 1024 *:32400 *:* users:(("Plex Media Serv",pid=6028,fd=56)) tcp LISTEN 0 511 [::]:80 [::]:* users:(("nginx",pid=6002,fd=6),("nginx",pid=6001,fd=6),("nginx",pid=6000,fd=6),("nginx",pid=5998,fd=6),("nginx",pid=5996,fd=6)) tcp LISTEN 0 64 [::]:40339 [::]:* tcp LISTEN 0 50 *:2038 *:* users:(("java",pid=6046,fd=52)) tcp LISTEN 0 2 [::1]:3350 [::]:* users:(("xrdp-sesman",pid=515,fd=7)) tcp LISTEN 0 1000 [::]:22 [::]:* users:(("dropbear",pid=338,fd=5)) tcp LISTEN 0 50 *:2039 *:* users:(("java",pid=6046,fd=44)) tcp LISTEN 0 512 *:9117 *:* users:(("jackett",pid=6076,fd=206)) tcp LISTEN 0 2 *:3389 *:* users:(("xrdp",pid=530,fd=11)) tcp LISTEN 0 50 [::]:445 [::]:* users:(("smbd",pid=5852,fd=42)) ```

EDIT : Still can't reach HTPC Manager

Joulinar commented 2 years ago

could you do a reboot and check following afterwards

journalctl -u deluged

ZiggyPi commented 2 years ago
journalctl -u deluged

``` root@DietPi-HTPC:~# journalctl -u deluged -- Journal begins at Thu 2022-07-07 23:17:02 CEST, ends at Thu 2022-07-07 23:35:01 CEST. -- Jul 07 23:20:20 DietPi-HTPC systemd[1]: Stopping Deluge Daemon (DietPi)... Jul 07 23:20:20 DietPi-HTPC systemd[1]: deluged.service: Succeeded. Jul 07 23:20:20 DietPi-HTPC systemd[1]: Stopped Deluge Daemon (DietPi). Jul 07 23:20:20 DietPi-HTPC systemd[1]: deluged.service: Consumed 2.198s CPU time. Jul 07 23:25:11 DietPi-HTPC systemd[1]: Started Deluge Daemon (DietPi). root@DietPi-HTPC:~# ```

MichaIng commented 2 years ago

The Deluge web frontent is somehow nut running:

systemctl start deluge-web
ZiggyPi commented 2 years ago

systemctl start deluge-web

This didn't help

journalctl -u deluged-web

``` root@DietPi-HTPC:~# journalctl -u deluge-web -- Journal begins at Thu 2022-07-07 23:17:02 CEST, ends at Thu 2022-07-07 23:37:13 CEST. -- Jul 07 23:25:11 DietPi-HTPC systemd[1]: Started Deluge Web UI (DietPi). Jul 07 23:25:15 DietPi-HTPC systemd[1]: deluge-web.service: Succeeded. Jul 07 23:25:15 DietPi-HTPC systemd[1]: deluge-web.service: Consumed 1.643s CPU time. Jul 07 23:37:12 DietPi-HTPC systemd[1]: Started Deluge Web UI (DietPi). Jul 07 23:37:13 DietPi-HTPC systemd[1]: deluge-web.service: Succeeded. Jul 07 23:37:13 DietPi-HTPC systemd[1]: deluge-web.service: Consumed 1.089s CPU time. root@DietPi-HTPC:~# ```

MichaIng commented 2 years ago

Ah, Deluge also needs to be reinstalled

sed -i '/^ExecStart=/s/deluge-web$/deluge-web -d/' /etc/systemd/system/deluge-web.service
systemctl daemon-reload
systemctl restart deluge-web
ZiggyPi commented 2 years ago 
root@DietPi-HTPC:~# sed -i '/^ExecStart=/deluge-web$/deluge-web -d/' /etc/systemd/system/deluge-web.service
sed: -e expression #1, char 15: extra characters after command

@MichaIng If you want i can share a teamviewer link with you, if that makes things easier

MichaIng commented 2 years ago 
sed -i '/^ExecStart=/s/deluge-web$/deluge-web -d/' /etc/systemd/system/deluge-web.service
systemctl daemon-reload
systemctl restart deluge-web
ZiggyPi commented 2 years ago

@MichaIng Okay deluge is working again :+1:

MichaIng commented 2 years ago

There seems to be no PHP FPM server. Did you reinstall PHP to have PHP7.4?

dietpi-software reinstall 85 89

And check HTPC Manager logs:

journalctl -u htpc-manager
ZiggyPi commented 2 years ago

I haven't reinstalled PHP, i though that was part of the guide (something that would be update automatically)

I ran the dietpi-software reinstall 85 89 command. (Organizr and Nextcloud get 502 bad gateway)

journalctl -u htpc-manager

``` root@DietPi-HTPC:~# journalctl -u htpc-manager -- Journal begins at Fri 2022-07-08 00:17:03 CEST, ends at Fri 2022-07-08 00:20:01 CEST. -- Jul 08 00:17:30 DietPi-HTPC systemd[1]: Stopping HTPC Manager (DietPi)... Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: 2022-07-08 00:17:30 :: cherrypy.error :: INFO :: [08/Jul/2022:00:17:30] ENGINE Caught signal SIGTERM. Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: 2022-07-08 00:17:30 :: cherrypy.error :: INFO :: [08/Jul/2022:00:17:30] ENGINE Bus STOPPING Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: 2022-07-08 00:17:30 :: apscheduler.scheduler :: INFO :: Scheduler has been shut down Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: 2022-07-08 00:17:30 :: cherrypy.error :: ERROR :: [08/Jul/2022:00:17:30] ENGINE Error in 'stop' listener > Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: Traceback (most recent call last): Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: File "/usr/local/lib/python3.9/dist-packages/cherrypy/process/wspbus.py", line 216, in publish Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: output.append(listener(*args, **kwargs)) Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: File "/usr/local/lib/python3.9/dist-packages/cherrypy/process/servers.py", line 264, in stop Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: self.httpserver.stop() Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: File "/usr/local/lib/python3.9/dist-packages/cherrypy/wsgiserver/__init__.py", line 2221, in stop Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: self.requests.stop(self.shutdown_timeout) Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: File "/usr/local/lib/python3.9/dist-packages/cherrypy/wsgiserver/__init__.py", line 1702, in stop Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: if worker is not current and worker.isAlive(): Jul 08 00:17:30 DietPi-HTPC HTPC Manager[6265]: AttributeError: 'WorkerThread' object has no attribute 'isAlive' Jul 08 00:17:30 DietPi-HTPC systemd[1]: htpc-manager.service: Main process exited, code=exited, status=70/SOFTWARE Jul 08 00:17:30 DietPi-HTPC systemd[1]: htpc-manager.service: Failed with result 'exit-code'. Jul 08 00:17:30 DietPi-HTPC systemd[1]: Stopped HTPC Manager (DietPi). Jul 08 00:17:30 DietPi-HTPC systemd[1]: htpc-manager.service: Consumed 12.095s CPU time. Jul 08 00:19:20 DietPi-HTPC systemd[1]: Started HTPC Manager (DietPi). Jul 08 00:19:25 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:25 :: root :: INFO :: Welcome to the Python 3 port of Hellowlol's HTPC Manager fork Jul 08 00:19:25 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:25 :: root :: INFO :: Loglevel set to info Jul 08 00:19:25 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:25 :: htpc.updater :: INFO :: Using GitUpdater engine Jul 08 00:19:25 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:25 :: apscheduler.scheduler :: INFO :: Added job "Updater.update_needed" to job store "default" Jul 08 00:19:25 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:25 :: modules.kodi :: WARNING :: No configured kodi-Servers. Jul 08 00:19:25 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:25 :: modules.newznab :: WARNING :: No configured Indexers. Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:26 :: htpc.server :: INFO :: Starting up webserver Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: ******************************************************************* Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: Starting HTPC Manager on port 8085. Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: Start your browser and go to http://localhost:8085/HTPC Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: ******************************************************************* Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:26 :: cherrypy.error :: INFO :: [08/Jul/2022:00:19:26] ENGINE Listening for SIGTERM. Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:26 :: cherrypy.error :: INFO :: [08/Jul/2022:00:19:26] ENGINE Listening for SIGHUP. Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:26 :: cherrypy.error :: INFO :: [08/Jul/2022:00:19:26] ENGINE Listening for SIGUSR1. Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:26 :: cherrypy.error :: INFO :: [08/Jul/2022:00:19:26] ENGINE Bus STARTING Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:26 :: cherrypy.error :: INFO :: [08/Jul/2022:00:19:26] ENGINE Serving on http://127.0.0.1:8085 Jul 08 00:19:26 DietPi-HTPC HTPC Manager[16328]: 2022-07-08 00:19:26 :: cherrypy.error :: INFO :: [08/Jul/2022:00:19:26] ENGINE Bus STARTED ```

MichaIng commented 2 years ago

Please update the cherrypy module:

pip3 install -U cherrypy
systemctl restart htpc-manager

I forgot that you setup a proxy, I hope the reinstall did not broke the Nginx proxy config somehow.

ZiggyPi commented 2 years ago

pip3 install -U cherrypy systemctl restart htpc-manager

This didn't fix the problem with HTPC-Manager

And the proxy i had setup was with Lighttpd, but i uninstalled that, and switched to Nginx. Still have to setup the proxy and ssl if everything works again.

Joulinar commented 2 years ago

yep because at the moment HTPC-Manager is listen to localhost only. Means, its reachable from the system itself. But not from local network

INFO :: [08/Jul/2022:00:19:26] ENGINE Serving on http://127.0.0.1:8085

and for NextCloud, I guess the web server configuration is missing as it was not installed for nginx but for lighttpd

ZiggyPi commented 2 years ago

Okay but i didnt change anything in the htpc-manager itself for the proxy.

And i have reinstalled nextcloud after i switched to nginx

MichaIng commented 2 years ago

Hmm it would have made much sense to change the HTPC host to 127.0.0.1 in case of a local proxy. The default is 0.0.0.0 and can be set via database only. I'll check how to change it manually with sqlite this evening.

About Nextcloud, is the database symlink now correct?

readlink -f /var/lib/mysql
ZiggyPi commented 2 years ago 
root@DietPi-HTPC:~# readlink -f /var/lib/mysql
/mnt/dietpi_userdata/mysql
MichaIng commented 2 years ago

Do webserver or PHP logs say something?

journalctl -u nginx -u php7.4-fpm
cat /var/log/nginx/error.log /var/log/php7.4-fpm.log
ZiggyPi commented 2 years ago 
root@DietPi-HTPC:~# journalctl -u nginx -u php7.4-fpm
-- Journal begins at Fri 2022-07-08 07:17:02 CEST, ends at Fri 2022-07-08 07:54:10 CEST. --
-- No entries --
root@DietPi-HTPC:~# cat /var/log/nginx/error.log /var/log/php7.4-fpm.log
root@DietPi-HTPC:~#
ZiggyPi commented 2 years ago

Got a new issue too

sonarr log file, download paused after complete in deluge

``` 2022-07-08` 07:21:06.0|Warn|ImportApprovedEpisodes|Couldn't import episode /HTPC/Downloads/Complete/The.Boys.S03E08.1080p.WEB.H264-GLHF[rarbg]/the.boys.s03e08.1080p.web.h264-glhf.mkv [v3.0.8.1507] System.UnauthorizedAccessException: Access to the path '/HTPC/Downloads/Complete/The.Boys.S03E08.1080p.WEB.H264-GLHF[rarbg]/the.boys.s03e08.1080p.web.h264-glhf.mkv' is denied. ---> System.IO.IOException: Permission denied --- End of inner exception stack trace --- at System.IO.FileSystem.DeleteFile (System.String fullPath) [0x0006d] in :0 at System.IO.File.Delete (System.String path) [0x00014] in :0 at NzbDrone.Mono.Disk.DiskProvider.TransferFilePatched (System.String source, System.String destination, System.Boolean overwrite, System.Boolean move) [0x00291] in <2da24ae1fe6e4b0189edfb4791d8f9a5>:0 at NzbDrone.Mono.Disk.DiskProvider.MoveFileInternal (System.String source, System.String destination) [0x00098] in <2da24ae1fe6e4b0189edfb4791d8f9a5>:0 at NzbDrone.Common.Disk.DiskProviderBase.MoveFile (System.String source, System.String destination, System.Boolean overwrite) [0x000e1] in :0 at NzbDrone.Common.Disk.DiskTransferService.TryMoveFileVerified (System.String sourcePath, System.String targetPath, System.Int64 originalSize) [0x00047] in :0 at NzbDrone.Common.Disk.DiskTransferService.TransferFile (System.String sourcePath, System.String targetPath, NzbDrone.Common.Disk.TransferMode mode, System.Boolean overwrite) [0x004b9] in :0 at NzbDrone.Core.MediaFiles.EpisodeFileMovingService.TransferFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Tv.Series series, System.Collections.Generic.List`1[T] episodes, System.String destinationFilePath, NzbDrone.Common.Disk.TransferMode mode) [0x00129] in :0 at NzbDrone.Core.MediaFiles.EpisodeFileMovingService.MoveEpisodeFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Parser.Model.LocalEpisode localEpisode) [0x00054] in :0 at NzbDrone.Core.MediaFiles.UpgradeMediaFileService.UpgradeEpisodeFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Parser.Model.LocalEpisode localEpisode, System.Boolean copyOnly) [0x001b0] in :0 at NzbDrone.Core.MediaFiles.EpisodeImport.ImportApprovedEpisodes.Import (System.Collections.Generic.List`1[T] decisions, System.Boolean newDownload, NzbDrone.Core.Download.DownloadClientItem downloadClientItem, NzbDrone.Core.MediaFiles.EpisodeImport.ImportMode importMode) [0x0029b] in :0 2022-07-08 07:29:45.9|Info|RssSyncService|Starting RSS Sync 2022-07-08 07:29:57.8|Info|DownloadDecisionMaker|Processing 380 releases 2022-07-08 07:30:03.9|Info|RssSyncService|RSS Sync Completed. Reports found: 380, Reports grabbed: 0 2022-07-08 07:31:55.9|Warn|ImportApprovedEpisodes|Couldn't import episode /HTPC/Downloads/Complete/The.Boys.S03E08.1080p.WEB.H264-GLHF[rarbg]/the.boys.s03e08.1080p.web.h264-glhf.mkv [v3.0.8.1507] System.UnauthorizedAccessException: Access to the path '/HTPC/Downloads/Complete/The.Boys.S03E08.1080p.WEB.H264-GLHF[rarbg]/the.boys.s03e08.1080p.web.h264-glhf.mkv' is denied. ---> System.IO.IOException: Permission denied --- End of inner exception stack trace --- at System.IO.FileSystem.DeleteFile (System.String fullPath) [0x0006d] in :0 at System.IO.File.Delete (System.String path) [0x00014] in :0 at NzbDrone.Mono.Disk.DiskProvider.TransferFilePatched (System.String source, System.String destination, System.Boolean overwrite, System.Boolean move) [0x00291] in <2da24ae1fe6e4b0189edfb4791d8f9a5>:0 at NzbDrone.Mono.Disk.DiskProvider.MoveFileInternal (System.String source, System.String destination) [0x00098] in <2da24ae1fe6e4b0189edfb4791d8f9a5>:0 at NzbDrone.Common.Disk.DiskProviderBase.MoveFile (System.String source, System.String destination, System.Boolean overwrite) [0x000e1] in :0 at NzbDrone.Common.Disk.DiskTransferService.TryMoveFileVerified (System.String sourcePath, System.String targetPath, System.Int64 originalSize) [0x00047] in :0 at NzbDrone.Common.Disk.DiskTransferService.TransferFile (System.String sourcePath, System.String targetPath, NzbDrone.Common.Disk.TransferMode mode, System.Boolean overwrite) [0x004b9] in :0 at NzbDrone.Core.MediaFiles.EpisodeFileMovingService.TransferFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Tv.Series series, System.Collections.Generic.List`1[T] episodes, System.String destinationFilePath, NzbDrone.Common.Disk.TransferMode mode) [0x00129] in :0 at NzbDrone.Core.MediaFiles.EpisodeFileMovingService.MoveEpisodeFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Parser.Model.LocalEpisode localEpisode) [0x00054] in :0 at NzbDrone.Core.MediaFiles.UpgradeMediaFileService.UpgradeEpisodeFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Parser.Model.LocalEpisode localEpisode, System.Boolean copyOnly) [0x001b0] in :0 at NzbDrone.Core.MediaFiles.EpisodeImport.ImportApprovedEpisodes.Import (System.Collections.Generic.List`1[T] decisions, System.Boolean newDownload, NzbDrone.Core.Download.DownloadClientItem downloadClientItem, NzbDrone.Core.MediaFiles.EpisodeImport.ImportMode importMode) [0x0029b] in :0 2022-07-08 07:45:16.5|Info|RssSyncService|Starting RSS Sync 2022-07-08 07:45:20.1|Info|DownloadDecisionMaker|Processing 380 releases 2022-07-08 07:45:25.6|Info|RssSyncService|RSS Sync Completed. Reports found: 380, Reports grabbed: 0 2022-07-08 07:48:59.7|Warn|ImportApprovedEpisodes|Couldn't import episode /HTPC/Downloads/Complete/The.Boys.S03E08.1080p.WEB.H264-GLHF[rarbg]/the.boys.s03e08.1080p.web.h264-glhf.mkv [v3.0.8.1507] System.UnauthorizedAccessException: Access to the path '/HTPC/Downloads/Complete/The.Boys.S03E08.1080p.WEB.H264-GLHF[rarbg]/the.boys.s03e08.1080p.web.h264-glhf.mkv' is denied. ---> System.IO.IOException: Permission denied --- End of inner exception stack trace --- at System.IO.FileSystem.DeleteFile (System.String fullPath) [0x0006d] in :0 at System.IO.File.Delete (System.String path) [0x00014] in :0 at NzbDrone.Mono.Disk.DiskProvider.TransferFilePatched (System.String source, System.String destination, System.Boolean overwrite, System.Boolean move) [0x00291] in <2da24ae1fe6e4b0189edfb4791d8f9a5>:0 at NzbDrone.Mono.Disk.DiskProvider.MoveFileInternal (System.String source, System.String destination) [0x00098] in <2da24ae1fe6e4b0189edfb4791d8f9a5>:0 at NzbDrone.Common.Disk.DiskProviderBase.MoveFile (System.String source, System.String destination, System.Boolean overwrite) [0x000e1] in :0 at NzbDrone.Common.Disk.DiskTransferService.TryMoveFileVerified (System.String sourcePath, System.String targetPath, System.Int64 originalSize) [0x00047] in :0 at NzbDrone.Common.Disk.DiskTransferService.TransferFile (System.String sourcePath, System.String targetPath, NzbDrone.Common.Disk.TransferMode mode, System.Boolean overwrite) [0x004b9] in :0 at NzbDrone.Core.MediaFiles.EpisodeFileMovingService.TransferFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Tv.Series series, System.Collections.Generic.List`1[T] episodes, System.String destinationFilePath, NzbDrone.Common.Disk.TransferMode mode) [0x00129] in :0 at NzbDrone.Core.MediaFiles.EpisodeFileMovingService.MoveEpisodeFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Parser.Model.LocalEpisode localEpisode) [0x00054] in :0 at NzbDrone.Core.MediaFiles.UpgradeMediaFileService.UpgradeEpisodeFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Parser.Model.LocalEpisode localEpisode, System.Boolean copyOnly) [0x001b0] in :0 at NzbDrone.Core.MediaFiles.EpisodeImport.ImportApprovedEpisodes.Import (System.Collections.Generic.List`1[T] decisions, System.Boolean newDownload, NzbDrone.Core.Download.DownloadClientItem downloadClientItem, NzbDrone.Core.MediaFiles.EpisodeImport.ImportMode importMode) [0x0029b] in :0 ```