OH NO! Another Big Problem

[Morgo]

Well, it seems that fate is conspiring against me to get this BB up and running properly :(

I have successfully imported members, forums and posts.

However, on the bulletin board - anything with more than 1 reply gives a zero-sized error when viewed.

You can view my board here:

http://eros.ultraservers.net/~df3/index.php

or when the DNS kicks in:

http://www.df3.net/index.php


This is starting to really frustrate me now! Surely, it can't be down to my incompetence?!

[Greg]

Sorry to hear about your board, but looks like the DNS has updated. :)

[wandrer]

Access/Error Logs ? What do they show ?

[John]

This appears to be very similar to the problem that site5 users have been having. We are launching a PHP bug report about this problem, as it appears to be a matter of PHP crashing.

As wandrer said, please could you have a look at your web server error logs and report anything anomalous.

Thanks,
John

[Morgo]

Unfortunately, I dont have access to the raw log files on this server. However, through the control panel it does give me the option of seeing the error messages. I checked this, but there were no errors which were related to the forums. Only a few 404 errors, but they are to be expected.

What can I do? I really need to get these boards up soon.

[John]

Which host are you using? Could you please ask you host to have a look at the web server's error logs for you, especially looking out for PHP seg faults or error # 400 .

I have been unable to get my http header analysis tool working to have a look at your site, but I will try again later.

John

[Morgo]

The host I am using is Powersurge (www.powersurge.net). I have the UNIX Professional virtual server package with them.

It's a pity, as on my NT account with them I get full log files. I'll send them an email, but they can be a bit slow at responding :(


[Edited by Morgo on 05-25-2000 at 01:14 PM]

[Morgo]

Just received this from Powersurge:

Sir, we have found something after scouring the log files and watching the
processes

[Thu May 25 06:21:12 2000] [notice] child pid 22171 exit signal Segmentation
fault (11)

That would be one of the errors we get.

We will install the newest php and see if that helps.

This should be done sometime this afternoon.

Im hoping this new implementation will fix it :)

I'll keep you posted. In the mean time, I hope that the little bit of info given by Powersurge can somehow help you.

[John]

Morgo - that is the same problem that we have been having on the site5 host. Could you post which version of PHP, MySQL and which web server you are using please.

Thanks,
John

[Morgo]

Well, I've just received a reply from Powersurge that they have upgraded to the latest version of PHP. I have requested details of the version numbers for mySQL and PHP, but they have yet to get back to me with them.

Unfortunately, the problem is still occurring. I have tried a couple of other variations. I clean installed v1.1 to see if I could view posts with more than 1 reply, but no joy. I then upgraded to 1.1.1 however I have had no luck with that either.

Short of changing hosts, I don't know what to do!!!!

[John]

I spent a long time working on this problem earlier this week. I have identified the offending code, and I can write a work around if PHP does not manage to figure out what is wrong.

I have made a post in the announcements forum regarding this issue.

John

[Morgo]

Thanks for the reply John... It's pretty damn frustrating. Im not sure what to do in the meantime, afterall I do need to get this bulletin board up and running!

:(

BTW - here are a couple more errors that Powersurge recieved on the latest version of PHP.

[Thu May 25 08:52:21 2000] [notice] child pid 9039 exit signal Segmentation
fault (11)
[Thu May 25 08:52:21 2000] [notice] child pid 9034 exit signal Segmentation
fault (11)

[Morgo]

Here is the version information given by Powersurge Tech Support:

Currently we have PHP3 and PHP4 running and MySQL 3.22.32, the PHP4 was
updated today.

[John]

That is a bug in PHP. Email me if you want the workaround. It will be included in the next version.

John

[Morgo]

Thanks John, but I have now changed my webhost to linuxwebhosts.com and everything is now hunky dory :)