Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter rkwon

    (@rkwon)

    In case anyone else runs across this issue, it turned out that my host had, on their end, installed “new devices to help improve the performance of customer websites on shared hosting platform. As a result of the new hardware, CGI scripts (Perl, PHP) and databases that use real directory paths such as /nameOf/directory/path/here/host.website cease to work.”

    The host was able to change the directory path so the user.ini file (and possibly the php.ini file) were pointing to the right (new) place(s).

    I did end up having to disable all plugins and reinstall them one-by-one to be able to access the login page, but I think that was a separate issue. Just wanted to say thanks to the community for the assistance and resolve my case for posterity.

    Forum: Fixing WordPress
    In reply to: HTTP Error 500

    @lyuda1 – try contacting the help desk at your hosting service. They may be able to walk you through some solutions.

    Thread Starter rkwon

    (@rkwon)

    @t-p – thank you; I have already tried renaming the .htaccess file (including just now) and it did not resolve the issue.

    The error persists whether I have no .htaccess file, a blank .htaccess file, a core/stock WordPress .htaccess file, or my .htaccess file that has been altered/hardened by BPSecurity.

    If it helps at all, I also receive a 500 internal server error when I attempt to read phpinfo().

    Thread Starter rkwon

    (@rkwon)

    If it helps at all, I still receive a 500 internal server error when I attempt to read phpinfo().

    Thread Starter rkwon

    (@rkwon)

    @robvas – I am sorry, but I am not sure what you mean.

    Thread Starter rkwon

    (@rkwon)

    Also, if it helps, here are details from the access log just before and after the 500 error appeared:

    
    54.36.150.39 - - [04/Apr/2020:22:40:15 -0400] "GET /comments/feed/ HTTP/1.1" 200 4947 "-" "Mozilla/5.0 (compatible; AhrefsBot/6.1; +http://ahrefs.com/robot/)"
    
    xxx.xxx.xxx.xxx - - [04/Apr/2020:22:40:39 -0400] "POST /wp-admin/admin-ajax.php HTTP/1.1" 200 47 "https://seareg.org/wp-admin/edit.php?s&post_status=all&post_type=nf_sub&action=-1&form_id=28&nf_form_filter&begin_date&end_date&paged=1&action2=-1" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:74.0) Gecko/20100101 Firefox/74.0"
    
    xx.xxx.xxx.xxx - - [04/Apr/2020:22:42:39 -0400] "POST /wp-cron.php?doing_wp_cron=1586054559.9006350040435791015625 HTTP/1.1" 200 - "https://seareg.org/wp-cron.php?doing_wp_cron=1586054559.9006350040435791015625" "WordPress/5.3.2; https://seareg.org"
    
    xxx.xxx.xxx.xxx - - [04/Apr/2020:22:42:39 -0400] "POST /wp-admin/admin-ajax.php HTTP/1.1" 200 47 "https://seareg.org/wp-admin/edit.php?s&post_status=all&post_type=nf_sub&action=-1&form_id=28&nf_form_filter&begin_date&end_date&paged=1&action2=-1" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:74.0) Gecko/20100101 Firefox/74.0"
    
    xxx.x.xxx.xxx - - [04/Apr/2020:22:44:25 -0400] "HEAD / HTTP/1.1" 500 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
    
    xxx.xxx.xxx.xxx - - [04/Apr/2020:22:44:39 -0400] "POST /wp-admin/admin-ajax.php HTTP/1.1" 200 47 "https://seareg.org/wp-admin/edit.php?s&post_status=all&post_type=nf_sub&action=-1&form_id=28&nf_form_filter&begin_date&end_date&paged=1&action2=-1" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:74.0) Gecko/20100101 Firefox/74.0"
    
    xx.xxx.xxx.xxx - - [04/Apr/2020:22:44:40 -0400] "POST /wp-cron.php?doing_wp_cron=1586054679.9844279289245605468750 HTTP/1.1" 200 - "https://seareg.org/wp-cron.php?doing_wp_cron=1586054679.9844279289245605468750" "WordPress/5.3.2; https://seareg.org"
    
    xxx.xxx.xxx.xxx - - [04/Apr/2020:22:46:39 -0400] "POST /wp-admin/admin-ajax.php HTTP/1.1" 500 519 "https://seareg.org/wp-admin/edit.php?s&post_status=all&post_type=nf_sub&action=-1&form_id=28&nf_form_filter&begin_date&end_date&paged=1&action2=-1" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:74.0) Gecko/20100101 Firefox/74.0"
    
    xxx.xxx.xxx.xxx - - [04/Apr/2020:22:48:39 -0400] "POST /wp-admin/admin-ajax.php HTTP/1.1" 500 519 "https://seareg.org/wp-admin/edit.php?s&post_status=all&post_type=nf_sub&action=-1&form_id=28&nf_form_filter&begin_date&end_date&paged=1&action2=-1" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:74.0) Gecko/20100101 Firefox/74.0"
    
    • This reply was modified 6 years, 1 month ago by Yui.
    • This reply was modified 6 years, 1 month ago by Yui. Reason: please use CODE button for proper formatting
    Thread Starter rkwon

    (@rkwon)

    The server error logs are all variations of the following:

    
    20131019T110727: seareg.org/index.php 
    PHP Warning:  Unknown: open(/var/php_sessions/sess_085ab28508e83370d4d1b01229f59150, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 
    PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/php_sessions) in Unknown on line 0 
     
    20131019T112730: seareg.org/wp-cron.php 
    PHP Warning:  Unknown: open(/var/php_sessions/sess_b599b09371845a582f4be0c600dd9b28, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 
    PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/php_sessions) in Unknown on line 0 
     
    20131019T112730: aus.vas.ind.seareg.org/index.php 
    PHP Warning:  Unknown: open(/var/php_sessions/sess_06bb6f7a21379fc05fd0892e1f1910c7, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 
    PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/php_sessions) in Unknown on line 0 
    
    20131020T152614: seareg.org/index.php 
    PHP Warning:  Unknown: open(/var/php_sessions/sess_b8ab47d01a4e0ccdea5610b00f16c23c, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 
    PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/php_sessions) in Unknown on line 0 
    
    20131020T153227: seareg.org/wp-login.php 
    PHP Warning:  Unknown: open(/var/php_sessions/sess_1673cb71a1046d7975601d002d15fe27, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 
    PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/php_sessions) in Unknown on line 0 
    .
    .
    .
    20131020T153248: seareg.org/wp-login.php 
    PHP Warning:  Unknown: open(/var/php_sessions/sess_1673cb71a1046d7975601d002d15fe27, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 
    PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/php_sessions) in Unknown on line 0 
     
    20131020T171937: seareg.org/index.php 
    PHP Warning:  Unknown: open(/var/php_sessions/sess_37ad09e09678cc9e59ffa67328069107, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 
    PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/php_sessions) in Unknown on line 0
    

    The only thing that seems to change is the timestamp and the particular attempted session tag. “aus.vas.ind.seareg.org/index.php” is also new, though.

    • This reply was modified 6 years, 1 month ago by rkwon.
    • This reply was modified 6 years, 1 month ago by Yui. Reason: email deleted
    • This reply was modified 6 years, 1 month ago by Yui. Reason: wrong reason for editing, i meant, use CODE for proper formatting
    Thread Starter rkwon

    (@rkwon)

    I also just attempted to manually change the theme via phpMyAdmin; that does not seem to have worked, either.

    Thread Starter rkwon

    (@rkwon)

    I manually reset the plugins using phpMyAdmin; the error persists.

    I renamed the directory of my currently active theme (twentytwelve) via my host’s FileManager; this also did not solve the problem. I tried logging in on a completely clean browser on different devices.

    Thread Starter rkwon

    (@rkwon)

    I will give it a try, thanks.

    Looking through my file manager, I can see that I updated three themes (twentytwenty, twentytwelve, and twentynineteen) a couple days (4/2) before the site broke (4/5).

    Thread Starter rkwon

    (@rkwon)

    Thank you – I am fairly certain that I updated a couple of plugins (though I cannot recall exactly which ones) and then edited the content of some pages.

Viewing 11 replies - 1 through 11 (of 11 total)