Odd page behavior in OJS 2.0

[leo]

I am having odd results installing Open Journal Systems. The installation process completes successfully, and I am able to automatically generate the mysql database required. I made the owner of the OJS directory root. However, once the installation is complete, Open Journal Systems doesn't function correctly. Clicking on links doesn't seem to update the page. I documented and duplicated the installation steps on my own Fedora test box and Open Journal Systems works fine.

What could I be missing? Has anyone else experienced the odd page behavior like I am? Below is my personal OJS setup and the isjournals.org OJS setup to show you an example. Let me know if you have any questions.

http://www.leodominguez.com/journals (WORKS)

http://www.isjournals.org/journals (ODD PAGE BEHAVIOR)

Here are the installation steps I have been performing:
-------------------------------------------------------
How I install Open Journal Systems
-------------------------------------------------------

Code: Select all

cd /home
wget http://pkp.sfu.ca/ojs/download/ojs-2.0.2-1.tar.gz
tar -xzvf ojs-2.0.2-1.tar.gz
rm ojs-2.0.2-1.tar.gz
mv ojs-2.0.2-1 journals
chown -R root:root journals
cd journals
php tools/install.php

-------------------------------------------------------

[asmecher]

Hello Leo,

Check your server logs to see if PHP is throwing an error message. It could be that PHP is hitting the memory limit configured in your php.ini file (see the memory_limit directive).

Regards,
Alec Smecher
Open Journal Systems Team

[leo]

Thanks for the suggestion of checking my logs. After checking I notice anytime I try to access pages on my OJS installation I generate the following errors:

Code: Select all

[Tue Oct 11 12:36:20 2005] [notice] child pid 10688 exit signal Segmentation fault (11)

I'm researching Segmentation fault (11) right now, has this been experienced by anyone else using OJS? Here is my server information:

http://www.isjournals.org/info.php

[asmecher]

Hi Leo,

A segmentation fault indicates a bug in your server software, probably in PHP, but potentially in Apache or MySQL. It could also be a library version mismatch.

I've seen some versions of PHP cause segmentation faults when the memory_limit in php.ini is exceeded. I use a setting of 16M; you may be able to get away with 12M.

Regards,
Alec Smecher
Open Journal Systems Team

[leo]

Thank you for your help. For those who run into this problem, I don't have a resoulution for you. Our problem was "fixed" by my web administrator rolling back PHP5 to PHP 4.3.11