ReVRiN

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

  • Last visited

 Content Type 

Posts posted by ReVRiN

    High CPU loads and 97% RAM usage

    in General Support

    Posted

    I had Lenovo D30 Thinkstation acting as my UNRAID box. Something happened and that box died. Good news I had a secondary unit that I simply moved my HDD's and USB key to the new box. Since doing so I have high temp warnings on my Parity Disk and Disk 1. Most of my CPU's are sitting at 100% and the I get running out of memory errors. I let it run for 16 hours figuring it work itself out.

     

    Any clues would be appreciated.

    k2so-diagnostics-20200518-1505.zip

    Cannot connect to unRaid shares from Windows 10

    in General Support

    Posted

    My primary gaming system shit the bed and I was unable to even hit the server post rebuild. Thank you for the instructions. My brain is on overload these last few weeks and I couldn't for the life of me fix my own system, yet I keep my firm's network running like clockwork. Ironic.

    Stay safe everyone, and stay the fuck home.

    [Support] binhex - NZBGet

    in Docker Containers

    Posted

    So in the last week NZBGet which has been flawless just shit the bed. The page wont load anymore:

     

    2019-07-17 14:29:05,710 INFO gave up: nzbget entered FATAL state, too many start retries too quickly

     

    So I wiped it off the face of my server and USB key (appdata) waited a couple days and rebooted a couple times (family got in the way of troubleshooting). So I just reloaded it and it launched as per normal and I was setting up all my settings and reloaded NZBGet only for it to do the same thing? Did they change something recently to break your docker BinHex?

     

    Created by...
    ___. .__ .__
    \_ |__ |__| ____ | |__ ____ ___ ___
    | __ \| |/ \| | \_/ __ \\ \/ /
    | \_\ \ | | \ Y \ ___/ > <
    |___ /__|___| /___| /\___ >__/\_ \
    \/ \/ \/ \/ \/
    https://hub.docker.com/u/binhex/

    2019-07-17 14:23:07.167944 [info] System information Linux 6a9b07e92b8c 4.19.56-Unraid #1 SMP Tue Jun 25 10:19:34 PDT 2019 x86_64 GNU/Linux
    2019-07-17 14:23:07.250336 [info] PUID defined as '99'
    2019-07-17 14:23:07.835115 [info] PGID defined as '100'
    2019-07-17 14:23:08.669714 [info] UMASK defined as '000'
    2019-07-17 14:23:08.694079 [info] Setting permissions recursively on volume mappings...
    2019-07-17 14:23:09.182446 [info] Starting Supervisor...
    2019-07-17 14:23:10,250 INFO Included extra file "/etc/supervisor/conf.d/nzbget.conf" during parsing
    2019-07-17 14:23:10,250 INFO Set uid to user 0 succeeded
    2019-07-17 14:23:10,254 INFO supervisord started with pid 6
    2019-07-17 14:23:11,256 INFO spawned: 'nzbget' with pid 48
    2019-07-17 14:23:11,257 INFO reaped unknown pid 7
    2019-07-17 14:23:11,263 DEBG 'nzbget' stdout output:
    [info] NZBGet configuration does not exist, copying default configuration file to /config/...

    2019-07-17 14:23:11,271 DEBG 'nzbget' stdout output:
    [info] Patching NZBGet config file for WebDir and ConfigTemplate locations...

    2019-07-17 14:23:12,272 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2019-07-17 14:28:59,609 DEBG 'nzbget' stderr output:
    /home/nobody/start.sh: line 26: 53 Segmentation fault /usr/local/bin/nzbget/nzbget -c /config/nzbget.conf -s 1>&-

    2019-07-17 14:28:59,609 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22513970354152 for <Subprocess at 22513970354224 with name nzbget in state RUNNING> (stdout)>
    2019-07-17 14:28:59,610 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22513970354440 for <Subprocess at 22513970354224 with name nzbget in state RUNNING> (stderr)>
    2019-07-17 14:28:59,610 INFO exited: nzbget (exit status 139; not expected)
    2019-07-17 14:28:59,610 DEBG received SIGCLD indicating a child quit
    2019-07-17 14:28:59,614 INFO spawned: 'nzbget' with pid 90
    2019-07-17 14:28:59,621 DEBG 'nzbget' stdout output:
    [info] NZBGet configuration file exists
    [info] Patching NZBGet config file for WebDir and ConfigTemplate locations...

    2019-07-17 14:28:59,634 DEBG 'nzbget' stderr output:
    /home/nobody/start.sh: line 26: 93 Segmentation fault /usr/local/bin/nzbget/nzbget -c /config/nzbget.conf -s 1>&-

    2019-07-17 14:28:59,635 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22513987597952 for <Subprocess at 22513970354224 with name nzbget in state STARTING> (stdout)>
    2019-07-17 14:28:59,635 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22513970371040 for <Subprocess at 22513970354224 with name nzbget in state STARTING> (stderr)>
    2019-07-17 14:28:59,635 INFO exited: nzbget (exit status 139; not expected)
    2019-07-17 14:28:59,635 DEBG received SIGCLD indicating a child quit
    2019-07-17 14:29:00,638 INFO spawned: 'nzbget' with pid 102
    2019-07-17 14:29:00,646 DEBG 'nzbget' stdout output:
    [info] NZBGet configuration file exists
    [info] Patching NZBGet config file for WebDir and ConfigTemplate locations...

    2019-07-17 14:29:00,660 DEBG 'nzbget' stderr output:
    /home/nobody/start.sh: line 26: 105 Segmentation fault /usr/local/bin/nzbget/nzbget -c /config/nzbget.conf -s 1>&-

    2019-07-17 14:29:00,660 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22513987597952 for <Subprocess at 22513970354224 with name nzbget in state STARTING> (stdout)>
    2019-07-17 14:29:00,660 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22513970371616 for <Subprocess at 22513970354224 with name nzbget in state STARTING> (stderr)>
    2019-07-17 14:29:00,660 INFO exited: nzbget (exit status 139; not expected)
    2019-07-17 14:29:00,660 DEBG received SIGCLD indicating a child quit
    2019-07-17 14:29:02,665 INFO spawned: 'nzbget' with pid 114
    2019-07-17 14:29:02,672 DEBG 'nzbget' stdout output:
    [info] NZBGet configuration file exists
    [info] Patching NZBGet config file for WebDir and ConfigTemplate locations...

    2019-07-17 14:29:02,684 DEBG 'nzbget' stderr output:
    /home/nobody/start.sh: line 26: 117 Segmentation fault /usr/local/bin/nzbget/nzbget -c /config/nzbget.conf -s 1>&-

    2019-07-17 14:29:02,684 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22513987597952 for <Subprocess at 22513970354224 with name nzbget in state STARTING> (stdout)>
    2019-07-17 14:29:02,684 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22513970370464 for <Subprocess at 22513970354224 with name nzbget in state STARTING> (stderr)>
    2019-07-17 14:29:02,685 INFO exited: nzbget (exit status 139; not expected)
    2019-07-17 14:29:02,685 DEBG received SIGCLD indicating a child quit
    2019-07-17 14:29:05,690 INFO spawned: 'nzbget' with pid 126
    2019-07-17 14:29:05,696 DEBG 'nzbget' stdout output:
    [info] NZBGet configuration file exists
    [info] Patching NZBGet config file for WebDir and ConfigTemplate locations...

    2019-07-17 14:29:05,709 DEBG 'nzbget' stderr output:
    /home/nobody/start.sh: line 26: 129 Segmentation fault /usr/local/bin/nzbget/nzbget -c /config/nzbget.conf -s 1>&-

    2019-07-17 14:29:05,710 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22513987597952 for <Subprocess at 22513970354224 with name nzbget in state STARTING> (stdout)>
    2019-07-17 14:29:05,710 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22513970369456 for <Subprocess at 22513970354224 with name nzbget in state STARTING> (stderr)>
    2019-07-17 14:29:05,710 INFO exited: nzbget (exit status 139; not expected)
    2019-07-17 14:29:05,710 DEBG received SIGCLD indicating a child quit
    2019-07-17 14:29:05,710 INFO gave up: nzbget entered FATAL state, too many start retries too quickly

    Silly sg_format question.

    in General Support

    Posted

    Is there any harm in opening the terminal window starting a reformat of and SAS drive using sg_format --format --size=512 -v /dev/XXX and then closing the terminal window? I've been leaving it open, but I worry that if I close it that I might lose the drive due to my stupidity.

     

    I brought home an EMC KTN-STL3 enclosure full of 4Tb drives and 3 200 Gb SSD Cache drives that my office was going to crush. So to ensure everything is completely gone I'm sg_formatting them all so they are seen by UNRAID, and then Preclearing them.