Serendipity Forums

[garvinhicking]

Hi Mela!

Seems like you do not run mod_php - so the errors would not be contained inside your httpd-error_log, but instead in a more general syslog, or a specific CgiErrorLog - can you check that?

Regards,
Garvin

[Mela]

Check. Nothing in the main-syslog and no CGI-Error-Log either, sorry.

/var/log/messages:

Code: Select all


Aug 27 09:41:07 neskaya kernel: pid 28685 (httpd), uid 80: exited on signal 4
Aug 27 09:41:12 neskaya kernel: pid 72757 (httpd), uid 80: exited on signal 4
Aug 27 09:41:12 neskaya kernel: pid 72762 (httpd), uid 80: exited on signal 4
Aug 27 09:43:01 neskaya kernel: pid 72781 (httpd), uid 80: exited on signal 4
Aug 27 09:43:02 neskaya kernel: pid 72784 (httpd), uid 80: exited on signal 4
Aug 27 09:43:07 neskaya kernel: pid 72786 (httpd), uid 80: exited on signal 4
Aug 27 09:43:09 neskaya kernel: pid 72765 (httpd), uid 80: exited on signal 4
Aug 27 09:43:09 neskaya kernel: pid 72782 (httpd), uid 80: exited on signal 4
Aug 27 09:43:10 neskaya kernel: pid 72779 (httpd), uid 80: exited on signal 4




[Mela]

Maybe I could adjust the loglevel to 'debug' and try again?

[Mela]

httpd-error_log Loglevel debug:

Code: Select all


[Thu Aug 27 10:26:59 2009] [info] mod_wsgi (pid=34552): Attach interpreter ''.
[Thu Aug 27 10:26:59 2009] [info] mod_wsgi (pid=34553): Attach interpreter ''.
[Thu Aug 27 10:27:09 2009] [notice] child pid 34541 exit signal Illegal instruction (4)
[Thu Aug 27 10:27:09 2009] [notice] child pid 34530 exit signal Illegal instruction (4)
[Thu Aug 27 10:27:09 2009] [info] mod_wsgi (pid=34554): Attach interpreter ''.
[Thu Aug 27 10:27:10 2009] [info] mod_wsgi (pid=34555): Attach interpreter ''.
[Thu Aug 27 10:27:10 2009] [info] mod_wsgi (pid=34556): Attach interpreter ''.
[Thu Aug 27 10:27:32 2009] [info] mod_wsgi (pid=34566): Attach interpreter ''.
[Thu Aug 27 10:27:33 2009] [info] mod_wsgi (pid=34567): Attach interpreter ''.
[Thu Aug 27 10:27:33 2009] [info] mod_wsgi (pid=34568): Attach interpreter ''.
[Thu Aug 27 10:28:13 2009] [notice] child pid 34567 exit signal Illegal instruction (4)
[Thu Aug 27 10:28:22 2009] [notice] child pid 34551 exit signal Illegal instruction (4)
[Thu Aug 27 10:28:23 2009] [notice] child pid 34553 exit signal Illegal instruction (4)
[Thu Aug 27 10:28:28 2009] [notice] child pid 34555 exit signal Illegal instruction (4)
[Thu Aug 27 10:28:28 2009] [notice] child pid 34546 exit signal Illegal instruction (4)
[Thu Aug 27 10:28:28 2009] [notice] child pid 34544 exit signal Illegal instruction (4)
[Thu Aug 27 10:28:29 2009] [notice] child pid 34540 exit signal Illegal instruction (4)
[Thu Aug 27 10:28:29 2009] [notice] child pid 34534 exit signal Illegal instruction (4)
[Thu Aug 27 10:28:29 2009] [info] mod_wsgi (pid=34576): Attach interpreter ''.
[Thu Aug 27 10:28:30 2009] [info] mod_wsgi (pid=34577): Attach interpreter ''.
[Thu Aug 27 10:28:30 2009] [info] mod_wsgi (pid=34578): Attach interpreter ''.
[Thu Aug 27 10:28:36 2009] [info] mod_wsgi (pid=34580): Attach interpreter ''.
[Thu Aug 27 10:28:37 2009] [notice] child pid 34566 exit signal Illegal instruction (4)
[Thu Aug 27 10:28:39 2009] [info] mod_wsgi (pid=34582): Attach interpreter ''.




[garvinhicking]

Hi!

Hm. Did you try to set the apache "ScriptLog" directive?

Regards,
Garvin

[Mela]

Yes. Tried it. Logfile stays blank.

[garvinhicking]

Hi!

Hm. I actually always use mod_php, so I'm not experienced in setting up CGI logging. Until someone uses mod_php to reproduce the error, or figure out a way to get CGI logging up and running, I can't really help here...

Regards,
Garvin

[Mela]

Ähm. Well. I am using certainly mod_php.

[garvinhicking]

Hi!

Ähm. Well. I am using certainly mod_php.

I thought HTTP 500 errors only happen with CGI?!

Regards,
Garvin

[Mela]

Sorry, I see the error lies in "I got the same problem."

No, I didn't get an error 500, but the blog is wrecked completely after the plugin upgrade.

Mela

[garvinhicking]

Hi Mela!

A blank page then, you mean with "wrecked"? Can you check your php.ini settings for error_reporting and error_log? (through phpinfo())?

Regards,
Garvin

[Wolfdog]

The plugin worked just fine till the last update, thus I assume the modifications/additions to the code base from thus previous version should be checked. Also, I am having issues with producing logs.
Why not just roll back to the previous version at least so we can use the plugin till this is fixed?

[Mela]

A blank page then, you mean with "wrecked"? Can you check your php.ini settings for error_reporting and error_log? (through phpinfo())?

I'm sorry, not until the day after tomorrow. party congress.

Mela

[ini]

Hi!

I have the same problem: I installed the new version of the plugin and now my blog is not working. When you try to visit it, it says "500 Internal Server Error". Error occurs permanent. I can visit the admin-page, but not my blog. I have already uninstalled the plugin, no change

Please help

Regards,
Ingrid

[ini]

Okay, I un-installed the whole folder via FTP and now I can visit my blog again (thank God!). But there is definitely something wrong with this plugin...