Odd issues with PHP/Mysql, anyone?

[colossus]

Hi:

A couple of days ago, I noticed that one of the admin areas of our web (hosted in shared-server Platinum) was not working: some of the administrative URLs of the wfsection module of our Xoops installation where throwing a "Premature end of script headers" error. I'm slowly tracing the complex PHP code involved to find the exact PHP sentence/MySQL query that raises the problem.

Question is, why does this code fail now when it has been working for years? I (think I) did not make any change in our web that can cause the error . It seems most probable to me that some obscure bug was lurking in the code that only now shows up.

I was wandering... Could it be related to some change in the server's configuration, may be regarding the recent cpanel update? While we find where the problem is, it would be useful to know if someone here at JaguarPC has been experiencing strange issues with PHP/MySQL engines in the last few days.

By the way: I opened a ticket as soon as I was aware of the problem, and staff are being extremely supportive and helpful with this issue.

Regards: Colossus

[Gwaihir]

The major server changeovers are now some months behind us. They can only be the "why now?" if you haven't visited those specific pages since.

Good luck with it!

[colossus]

The major server changeovers are now some months behind us. They can only be the "why now?" if you haven't visited those specific pages since.

Thanks for the yor fast replay, Windlord, good suggestion... But no, migration to PHP-CGI did not affect our web at all.

Whatever has happended, it happend a few hours before I noticed it (since 2007-01-17 till now), as I surf those areas daily :-)

Regards: Colossus

[Vin DSL]

I would get a dialog going with 'Tech Support'. (keyword - dialog)

Something similar happened to a nice lady, here in the threads, the other day...

Different person, different software, different problem (sort of). Her scripts had been working fine, with no changes to the code, but suddenly she was running into problems similar to yours. Turned out that her site was bumping up against 'the memory limit'.

Perhaps, JagPC has changed something on 'their side' recently, that nobody (except senior staff) is aware of. Who knows? However, I think this mystery should be investigated by Tech Support...

[colossus]

...
Something similar happened to a nice lady, here in the threads, the other day...
...
Turned out that her site was bumping up against 'the memory limit'.

That would make sense, it fits with what I've been able to find out until now following the code. Thanks for the comment.

Could you link that thread, Vin?

Regards: Colossus

[Vin DSL]

Could you link that thread, Vin?

Yeah, but I was being a real ass. You sure you want to read it?

[Vin DSL]

I sent the link. Check your mail.

I can't PM here...

[colossus]

I sent the link. Check your mail.

Got it. Thank you, I've read the thread and it looks promising.

Regards: Colossus

[Spathiphyllum]

I was wandering... Could it be related to some change in the server's configuration, may be regarding the recent cpanel update? While we find where the problem is, it would be useful to know if someone here at JaguarPC has been experiencing strange issues with PHP/MySQL engines in the last few days.

Yes, I have been getting a "Premature end of script headers" error logged in my cPanel log in recent days that I had never observed before from a mySQL connecting Perl script. Oddly, I cannot see any STDOUT error in the datastream as the dynamic content parses properly; however, there is an effect on cookie data in that data seems to get recalled from cache rather than refreshing anew and recalling new cookie data on reload. That points to a header issue. I had been assuming it was a browser issue setting that I had accidentally switched/misconfigured.

Curiously, the original code author uses shared modules and similar subroutines in several scripts to the suite and only one script (as far as I can tell) is creating this output error. I've not noticed any real effect on the application's work other than to know that it's logging an error that seems not to mean anything other than an idiosyncrasy that I can workaround. Unfortunately, I don't have time right now to parse with fine-toothed comb the code when it could be a server setting that's inducing the problem. I'll worry about it after I get moved to that new server which was said to be imminent a few days ago.

If and when I figure it out, I'll try to remember to update you here.

[colossus]

Well, VinDSL was right, support has raised memory limit and everything is working fine again.

Thank you so much, Vin, for pointing out the problem.

And, this time, a little scolding to Jag's techs: you should have realized that the problem was the same odd issue that showed up with another account (wich Masood fixed only two days ago). Good work anyway, all is well that ends well.

Regards: Colossus

[Vin DSL]

My pleasure!