Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author nintechnet

    (@nintechnet)

    Hi

    It looks like a PHP error. Can you check your HTTP and PHP error logs? There is probably some info about the problem.

    Thread Starter anasshehadeh

    (@anasshehadeh)

    there is big problem there is no HTTP and PHP error logs

    Thread Starter anasshehadeh

    (@anasshehadeh)

    [Thu Jul 23 05:49:37.306050 2015] [suexec:notice] [pid 9517] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Thu Jul 23 05:49:37.325286 2015] [auth_digest:notice] [pid 9518] AH01757: generating secret for digest authentication …
    [Thu Jul 23 05:49:37.325887 2015] [lbmethod_heartbeat:notice] [pid 9518] AH02282: No slotmem from mod_heartmonitor
    [Thu Jul 23 05:49:37.340665 2015] [mpm_prefork:notice] [pid 9518] AH00163: Apache/2.4.12 (Amazon) configured — resuming normal operations
    [Thu Jul 23 05:49:37.340682 2015] [core:notice] [pid 9518] AH00094: Command line: ‘/usr/sbin/httpd’

    [Thu Jul 23 05:49:58.365108 2015] [core:notice] [pid 9518] AH00052: child pid 9521 exit signal Segmentation fault (11)

    Plugin Author nintechnet

    (@nintechnet)

    Can you try to run WordPress in debug mode? Maybe it will output the PHP error(s):

    1. Open the wp-config.php and locate this line:

    define('WP_DEBUG', false);

    2. Replace it with:

    define('WP_DEBUG', true);

    After your test, don’t forget to restore the original line.

    You can also try to modify your PHP INI file:

    1. Force PHP to ouput error to the screen, open the PHP INI file and add those lines:

    ; Display errors:
    error_reporting = E_ALL | E_STRICT
    display_errors = On

    2. Force PHP to log errors to file as well, open the PHP INI file and add those lines:

    ; Log errors:
    log_errors = On
    error_log = /path/to/errors.log

    Replace /path/to/ with the full path where you want the log to be saved.

    Thread Starter anasshehadeh

    (@anasshehadeh)

    the same thing ??

    —————————————
    [Thu Jul 23 05:49:58.365108 2015] [core:notice] [pid 9518] AH00052: child pid 9521 exit signal Segmentation fault (11)
    [Thu Jul 23 07:46:01.571750 2015] [mpm_prefork:notice] [pid 9518] AH00169: caught SIGTERM, shutting down
    [Thu Jul 23 07:46:01.669174 2015] [suexec:notice] [pid 9843] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Thu Jul 23 07:46:01.690987 2015] [auth_digest:notice] [pid 9844] AH01757: generating secret for digest authentication …
    [Thu Jul 23 07:46:01.691631 2015] [lbmethod_heartbeat:notice] [pid 9844] AH02282: No slotmem from mod_heartmonitor
    [Thu Jul 23 07:46:01.707874 2015] [mpm_prefork:notice] [pid 9844] AH00163: Apache/2.4.12 (Amazon) configured — resuming normal operations
    [Thu Jul 23 07:46:01.707899 2015] [core:notice] [pid 9844] AH00094: Command line: ‘/usr/sbin/httpd’
    [Thu Jul 23 07:46:34.750710 2015] [core:notice] [pid 9844] AH00052: child pid 9855 exit signal Segmentation fault (11)
    [Thu Jul 23 08:12:07.707730 2015] [core:notice] [pid 9844] AH00052: child pid 9858 exit signal Segmentation fault (11)
    [Thu Jul 23 08:14:08.617298 2015] [mpm_prefork:notice] [pid 9844] AH00169: caught SIGTERM, shutting down
    [Thu Jul 23 08:14:08.720584 2015] [suexec:notice] [pid 9944] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Thu Jul 23 08:14:08.740938 2015] [auth_digest:notice] [pid 9945] AH01757: generating secret for digest authentication …
    [Thu Jul 23 08:14:08.741575 2015] [lbmethod_heartbeat:notice] [pid 9945] AH02282: No slotmem from mod_heartmonitor
    [Thu Jul 23 08:14:08.756816 2015] [mpm_prefork:notice] [pid 9945] AH00163: Apache/2.4.12 (Amazon) configured — resuming normal operations
    [Thu Jul 23 08:14:08.756844 2015] [core:notice] [pid 9945] AH00094: Command line: ‘/usr/sbin/httpd’

    Plugin Author nintechnet

    (@nintechnet)

    You can try to edit the ninjafirewall/install.php script.
    Open it and line 21, right after the copyright, add those 2 lines:

    error_reporting(-1);
    ini_set('display_errors', '1');

    Hopefully, that will display the error.

    You can also try to add those 2 lines as well:

    ini_set("log_errors", 1);
    ini_set("error_log", "/path/to/php-error.log");

    Here again, replace “/path/to/php-error.log” with the full path where you want the log to be saved.

    Thread Starter anasshehadeh

    (@anasshehadeh)

    hi thanks
    i solved the problem , it’s from my side not from ninjafirewall or amazon aws.

    i was rename index.php to another name , this prevent ninjafirewall to find index.php

    ps : update you’r plugin to show error or warning if can’t find index.php

    thanks

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘white screen amazon aws ami vps ec2’ is closed to new replies.