Closed ZiggyPi closed 3 years ago
MichaIng
commented
3 years ago coturn.service: Failed to determine user credentials: No such process
This seems to happen when the user does not exist. Let's see if a reinstall restores it:
apt install --reinstall coturn
systemctl restart coturn
sleep 1
journalctl -u coturn
ZiggyPi
commented
3 years ago @MichaIng
I am still seeing the same error
Joulinar
commented
3 years ago Nope you need to look to the time stamp. The one from Apr 08 21:20:57 seems to be fine
ZiggyPi
commented
3 years ago @Joulinar
Okay nice. So 3 down 5 to go? 🙈
MichaIng
commented
3 years ago Ubooquity and Lidarr as well fail because of their users missing. A reinstall should be easiest here:
dietpi-software reinstall 80 106That might fix Sonarr as well as it says something about updating Mono runtime, which is included in the Lidarr reinstall.
For XRDP we should create fresh logs then:
systemctl restart xrdp
sleep 1
journalctl -u xrdp@MichaIng
Will i loose my sonarr and radarr data if i do a reinstall?
MichaIng
commented
3 years ago Nope, all data and config is preserved, only the install/program files/binaries are updates.
ZiggyPi
commented
3 years ago @MichaIng
MichaIng
commented
3 years ago So far so good. Lets see which ones are working now and how the XRDP logs say:
dietpi-servives status
journalctl -u xrdpsomehow NextCloud is still failing and stuck in maintenance mode. Maybe a reboot would be good to see what is missing still and if everything is surviving 😃
ZiggyPi
commented
3 years ago @MichaIng
I will also do a reboot
MichaIng
commented
3 years ago So somehow many service users have gone, same for XRDP and likely Sonarr:
apt install --reinstall nzbdrone xrdp
usermod -aG redis www-data # this probably fixes Nextcloud
journalctl -u lighttpd -u lidarr@MichaIng
Joulinar
commented
3 years ago hmm there seems to be something running on port 80 (http) already
Apr 08 23:32:34 DietPi-HTPC lighttpd[1578]: 2021-04-08 23:32:33: (network.c.313) can't bind to socket: 0.0.0.0:80 Address already in us
pls can you have a look ss -tulpn | grep LISTEN
ZiggyPi
commented
3 years ago @Joulinar
Joulinar
commented
3 years ago you have installed Nginx along with Lighttpd. Means it's 2 web server now. This of course is not going to work.
tcp LISTEN 0 128 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=1389,fd=5),("nginx",pid=1387,fd=5),("nginx",pid=1386,fd=5),("nginx",pid=1385,fd=5),("nginx",pid=1384,fd=5))
any particular reason for this?
ZiggyPi
commented
3 years ago @Joulinar I installed ngix brcaise i founda tutorial on setting up reverse proxy for htpc manager so i could reach sonarr and radarr from outside the network. But never got it to work so i stopped trying.
Joulinar
commented
3 years ago well you would need to decide what to do with NextCloud, keep it with Lighttpd or reinstall on Nginx. If you like to continue with Lighttpd, you would need to change port away from http 80 to 81. Otherwise Lighttpd will not start. You are not able to run Nginx and Lighttpd on same port 80.
ZiggyPi
commented
3 years ago @Joulinar Okay i am not using nginx now. Maybe in the future.so how would i go about changing the port?
MichaIng
commented
3 years ago Also Lighttpd can be used add proxy, or Sonarr/Radarr can be directly accessed when forwarding their port from the router. But let's fix all services locally first.
If you don't use Nginx currently, I suggest to purge it, so no port changes are required:
apt purge nginx
apt autopurgeThere is still this issue with Mono runtime on Sonarr and Lidarr. Let's see if reinstalling it helps:
apt install --reinstall mono-runtime
# Ah and probably a full upgrade is required to get the latest version
apt full-upgrade
systemctl restart sonarr lidarr
sleep 3
journalctl -u sonarr -u lidarr@MichaIng
MichaIng
commented
3 years ago I think there are multiple mono versions installed, as the runtime package is current v6 already while Lidarr and Sonarr are grabbing a v4.5 library file somehow. Can you please show:
which -a mono
dpkg -l | grep mono
dpkg -S /usr/lib/mono/4.5/mscorlib.dll@MichaIng
MichaIng
commented
3 years ago Hmm, while the package name and path looks like 4.5, the package version is 6.X. Does reinstalling it help?
apt install --reinstall libmono-corlib4.5-cil
systemctl restart sonarr
sleep 1
journalctl -u sonarr@MichaIng
Joulinar
commented
3 years ago @MichaIng Not sure if this is something that could help https://github.com/mono/mono/issues/12578
MichaIng
commented
3 years ago Hmm, the error seems very application specific and in some cases I found a simple clean reinstall of Mono. Let's see if that helps:
dietpi-software uninstall 150
apt-mark auto $(dpkg --get-selections 'libmono-*' 'mono-*' | mawk '{print $1}')
apt autopurge
dietpi-software install 150@ZiggyPi If you like, I can do some remote desktop support, which should speed things up, and I'm interested in this case as Sonarr, Radarr and Lidarr migration/verification is part of next DietPi release and compatibility with current Mono should hence be assured. Does XRDP work again, or do you have a VNC server installed as well, so that you would be able to follow what I'm doing?
systemctl status xrdp vncserver@MichaIng
Remote support is okay with me. I think i jave remote desktop but i never used it. May you can give me instructions to change the password. Because i saved the password to auto login and im afraid i dont remember the password. And instructions how to give you access. The only way i have been logging in is via juicyssh app on android and putty on windows.
MichaIng
commented
3 years ago I think Sonarr blocked the autoremoval of Mono and this library mismatch broke even complete APT install now...
I see a VNC server is running, which is fine. But it runs on an own virtual desktop, which cannot be easily shared by two users. Most transparent for you would be:
# Switch to shared desktop mode
G_CONFIG_INJECT 'SOFTWARE_VNCSERVER_SHARE_DESKTOP=' 'SOFTWARE_VNCSERVER_SHARE_DESKTOP=1' /boot/dietpi.txt
# Create a strong true random password
tr -dc '[:alnum:]' < /dev/random | head -c32; echo
# Apply that password for the VNC server
vncpasswd
# Restart the VNC server service to have the change take effect
systemctl restart vncserver
# Start a desktop session, once ready
startxVNC runs on port 5901, so you'd need to forward this from your router. At best send me that password along with our public IP/domain via PM in our forum, that is safer than email 😄: https://dietpi.com/phpbb/ucp.php?i=pm&mode=compose&u=3157
Ah, and add a date/time when it would fit for you, so you can watch what I'm doing on your local screen.
ZiggyPi
commented
3 years ago @MichaIng
Sorry to say there was another hickup
And a date and time partly depends on the time differenxe. I'm from The Netherlands, you?
ravenclaw900
commented
3 years ago I think that for a desktop to work, you have to have an HDMI cable plugged in to the device. Is there one?
Joulinar
commented
3 years ago Better to have a look to /var/log/Xorg.0.log
ZiggyPi
commented
3 years ago @ravenclaw900 no it's a headless setup
@Joulinar
root@DietPi-HTPC:~# /var/log/Xorg.0.log
-bash: /var/log/Xorg.0.log: Permission deniedIt is not a file to execute. Try cat /var/log/Xorg.0.log 😉
MichaIng
commented
3 years ago Ah okay, with a headless setup no X server can be started directly. Hmm, I actually never tested it two users can connect to the same virtual desktop session. Let's try that:
G_CONFIG_INJECT 'SOFTWARE_VNCSERVER_SHARE_DESKTOP=' 'SOFTWARE_VNCSERVER_SHARE_DESKTOP=0' /boot/dietpi.txt
systemctl restart vncserver
sleep 5
htop # should show an "Xtigervnc :1" process now, hit "q" to exitNow you should be able to connect via any VNC viewer. Here the most simple standalone executable for Windows: https://www.tightvnc.com/download/1.3.10/tightvnc-1.3.10_x86_viewer.zip
Type in the Pi's LAN IP + :1 (e.g. 192.168.1.2:1) and hit "Connect". Then enter the password you set previously. I hope then that I'm able to connect to the very same session via public <IP/hostname>:1.
Joulinar
commented
3 years ago You could you Team Viewer as well to look to same windows desktop
MichaIng
commented
3 years ago But TeamViewer also needs to be executed from a local desktop, doesn't it? As no screen is attached, we need a purely virtual X server session.
Joulinar
commented
3 years ago I mean to connect from Windows to Windows desktop and than use PuTTY. No need for X server and port forwarding
MichaIng
commented
3 years ago Ah yes that would be an option as well, actually the simpler and saver one 👍. Here the link for TeamViewer: https://www.teamviewer.com/download/windows/ Run it on your Windows, share your ID and password with me (per mail or better forum PM) and start on SSH session. So I can remote control your Pi through your desktop PC. Theoretically Windows remote desktop would work the same way, but AFAIK TeamViewer has the safer protocol. No need to create a TeamViewer account btw.
ZiggyPi
commented
3 years ago @MichaIng
I just send you a PM on the DietPi forum
If you can tell me what time fits best for you, i will make sure i'm at my computer
MichaIng
commented
3 years ago We finally fixed the issues, which was not trivial:
php -v and mariadb -V showed a different version than the package.@ZiggyPi Btw, to setup an HTPC Manager proxy with Lighttpd proxy, try the following:
lighty-enable-mod proxy
cat << 'EOF' > /etc/lighttpd/conf-available/99-htpc.conf
$HTTP["url"] =~ "^/htpc" {
proxy.server = ( "" => ( ( "host" => "127.0.0.1", "port" => 6789 ) ) )
proxy.header = ( "map-urlpath" => ( "/htpc" => "" ) )
}
EOF
lighty-enable-mod htpc
systemctl restart lighttpdWell done @MichaIng 👍
MichaIng
commented
3 years ago I mark this issue as closed. In case, for Lighttpd proxy, please open a new issue.
Details:
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Any idea how i can resolve this. I dont really need the update. But i was hoping it would fix jackett. But now i can get the terminal up but nothing else is working. No access to sonarr, radarr or other webservices and no acceas to samba.
Additional logs: