W0nderW0lf

Hat echt keiner das Problem gehabt?

Moin alle, ich habe ein Problem mit meinem Server. Ich kann keine Versionen mehr Abfragen. Egal ob Docker Container oder Plugins. An meiner Internetverbindung kann es nicht liegen, da ich weiterhin händisch über force-update oder den App Market updaten kann. Das klappt alles ohne Probleme. Meine Container erreiche ich auch von außerhalb. Das Problem scheint mit dem letzten Update gekommen zu sein.. Wenn ich bei Plugins ein Update-Check mache, kommt folgendes: Checking connectivity ... No response, aborting! Ich habe bereits dieses "Docker-Patch" Plugin installiert, aber das hat nichts gebracht. (Und ja... natürlich habe ich neugestartet) Habt ihr noch eine idee, oder auf 6.12 warten? VG

Of course. It is definitely no connection issue on my side, since I can still access running containers from outside my network.

But I can still download and install all docker images and plugins in the app market. I don't only have issues requesting versions for docker, but also for plugins. If something on my network would block it, i'd seen it. I have not changed my network config for quite a while now. Only updated my unraid with all it's features that wanted to be updated.

Just installed the patch and rebooted. Glad I am not the only one with this problem. Same as @luckyheiko I cannot get updates.

I installed it but still the same issue.

Hello everyone, I need help with my Server. I usually power my server 1-2 times per month for a day. Today I booted up, logged in, saw update notifications for container, plugins and appstore etc. I installed the updates and went to the docker section and updated those. I started updating container, but I noticed that there are container updates I should receive, but they are not available. When I check status on Docker Updates or Plugin Updates, I receive: Version = not available. Manual Plugin Check: Checking connectivity ... No response, aborting! I have not changed the network config for my Server LAN. When I check the App Store, I can not only see Container, I can also download and deploy container on my server. So here is something not right. What Server is unraid using for checking updates for plugins + container? I added a diagnostics log for you to review if needed. nasty-diagnostics-20230209-1407.zip

Ah. Ja sehr verwirrend. Bei solchen Announcements gehe ich vom Release aus, und nicht nach einer Umfrage..

Moin moin, wie der Titel schon sagt, finde ich leider kein Update auf meinem Server. Nur im "Next" Branch. https://unraid.net/blog/6-10-rc3 Dauert es noch bis das neue Release auf den Mirrors verfügbar ist?

In that case, maybe a "rolling" log would be a good idea to implement

I hope I understand it right with the screenshot: Unfortunately the log is with +140mb too big. Cant upload it.Ripper.log Maybe the size could be the problem for the webserver.

Hi and thx for that quick update. I got good and bad news. The good news: The webui is working. and my Slipknot CD and others are now being tagged correctly. The bad news: In the Webui the log window is empty and causes performance issue. Tested on chromium and firefox in private mode. On chrome it crashes after a short while and on firefox nothing happens. There is no error or warning in the logs. The log under /config/Ripper.log is running. So I guess thats some html related problems.

I use "latest" The log is pretty silent. Doesnt mention the webui, although I provided credentials and web path "/" Here fresh log after update: *** Running /etc/my_init.d/10_syslog-ng.init... [2021-12-19T18:15:53.993562] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.25 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file; config-version='3.13' [2021-12-19T18:15:54.887488] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Dec 19 18:15:54 f9b4ad4fa244 syslog-ng[13]: syslog-ng starting up; version='3.25.1' Dec 19 18:15:54 f9b4ad4fa244 syslog-ng[13]: WARNING: log-fifo-size() works differently starting with syslog-ng 3.22 to avoid dropping flow-controlled messages when log-fifo-size() is misconfigured. From now on, log-fifo-size() only affects messages that are not flow-controlled. (Flow-controlled log paths have the flags(flow-control) option set.) To enable the new behaviour, update the @version string in your configuration and consider lowering the value of log-fifo-size().; *** Running /etc/my_init.d/ripper.sh... Using this daily? Please sponsor me at https://github.com/sponsors/rix1337 - any amount counts! 19.12.2021 18:15:55 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds. Is there a way to find out, why some disc infos cannot be red? I mean my Slipknot CD is brand new and has not a single scratch and either the album name nor the track names are extracted. Its like 20% of my collection has this problem.

Hi, first thx for making ripper! Coffee donation arrives new years eve. I wanted to ask what trick I have to use to enable the WebUI? I already provided credentials in the customization. But nothing happens after that. The log is not showing errors, nor does unRAID provide the "webui" button. Manually going to ip+port via http isnt working too. I want to find out why Some of my CD's are "unknown albums" with nameless tracks. Tried to import Slipknot - Iowa and some others..

I know that fact. I always stick it in USB2, since my MB doesnt want UEFI over USB3