Jump to content

dirrtyjoe

Members
  • Posts

    202
  • Joined

  • Last visited

Posts posted by dirrtyjoe

  1. Thanks for creating this.  After having pi-hole running for days/weeks I get the following error logs when trying to load the pi-hole gui:

     

    2016/09/23 14:57:19 [error] 242#242: *49 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 93 bytes) in /var/www/html/admin/data.php on line 176" while reading response header from upstream, client: 192.168.1.131, server: , request: "GET /admin/api.php?summaryRaw&getQuerySources HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.252", referrer: "http://192.168.1.252/admin/"
    2016/09/23 14:57:19 [error] 242#242: *44 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 96 bytes) in /var/www/html/admin/data.php on line 176" while reading response header from upstream, client: 192.168.1.131, server: , request: "GET /admin/api.php?summary HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.252", referrer: "http://192.168.1.252/admin/"
    2016/09/23 14:57:19 [error] 242#242: *50 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 96 bytes) in /var/www/html/admin/data.php on line 176" while reading response header from upstream, client: 192.168.1.131, server: , request: "GET /admin/api.php?getForwardDestinations HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.252", referrer: "http://192.168.1.252/admin/"
    2016/09/23 14:57:19 [error] 242#242: *47 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 96 bytes) in /var/www/html/admin/data.php on line 176" while reading response header from upstream, client: 192.168.1.131, server: , request: "GET /admin/api.php?overTimeData HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.252", referrer: "http://192.168.1.252/admin/"
    2016/09/23 14:57:19 [error] 242#242: *48 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 96 bytes) in /var/www/html/admin/data.php on line 176" while reading response header from upstream, client: 192.168.1.131, server: , request: "GET /admin/api.php?getQueryTypes HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.252", referrer: "http://192.168.1.252/admin/"
    

     

    These are the requests to the backend for the graph content, and the end result is that the graphs never load (you're left with spinning 'loading arrows').

     

    It's discussed in the following github page, and you may need to upgrade php-fpm version:

     

    https://github.com/pi-hole/pi-hole/issues/375

     

    I'm available to test anything you need to.  I'll also try to fix it myself if/when I have the time.

     

     

     

    To explicitly respond to your message, is this related to the log file sizes (the reason I have the Userscript piece to my above comment)? I don't believe spants installs the cron automatically so if you forgot to do that piece (or overlooked it) the logs may simply be getting too big.

  2. I moved to diginc's repo as it is "directly" tied to the pi-hole development (https://hub.docker.com/r/diginc/pi-hole/). I took spants' template, changed the repository to: 'diginc/pi-hole:alpine' and the docker hub URL to: 'https://hub.docker.com/r/diginc/pi-hole/'.

     

    diginc added a parameter to meet the necessary changes that urged spants to create his container, which is disabling IPV6 support so if you add a new container variable:

    Name: Key 4

    Key: IPv6

    Value: False

    Default Value: False

     

    you should be up and running as spants designed but using the container that follows the pi-hole development a bit closer. Been running for a few weeks and haven't had an issue.

     

     

    One other thing I did was install the User Scripts plugin and then create the cron script in: /boot/config/plugins/user.scripts/scripts/pihole/ (following the plugin structure, the script is named 'script'). Then I edit the UserScript settings to run it at the interval of my choosing (each morning).

     

    My script looks like (just converted the cron file):

     

    #!/bin/bash

    DOCKER_NAME=pihole

    PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

     

     

    #          Download any updates from the adlists

    docker exec $DOCKER_NAME pihole updateGravity > /dev/null

     

    # Pi-hole: Update the Web interface shortly after gravity runs

    #          This should also update the version number if it is changed in the dashboard repo

    #docker exec $DOCKER_NAME pihole updateDashboard > /dev/null

     

    # Pi-hole: Parse the log file before it is flushed and save the stats to a database

    #          This will be used for a historical view of your Pi-hole's performance

    #docker exec $DOCKER_NAME dailyLog.sh # note: this is outdated > /dev/null

     

    # Pi-hole: Flush the log daily at 11:58 so it doesn't get out of control

    #          Stats will be viewable in the Web interface thanks to the cron job above

    docker exec $DOCKER_NAME  pihole flush > /dev/null

     

  3. I think so. As it is easy to setup, why not give it a go and let me know what you prefer.

     

    For disclosure- I don't use them as I have ad blocking on my router = http://www.snbforums.com/threads/beta-ab-solution-1-08-beta2-is-out.34021/

     

    I took that approach. I like the dashboard and logging so I'll keep it! Thanks!

     

    But... I'm receiving the following error when trying to add to the whitelist from the web interface:

     

     

    ==> /var/log/nginx/error.log <==

    2016/08/30 20:02:04 [error] 239#239: *21 FastCGI sent in stderr: "PHP message: PHP Warning: error_log(/var/log/lighttpd/pihole_php.log): failed to open stream: No such file or directory in /var/www/html/admin/php/add.php on line 3" while reading response header from upstream, client: 192.168.1.206, server: , request: "POST /admin/php/add.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.188", referrer: "http://192.168.1.188/admin/list.php?l=white"

     

     

    Any idea why I'm running into this or how to resolve it?

  4. i'd say more like a totally separate container for this. otherwise that's two containers have to bloat with the dependencies for this.

     

     

    My initial thought as well, although I'm not sure how the tie in to the post processing will work smoothly with it living in a different container. Although, it very well could be a very easy solution I'm missing... I'm anxious to see what the LinuxServer.io team comes up with.

  5.  

    I posted this in the master thread, but anyway we can get support for mp4 automator built in (or maybe a second container)?

     

    https://github.com/mdhiggins/sickbeard_mp4_automator/

    Please  make a issue on github. And I'll look into it tomorrow.

     

     

    Thanks! Issue posted along with this comment:

     

    it might make sense to have NZBGet / SABnzbd support this rather than each PVR application. Ultimately I'm looking for a way to automate the remux process to help out my processor and limit transcoding requirements for Plex. Where that lives, I'm not sure I care too much (personally).

  6. I'm curious if it would be possible to create a version of the plex container with this included:

     

    https://github.com/wnielson/Plex-Remote-Transcoder

     

     

    Would love to be able to utilize some of my other boxes.

     

    lonix: any chance you plan on implementing this anytime soon. Maybe it warrants a separate docker image? I'm considering taking a look but if you're planning in it I may wait for your solution.

×
×
  • Create New...