Jump to content

kaleb112494

Members
 View Profile  See their activity

  • Posts

    8

  • Joined

  • Last visited

 Content Type 

Posts posted by kaleb112494

    The web user interface becomes inaccessible due to a crash of the NGINX server.

    in General Support

    Posted · Edited by kaleb112494

    On 7/3/2023 at 3:24 PM, seanwalter said:

    For now I have this script in my /mnt/cache directory so that I can ssh into unraid and manually restart nginx

     

    Thank you for this. I have been experiencing this issue since 6.10.X, as I am notorious for leaving browser sessions open. Back before unraid-api, I was able to just restart rc.nginx without issue, but that solution stopped working after 6.11.3. Similar resolution, different methodology.

    EDIT: I suppose we can't really call it a solution until the problem ceases to occur in the first place.

    [PLUG-IN] NerdTools

    in Plugin Support

    Posted

    On 10/11/2022 at 8:57 AM, Naticus said:

    First, thanks for all the work you're doing on this!  I thought it was just my install of NerdPack that was broken until I found this package.

     

    Second, one tool I am really missing from NerdPack is ctop, found here:

    https://github.com/bcicen/ctop

     

    Thanks again!

    Thanks for creating a quick replacement for NerdPack! I second ctop, great little program to keep Docker containers in check.

    ACPI Error fills up syslog fast

    in General Support

    Posted

    Following, as I am experiencing a similar issue. 
     

    Quote

    Mar 16 17:58:26 UnRaid kernel: ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.POT3._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20220331/psparse-529) Mar 16 17:58:26 UnRaid kernel: ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.PO11._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20220331/psparse-529) Mar 16 17:58:26 UnRaid kernel: ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.POT4._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20220331/psparse-529) Mar 16 17:58:26 UnRaid kernel: ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.PO12._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20220331/psparse-529) Mar 16 17:58:26 UnRaid kernel: ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.POT5._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20220331/psparse-529) Mar 16 17:58:26 UnRaid 


    Removed some lines, as it's ~22 lines long. For my system, I'm using an R9 5900 (non-x), which is not listed as supported by my board, but this issue has only recently started for me. I was getting >4 month uptime until about 2 months ago. Nothing has changed since then, other than updating plugins and whatnot.

    Based on "SB.PCI0" in the error, it looks like it's related to a PCIe device? PCI0 is where my X520-DA2 is located currently. When my server goes offline, I am unable to reach it via the network. I haven't been home when this occurs to see if it is responsive other than network. Like other posts, there doesn't appear to be anything in /var/log/syslog (and by extension, /boot/logs) that states anything about a kernel issue, and the ACPI issue only reads during boot.

    If nothing else, I hope that my diagnostics have similarities to OP's so that we can find a solution.

    unraid-diagnostics-20230316-1819.zip

    HELP - Docker Service failed to start

    in Docker Engine

    Posted

    Hey guys, haven't ran into this one before. Wish I knew docker a little better, but hopefully someone can help educate me on what to look for. Had an issue with an NVME pool in BTRFS RAID 10 where one of the drives went AWOL for a few hours. The pool reestablished itself automagically into a 2TB pool instead of 1TB, so I'm not sure what happened there. Removed power, waited for caps to dissolve power, then started back up, where NVME returned from it's vacation.

     

    Already balanced the pool and rebooted, which did not resolve the issue. Any help would be appreciated. I've already created a backup of the important data on the pool, so I can start from scratch if necessary - but I'm really, really, REALLY trying to avoid that if possible.

    TIA for any assistance.

    Screenshot from 2022-04-02 15-49-12.png

    Screenshot from 2022-04-02 15-54-12.png

    liteserver-diagnostics-20220402-1541.zip

    [Support] cheesemarathons repo

    in Docker Containers

    Posted

    On 12/4/2021 at 1:42 PM, cheesemarathon said:

    Image was last updated 3 months ago. The last release on github was 8 months ago. Docker image appears to be maintained by the same guy who maintains the github repo. So if you wish for the docker to be updated, i would create an issue on github.

    Thanks for the reply. I reached out, and they've been maintaining the package in nightly rolling releases, as opposed to commiting to the master image on GH, which then causes the Docker image to not get these nightly updates. Or so I'm told 😅

    • Thanks 1
×
×
  • Create New...