Jump to content

Adam64

Members
  • Posts

    114
  • Joined

  • Last visited

Posts posted by Adam64

  1. Hello,  My server seems to be working fine, but when I log in I notice that my log fills up with these errors:

     

    Feb 22 15:44:12 Server nginx: 2024/02/22 15:44:12 [error] 7802#7802: *154727 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 10.0.3.106, server: , request: "POST /plugins/dynamix.my.servers/include/unraid-api.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "10.0.3.20", referrer: "http://10.0.3.20/Main"

     

    I've googled it and it seems like people have seen this happen caused by plugins, but my plugins haven't changed for years so it doesn't seem like it's that.  It happens with both Firefox and Edge.

  2. 9 hours ago, sonic6 said:

     

     

    Okay, changed the docker stop timeout to 300s, but with today backup i run into the same problem.

    Backup for thoes containers were skipped.

    This wasn't the case for any backup in the old version.

    Also then the container weren't started after the "backup" (which wasn't made).

    I also would post a Logfile, but there isn't one.

    There isn't also any notification about the failed backups?

     

    I don't think i am the only one with this problem, but without any notification, there were much user who would notice this.

     

    What do i have to share for information, or what can i do, to prevent this?

     

     

    I think I've been having this problem as well.  I just happened to be up this morning when my backup was happening and Plex seemed to restart too fast, so I checked and found that the backup was failing -- and had failed the last couple of weeks without a notification.  I tried a couple of times to backup manually and it failed each time.

     

    Changing the backup type to "stop all containers, backup, start all containers" fixed it for me.

    • Thanks 1
  3. Hello,  I've been running the 4.6 beta and now that it's released I'd like to switch to the released version (4.6.50).  When I change the tag from beta to latest, the docker downloads 4.5.  Does lsio need to do something to the docker to indicate that the release is 4.6.50?

  4. On 6/8/2020 at 6:52 AM, bonienl said:

    Update: there is a lot going one

    I agree that it's not okay to complain about not hearing anything since B1.  If for no other reason than this is a crazy time (I've thought a few times "man, I hope those guys aren't sick").  But I would say that it's a missed opportunity to not share at least something of what's happening behind the scenes.  This is a pretty committed and passionate user-base, and some level of sharing would only strengthen it.  I work in big-tech myself, so I get the struggle of figuring out how much to share with your customers.  A monthly blog with some latest development details, near-term roadmap info, things to look forward to with unraid, etc, would go a long way IMHO. 

    • Like 10
  5. 1 hour ago, Djoss said:

    By running the same tool as the article:

     

    
    trivy --clear-cache jlesage/nginx-proxy-manager:latest
    2019-07-02T07:20:28.768-0400	INFO	Removing image caches...
    2019-07-02T07:20:28.826-0400	INFO	Updating vulnerability database...
    2019-07-02T07:20:35.328-0400	INFO	Detecting Alpine vulnerabilities...
    
    jlesage/nginx-proxy-manager:latest (alpine 3.8.4)
    =================================================
    Total: 3 (UNKNOWN: 0, LOW: 1, MEDIUM: 2, HIGH: 0, CRITICAL: 0)
    
    +---------+------------------+----------+-------------------+---------------+--------------------------------+
    | LIBRARY | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |             TITLE              |
    +---------+------------------+----------+-------------------+---------------+--------------------------------+
    | mariadb | CVE-2019-2628    | MEDIUM   | 10.2.24-r0        | 10.2.24.r0    | mysql: InnoDB unspecified      |
    |         |                  |          |                   |               | vulnerability (CPU Apr 2019)   |
    +         +------------------+          +                   +               +--------------------------------+
    |         | CVE-2019-2627    |          |                   |               | mysql: Server: Security:       |
    |         |                  |          |                   |               | Privileges unspecified         |
    |         |                  |          |                   |               | vulnerability (CPU Apr 2019)   |
    +         +------------------+----------+                   +               +--------------------------------+
    |         | CVE-2019-2614    | LOW      |                   |               | mysql: Server: Replication     |
    |         |                  |          |                   |               | unspecified vulnerability (CPU |
    |         |                  |          |                   |               | Apr 2019)                      |
    +---------+------------------+----------+-------------------+---------------+--------------------------------+

     

     

    Thanks!

  6. 2 hours ago, binhex said:

    nope they are already in there:-

     

    
                    pia_port_forward_enabled_endpoints_array=\
                    ("ca-vancouver.${pia_domain_suffix} (CA Vancouver)" \
                    "ca-toronto.${pia_domain_suffix} (CA Toronto)" \
                    "ca-montreal.${pia_domain_suffix} (CA Montreal)" \
                    "czech.${pia_domain_suffix} (Czech Republic)" \
                    "spain.${pia_domain_suffix} (Spain)" \
                    "swiss.${pia_domain_suffix} (Switzerland)" \
                    "sweden.${pia_domain_suffix} (Sweden)" \
                    "france.${pia_domain_suffix} (France)" \
                    "de-berlin.${pia_domain_suffix} (Germany)" \
                    "de-frankfurt.${pia_domain_suffix} (Germany)" \
                    "ro.${pia_domain_suffix} (Romania)" \
                    "israel.${pia_domain_suffix} (Israel)")

     

    hmm ok leave it with me.

     

    edit - fixed and new image built, please pull down.

     

    Thanks!

  7. 8 minutes ago, rzeeman711 said:

    This morning after updating I was getting the following error that prevented deluge from starting up.

     

    I went to that shell script and removed the first backslash in front of that snippet and restarted and it started working again.

    Well.. not sure that that fixes it, but it does make it work.  :)

     

    Here's what I got in the log when I made that change:

     

    2018-12-03 15:35:06,510 DEBG 'start-script' stdout output:

    /root/getvpnport.sh: line 43: ca-vancouver.privateinternetaccess.com (CA Vancouver): command not found

    2018-12-03 15:35:06,510 DEBG 'start-script' stdout output:

    [warn] PIA endpoint 'ca-vancouver.privateinternetaccess.com' doesn't support port forwarding, DL/UL speeds will be slow

    [info] Please consider switching to an endpoint that does support port forwarding, shown below:-

    [info]

  8. 6 minutes ago, rzeeman711 said:

    This morning after updating I was getting the following error that prevented deluge from starting up.

     

    I went to that shell script and removed the first backslash in front of that snippet and restarted and it started working again.

    Brilliant!  Thanks.

  9. Good morning.  Woke up to DelugeVPN not working this morning and this in the log:

     

    2018-12-03 15:24:27,033 DEBG 'start-script' stdout output:

    /root/getvpnport.sh: line 42: syntax error near unexpected token `('

    /root/getvpnport.sh: line 42: ` ("ca-vancouver.${pia_domain_suffix} (CA Vancouver)" \'

     

    Here's the area in the script:

     

                    pia_port_forward_enabled_endpoints_array=\
                    ("ca-vancouver.${pia_domain_suffix} (CA Vancouver)" \
                    "ca-toronto.${pia_domain_suffix} (CA Toronto)" \
                    "ca-montreal.${pia_domain_suffix} (CA Montreal)" \
                    "czech.${pia_domain_suffix} (Czech Republic)" \
                    "spain.${pia_domain_suffix} (Spain)" \
                    "swiss.${pia_domain_suffix} (Switzerland)" \
                    "sweden.${pia_domain_suffix} (Sweden)" \
                    "france.${pia_domain_suffix} (France)" \
                    "de-berlin.${pia_domain_suffix} (Germany)" \
                    "de-frankfurt.${pia_domain_suffix} (Germany)" \
                    "ro.${pia_domain_suffix} (Romania)" \
                    "israel.${pia_domain_suffix} (Israel)")

     

    Apparently it doesn't like the parenthesis around the list.  Delugevpn will start if I remove them, but obviously I don't want to mess with it too much.  :)

  10. Well, my issue started again.  The Sonarr docker constantly using 30% of my processor power, and 28GB of my 32GB of RAM.  Attached is a screenshot from cAdvisor.  Not sure where to go from here on this.  Any other ideas?  Nothing in the queue (in fact, I disabled the download client and the indexer to see if it made any difference) and no tasks running that I can tell.

     

    edit:  the processor is a corei7-4770, so that's quite a bit of processing power being used.

    FWIW I installed Binhex's sonarr docker and it seems to be working correctly.  Since it's the same app I think there's a memory leak in this docker (though it's odd that I'm the only one seeing the issue).

     

    Sent from my SM-T810 using Tapatalk

     

    I would argue that the fact that you're the only one seeing it would go against it being a memory leak.  Especially as most of us are running it on less powerful hardware than you.

     

    Fair enough.  I wish there was some way to troubleshoot it further.  After a few days on Binhex's docker the constant 30% CPU utilization started and RAM usage started increasing.  So... i guess this is a Sonarr issue.  Not sure what's special about my setup as I'm not doing anything fancy.

  11. Well, my issue started again.  The Sonarr docker constantly using 30% of my processor power, and 28GB of my 32GB of RAM.  Attached is a screenshot from cAdvisor.  Not sure where to go from here on this.  Any other ideas?  Nothing in the queue (in fact, I disabled the download client and the indexer to see if it made any difference) and no tasks running that I can tell.

     

    edit:  the processor is a corei7-4770, so that's quite a bit of processing power being used.

    FWIW I installed Binhex's sonarr docker and it seems to be working correctly.  Since it's the same app I think there's a memory leak in this docker (though it's odd that I'm the only one seeing the issue).

     

    Sent from my SM-T810 using Tapatalk

     

     

  12. Well, my issue started again.  The Sonarr docker constantly using 30% of my processor power, and 28GB of my 32GB of RAM.  Attached is a screenshot from cAdvisor.  Not sure where to go from here on this.  Any other ideas?  Nothing in the queue (in fact, I disabled the download client and the indexer to see if it made any difference) and no tasks running that I can tell.

     

    edit:  the processor is a corei7-4770, so that's quite a bit of processing power being used.

    Capture.JPG.b63ecfd26e72b7ba3ccfaf16ca668493.JPG

×
×
  • Create New...