Process Killed all the Time? #127
-
|
Hello together, My Environment:
OK, this old Radio is still not working, but that is a topic to discuss later ;-) I used @TheBossME 's bash Script for installing. Worked perfect so far, as sudo was not installed i removed the sudo's in front of some commands, cause in the LXC i'm root, so it wasn't necessary. But i saw, that the service did not run all the time. root@ytuner:/opt/ytuner# ./ytuner It run's about 30 secons, then it kills. For a Test, i disabled Radiobrowser: Then the Service Keeps running. BTW: I reanimated an Noxon iRadio 360 (the 300 with Stereo Speaker) with xonox, works perfectly ;) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
|
@schrecki3000 thanks for your response and using my quick and dirty created script. Nice that you're using Proxmox and pihole (mee too) We noticed since a while that api communication sometimes do not work properly. Greg is working on ytuner release 2.x For the moment try different api string in ytuner.ini ;RBAPIURL=https://all.api.radio-browser.info If you are using catPermMemDB which I recommend, you should wait a moment while downloading the database in background Take a look into /opt/ytuner/db/rb.db should exist after download finished. I also recommend for you using dnsmasq entries in pihole for redirection of the vtuner.com requests for your radios. You will see in in pihole which vtuner.com radio domains are requested. The ytuner service should restart automatically while rebooting. Change your ytuner.service file too the following Are you using an LXC container for ytuner ?. I have separated pihole and ytuner in their own LXC containers. I requested Greg if he has time for programming additional api interface for using the tunein api as an option. I do recommend using Debian 12 containers for ytuner and pihole.
address=/winston.vtuner.com/192.168.xx.xx (ytuner ip)
Regards |
Beta Was this translation helpful? Give feedback.
-
|
Hi Beatrice, thanks for quick reply, I'm glad! RBAPIURL=http://at1.api.radio-browser.info/ seems to work for now, thanks for that hint! Of yourse there are different containers, pihole and pialert are in one container (serving 6 VLANS (UDM Pro working here)) and the xonox and the ytuner are also in separate containers. Together with 10 other Containers and 2 VM's ;-) I checked the setting in ytuner.ini you mentioned: But in /opt/ytuner/db there is no file :( I changed the ytuner.service file to your recommendation, i will monitor it if it's running continously (uptima kuma is also running here ;-) ), but it looks good. I think the change of the RBAPIURL was the solution here. So far so good, i think i'll wait for v2 from Greg, i don't want to steal your worthy time. I'll try to get the old device running again when the V2 is released. It's this one (don't laugh): https://www.heise.de/news/Internetradio-von-1-1-1052221.html It's not a Must that it is running, but it would be a nice to have if it is doable with low effort. I'm not a Fan of electronic waste caused by cloud providers that shut down their service, so i tried to keep it alive and google showed me this project. Was the same with my Noxon iRadio 360 and the xonox project. Running fine again in Homeoffice now. Thanks for you help!!! OT: Respect, 37M Domains in piHole 🦾 |
Beta Was this translation helpful? Give feedback.





@TheBossME
Hi, good news, no more killing ;-)
It was not a DNS issue or an issue with the radiobrowser servers.
As i heard that it does not need much resources, after installation i checked the memory consumption, which was very low, so i limited the containers RAM to 128MB and the SWAP to about 32MB.
After a lot of trial and error i started ytuner service and switched over to the "Summary" view in Proxmox...
Memory ran full...
I changed to 512MB and 128MB SWAP, service now working fine. And also the rb.db is now there.