Jump to content

SavagelyCalm

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

 Content Type 

Posts posted by SavagelyCalm

    [Support] binhex - Plex

    in Docker Containers

    Posted · Edited by SavagelyCalm

    Hi im getting this in my logs for Binhex Plex, Radarr, Sonarr, prowlarr and crusader. Weirdly enough Binhex-Deluge only starts, been using Bin-Hex for years and havent changed anything

     

    2024-04-12 13:02:09.129783 [info] Host is running unRAID
    2024-04-12 13:02:09.152002 [info] System information Linux af1ee9e95dd7 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux
    2024-04-12 13:02:09.176885 [info] PUID defined as '99'
    2024-04-12 13:02:09.204597 [info] PGID defined as '100'

     

    Anyone point me in the right direction of a fix?

     

    Edit- checked logs and server was restart accidently by my wife lol, who just owned up to it if that helps

     

    Running the latest unraid

     

    syslog says

     

    Apr 12 16:23:13 MarksServer kernel: docker0: port 3(veth4902f38) entered blocking state
    Apr 12 16:23:13 MarksServer kernel: docker0: port 3(veth4902f38) entered disabled state
    Apr 12 16:23:13 MarksServer kernel: device veth4902f38 entered promiscuous mode
    Apr 12 16:23:13 MarksServer kernel: docker0: port 3(veth4902f38) entered blocking state
    Apr 12 16:23:13 MarksServer kernel: docker0: port 3(veth4902f38) entered forwarding state
    Apr 12 16:23:13 MarksServer kernel: docker0: port 3(veth4902f38) entered disabled state
    Apr 12 16:23:13 MarksServer kernel: eth0: renamed from veth228fd54
    Apr 12 16:23:13 MarksServer kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4902f38: link becomes ready
    Apr 12 16:23:13 MarksServer kernel: docker0: port 3(veth4902f38) entered blocking state
    Apr 12 16:23:13 MarksServer kernel: docker0: port 3(veth4902f38) entered forwarding state
    Apr 12 16:23:13 MarksServer kernel: docker0: port 4(vethaa81413) entered blocking state
    Apr 12 16:23:13 MarksServer kernel: docker0: port 4(vethaa81413) entered disabled state
    Apr 12 16:23:13 MarksServer kernel: device vethaa81413 entered promiscuous mode
    Apr 12 16:23:13 MarksServer kernel: docker0: port 4(vethaa81413) entered blocking state
    Apr 12 16:23:13 MarksServer kernel: docker0: port 4(vethaa81413) entered forwarding state
    Apr 12 16:23:14 MarksServer kernel: eth0: renamed from veth55058dd
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(vethaa81413) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth4902f38) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: veth228fd54: renamed from eth0
    Apr 12 16:23:14 MarksServer kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethaa81413: link becomes ready
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(vethaa81413) entered blocking state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(vethaa81413) entered forwarding state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth4902f38) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: device veth4902f38 left promiscuous mode
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth4902f38) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth0394350) entered blocking state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth0394350) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: device veth0394350 entered promiscuous mode
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth0394350) entered blocking state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth0394350) entered forwarding state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth0394350) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(vethaa81413) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: eth0: renamed from vethed81965
    Apr 12 16:23:14 MarksServer kernel: veth55058dd: renamed from eth0
    Apr 12 16:23:14 MarksServer kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0394350: link becomes ready
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth0394350) entered blocking state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth0394350) entered forwarding state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(vethaa81413) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: device vethaa81413 left promiscuous mode
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(vethaa81413) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(veth435e3b1) entered blocking state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(veth435e3b1) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: device veth435e3b1 entered promiscuous mode
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(veth435e3b1) entered blocking state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(veth435e3b1) entered forwarding state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(veth435e3b1) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth0394350) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: vethed81965: renamed from eth0
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth0394350) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: device veth0394350 left promiscuous mode
    Apr 12 16:23:14 MarksServer kernel: docker0: port 3(veth0394350) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: eth0: renamed from vethdad84ff
    Apr 12 16:23:14 MarksServer kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth435e3b1: link becomes ready
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(veth435e3b1) entered blocking state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(veth435e3b1) entered forwarding state
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(veth435e3b1) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: vethdad84ff: renamed from eth0
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(veth435e3b1) entered disabled state
    Apr 12 16:23:14 MarksServer kernel: device veth435e3b1 left promiscuous mode
    Apr 12 16:23:14 MarksServer kernel: docker0: port 4(veth435e3b1) entered disabled state

    Bin Hex Dockers

    in General Support

    Posted

    I using unraid 6.12.10

     

    Just noticed today all of my binhex containers wont start and the log shows

     

    2024-04-12 13:02:09.129783 [info] Host is running unRAID
    2024-04-12 13:02:09.152002 [info] System information Linux af1ee9e95dd7 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux
    2024-04-12 13:02:09.176885 [info] PUID defined as '99'
    2024-04-12 13:02:09.204597 [info] PGID defined as '100'

     

    Anyone point me in the right direction of a fix?

    My Servers - Provision Greyed out

    in General Support

    Posted

    18 minutes ago, ljm42 said:

    On your client computer (not Unraid) open a command prompt and type:

       ping yourpersonalhash.unraid.net

    (the easiest way to get yourpersonalhash is to copy/paste it out of the error message that you took a screenshot of)

     

    What is the result?

     

     

    The IP address is wrong as I've changed routers and update DNS is greyed out :( So the Hash is pinging my old local IP address.

     

     

     

     

    tempsnip.png

    My Servers - Provision Greyed out

    in General Support

    Posted · Edited by SavagelyCalm

    4 hours ago, Squid said:

    Set Use SSL to be auto

     

    Thanks Squid - The simple fix lol

     

    Now I'm banging my head with this, Put Merlin firmware on the Asus router to see the extra options.

     

    DNS rebinding protection turned off

    DNS Servers changed to google/OpenDNS and then Cloudflare. Getting these errors still.

     

    Restarted unraid.net API

     

     

     

    2.PNG

    1_LI (2).jpg

    My Servers - Provision Greyed out

    in General Support

    Posted

    Hi, I just changed routers and couldnt access my server at all as I had remote access on and a SSL cert provisioned.

     

    So I loaded on the unraid gui to and turned off SSL/TLS to regain access. But the renew button was greyed out. (I updated the DNS), I needed to renew the SSL as I had a new router.

     

    I've deleted the SSL configs on the flash drive to see if I could provision, but now it's greyed out with a date in the future :(

     

    Can anyone help with reprovisioning? I'm using an Asus RT-AX88u and have set my DNS to google.

     

     

    Capture.PNG

    New Router Supports Link Aggregation

    in General Support

    Posted

    Hi all,

     

    My new router comes next week and it supports link aggregation. 

     

    Router https://www.tp-link.com/uk/home-networking/wifi-router/archer-ax11000/

     

    My unraid setup is basic, I only use it for Media Management, Plex, Sonarr, Radar, etc. Its running on my old PC.

     

    Gigabyte Gaming 5 x99 Motherboard with Intel 5820k CPU, etc.

     

    I'd like to add/buy a 2 Port PCE-E ethernet card, to run link aggregation. Would anyone have any recommendations?

     

    Thank you

    [Support] binhex - Sonarr

    in Docker Containers

    Posted

    Hi all, plugin has been working flawlessly for a year now. After I updated today I get the following error

      

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

2021-03-09 00:13:37.202162 [info] Host is running unRAID
2021-03-09 00:13:37.225476 [info] System information Linux 52631f8cb8ed 5.10.19-Unraid #1 SMP Sat Feb 27 08:00:30 PST 2021 x86_64 GNU/Linux
2021-03-09 00:13:37.251512 [info] OS_ARCH defined as 'x86-64'
2021-03-09 00:13:37.277347 [info] PUID defined as '99'
2021-03-09 00:13:37.305360 [info] PGID defined as '100'
2021-03-09 00:13:37.336239 [info] UMASK defined as '000'
2021-03-09 00:13:37.361522 [info] Permissions already set for volume mappings
2021-03-09 00:13:37.387798 [info] Deleting files in /tmp (non recursive)...
2021-03-09 00:13:37.414435 [info] Starting Supervisor...
2021-03-09 00:13:37,578 INFO Included extra file "/etc/supervisor/conf.d/sonarr.conf" during parsing
2021-03-09 00:13:37,578 INFO Set uid to user 0 succeeded
2021-03-09 00:13:37,580 INFO supervisord started with pid 6
2021-03-09 00:13:38,582 INFO spawned: 'sonarr' with pid 56
2021-03-09 00:13:38,583 INFO reaped unknown pid 7 (exit status 0)
2021-03-09 00:13:38,595 DEBG 'sonarr' stderr output:
Cannot open assembly '/usr/lib/sonarr/NzbDrone.exe': No such file or directory.

2021-03-09 00:13:38,602 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22677225375680 for <Subprocess at 22677225376016 with name sonarr in state STARTING> (stdout)>
2021-03-09 00:13:38,602 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22677225375248 for <Subprocess at 22677225376016 with name sonarr in state STARTING> (stderr)>
2021-03-09 00:13:38,603 INFO exited: sonarr (exit status 2; not expected)
2021-03-09 00:13:38,603 DEBG received SIGCHLD indicating a child quit
2021-03-09 00:13:39,606 INFO spawned: 'sonarr' with pid 60
2021-03-09 00:13:39,619 DEBG 'sonarr' stderr output:
Cannot open assembly '/usr/lib/sonarr/NzbDrone.exe': No such file or directory.

2021-03-09 00:13:39,625 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22677225375728 for <Subprocess at 22677225376016 with name sonarr in state STARTING> (stdout)>
2021-03-09 00:13:39,626 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22677224939040 for <Subprocess at 22677225376016 with name sonarr in state STARTING> (stderr)>
2021-03-09 00:13:39,626 INFO exited: sonarr (exit status 2; not expected)
2021-03-09 00:13:39,626 DEBG received SIGCHLD indicating a child quit
2021-03-09 00:13:41,630 INFO spawned: 'sonarr' with pid 64
2021-03-09 00:13:41,643 DEBG 'sonarr' stderr output:
Cannot open assembly '/usr/lib/sonarr/NzbDrone.exe': No such file or directory.

2021-03-09 00:13:41,650 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22677225375248 for <Subprocess at 22677225376016 with name sonarr in state STARTING> (stdout)>
2021-03-09 00:13:41,651 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22677225536000 for <Subprocess at 22677225376016 with name sonarr in state STARTING> (stderr)>
2021-03-09 00:13:41,651 INFO exited: sonarr (exit status 2; not expected)
2021-03-09 00:13:41,651 DEBG received SIGCHLD indicating a child quit
2021-03-09 00:13:44,655 INFO spawned: 'sonarr' with pid 68
2021-03-09 00:13:44,667 DEBG 'sonarr' stderr output:
Cannot open assembly '/usr/lib/sonarr/NzbDrone.exe': No such file or directory.

2021-03-09 00:13:44,673 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22677225375728 for <Subprocess at 22677225376016 with name sonarr in state STARTING> (stdout)>
2021-03-09 00:13:44,673 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22677224938944 for <Subprocess at 22677225376016 with name sonarr in state STARTING> (stderr)>
2021-03-09 00:13:44,673 INFO exited: sonarr (exit status 2; not expected)
2021-03-09 00:13:44,673 DEBG received SIGCHLD indicating a child quit
2021-03-09 00:13:45,675 INFO gave up: sonarr entered FATAL state, too many start retries too quickly

     

     

    Can anyone help or point me in the direction of a fix? Thanks

×
×
  • Create New...