Jump to content

Squid

Community Developer
  • Posts

    28,769
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. Reason why it's not marked as being incompatible and it hasn't been said point blank that it's going to disappear is because the deadline for this to happen is when 6.11 stable is released. App policies dictate in a situation like this to wait for stable to be released as there is no evidence that the plugin will not get updated. Since I don't believe that it will actually get updated I initiated a conversation with limetech including @ich777 and a solution was formed to handle this eventuality mainly with regards to the trickle down effect it would cause for other popular plugins, notably System Temp. My official announcement stating that this plugin is no longer available going forward will not come until stable is released and our assumption as to the status of the plugin is proven correct.
  2. Nothing obviously wrong. Are you sure that the drives have power?
  3. It appears that there's corruption on the cache drive / nvme @JorgeB is the best to respond / offer up suggestions. Wait for him to reply.
  4. On any given file at any given time, the source files on master will never match what's in the package. Primarily because the master branch for CA is the only branch I use in dev and always reflects the current state of the files on my system and not the files in the release versions which are contained within the applicable .txz
  5. Yeah, that is going to be your entire problem. Both the logs and CA's diagnostics show that the date is March 15, 2019 and SSL fails if the date is significantly out for security reasons. Settings - Date & Time. set the correct date & time and also give the system a couple of ntp servers
  6. I'll need to see CA's diagnostics Apps, then Settings Enable Debugging and apply Back within CA after the message reappears click the Debugging link at the very bottom Doubt it'll say anything other than it was unable to download the feed, but you never know.
  7. CA for the most part works against the templates which the maintainers supply, so if you install and then rename it those will not show up within a search, because that particular "app" for all intents and purposes does not exist in the feed. However, both Installed apps and previous apps are well aware of renaming and will handle actions within those sections on renamed and/or apps which aren't known to the feed. I can see however what you're wanting and the use for it and will have to think about it. There's a ton of extra processing involved in handling both Installed and Previous apps (you can tell since they do take longer to appear than simply browsing to a category). You can BTW already search for repository name, and the actual author of the app, but as stated this will bring up the results from what is in the feed and available to be installed, not what you have customized in either installed or previous
  8. Can you ping raw.githubusercontent.com along with s3.amazonaws.com
  9. Are you guys running via a proxy? Neither of your debugs shows that CA can download at all.
  10. It would also be worthwhile to upgrade to 6.10.3 (as there's numerous bug fixes), along with purchasing a legit key instead of running a cracked version which probably has issues / viruses / etc
  11. Also, have you run a memtest from the boot menu? (If you boot via UEFI mode, you will need to temporarily switch to Legacy in order to run the test)
  12. Hmm... Are you having any issues? Everything looks ok at first glance.
  13. Try changing the references from /mnt/remotes/... to instead be /mnt/disks/... and see if that immediately lets it start up
  14. When this happens again, edit the template make a change (any change) and then revert it. Then Apply The docker run command will pop up which will tell us the error that is happening
  15. How does it "Not Start" I do the same thing with Plex and have basically zero issues (short of the obvious that half the movies / TV is missing from the library)
  16. Yeah, actually you're correct -> I mixed up what I posted where and here was that I expected dmacias to return. A couple of days later I posted elsewhere amd revised that I didn't think it was going to happen
  17. Unraid never has been marketed as a general purpose linux distribution. Its more akin to an appliance.
  18. Just to reiterate a previous comment I made here, but as of this moment I am not expecting NerdPack (or DevPack) to be updated, and when 6.11.0 stable is released this plugin will be marked as being incompatible.
  19. Then you have memory issues, as that file does not match watch the MD5s in the package
  20. Have you customized CA??? 2022-08-08 16:08:38 Community Applications Version: 2022.07.26 2022-08-08 16:08:38 Unraid version: 6.9.0 2022-08-08 16:08:38 MD5's: ./Apps.page: FAILED
  21. Your load average is basically sky high 14:01:32 up 1 day, 22:37, 0 users, load average: 18.98, 19.33, 19.05 Cores: 8 On an 8 core machine, 100% utilization of the cpu means a load of 8. You're running at the time of the diagnostics ~19 which means that for every process running, there's another 2.5 also wanting to run but they can't as the CPU is already running full tilt.
  22. The genesis of this Tools was that for the longest time, the New Permissions tool only allowed you to run it against all disks or individual disks. This would trash the appdata share since it would more than likely get included when you ran the tool. Docker Safe Permissions runs against every share with the exception of appdata. If you want to further narrow it down to specific disks or shares, then you run the New Permissions tools and double check that you're not inadvertently including appdata
  23. Your second result is to be expected because your first one was more than likely a non-correcting check which means that the second one will give the exact same result. The question though is why on the first one you're getting the millions of errors. Did you change drives or anything between 7/17 and 8/6?
×
×
  • Create New...