Bazarr is not reachable on Dietpi anymore (does not start?)

Troubleshooting
1

Required Information

  • DietPi version 9.0.2 - Native PC

Additional Information (if applicable)

  • Software title | Bazarr
  • Software was installed and it worked. now after powering up my server again, everything works except Bazarr. its not reachable under :6767
  • i swapt my media HDD, and pointed within sonarr/radarr to my my media HDD. could reach these *arrs without an issue
root@DietPi:~# dietpi-software install 180
[  OK  ] DietPi-Software | Initialised database
[  OK  ] DietPi-Software | Reading database

 DietPi-Software
─────────────────────────────────────────────────────
 Mode: Automated install

[ INFO ] DietPi-Software | 180: Bazarr is already installed
[ INFO ] DietPi-Software | Use "dietpi-software reinstall 180" to force rerun of installation and configuration steps for Bazarr.
[  OK  ] DietPi-Software | No changes applied for: Bazarr

and

root@DietPi:~# systemctl restart bazarr
root@DietPi:~#

image

service seems to run and all looks good.

my question is to how do I “re-install” it without loosing my Bazarr configuration.

2

can you check following

ss -tulpn | grep LISTEN
journalctl -u bazarr.service
systemctl status bazarr.service

dietpi-software reinstall 180
3

It’s even in the output of the failed install attempt:

1 Like
4

for the first comment, the output is to long for here. so I pasted it here:

https://pastecode.io/s/yxk8fqwk

it seems that’s an issue with the media HDD which I swapped.

therefore de-installed bazarr via dietpi-launcher, and installed it fresh again. then rebooted my server.

gonna start fresh

5

I guess you are using different mount point for the new HDD leading to the issue. But you would need to use old mount point to fix this.

Can you share

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
6

i have already deleted Bazarr and re-installed it. so now I can configure it again with the correct media HDD. thanks though for your help.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.