Viewing 15 replies - 1 through 15 (of 21 total)
  • Plugin Author Steve

    (@steveatty)

    You mean you open a new window and try to load your site and it times out?

    How many posts are you processing for comment handling? Are you on shared or dedicated server hosting?

    Is there anything in your apache error logs? It would sound like you’re running out of resources somewhere.

    Thread Starter mippie32

    (@mippie32)

    Thanks for the reply:

    Yes, thats what I mean.

    its only less than 500 blogs with equally not so many comments, a few hundred.

    I am on a dedicated, whooping fast server with 8GB ram 😉

    I don’t seen anything remotely related in error.log in /var/log/apache2. I was actually thinking about a table lock, is that possible??

    Thanks for any hints

    Pim
    http://upsyndroom.nl

    Plugin Author Steve

    (@steveatty)

    Shouldn’t be a table lock – none of the transactions are long running.

    Do you see anything in your php error logs?

    When it times out what happens?

    Can you post the support information from the Wordbooker options page?

    Thread Starter mippie32

    (@mippie32)

    Thanks Steve, for your kind support as always. I will check this and let you know tomorrow. Also the support information

    Thread Starter mippie32

    (@mippie32)

    Hmz, weird, cant find my errorlog.

    I have this in my php.ini:
    error_reporting = E_ALL & ~E_DEPRECATED
    display_startup_errors = On
    display_errors = Off
    log_errors = On
    error_log = /var/log/php-errors.log
    log_errors_max_len = 1024

    But no /var/log/php-errors.log
    See also http://upsyndroom.nl/info.php

    Weird? Anyway, I did some tweaking to nginx, and now I can reproduce the timeout again, could it be related?

    Thread Starter mippie32

    (@mippie32)

    And this is the apache log:

    [Sun Aug 04 10:57:41 2013] [notice] Digest: generating secret for digest authentication …
    [Sun Aug 04 10:57:41 2013] [notice] Digest: done
    [Sun Aug 04 10:57:41 2013] [notice] mod_bw : Memory Allocated 0 bytes (each conf takes 48 bytes)
    [Sun Aug 04 10:57:41 2013] [notice] mod_bw : Version 0.92 – Initialized [0 Confs]
    [Sun Aug 04 10:57:41 2013] [error] python_init: Python version mismatch, expected ‘2.7.2+’, found ‘2.7.3’.
    [Sun Aug 04 10:57:41 2013] [error] python_init: Python executable found ‘/usr/bin/python’.
    [Sun Aug 04 10:57:41 2013] [error] python_init: Python path being used ‘/usr/lib/python2.7/:/usr/lib/python2.7/plat-linux2:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload’.
    [Sun Aug 04 10:57:41 2013] [notice] mod_python: Creating 8 session mutexes based on 2400 max processes and 0 max threads.
    [Sun Aug 04 10:57:41 2013] [notice] mod_python: using mutex_directory /tmp
    [Sun Aug 04 10:57:41 2013] [notice] Apache/2.2.22 (Ubuntu) DAV/2 mod_fcgid/2.3.7 mod_jk/1.2.32 mod_python/3.3.1 Python/2.7.3 mod_ssl/2.2.22 OpenSSL/1.0.1 mod_perl/2.0.5 Perl/v5.14.2 configured — resuming normal operations
    [Sun Aug 04 11:00:07 2013] [notice] caught SIGTERM, shutting down
    [Sun Aug 04 11:00:07 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
    [Sun Aug 04 11:00:07 2013] [notice] Digest: generating secret for digest authentication …
    [Sun Aug 04 11:00:07 2013] [notice] Digest: done
    [Sun Aug 04 11:00:07 2013] [notice] mod_bw : Memory Allocated 0 bytes (each conf takes 48 bytes)
    [Sun Aug 04 11:00:07 2013] [notice] mod_bw : Version 0.92 – Initialized [0 Confs]
    [Sun Aug 04 11:00:07 2013] [error] python_init: Python version mismatch, expected ‘2.7.2+’, found ‘2.7.3’.
    [Sun Aug 04 11:00:07 2013] [error] python_init: Python executable found ‘/usr/bin/python’.
    [Sun Aug 04 11:00:07 2013] [error] python_init: Python path being used ‘/usr/lib/python2.7/:/usr/lib/python2.7/plat-linux2:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload’.
    [Sun Aug 04 11:00:07 2013] [notice] mod_python: Creating 8 session mutexes based on 2400 max processes and 0 max threads.
    [Sun Aug 04 11:00:07 2013] [notice] mod_python: using mutex_directory /tmp
    [Sun Aug 04 11:00:07 2013] [notice] Apache/2.2.22 (Ubuntu) DAV/2 mod_fcgid/2.3.7 mod_jk/1.2.32 mod_python/3.3.1 Python/2.7.3 mod_ssl/2.2.22 OpenSSL/1.0.1 mod_perl/2.0.5 Perl/v5.14.2 configured — resuming normal operations
    [Sun Aug 04 11:01:31 2013] [notice] caught SIGTERM, shutting down
    [Sun Aug 04 11:01:31 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
    [Sun Aug 04 11:01:31 2013] [notice] Digest: generating secret for digest authentication …
    [Sun Aug 04 11:01:31 2013] [notice] Digest: done
    [Sun Aug 04 11:01:31 2013] [notice] mod_bw : Memory Allocated 0 bytes (each conf takes 48 bytes)
    [Sun Aug 04 11:01:31 2013] [notice] mod_bw : Version 0.92 – Initialized [0 Confs]
    [Sun Aug 04 11:01:31 2013] [error] python_init: Python version mismatch, expected ‘2.7.2+’, found ‘2.7.3’.
    [Sun Aug 04 11:01:31 2013] [error] python_init: Python executable found ‘/usr/bin/python’.
    [Sun Aug 04 11:01:31 2013] [error] python_init: Python path being used ‘/usr/lib/python2.7/:/usr/lib/python2.7/plat-linux2:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload’.
    [Sun Aug 04 11:01:31 2013] [notice] mod_python: Creating 8 session mutexes based on 2400 max processes and 0 max threads.
    [Sun Aug 04 11:01:31 2013] [notice] mod_python: using mutex_directory /tmp
    [Sun Aug 04 11:01:31 2013] [notice] Apache/2.2.22 (Ubuntu) DAV/2 mod_fcgid/2.3.7 mod_jk/1.2.32 mod_python/3.3.1 Python/2.7.3 mod_ssl/2.2.22 OpenSSL/1.0.1 mod_perl/2.0.5 Perl/v5.14.2 configured — resuming normal operations

    Plugin Author Steve

    (@steveatty)

    Can you post the info from the wordbooker options page – that way we can see what Wordbooker thinks what the configuration is.

    Where are you using nginx? If you’re using that to host your blog then we’ll need to see any errors from its logs.

    I always dump my php error logs into /tmp

    Thread Starter mippie32

    (@mippie32)

    nginx comes with parallels 11. I thinks it replaces apache for static pages. So maybe no effect.

    I changed php.ini
    error_reporting = E_ALL & ~E_DEPRECATED
    display_startup_errors = On
    display_errors = Off
    log_errors = On
    error_log = /tmp/php-errors.log

    restarted:
    sudo /etc/init.d/apache2 restart

    But still, no log in /tmp ?!~

    This is the info from settings page (thanks again)
    https://dl.dropboxusercontent.com/u/620272/wordbooker.txt

    Thread Starter mippie32

    (@mippie32)

    Ooh, I find this strange, Wordbooker says max_execution_time=60 while I have in php.ini it set to 300?

    Plugin Author Steve

    (@steveatty)

    which php.ini – you’ll have several under the /etc/php5 directory – one for apache (mod_php), one for cmd (command line) and one for cgi (when you’re running php through cgi).

    Thread Starter mippie32

    (@mippie32)

    Aha! When i check info.php it says in fact
    /var/www/vhosts/system/upsyndroom.nl/etc/php.ini

    this is new to me, but the .ini begins with:
    ; ATTENTION!
    ;
    ; DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
    ; SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.

    ???

    Thread Starter mippie32

    (@mippie32)

    http://upsyndroom.nl/info.php

    its confusing 🙁

    /etc/php5/cgi/conf.d/00-ioncube-loader-5.3.ini, /etc/php5/cgi/conf.d/apc.ini, /etc/php5/cgi/conf.d/curl.ini, /etc/php5/cgi/conf.d/gd.ini, /etc/php5/cgi/conf.d/imap.ini, /etc/php5/cgi/conf.d/mysql.ini, /etc/php5/cgi/conf.d/mysqli.ini, /etc/php5/cgi/conf.d/pdo.ini, /etc/php5/cgi/conf.d/pdo_mysql.ini, /etc/php5/cgi/conf.d/pdo_sqlite.ini, /etc/php5/cgi/conf.d/sqlite3.ini, /etc/php5/cgi/conf.d/xsl.ini, /etc/php5/cgi/conf.d/zend_extensions_psa.ini

    Plugin Author Steve

    (@steveatty)

    its just the php.ini files… mine has:

    steve@kodaly:/etc/php5$ find . -name ‘php.ini’
    ./apache2/php.ini
    ./cgi/php.ini
    ./cli/php.ini

    And as I’m running php through cgi its the the one in the cgi directory I edit.

    And my info.php agrees:

    http://wordbooker.tty.org.uk/info.php

    and your info.php reports:

    Configuration File (php.ini) Path /etc/php5/cgi

    but then reports that its picking it up from another location… which is very odd :

    Loaded Configuration File /var/www/vhosts/system/upsyndroom.nl/etc/php.ini

    whereas mine reports:

    Loaded Configuration File /etc/php5/cgi/php.ini

    Thread Starter mippie32

    (@mippie32)

    Thanks, I got it now, it seems like everything is different on this server 🙁 the correct file is
    /etc/php5/apache2/php.ini

    So, in this file I loaded now the settings, from which I wrongly assumed were already active.

    But still, this doesnt change, that will comments are running I the site freezes.. Will do some more checkings myself alo.

    Plugin Author Steve

    (@steveatty)

    Well hopefully now we’ll see any errors – how long does the comment handling take to run in the foreground?

Viewing 15 replies - 1 through 15 (of 21 total)
  • The topic ‘running wordbooker, for example processing comments (interactively) and opening’ is closed to new replies.