Posts Tagged “error_log”

Today I was adding a note to a WordPress article I had written a couple of days ago and it appeared to POST without issue after I clicked the Update button in the WordPress admin. I went to the front-end of the site to verify the new content formatted correctly and to my surprise it wasn’t displaying so I figured I must have left a HTML tag or something open since I didn’t get any errors within the WordPress admin when I clicked the Update button for the Post. After further review the content didn’t exist and it appeared that the article had not posted the update at all since there were zero revisions from today. Fixing the problem is easy by using the below information that describes where I located the error, the error itself, and how to resolve it by issuing a single MySQL command.

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , , , , , , , , , , , , , , , , , ,

Comments No Comments »

After upgrading PHP recently on a CentOS Linux server from PHP 5.2.X to PHP 5.3.X I ran into numerous minor issues. One of the issues was with a web application that requires the ionCube PHP Encoder libraries to function properly. After upgrading PHP I noticed some errors in the Apache error logs including the ionCube Apache module that was failing to load. Below I display the entire error from the Apache error_log file and how to easily resolve the issue by installing a single package via the Yum Package Manager.

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , , , , , , , , , , , , , ,

Comments No Comments »

In the process of creating a mirror image of a current WordPress to be used for development purposes I ran into a PHP error that I had not seen before. The current version of WordPress was working without issue but because many of the settings needed to be modified for the installation to work with a different domain pointed to it. Even after modifying the settings that I had modified in previous instances to make WordPress work with an updated domain name I was still getting an error related to the WordPress Theme. I enabled some PHP error logging, started looking for answers on the web, and then implemented some changes described below to resolve the error.

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , , , , , , , ,

Comments No Comments »

After modify some Perl modules with CPAN I started getting the below errors in the Apache error_log.

Errors:
[Sun Jul 12 14:15:03 2009] [notice] child pid 4329 exit signal Segmentation fault (11)
[Sun Jul 12 14:15:27 2009] [notice] child pid 4331 exit signal Segmentation fault (11)
[Sun Jul 12 14:15:30 2009] [notice] child pid 5065 exit signal Segmentation fault (11)
[Sun Jul 12 14:15:31 2009] [notice] child pid 4339 exit signal Segmentation fault (11)
[Sun Jul 12 14:15:48 2009] [notice] child pid 10111 exit signal Segmentation fault (11)
[Sun Jul 12 14:15:48 2009] [notice] child pid 4325 exit signal Segmentation fault (11)

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , , , , , , ,

Comments 1 Comment »

I ran into some errors with my PHP modules on a CentOS server running ISPConfig to host web sites. I decided instead of in depth troubleshooting that it might be easier to go ahead and upgrade PHP since by default the yum package manager will limit you to PHP version 5.1 yet I knew that PHP version 5.2 had been out for a long time. What I needed to do was locate a yum repository that would allow me to upgrade PHP to version 5.2 using yum. The catch was to make sure that every necessary PHP module had an updated package available via the new yum repository. Below I describe upgrading PHP version 5.1 to PHP version 5.2 on CentOS running ISPConfig.

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , , , , , , , , , , , ,

Comments 17 Comments »